diff options
| author | Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> | 2019-08-20 14:04:49 +0900 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2019-08-22 18:29:26 +0100 |
| commit | 4168ddabb480bef818c93f378428632fb681b500 (patch) | |
| tree | f4bd55b286b476206babd0f04c9d54c3074315c1 /tools/perf/scripts/python/stackcollapse.py | |
| parent | ASoC: mediatek: mt8183: switch tdm pins gpio function when playback on or off (diff) | |
| download | linux-4168ddabb480bef818c93f378428632fb681b500.tar.gz linux-4168ddabb480bef818c93f378428632fb681b500.zip | |
ASoC: soc-core: use device_register()
It is easy to read code if it is cleanly using paired function/naming,
like start <-> stop, register <-> unregister, etc, etc.
But, current ALSA SoC code is very random, unbalance, not paired, etc.
soc-core.c is using device_unregiser(), but there is no its paired
device_regiser(). We can find its code at soc_post_component_init()
which is using device_initialize() and device_add().
Here, device_initialize() + device_add() = device_register().
-- linux/drivers/base/core.c --
int device_register(struct device *dev)
{
device_initialize(dev);
return device_add(dev);
}
device_initialize() is doing each dev member's initialization only,
not related to device parent/release/groups.
Thus, we can postpone it.
let's use device_register() instead of device_initialize()/device_add().
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Link: https://lore.kernel.org/r/878sro1ldw.wl-kuninori.morimoto.gx@renesas.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
