From: Kenneth Westfield <kwestfie@codeaurora.org>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
David Brown <davidb@codeaurora.org>,
Bryan Huntsman <bryanh@codeaurora.org>,
Greg KH <gregkh@linuxfoundation.org>,
Banajit Goswami <bgoswami@codeaurora.org>,
Patrick Lai <plai@codeaurora.org>,
ALSA Mailing List <alsa-devel@alsa-project.org>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
MSM Mailing List <linux-arm-msm@vger.kernel.org>,
srinivas.kandagatla@linaro.org,
Kenneth Westfield <kwestfie@codeaurora.org>
Subject: Re: [alsa-devel] [Patch V4 00/10] ASoC: QCOM: Add support for ipq806x SOC
Date: Wed, 11 Feb 2015 17:05:52 -0800 [thread overview]
Message-ID: <20150212010551.GA7330@kwestfie-linux.qualcomm.com> (raw)
In-Reply-To: <20150211022634.GO2593@finisterre.sirena.org.uk>
On Tue, Feb 10, 2015 at 06:26:34PM -0800, Mark Brown wrote:
> On Sun, Feb 08, 2015 at 10:45:11PM -0800, Kenneth Westfield wrote:
> > On Sat, Feb 07, 2015 at 06:32:29AM +0800, Mark Brown wrote:
>
> > > I'd really like to see some discussion as to how this is all supposed
> to
> > > be handled - how will these direct hardware access drivers and device
> > > trees work when someone does want to use the DSP (without causing
> > > problems), and how will we transition from one to the other. This is
> > > particularly pressing if there are use cases where people will want to
> > > switch between the two modes at runtime.
>
> > > What I'm trying to avoid here is being in a situation where we have
> > > existing stable DT bindings which we have to support but which
> conflict
> > > with the way that people want to use the systems.
>
> > The ipq806x SOC has no LPASS DSP. On SOCs with a DSP, these drivers
> > would not be enabled.
>
> OK, but I'm guessing that they're using the same IP that is in other
> SoCs which do have the DSP so even if you don't care for this device it
> might still be an issue.
>
> > These drivers are prefixed with "lpass" to differentiate themselves from
> > other drivers that would interact with a DSP, rather than the LPASS
> > hardware directly.
>
> Right, it may be that all that's needed here is some indication as to
> how to describe a system which *does* have a DSP. Perhaps require that
> the devices be children of the DSP, that way if people want to access
> the hardware directly they can load a dummy driver for the DSP that just
> passes things through if they don't want to use the DSP?
Replacing DSP-based drivers with LPASS-based drivers would be something that
should be handled by Kconfig selections. For the DT, the DSP-related
nodes and the LPASS-related nodes shouldn't overlap. There should be a
DSP-based DT binding and a separate LPASS-based DT binding. Tying one
or the other to the sound node (but not both), should work.
--
Kenneth Westfield
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-02-12 1:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 20:53 [Patch V4 00/10] ASoC: QCOM: Add support for ipq806x SOC Kenneth Westfield
2015-02-05 20:53 ` [Patch V4 01/10] MAINTAINERS: Add QCOM audio ASoC maintainer Kenneth Westfield
2015-02-05 20:53 ` [Patch V4 02/10] ASoC: max98357a: Document MAX98357A bindings Kenneth Westfield
2015-02-06 22:12 ` Mark Brown
[not found] ` <1423169626-22166-1-git-send-email-kwestfie-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-02-05 20:53 ` [Patch V4 03/10] ASoC: qcom: Document LPASS CPU bindings Kenneth Westfield
2015-02-06 22:18 ` Mark Brown
2015-02-09 6:38 ` Kenneth Westfield
[not found] ` <20150209063822.GA19870-VfhoOQ2zEbNBVvN7MMdr1KRtKmQZhJ7pQQ4Iyu8u01E@public.gmane.org>
2015-02-09 8:08 ` Mark Brown
2015-02-05 20:53 ` [Patch V4 05/10] ASoC: ipq806x: add LPASS header files Kenneth Westfield
[not found] ` <1423169626-22166-6-git-send-email-kwestfie-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-02-06 22:58 ` Mark Brown
2015-02-05 20:53 ` [Patch V4 07/10] ASoC: ipq806x: Add LPASS platform driver Kenneth Westfield
2015-02-06 22:55 ` Mark Brown
2015-02-06 22:32 ` [Patch V4 00/10] ASoC: QCOM: Add support for ipq806x SOC Mark Brown
2015-02-09 6:45 ` Kenneth Westfield
2015-02-11 2:26 ` Mark Brown
2015-02-12 1:05 ` Kenneth Westfield [this message]
2015-02-12 2:53 ` [alsa-devel] " Mark Brown
[not found] ` <20150212025341.GT2593-bheZrs9scGb3/WHNxyQH9YN0K6Il/+VY@public.gmane.org>
2015-02-12 7:20 ` Patrick Lai
2015-02-14 5:25 ` Mark Brown
2015-02-05 20:53 ` [Patch V4 04/10] ASoC: codec: Add MAX98357A codec driver Kenneth Westfield
2015-02-06 22:13 ` Mark Brown
2015-02-05 20:53 ` [Patch V4 06/10] ASoC: ipq806x: Add LPASS CPU DAI driver Kenneth Westfield
2015-02-06 22:40 ` Mark Brown
2015-02-05 20:53 ` [Patch V4 08/10] ASoC: qcom: Add ability to build QCOM drivers Kenneth Westfield
[not found] ` <1423169626-22166-9-git-send-email-kwestfie-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-02-06 23:00 ` Mark Brown
2015-02-05 20:53 ` [Patch V4 09/10] ASoC: Allow for building " Kenneth Westfield
2015-02-05 20:53 ` [Patch V4 10/10] ARM: dts: Model IPQ LPASS audio hardware Kenneth Westfield
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=20150212010551.GA7330@kwestfie-linux.qualcomm.com \
--to=kwestfie@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=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=plai@codeaurora.org \
--cc=srinivas.kandagatla@linaro.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