[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8e7c50f79165374935f42c15aeff42a8@agner.ch>
Date: Wed, 28 Jan 2015 10:08:38 +0100
From: Stefan Agner <stefan@...er.ch>
To: Bhuvanchandra DV <bhuvanchandra.dv@...adex.com>
Cc: mark.rutland@....com, shawn.guo@...aro.org, robh+dt@...nel.org,
pawel.moll@....com, ijc+devicetree@...lion.org.uk,
galak@...eaurora.org, linux@....linux.org.uk, broonie@...nel.org,
B44548@...escale.com, Li.Xiubo@...escale.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH 1/7] ARM: vf610: add second DSPI instance
On 2015-01-27 11:57, Bhuvanchandra DV wrote:
> Acked-by: Stefan Agner <stefan@...er.ch>
> Signed-off-by: Bhuvanchandra DV <bhuvanchandra.dv@...adex.com>
> ---
> arch/arm/boot/dts/vf500.dtsi | 4 ++++
> arch/arm/boot/dts/vfxxx.dtsi | 11 +++++++++++
> 2 files changed, 15 insertions(+)
>
> diff --git a/arch/arm/boot/dts/vf500.dtsi b/arch/arm/boot/dts/vf500.dtsi
> index 1dbf8d2..f5f807c 100644
> --- a/arch/arm/boot/dts/vf500.dtsi
> +++ b/arch/arm/boot/dts/vf500.dtsi
> @@ -66,6 +66,10 @@
> interrupts = <GIC_SPI 67 IRQ_TYPE_LEVEL_HIGH>;
> };
>
> +&dspi1 {
> + interrupts = <GIC_SPI 68 IRQ_TYPE_LEVEL_HIGH>;
> +};
> +
> &edma0 {
> interrupts = <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>,
> <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>;
> diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
> index a29c7ce..789744b 100644
> --- a/arch/arm/boot/dts/vfxxx.dtsi
> +++ b/arch/arm/boot/dts/vfxxx.dtsi
> @@ -139,6 +139,17 @@
> status = "disabled";
> };
>
> + dspi1: dspi1@...2d000 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "fsl,vf610-dspi";
> + reg = <0x4002d000 0x1000>;
> + clocks = <&clks VF610_CLK_DSPI1>;
> + clock-names = "dspi";
> + spi-num-chipselects = <5>;
> + status = "disabled";
> + };
> +
> sai2: sai@...31000 {
> compatible = "fsl,vf610-sai";
> reg = <0x40031000 0x1000>;
Acked-by: Stefan Agner <stefan@...er.ch>
Shawn, this will conflict with the pending MSCM driver patchset. I
probably have to resend the MSCM patchset anyway, also, the fix would be
trivial anyway.
--
Stefan
--
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/
Powered by blists - more mailing lists