From: Shawn Guo <shawn.guo@linaro.org>
To: Stefan Agner <stefan@agner.ch>
Cc: kernel@pengutronix.de, jic23@kernel.org, knaack.h@gmx.de,
lars@metafoo.de, pmeerw@pmeerw.net, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
B38611@freescale.com, maitysanchayan@gmail.com,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] ARM: dts: add property for maximum ADC clock frequencies
Date: Mon, 23 Mar 2015 21:30:31 +0800 [thread overview]
Message-ID: <20150323133030.GD28410@dragon> (raw)
In-Reply-To: <80ba0aa345e8bb04e23e2988f51a851d@agner.ch>
On Mon, Mar 16, 2015 at 04:17:55PM +0100, Stefan Agner wrote:
> Forgot to add i.MX/Vybrid maintainers Shawn and Sascha.
>
> On 2015-03-16 16:10, Stefan Agner wrote:
> > The ADC clock frequency is limited depending on modes used. Add
> > device tree property which allow to set the mode used and the
> > maximum frequency ratings for the instance. These allows to
> > set the ADC clock to a frequency which is within specification
> > according to the actual mode used.
> >
> > Acked-by: Fugang Duan <B38611@freescale.com>
> > Signed-off-by: Stefan Agner <stefan@agner.ch>
> > ---
> > Documentation/devicetree/bindings/iio/adc/vf610-adc.txt | 9 +++++++++
Bindings doc shouldn't be part of dts change, and needs to be approved
by DT maintainers.
Shawn
> > arch/arm/boot/dts/vfxxx.dtsi | 4 ++++
> > 2 files changed, 13 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/iio/adc/vf610-adc.txt
> > b/Documentation/devicetree/bindings/iio/adc/vf610-adc.txt
> > index 1a4a43d..3eb40e2 100644
> > --- a/Documentation/devicetree/bindings/iio/adc/vf610-adc.txt
> > +++ b/Documentation/devicetree/bindings/iio/adc/vf610-adc.txt
> > @@ -11,6 +11,13 @@ Required properties:
> > - clock-names: Must contain "adc", matching entry in the clocks property.
> > - vref-supply: The regulator supply ADC reference voltage.
> >
> > +Recommended properties:
> > +- fsl,adck-max-frequency: Maximum frequencies according to datasheets operating
> > + requirements. Three values are required, depending on conversion mode:
> > + - Frequency in normal mode (ADLPC=0, ADHSC=0)
> > + - Frequency in high-speed mode (ADLPC=0, ADHSC=1)
> > + - Frequency in low-power mode (ADLPC=1, ADHSC=0)
> > +
> > Example:
> > adc0: adc@4003b000 {
> > compatible = "fsl,vf610-adc";
> > @@ -18,5 +25,7 @@ adc0: adc@4003b000 {
> > interrupts = <0 53 0x04>;
> > clocks = <&clks VF610_CLK_ADC0>;
> > clock-names = "adc";
> > + fsl,adck-max-frequency = <30000000>, <40000000>,
> > + <20000000>;
> > vref-supply = <®_vcc_3v3_mcu>;
> > };
> > diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
> > index a29c7ce..c6609bd 100644
> > --- a/arch/arm/boot/dts/vfxxx.dtsi
> > +++ b/arch/arm/boot/dts/vfxxx.dtsi
> > @@ -189,6 +189,8 @@
> > clocks = <&clks VF610_CLK_ADC0>;
> > clock-names = "adc";
> > status = "disabled";
> > + fsl,adck-max-frequency = <30000000>, <40000000>,
> > + <20000000>;
> > };
> >
> > wdoga5: wdog@4003e000 {
> > @@ -387,6 +389,8 @@
> > clocks = <&clks VF610_CLK_ADC1>;
> > clock-names = "adc";
> > status = "disabled";
> > + fsl,adck-max-frequency = <30000000>, <40000000>,
> > + <20000000>;
> > };
> >
> > esdhc1: esdhc@400b2000 {
>
prev parent reply other threads:[~2015-03-23 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 15:10 [PATCH v2 0/3] iio: adc: vf610: respect ADC clocking limitations Stefan Agner
2015-03-16 15:10 ` [PATCH v2 2/3] iio: adc: vf610: implement configurable conversion modes Stefan Agner
2015-03-21 12:11 ` Jonathan Cameron
[not found] ` <1426518614-20201-1-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>
2015-03-16 15:10 ` [PATCH v2 1/3] iio: adc: vf610: use ADC clock within specification Stefan Agner
2015-03-16 15:10 ` [PATCH v2 3/3] ARM: dts: add property for maximum ADC clock frequencies Stefan Agner
2015-03-16 15:17 ` Stefan Agner
2015-03-23 13:30 ` Shawn Guo [this message]
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=20150323133030.GD28410@dragon \
--to=shawn.guo@linaro.org \
--cc=B38611@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=stefan@agner.ch \
/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).