From: Jason Gunthorpe <jgg@nvidia.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Leon Romanovsky <leon@kernel.org>,
gregkh@linuxfoundation.org,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
linux-kernel@vger.kernel.org, hui.wang@canonical.com,
Vinod Koul <vkoul@kernel.org>,
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: Wed, 9 Jun 2021 12:10:22 -0300 [thread overview]
Message-ID: <20210609151022.GF1002214@nvidia.com> (raw)
In-Reply-To: <07dbe0a2-0abb-810b-ef39-b83511d3f3e0@linux.intel.com>
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.
If there is a strong defined HW boundary and no software interface
then the mfd subsytem may be a better choice.
For a software layer I expect to see some 'handle' and then a set of
APIs to work within that. It is OK if that 'handle' refers to some HW
resources that the API needs to work, the purpose of this is to
control HW after all.
You might help Vinod by explaining what the SW API is here.
Jason
next prev parent reply other threads:[~2021-06-09 15:11 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 [this message]
2021-06-09 16:00 ` Pierre-Louis Bossart
2021-06-11 11:26 ` Vinod Koul
2021-06-11 13:29 ` Greg KH
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=20210609151022.GF1002214@nvidia.com \
--to=jgg@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=david.m.ertman@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.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;
as well as URLs for NNTP newsgroup(s).