From: "Rojewski, Cezary" <cezary.rojewski@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: <broonie@kernel.org>, <tiwai@suse.com>, <perex@perex.cz>,
<amade@asmblr.net>, <linux-sound@vger.kernel.org>
Subject: Re: [PATCH] ASoC: core: Move all users to deferrable card binding
Date: Tue, 12 May 2026 10:14:08 +0200 [thread overview]
Message-ID: <4b1260ba-4584-4a73-92bb-022ebdabafb3@intel.com> (raw)
In-Reply-To: <87ecjin300.wl-kuninori.morimoto.gx@renesas.com>
On 5/11/2026 3:34 AM, Kuninori Morimoto wrote:
>
> Hi Cezary
>
> Thank you for the patch.
> And sorry for my late response, it was long holiday in Japan.
Thank you for finding the time for review and asking the questions!
(...)
>
> It looks more simple, thank you !
>
> 2 questions.
>
> Q1. this means, devm_ register user can use auto rebind, normal user can't,
> but is this correct ?
Rebind is now the default, regardless of the method a driver registers a
card. devm_xxx() variant causes the snd_soc_bind_card() to be managed
and the card is automatically unbound (unregistered) when the device is
detached. Apart from that, there's no difference between the classic
(non-devm) and the managed (devm) way.
> Q2. If so, list_xxx() can be done in devm_snd_soc_bind_card(), instead of
> normal snd_soc_bind_card(), but what do you think ?
Guess if Q1 answer is "no", then Q2 needs no discussion. Feel free to
correct me/ask again if I'm wrong about this.
Kind regards,
Czarek
prev parent reply other threads:[~2026-05-12 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 14:07 [PATCH] ASoC: core: Move all users to deferrable card binding Cezary Rojewski
2026-05-11 1:06 ` Mark Brown
2026-05-11 1:34 ` Kuninori Morimoto
2026-05-12 8:14 ` Rojewski, Cezary [this message]
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=4b1260ba-4584-4a73-92bb-022ebdabafb3@intel.com \
--to=cezary.rojewski@intel.com \
--cc=amade@asmblr.net \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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