[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <55956B7E.9010606@pid1solutions.com>
Date: Thu, 02 Jul 2015 12:49:02 -0400
From: Cory Tusar <cory.tusar@...1solutions.com>
To: Stefan Agner <stefan@...er.ch>
CC: robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
shawnguo@...nel.org, kernel@...gutronix.de, han.xu@...escale.com,
dwmw2@...radead.org, computersforpeace@...il.com,
linux@....linux.org.uk, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mtd@...ts.infradead.org, andrew@...n.ch
Subject: Re: [RFC PATCH 2/7] ARM: dts: vfxxx: Include support for qspi1 functionality.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/02/2015 09:44 AM, Stefan Agner wrote:
> On 2015-07-01 22:20, Cory Tusar wrote:
>> This commit extends the existing Vybrid QSPI devicetree implementation
>> to also describe the qspi1 functional block.
>>
>> Signed-off-by: Cory Tusar <cory.tusar@...1solutions.com>
>> ---
>> arch/arm/boot/dts/vfxxx.dtsi | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
>> index 089a263..a7c370e 100644
>> --- a/arch/arm/boot/dts/vfxxx.dtsi
>> +++ b/arch/arm/boot/dts/vfxxx.dtsi
>> @@ -251,6 +251,19 @@
>> status = "disabled";
>> };
>>
>> + qspi1: quadspi@...c4000 {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + compatible = "fsl,vf610-qspi";
>> + reg = <0x400c4000 0x1000>, <0x50000000 0x10000000>;
>> + reg-names = "QuadSPI", "QuadSPI-memory";
>> + interrupts = <25 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&clks VF610_CLK_QSPI1_EN>,
>> + <&clks VF610_CLK_QSPI1>;
>> + clock-names = "qspi_en", "qspi";
>> + status = "disabled";
>> + };
>> +
>> iomuxc: iomuxc@...48000 {
>> compatible = "fsl,vf610-iomuxc";
>> reg = <0x40048000 0x1000>;
>
> This seem to be at the wrong place under aips0. qspi1 should be under
> aips1. just before fec0. But other than that, I checked the addresses
> looks good to me. Hence with that change applied you can include:
>
> Reviewed-by: Stefan Agner <stefan@...er.ch>
Hi Stefan,
Thanks for the review. Will update for the next version.
You'd think I would've checked that after making the same goof with
i2c... :/
- -Cory
- --
Cory Tusar
Principal
PID 1 Solutions, Inc.
"There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies, and the
other way is to make it so complicated that there are no obvious
deficiencies." --Sir Charles Anthony Richard Hoare
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlWVa34ACgkQHT1tsfGwHJ/yCwCfU0jadwpYzOmZ86jDqSvtht+A
XvkAoKqfQJQmwVSibjxRDe57DcCWYlXd
=+QPB
-----END PGP SIGNATURE-----
--
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