From: Vinod <vkoul@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: broonie@kernel.org, lgirdwood@gmail.com,
alsa-devel@alsa-project.org, perex@perex.cz, tiwai@suse.com,
linux-kernel@vger.kernel.org, rohitkr@codeaurora.org,
bgoswami@codeaurora.org
Subject: Re: [PATCH] ASoC: core: add support to card re-bind/unbind using component framework
Date: Thu, 12 Jul 2018 16:29:10 +0530 [thread overview]
Message-ID: <20180712105910.GU3219@vkoul-mobl> (raw)
In-Reply-To: <20180711084318.11786-1-srinivas.kandagatla@linaro.org>
On 11-07-18, 09:43, Srinivas Kandagatla wrote:
> This patch aims at add achieving dynamic behaviour of audio card when
> the dependent components disappear and reappear.
>
> With this patch the card is removed if any of the dependent component
> is removed and card is added back if the dependent component comes back.
> All this is done using component framework and matching based on
> component name.
>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Looks fine mostly, some nitpicks below:
> ---
>
> During discussion regarding card re-binding when components unregister
> and register back at https://lkml.org/lkml/2018/7/9/785 it was suggested
> that component framework can be added into core to provide this feature.
>
> With this new changes the card will re-bind once the dependent component
> re-registers after unregistering. This works based on the match done
> from component name using component framework.
>
> I have tested this patch with qdsp start-stop usecase for more than 10000
> times in loop on Qcom platforms.
>
> I will send qdsp side cleanup patches once I get some feedback on this patch.
>
>
> include/sound/soc.h | 5 ++++
> sound/soc/soc-core.c | 70 ++++++++++++++++++++++++++++++++++++++++++++++++----
> 2 files changed, 70 insertions(+), 5 deletions(-)
>
> diff --git a/include/sound/soc.h b/include/sound/soc.h
> index 870ba6b64817..b94149d29c0d 100644
> --- a/include/sound/soc.h
> +++ b/include/sound/soc.h
> @@ -17,6 +17,7 @@
> #include <linux/workqueue.h>
> #include <linux/interrupt.h>
> #include <linux/kernel.h>
> +#include <linux/component.h>
> #include <linux/regmap.h>
> #include <linux/log2.h>
> #include <sound/core.h>
> @@ -1088,6 +1089,10 @@ struct snd_soc_card {
>
> struct work_struct deferred_resume_work;
>
> + /* component framework related */
> + bool components_added;
> + struct component_match *match;
> +
> /* lists of probed devices belonging to this card */
> struct list_head component_dev_list;
>
> diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c
> index 6d33634b934b..377ed8e67686 100644
> --- a/sound/soc/soc-core.c
> +++ b/sound/soc/soc-core.c
> @@ -279,11 +279,31 @@ static inline void snd_soc_debugfs_exit(void)
>
> #endif
>
> +static int snd_soc_card_comp_compare(struct device *dev, void *data)
Why not make last arg as name and avoid void *
> +{
> + struct snd_soc_component *component = NULL;
> + struct snd_soc_component *t;
why do you need two variables for this
> +
> + lockdep_assert_held(&client_mutex);
> + list_for_each_entry(t, &component_list, list) {
> + if (dev == t->dev) {
> + component = t;
you can skip this line and use t in below code.
> + break;
> + }
> + }
> +
> + if (component && !strcmp(component->name, data))
strncmp?
--
~Vinod
next prev parent reply other threads:[~2018-07-12 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 8:43 Srinivas Kandagatla
2018-07-12 10:59 ` Vinod [this message]
2018-07-12 12:02 ` Srinivas Kandagatla
2018-07-12 12:39 ` Vinod
[not found] ` <68715fbc-9447-dfaf-3fe5-4200684c2cbc@linux.intel.com>
2018-07-12 15:42 ` [alsa-devel] " Takashi Iwai
2018-07-12 15:54 ` Pierre-Louis Bossart
2018-07-12 16:17 ` Mark Brown
2018-07-12 15:58 ` Mark Brown
2018-07-12 16:43 ` Vinod
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180712105910.GU3219@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rohitkr@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome