[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200506155311.GG5299@sirena.org.uk>
Date: Wed, 6 May 2020 16:53:11 +0100
From: Mark Brown <broonie@...nel.org>
To: Jerome Brunet <jbrunet@...libre.com>
Cc: Sameer Pujar <spujar@...dia.com>, perex@...ex.cz, tiwai@...e.com,
kuninori.morimoto.gx@...esas.com, nicoleotsuka@...il.com,
alsa-devel@...a-project.org, swarren@...dia.com,
linux-kernel@...r.kernel.org, nwartikar@...dia.com,
lgirdwood@...il.com, jonathanh@...dia.com, viswanathl@...dia.com,
sharadg@...dia.com, thierry.reding@...il.com,
atalambedu@...dia.com, linux-tegra@...r.kernel.org,
digetx@...il.com, rlokhande@...dia.com, mkumard@...dia.com,
dramesh@...dia.com
Subject: Re: [RFC] DPCM for Tegra
On Wed, May 06, 2020 at 04:47:09PM +0200, Jerome Brunet wrote:
> On Wed 06 May 2020 at 16:12, Sameer Pujar <spujar@...dia.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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists