[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150307111838.GI28806@sirena.org.uk>
Date: Sat, 7 Mar 2015 11:18:38 +0000
From: Mark Brown <broonie@...nel.org>
To: Kumar Gala <galak@...eaurora.org>
Cc: Kenneth Westfield <kwestfie@...eaurora.org>,
Takashi Iwai <tiwai@...e.de>,
Liam Girdwood <lgirdwood@...il.com>,
Banajit Goswami <bgoswami@...eaurora.org>,
Patrick Lai <plai@...eaurora.org>,
David Brown <davidb@...eaurora.org>,
Bryan Huntsman <bryanh@...eaurora.org>,
Greg KH <gregkh@...uxfoundation.org>,
ALSA Mailing List <alsa-devel@...a-project.org>,
MSM Mailing List <linux-arm-msm@...r.kernel.org>,
Device Tree Mailing List <devicetree@...r.kernel.org>,
Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Patch V7 02/10] ASoC: qcom: Document LPASS CPU bindings
On Fri, Mar 06, 2015 at 04:06:48PM -0600, Kumar Gala wrote:
As previously and repeatedly requested please fix your mailer to word
wrap within paragraphs, not doing this makes your mails harder to read
and reply to. I've reflowed your message for legibility.
> > The audio DSP is, in fact, contained within the audio subsystem. The
> > representation of that relationship in the DT, I believe, would be a subnode.
> > OTOH, if there is a strong sentiment towards using a phandle, that would be
> > fine with me.
> Just depends on how we communicate with the DSP. If its mostly via
> MMIO access than a sub node makes sense. If its via some other
> RPC/communication mechanism than possibly a phandle. Trying to
> understand a bit more to than see what I’d recommend.
It should be a phandle, while these things are all part of the same
logical function in the CPU they're separate IPs and there may be many
DAIs.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists