From: Sameer Pujar <spujar@nvidia.com>
To: Mark Brown <broonie@kernel.org>, Jerome Brunet <jbrunet@baylibre.com>
Cc: <spujar@nvidia.com>, <perex@perex.cz>, <tiwai@suse.com>,
<kuninori.morimoto.gx@renesas.com>, <nicoleotsuka@gmail.com>,
<alsa-devel@alsa-project.org>, <swarren@nvidia.com>,
<linux-kernel@vger.kernel.org>, <nwartikar@nvidia.com>,
<lgirdwood@gmail.com>, <jonathanh@nvidia.com>,
<viswanathl@nvidia.com>, <sharadg@nvidia.com>,
<thierry.reding@gmail.com>, <atalambedu@nvidia.com>,
<linux-tegra@vger.kernel.org>, <digetx@gmail.com>,
<rlokhande@nvidia.com>, <mkumard@nvidia.com>,
<dramesh@nvidia.com>
Subject: Re: Re: [RFC] DPCM for Tegra
Date: Wed, 6 May 2020 21:39:58 +0530 [thread overview]
Message-ID: <74e724ec-72c9-e06a-cada-85110c9b145b@nvidia.com> (raw)
In-Reply-To: <20200506155311.GG5299@sirena.org.uk>
On 5/6/2020 9:23 PM, Mark Brown wrote:
> On Wed, May 06, 2020 at 04:47:09PM +0200, Jerome Brunet wrote:
>> On Wed 06 May 2020 at 16:12, Sameer Pujar <spujar@nvidia.com> wrote:
>>> XBAR currently exports all routing widgets which can be used to
>>> interconnect multiple components and thus implements Mux widgets. Fixing
>>> the routing paths in driver would limit anyone to try a different
>>> combination as per the need, unless driver is modified.
>> I did not mean that you should restrict the routing ability of your SoC,
>> quite the opposite actually.
>> You should just expose it correctly
> Yes, it's going to be less effort in the long run if nothing else.
This is what below reference tried to achieve in the original series,
where all Mux widgets and corresponding kcontrols were exposed.
[1]
http://patchwork.ozlabs.org/project/linux-tegra/patch/1582180492-25297-6-git-send-email-spujar@nvidia.com/
However it has DAI declarations too, that was mainly because
codec-to-codec links were used to connect multiple components. DT would
expose all these links (please note that machine driver was not sent as
part of the original series). May be with DPCM these additional DAIs can
be avoided, but it comes with few challenges highlighted in this RFC patch.
prev parent reply other threads:[~2020-05-06 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 12:41 [RFC] DPCM for Tegra Sameer Pujar
2020-05-04 17:55 ` Mark Brown
2020-05-06 11:51 ` Jerome Brunet
2020-05-06 14:12 ` Sameer Pujar
2020-05-06 14:47 ` Jerome Brunet
2020-05-06 15:53 ` Mark Brown
2020-05-06 16:09 ` Sameer Pujar [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=74e724ec-72c9-e06a-cada-85110c9b145b@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=atalambedu@nvidia.com \
--cc=broonie@kernel.org \
--cc=digetx@gmail.com \
--cc=dramesh@nvidia.com \
--cc=jbrunet@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=nicoleotsuka@gmail.com \
--cc=nwartikar@nvidia.com \
--cc=perex@perex.cz \
--cc=rlokhande@nvidia.com \
--cc=sharadg@nvidia.com \
--cc=swarren@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.com \
--cc=viswanathl@nvidia.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).