From: "Yang, Wenyou" <Wenyou.Yang@atmel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Richard Genoud <richard.genoud@gmail.com>,
Mark Brown <broonie@kernel.org>,
"Ferre, Nicolas" <Nicolas.FERRE@atmel.com>
Subject: RE: linux-next: manual merge of the arm-soc tree with the spi-mb tree
Date: Fri, 26 Apr 2013 07:48:51 +0000 [thread overview]
Message-ID: <B256D81BAE5131468A838E5D7A24364154234E9D@penmbx02> (raw)
In-Reply-To: <20130426170649.d21c2d7a74e56d836ff6f04f@canb.auug.org.au>
Hi,
It is OK for spi
Thanks
Best Regards,
Wenyou Yang
> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> Sent: 2013年4月26日 15:07
> To: Olof Johansson; Arnd Bergmann; linux-arm-kernel@lists.infradead.org
> Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; Yang, Wenyou;
> Richard Genoud; Mark Brown; Ferre, Nicolas
> Subject: linux-next: manual merge of the arm-soc tree with the spi-mb tree
>
> Hi all,
>
> Today's linux-next merge of the arm-soc tree got a conflict in
> arch/arm/boot/dts/at91sam9x5.dtsi between commits d50f88a0c304 ("ARM:
> dts: add spi nodes for atmel SoC") and a68b728f7a21 ("ARM: dts: add pinctrl
> property for spi node for atmel SoC") from the spi-mb tree and commits
> e9a72ee81d58 ("ARM: at91: dt: at91sam9x5: add i2c pinctrl"),
> 463c9c7bf1f3 ("ARM: at91: dt: at91sam9x5: add i2c-gpio pinctrl") and
> b909c6c94462 ("ARM: at91/at91sam9x5: add RTC node") from the arm-soc
> tree.
>
> I fixed it up (hopefully - see below) and can carry the fix as necessary (no action
> is required).
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> diff --cc arch/arm/boot/dts/at91sam9x5.dtsi index 347b438,284bf24..0000000
> --- a/arch/arm/boot/dts/at91sam9x5.dtsi
> +++ b/arch/arm/boot/dts/at91sam9x5.dtsi
> @@@ -343,23 -343,53 +343,70 @@@
> };
> };
>
> + spi0 {
> + pinctrl_spi0: spi0-0 {
> + atmel,pins =
> + <0 11 0x1 0x0 /* PA11 periph A SPI0_MISO
> pin */
> + 0 12 0x1 0x0 /* PA12 periph A SPI0_MOSI
> pin */
> + 0 13 0x1 0x0>; /* PA13 periph A
> SPI0_SPCK pin */
> + };
> + };
> +
> + spi1 {
> + pinctrl_spi1: spi1-0 {
> + atmel,pins =
> + <0 21 0x2 0x0 /* PA21 periph B SPI1_MISO
> pin */
> + 0 22 0x2 0x0 /* PA22 periph B SPI1_MOSI
> pin */
> + 0 23 0x2 0x0>; /* PA23 periph B
> SPI1_SPCK pin */
> + };
> + };
> + i2c0 {
> + pinctrl_i2c0: i2c0-0 {
> + atmel,pins =
> + <0 30 0x1 0x0 /* PA30 periph A I2C0 data */
> + 0 31 0x1 0x0>; /* PA31 periph A I2C0
> clock */
> + };
> + };
> +
> + i2c1 {
> + pinctrl_i2c1: i2c1-0 {
> + atmel,pins =
> + <2 0 0x3 0x0 /* PC0 periph C I2C1 data */
> + 2 1 0x3 0x0>; /* PC1 periph C I2C1 clock */
> + };
> + };
> +
> + i2c2 {
> + pinctrl_i2c2: i2c2-0 {
> + atmel,pins =
> + <1 4 0x2 0x0 /* PB4 periph B I2C2 data */
> + 1 5 0x2 0x0>; /* PB5 periph B I2C2 clock */
> + };
> + };
> +
> + i2c_gpio0 {
> + pinctrl_i2c_gpio0: i2c_gpio0-0 {
> + atmel,pins =
> + <0 30 0x0 0x2 /* PA30 gpio multidrive I2C0
> data */
> + 0 31 0x0 0x2>; /* PA31 gpio multidrive
> I2C0 clock */
> + };
> + };
> +
> + i2c_gpio1 {
> + pinctrl_i2c_gpio1: i2c_gpio1-0 {
> + atmel,pins =
> + <2 0 0x0 0x2 /* PC0 gpio multidrive I2C1
> data */
> + 2 1 0x0 0x2>; /* PC1 gpio multidrive I2C1
> clock */
> + };
> + };
> +
> + i2c_gpio2 {
> + pinctrl_i2c_gpio2: i2c_gpio2-0 {
> + atmel,pins =
> + <1 4 0x0 0x2 /* PB4 gpio multidrive I2C2
> data */
> + 1 5 0x0 0x2>; /* PB5 gpio multidrive I2C2
> clock */
> + };
> + };
>
> pioA: gpio@fffff400 {
> compatible = "atmel,at91sam9x5-gpio",
> "atmel,at91rm9200-gpio"; @@@ -548,27 -587,12 +604,33 @@@
> };
> };
>
> + spi0: spi@f0000000 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "atmel,at91rm9200-spi";
> + reg = <0xf0000000 0x100>;
> + interrupts = <13 4 3>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_spi0>;
> + status = "disabled";
> + };
> +
> + spi1: spi@f0004000 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "atmel,at91rm9200-spi";
> + reg = <0xf0004000 0x100>;
> + interrupts = <14 4 3>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_spi1>;
> + status = "disabled";
> + };
> + rtc@fffffeb0 {
> + compatible = "atmel,at91rm9200-rtc";
> + reg = <0xfffffeb0 0x40>;
> + interrupts = <1 4 7>;
> + status = "disabled";
> + };
> };
>
> nand0: nand@40000000 {
next prev parent reply other threads:[~2013-04-26 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 7:06 linux-next: manual merge of the arm-soc tree with the spi-mb tree Stephen Rothwell
2013-04-26 7:21 ` Richard Genoud
2013-04-26 7:48 ` Yang, Wenyou [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-02 5:18 Stephen Rothwell
2012-10-02 5:13 Stephen Rothwell
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=B256D81BAE5131468A838E5D7A24364154234E9D@penmbx02 \
--to=wenyou.yang@atmel.com \
--cc=Nicolas.FERRE@atmel.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=richard.genoud@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).