From: Kumar Gala <galak@codeaurora.org>
To: Kenneth Westfield <kwestfie@codeaurora.org>
Cc: Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Banajit Goswami <bgoswami@codeaurora.org>,
Patrick Lai <plai@codeaurora.org>,
David Brown <davidb@codeaurora.org>,
Bryan Huntsman <bryanh@codeaurora.org>,
Greg KH <gregkh@linuxfoundation.org>,
ALSA Mailing List <alsa-devel@alsa-project.org>,
MSM Mailing List <linux-arm-msm@vger.kernel.org>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Patch V7 02/10] ASoC: qcom: Document LPASS CPU bindings
Date: Fri, 6 Mar 2015 16:06:48 -0600 [thread overview]
Message-ID: <37AEDC0C-448D-4F3A-B87D-C37B9F2D8E1B@codeaurora.org> (raw)
In-Reply-To: <20150306220342.GA25363@kwestfie-linux.qualcomm.com>
On Mar 6, 2015, at 4:03 PM, Kenneth Westfield <kwestfie@codeaurora.org> wrote:
> On Fri, Mar 06, 2015 at 10:07:01AM -0600, Kumar Gala wrote:
>> On Mar 5, 2015, at 7:51 PM, Kenneth Westfield <kwestfie@codeaurora.org> wrote:
>>> On Thu, Mar 05, 2015 at 12:52:30PM -0600, Kumar Gala wrote:
>>>> On Mar 3, 2015, at 6:21 PM, Kenneth Westfield <kwestfie@codeaurora.org> wrote:
>>>>
>>>>> +++ b/Documentation/devicetree/bindings/sound/qcom,lpass-cpu.txt
>>>>> @@ -0,0 +1,49 @@
>>>>> +* Qualcomm Technologies LPASS CPU DAI
>>>>> +
>>>>> +Required subnodes:
>>>>> +
>>>>> +- qcom,adsp : Audio DSP sub-node
>>>>> +
>>>>> +Optional Audio DSP subnode properties:
>>>>> +
>>>>> +- status : "disabled" indicates the adsp is not available.
>>>>> +
>>>>
>>>> What is the intent of this subnode?
>>>>
>>>
>>> From the cover letter:
>>> Even though the ipq806x LPASS does not contain an audio DSP, other SOCs
>>> do have one. For those SOCs, the audio DSP typically controls the
>>> hardware blocks in the LPASS. Hence, different CPU DAI driver(s) would
>>> need to be used in order to facilitate audio with the DSP. As such, the
>>> LPASS DT contains an adsp subnode, which is disabled for this SOC. The
>>> same subnode should be enabled and populated for other SOCs that do
>>> contain an audio DSP. Not using the audio DSP would require different
>>> CPU DAI driver(s), in addition to possible bootloader and/or firmware
>>> changes.
>>>
>>> This was the result of a request from Mark. See here:
>>> http://thread.gmane.org/gmane.linux.drivers.devicetree/109331/focus=11633
>>
>> Two quick comments before I read Mark?s comments.
>>
>> 1. Its not normal practice to put something into a DT that does not exist. Having a node, but marking it disabled implies existence.
>
> Will change the DT definition to optional.
>
>> 2. How would one normally address the audio DSP if it did exist. I?m just wondering if having a subnode is the proper solution vs maybe a phandle
>
> 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.
- k
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-03-06 22:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 0:21 [Patch V7 00/10] ASoC: QCOM: Add support for ipq806x SOC Kenneth Westfield
2015-03-04 0:21 ` [Patch V7 01/10] MAINTAINERS: Add QCOM audio ASoC maintainer Kenneth Westfield
2015-03-05 17:39 ` Mark Brown
2015-03-04 0:21 ` [Patch V7 02/10] ASoC: qcom: Document LPASS CPU bindings Kenneth Westfield
2015-03-05 17:38 ` Mark Brown
2015-03-05 18:52 ` Kumar Gala
2015-03-06 1:51 ` Kenneth Westfield
2015-03-06 16:07 ` Kumar Gala
2015-03-06 22:03 ` Kenneth Westfield
2015-03-06 22:06 ` Kumar Gala [this message]
2015-03-07 11:18 ` Mark Brown
2015-03-04 0:21 ` [Patch V7 03/10] ASoC: qcom: Document Storm bindings Kenneth Westfield
2015-03-06 11:18 ` Mark Brown
2015-03-04 0:21 ` [Patch V7 04/10] ASoC: qcom: add LPASS header files Kenneth Westfield
2015-03-05 17:13 ` Mark Brown
2015-03-04 0:21 ` [Patch V7 05/10] ASoC: qcom: Add LPASS CPU DAI driver Kenneth Westfield
2015-03-05 17:38 ` Mark Brown
2015-03-04 0:21 ` [Patch V7 06/10] ASoC: qcom: Add LPASS platform driver Kenneth Westfield
2015-03-05 17:38 ` Mark Brown
2015-03-04 0:21 ` [Patch V7 07/10] ASoC: qcom: Add Storm machine driver Kenneth Westfield
2015-03-04 0:21 ` [Patch V7 08/10] ASoC: qcom: Add ability to build QCOM drivers Kenneth Westfield
2015-03-04 0:21 ` [Patch V7 09/10] ASoC: Allow for building " Kenneth Westfield
2015-03-04 0:21 ` [Patch V7 10/10] ARM: dts: Model IPQ LPASS audio hardware Kenneth Westfield
2015-03-05 17:40 ` Mark Brown
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=37AEDC0C-448D-4F3A-B87D-C37B9F2D8E1B@codeaurora.org \
--to=galak@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kwestfie@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plai@codeaurora.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®