summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/interrupts.py
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2025-07-14 11:34:08 +0100
committerMark Brown <broonie@kernel.org>2025-07-14 11:34:08 +0100
commit5f120ccf28c5f73d9801d34cad2d29280f2682ec (patch)
tree0df8d736f1b277eb61249a86966664dfb94df60a /scripts/gdb/linux/interrupts.py
parentaf241e3fa4d823f8af899c92fd50d020816a1860 (diff)
parentf00e06296ba3f0d8440030afe8cc2258758b7af7 (diff)
ASoC: set bias_level at if
Merge series from Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>: ASoC has 2 functions to set bias level. (A) snd_soc_dapm_force_bias_level() (B) snd_soc_dapm_set_bias_level() (A) sets dapm->bias_level, but (B) is not. I think we should set it on both (A) and (B). I think it is miss or bug, but Samsung is the only vendor that feels a problem about this. I think this patch (= [1/5]) is correct approach, but some non-samsung vendor might get affect from this patch-set, so I added [RFC] on this patch-set. Furthermore, (B) cares both Card and Component, (A) cares Component only. I guess it is the reason why it is called as "force" bias_level function. (A) is used from each drivers, (B) is used from soc-dapm only. I'm not 100% sure though, except special cases, each driver should use (B), I guess ?
Diffstat (limited to 'scripts/gdb/linux/interrupts.py')
0 files changed, 0 insertions, 0 deletions