From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
alsa-devel@alsa-project.org
Cc: linux-kernel@vger.kernel.org, tiwai@suse.de, broonie@kernel.org,
vkoul@kernel.org, gregkh@linuxfoundation.org,
liam.r.girdwood@linux.intel.com, jank@cadence.com,
joe@perches.com
Subject: Re: [alsa-devel] [PATCH 0/2] soundwire: fix Kconfig select/depend issues
Date: Fri, 12 Apr 2019 09:17:35 -0500 [thread overview]
Message-ID: <aaa3f184-bcd5-70fd-b8fa-e6e361253ede@linux.intel.com> (raw)
In-Reply-To: <189ee558-766c-0e94-9570-3bf283681795@linaro.org>
On 4/12/19 5:06 AM, Srinivas Kandagatla wrote:
>
>
> On 11/04/2019 20:28, Pierre-Louis Bossart wrote:
>> 0-day/Kbuild starts complaining about missed module dependencies and
>> compilation issues. Since codecs and soc drivers need to be compilable
>> independently, let's fix this using the following model:
>>
>> SOUNDWIRE_INTEL ---- select -----------
>> |
>> v
>> REGMAP_SOUNDWIRE --- select ---> SOUNDWIRE_BUS
>>
>
> Last time when I looked at this, Kconfig symbols SOUNDWIRE_BUS and
> SOUNDWIRE looked totally redundant and bit over done.
>
> Removing SOUNDWIRE_BUS Kconfig did clean it up and made it bit more
> align with others
Good point, but no. This is intentional and follows the Kconfig pattern
pattern described by Takashi at https://lkml.org/lkml/2017/11/17/47
yes, this SOUNDWIRE is overkill for now, but let's assume there is a
second non-intel implementation (which I understand as very likely given
all the threads on ARM64 support). In that case you'd really want a
top-level selector option that has no actual compilation impact - not
used in any Makefile or code - but enables the sub-options and let
users/distros select the platforms they care about.
SOUNDWIRE_BUS is really the lowest-common denominator that will be used
by all drivers at the end.
> regarding REGMAP_SOUNDWIRE, It should be selected by the codec/soundwire
> slave drivers isn't it?
yes, that was the intent.
Thanks
-Pierre
next prev parent reply other threads:[~2019-04-12 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 19:28 [PATCH 0/2] soundwire: fix Kconfig select/depend issues Pierre-Louis Bossart
2019-04-11 19:28 ` [PATCH 1/2] regmap: soundwire: fix Kconfig select/depend issue Pierre-Louis Bossart
2019-04-12 8:38 ` Takashi Iwai
2019-04-12 8:46 ` Mark Brown
2019-04-12 14:07 ` [alsa-devel] " Pierre-Louis Bossart
2019-04-12 14:18 ` Mark Brown
2019-04-12 14:21 ` Takashi Iwai
2019-04-14 10:20 ` Vinod Koul
2019-04-11 19:28 ` [PATCH 2/2] soundwire: fix SOUNDWIRE_BUS option Pierre-Louis Bossart
2019-04-12 10:06 ` [PATCH 0/2] soundwire: fix Kconfig select/depend issues Srinivas Kandagatla
2019-04-12 14:17 ` Pierre-Louis Bossart [this message]
2019-04-12 14:27 ` [alsa-devel] " Mark Brown
2019-04-12 14:56 ` Pierre-Louis Bossart
2019-04-14 10:13 ` Vinod Koul
2019-04-15 12:50 ` [alsa-devel] " Pierre-Louis Bossart
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=aaa3f184-bcd5-70fd-b8fa-e6e361253ede@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jank@cadence.com \
--cc=joe@perches.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vkoul@kernel.org \
/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