From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: alsa-devel@alsa-project.org, vinod.koul@linaro.org,
linux-kernel@vger.kernel.org, hui.wang@canonical.com,
vkoul@kernel.org, srinivas.kandagatla@linaro.org,
sanyog.r.kale@intel.com,
Bard Liao <yung-chuan.liao@linux.intel.com>,
rander.wang@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH] soundwire: intel: move to auxiliary bus
Date: Fri, 26 Mar 2021 11:24:48 -0500 [thread overview]
Message-ID: <e76719e4-57aa-2a19-c9e4-469bab4ef1ca@linux.intel.com> (raw)
In-Reply-To: <YFtchhxHDjfbyY46@kroah.com>
On 3/24/21 10:36 AM, Greg KH wrote:
> On Wed, Mar 24, 2021 at 09:55:01AM -0500, Pierre-Louis Bossart wrote:
>> Note at this point it would mean an API change and impact the existing
>> Nvidia/Mellanox code, we are using the same sequence as them
>
> THere is no "stable api" in the kernel, so if something has to change,
> that's fine, we can change the users at the same time, not an issue.
What I meant is that this requires consensus to make a change, and so
far I haven't seen any burning desire from the contributors to revisit
the 2-step sequence.
I will however modify the code in this patch to implement a SoundWire
'linkdev' register/unregister function, it'll be much easier to review
and maintain, and will follow the same pattern as the mlx5 code (all
errors and domain-specific initializations handled in the same
function). Draft code being tested is at
https://github.com/thesofproject/linux/pull/2809
prev parent reply other threads:[~2021-03-26 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 0:43 [PATCH] soundwire: intel: move to auxiliary bus Bard Liao
2021-03-23 6:48 ` Vinod Koul
2021-03-23 7:37 ` Greg KH
2021-03-23 17:29 ` Pierre-Louis Bossart
2021-03-24 10:50 ` Vinod Koul
2021-03-24 15:03 ` Pierre-Louis Bossart
2021-03-23 7:37 ` Greg KH
2021-03-23 18:04 ` Pierre-Louis Bossart
2021-03-23 18:32 ` Greg KH
2021-03-23 19:14 ` Pierre-Louis Bossart
2021-03-24 9:30 ` Greg KH
2021-03-24 14:55 ` Pierre-Louis Bossart
2021-03-24 15:36 ` Greg KH
2021-03-26 16:24 ` Pierre-Louis Bossart [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=e76719e4-57aa-2a19-c9e4-469bab4ef1ca@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rander.wang@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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