linux-kernel - Re: [PATCH v2 3/3] ARM: dts: add property for maximum ADC clock frequencies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150323133030.GD28410@dragon>
Date:	Mon, 23 Mar 2015 21:30:31 +0800
From:	Shawn Guo <shawn.guo@...aro.org>
To:	Stefan Agner <stefan@...er.ch>
Cc:	kernel@...gutronix.de, jic23@...nel.org, knaack.h@....de,
	lars@...afoo.de, pmeerw@...erw.net, robh+dt@...nel.org,
	pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
	B38611@...escale.com, maitysanchayan@...il.com,
	devicetree@...r.kernel.org, linux-iio@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/3] ARM: dts: add property for maximum ADC clock
 frequencies

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@...escale.com>
> > Signed-off-by: Stefan Agner <stefan@...er.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@...3b000 {
> >  	compatible = "fsl,vf610-adc";
> > @@ -18,5 +25,7 @@ adc0: adc@...3b000 {
> >  	interrupts = <0 53 0x04>;
> >  	clocks = <&clks VF610_CLK_ADC0>;
> >  	clock-names = "adc";
> > +	fsl,adck-max-frequency = <30000000>, <40000000>,
> > +				<20000000>;
> >  	vref-supply = <&reg_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@...3e000 {
> > @@ -387,6 +389,8 @@
> >  				clocks = <&clks VF610_CLK_ADC1>;
> >  				clock-names = "adc";
> >  				status = "disabled";
> > +				fsl,adck-max-frequency = <30000000>, <40000000>,
> > +							<20000000>;
> >  			};
> >  
> >  			esdhc1: esdhc@...b2000 {
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/