From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
moderated for non-subscribers <alsa-devel@alsa-project.org>,
<patches@opensource.cirrus.com>, <geert@linux-m68k.org>
Subject: Re: linux-next: Tree for Feb 18 (sound/soc/codecs/wm5110.c)
Date: Tue, 18 Feb 2020 13:09:25 +0000 [thread overview]
Message-ID: <20200218130925.GG108283@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <20200218113116.GA4232@sirena.org.uk>
On Tue, Feb 18, 2020 at 11:31:16AM +0000, Mark Brown wrote:
> On Tue, Feb 18, 2020 at 10:09:59AM +0000, Charles Keepax wrote:
> > 2) We could update the machine drivers to a depends on and make
> > the CODEC symbols manually selectable. I guess this also has the
> > advantages that it would be necessary for the simple card stuff
> > that seems to be everyones first choice for machine drivers these
> > days.
>
> That's not good, it means people have to know exactly what CODECs and
> DAIs are on their board to even see the config option.
>
> > Mark do you have any strong feelings on this I am leaning towards
> > 2?
>
> Why not just continue adding the relevant dependencies to the machine
> drivers like we've always done?
Hmm... a good point. The machine drivers are already depending
on MFD_ARIZONA, if we swapped that for the actual CODECs
involved I guess that should fix the situation as well.
I will fire out a patch shortly.
Thanks,
Charles
prev parent reply other threads:[~2020-02-18 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 4:28 linux-next: Tree for Feb 18 Stephen Rothwell
2020-02-18 6:31 ` linux-next: Tree for Feb 18 (drivers/staging/media/rkisp1/) Randy Dunlap
2020-02-18 12:49 ` Helen Koike
2020-02-18 7:04 ` linux-next: Tree for Feb 18 (sound/soc/codecs/wm5110.c) Randy Dunlap
2020-02-18 7:05 ` Randy Dunlap
2020-02-18 10:09 ` Charles Keepax
2020-02-18 11:31 ` Mark Brown
2020-02-18 13:09 ` Charles Keepax [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=20200218130925.GG108283@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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