From: Kenneth Westfield <kwestfie@codeaurora.org>
To: Mark Brown <broonie@kernel.org>
Cc: Device Tree Mailing List <devicetree@vger.kernel.org>,
ALSA Mailing List <alsa-devel@alsa-project.org>,
Banajit Goswami <bgoswami@codeaurora.org>,
Takashi Iwai <tiwai@suse.de>,
Greg KH <gregkh@linuxfoundation.org>,
Patrick Lai <plai@codeaurora.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
MSM Mailing List <linux-arm-msm@vger.kernel.org>,
David Brown <davidb@codeaurora.org>
Subject: Re: [Patch V4 03/10] ASoC: qcom: Document LPASS CPU bindings
Date: Sun, 8 Feb 2015 22:38:23 -0800 [thread overview]
Message-ID: <20150209063822.GA19870@kwestfie-linux.qualcomm.com> (raw)
In-Reply-To: <20150206221823.GF31311@finisterre.sirena.org.uk>
On Sat, Feb 07, 2015 at 06:18:23AM +0800, Mark Brown wrote:
> On Thu, Feb 05, 2015 at 12:53:39PM -0800, Kenneth Westfield wrote:
>
> > +- qcom,system-clock-shift : Add this bool property if the default
> > + frequency of the system clock needs to
> > + be reduced.
> > +- qcom,system-clock-shift-compare : A numerical value used to right-shift
> > + the default system clock frequency for
> > + comparison with the target bit clock
> > + frequency.
> > +- qcom,system-clock-shift-amount : A numerical value used to right-shift
> > + the default system clock frequency.
> > +- qcom,alternate-sysclk : Add this bool property if the default
> > + frequency of the system clock cannot
> > + divide down to the target bit clock
> > + frequency.
> > +- qcom,alternate-sysclk-bitwidth : A numerical value representing the
> > + sample bitwidth which requires use of
> > + the alternate system clock frequency.
> > +- qcom,alternate-sysclk-frequency : A numerical value representing the new
> > + system clock frequency to use.
>
> None of these seem like they are appropriate for device tree properties,
> they appear to be choosing a specific clocking configuration which is
> something that would normally be done as part of the system integration
> in the machine driver rather than in the DAI driver. This binding won't
> work in cases where the clocks are being changed at runtime and would
> limit systems where that becomes possible in future.
So I add a machine driver that selects the clocking freq in hw_params
and calls set_sysclk in the DAIs.
The DT node for the machine driver would look something like:
default_system_clock_frequency = < xxxxxx >;
alternate_system_clock_frequency = < xxxxxx >;
cpu_dai = < &cpu >;
codec_dai = < &codec >;
pinctrl... ?
Does this sound ok? Also, would it make sense to move the pinctrl back
to the machine driver?
--
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-09 6:38 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
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
[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 [this message]
[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 ` [alsa-devel] " Kenneth Westfield
2015-02-12 2:53 ` 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 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=20150209063822.GA19870@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=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;
as well as URLs for NNTP newsgroup(s).