From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Mark Brown <broonie@kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
linux-renesas-soc@vger.kernel.org,
Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>, Simon <horms@verge.net.au>
Subject: Re: [alsa-devel] Question about struct snd_soc_dai() :: cpu_dai->codec
Date: Thu, 28 Jul 2016 09:16:43 +0530 [thread overview]
Message-ID: <20160728034643.GH9681@localhost> (raw)
In-Reply-To: <s5hpopy6dbi.wl-tiwai@suse.de>
On Wed, Jul 27, 2016 at 10:22:41PM +0200, Takashi Iwai wrote:
> On Wed, 27 Jul 2016 20:22:33 +0200,
> Mark Brown wrote:
> >
> > On Wed, Jul 27, 2016 at 08:11:49PM +0200, Takashi Iwai wrote:
> >
> > > I'm wondering whether it's a better option to block the unbind
> > > behavior, either in driver base (allowing to return an error) or in
> > > the sound side (waiting in remove() until the sane point).
> >
> > That's certainly going to be a lot easier and part of the reason it's
> > never been looked at much is that (unlike USB) there's very little
> > reason why an ASoC sound card would ever be hotplugged - even in
> > development these days the normal development flow involves rebooting.
I agree, it makese no sense for devices to be hotplugged. And for
developement flows people can do rmmond and insmod. That works fine!
> Actually there is already the suppress_bind_attr flag in struct
> device_driver. For a simple platform driver like snd-soc-rcar, it's
> easy like:
I like this idea, should we do this per driver or in core? I think we should
let drivers decide..
> diff --git a/sound/soc/sh/rcar/core.c b/sound/soc/sh/rcar/core.c
> index 3351a701c60e..d019824927de 100644
> --- a/sound/soc/sh/rcar/core.c
> +++ b/sound/soc/sh/rcar/core.c
> @@ -1251,6 +1251,7 @@ static struct platform_driver rsnd_driver = {
> .driver = {
> .name = "rcar_sound",
> .of_match_table = rsnd_of_match,
> + .suppress_bind_attrs = true,
> },
> .probe = rsnd_probe,
> .remove = rsnd_remove,
>
> Then there will be no sysfs bind/unbind for this driver.
> (Note: totally untested: let me know if it really works.)
>
> The same technique is likely available for i2c and spi codec drivers.
> But it's another open question whether we should suppress the sysfs
> bind/unbind of these devices at all. My gut feeling is that sysfs
> bind/unbind are mostly useless for drivers like ASoC codecs. At
> least, it would be much safer to disable for now.
--
~Vinod
next prev parent reply other threads:[~2016-07-28 3:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 5:41 Question about struct snd_soc_dai() :: cpu_dai->codec Kuninori Morimoto
2016-07-27 3:21 ` [alsa-devel] " Vinod Koul
2016-07-27 3:42 ` Kuninori Morimoto
2016-07-27 5:57 ` Takashi Iwai
2016-07-27 6:36 ` Kuninori Morimoto
2016-07-27 17:21 ` Vinod Koul
2016-07-27 18:04 ` Mark Brown
2016-07-27 18:11 ` Takashi Iwai
2016-07-27 18:22 ` Mark Brown
2016-07-27 20:22 ` Takashi Iwai
2016-07-28 3:46 ` Vinod Koul [this message]
2016-07-28 20:33 ` Lars-Peter Clausen
2016-07-28 20:42 ` Takashi Iwai
2016-07-28 20:43 ` Lars-Peter Clausen
2016-07-28 20:44 ` Mark Brown
2016-07-29 0:30 ` Takashi Sakamoto
2016-07-29 9:07 ` Lars-Peter Clausen
2016-07-29 16:07 ` Vinod Koul
2016-07-29 20:41 ` Takashi Iwai
2016-07-29 21:45 ` Takashi Sakamoto
2016-07-29 22:08 ` Mark Brown
2016-08-04 3:17 ` Takashi Sakamoto
2016-08-04 10:28 ` Mark Brown
2016-08-04 12:12 ` Takashi Sakamoto
2016-08-04 12:27 ` Takashi Iwai
2016-08-04 13:39 ` Takashi Sakamoto
2016-08-04 13:52 ` Takashi Iwai
2016-07-28 20:24 ` [alsa-devel] " Lars-Peter Clausen
2016-07-29 2:24 ` Kuninori Morimoto
2016-07-29 9:01 ` Lars-Peter Clausen
2016-07-29 14:41 ` Mark Brown
2016-08-01 3:45 ` Kuninori Morimoto
2016-08-02 6:47 ` Kuninori Morimoto
2016-08-03 19:32 ` [alsa-devel] " Lars-Peter Clausen
2016-08-04 2:38 ` Kuninori Morimoto
2016-08-04 8:21 ` Lars-Peter Clausen
2016-08-04 20:56 ` [alsa-devel] " Mark Brown
2016-08-05 7:29 ` Kuninori Morimoto
2016-08-04 20:37 ` Mark Brown
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=20160728034643.GH9681@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).