From: Greg KH <gregkh@linuxfoundation.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
alsa-devel@alsa-project.org, Leon Romanovsky <leon@kernel.org>,
linux-kernel@vger.kernel.org,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
hui.wang@canonical.com, Dave Ertman <david.m.ertman@intel.com>,
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 v4] soundwire: intel: move to auxiliary bus
Date: Fri, 11 Jun 2021 15:29:24 +0200 [thread overview]
Message-ID: <YMNlND32rR9aKWeW@kroah.com> (raw)
In-Reply-To: <YMNIfHPRcgKLXJ0v@vkoul-mobl>
On Fri, Jun 11, 2021 at 04:56:52PM +0530, Vinod Koul wrote:
> On 09-06-21, 12:10, Jason Gunthorpe wrote:
> > On Wed, Jun 09, 2021 at 09:44:08AM -0500, Pierre-Louis Bossart wrote:
> >
> > > The consensus for the auxiliary_device model was hard to reach, and the
> > > agreement was to align on a minimal model. If you disagree with the
> > > directions, you will have to convince Nvidia/Mellanox and Intel networking
> > > folks who contributed the solution to do something different.
> >
> > The purpose of the aux devices was primarily to bind a *software*
> > interface between two parts of the kernel.
>
> Then I dont think this example is valid... This example has a PCI device,
> which represents a DSP, HDA controller, DMICs, Soundwire
> links... So at least here it is hardware.
Yes, and that's fine, and exactly what aux devices were created for.
You divide up a single logically addressable device into differently
handled portions.
Not all hardware specs were as "smart" as USB was in allowing multiple
drivers to bind to the same physical USB device and talk to it at the
same time :)
Luckily the USB spec authors learned from the mistakes of PCI...
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-11 13:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 5:21 [PATCH v4] soundwire: intel: move to auxiliary bus Bard Liao
2021-05-25 18:30 ` Pierre-Louis Bossart
2021-05-31 10:19 ` Vinod Koul
2021-06-01 13:56 ` Pierre-Louis Bossart
2021-06-09 4:46 ` Vinod Koul
2021-06-09 14:44 ` Pierre-Louis Bossart
2021-06-09 15:10 ` Jason Gunthorpe
2021-06-09 16:00 ` Pierre-Louis Bossart
2021-06-11 11:26 ` Vinod Koul
2021-06-11 13:29 ` Greg KH [this message]
2021-06-09 19:02 ` Greg KH
2021-06-11 11:59 ` Vinod Koul
2021-06-11 14:51 ` Pierre-Louis Bossart
2021-06-14 4:43 ` Vinod Koul
2021-06-14 4:42 ` Vinod Koul
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=YMNlND32rR9aKWeW@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=david.m.ertman@intel.com \
--cc=hui.wang@canonical.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--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