linux-kernel - Re: [PATCH 3/3] ARM: dts: vf610: add remaining SAI instaces

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <7c3b0b28706f2bf1cf656c7dc2daf31d@agner.ch>
Date:	Wed, 27 Jan 2016 16:31:48 -0800
From:	Stefan Agner <stefan@...er.ch>
To:	shawnguo@...nel.org
Cc:	galak@...eaurora.org, ijc+devicetree@...lion.org.uk,
	mark.rutland@....com, pawel.moll@....com, robh+dt@...nel.org,
	Li.Xiubo@...escale.com, zidan.wang@...escale.com,
	linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
	linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
	kernel@...gutronix.de, mturquette@...libre.com,
	sboyd@...eaurora.org
Subject: Re: [PATCH 3/3] ARM: dts: vf610: add remaining SAI instaces

Hi Shawn,

The rest of the patchset has been applied during rc phase of v4.4, I
guess this one was scheduled for the next release (v4.5). However, I
just realized that this seemed to have slipped through...

--
Stefan

On 2015-10-17 21:05, Stefan Agner wrote:
> This adds the remaining SAI instances SAI0, SAI1 and SAI3. All
> instances are very similar, except that the DMA channel of SAI3
> is available on MUX1 (compared to MUX0 for SAI0-SAI2). Also,
> SAI3 has a slightly different memory map due to a deeper FIFO,
> however in practice the current driver works for SAI3 fine.
> 
> Signed-off-by: Stefan Agner <stefan@...er.ch>
> ---
>  arch/arm/boot/dts/vfxxx.dtsi | 42 ++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 42 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
> index c2a4d1c..b45bc81 100644
> --- a/arch/arm/boot/dts/vfxxx.dtsi
> +++ b/arch/arm/boot/dts/vfxxx.dtsi
> @@ -174,6 +174,34 @@
>  				status = "disabled";
>  			};
>  
> +			sai0: sai@...2f000 {
> +				compatible = "fsl,vf610-sai";
> +				reg = <0x4002f000 0x1000>;
> +				interrupts = <84 IRQ_TYPE_LEVEL_HIGH>;
> +				clocks = <&clks VF610_CLK_SAI0>,
> +					<&clks VF610_CLK_SAI0_DIV>,
> +					<&clks 0>, <&clks 0>;
> +				clock-names = "bus", "mclk1", "mclk2", "mclk3";
> +				dma-names = "tx", "rx";
> +				dmas = <&edma0 0 17>,
> +					<&edma0 0 16>;
> +				status = "disabled";
> +			};
> +
> +			sai1: sai@...30000 {
> +				compatible = "fsl,vf610-sai";
> +				reg = <0x40030000 0x1000>;
> +				interrupts = <85 IRQ_TYPE_LEVEL_HIGH>;
> +				clocks = <&clks VF610_CLK_SAI1>,
> +					<&clks VF610_CLK_SAI1_DIV>,
> +					<&clks 0>, <&clks 0>;
> +				clock-names = "bus", "mclk1", "mclk2", "mclk3";
> +				dma-names = "tx", "rx";
> +				dmas = <&edma0 0 19>,
> +					<&edma0 0 18>;
> +				status = "disabled";
> +			};
> +
>  			sai2: sai@...31000 {
>  				compatible = "fsl,vf610-sai";
>  				reg = <0x40031000 0x1000>;
> @@ -188,6 +216,20 @@
>  				status = "disabled";
>  			};
>  
> +			sai3: sai@...32000 {
> +				compatible = "fsl,vf610-sai";
> +				reg = <0x40032000 0x1000>;
> +				interrupts = <87 IRQ_TYPE_LEVEL_HIGH>;
> +				clocks = <&clks VF610_CLK_SAI3>,
> +					<&clks VF610_CLK_SAI3_DIV>,
> +					<&clks 0>, <&clks 0>;
> +				clock-names = "bus", "mclk1", "mclk2", "mclk3";
> +				dma-names = "tx", "rx";
> +				dmas = <&edma0 1 9>,
> +					<&edma0 1 8>;
> +				status = "disabled";
> +			};
> +
>  			pit: pit@...37000 {
>  				compatible = "fsl,vf610-pit";
>  				reg = <0x40037000 0x1000>;