From: <Claudiu.Beznea@microchip.com>
To: <Durai.ManickamKR@microchip.com>, <Nicolas.Ferre@microchip.com>,
<Cristian.Birsan@microchip.com>, <Hari.PrasathGE@microchip.com>,
<davem@davemloft.net>, <krzysztof.kozlowski+dt@linaro.org>,
<alexandre.belloni@bootlin.com>, <arnd@arndb.de>,
<olof@lixom.net>, <soc@kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <Manikandan.M@microchip.com>,
<Kavyasree.Kotagiri@microchip.com>,
<Horatiu.Vultur@microchip.com>
Subject: Re: [PATCHv1 1/8] ARM: dts: at91: sam9x60: Fix the label numbering for the flexcom functions
Date: Mon, 31 Oct 2022 10:25:18 +0000 [thread overview]
Message-ID: <52ed373d-24a6-fb8f-a70e-4345188e7739@microchip.com> (raw)
In-Reply-To: <20221031033653.43269-2-durai.manickamkr@microchip.com>
On 31.10.2022 05:36, Durai Manickam KR wrote:
> From: Manikandan M <manikandan.m@microchip.com>
>
> Fixed the label numbering of the flexcom functions so that all
> 13 flexcom functions of sam9x60 are in the following order when the missing
> flexcom functions are added:
>
> flx0: uart0, spi0, i2c0
> flx1: uart1, spi1, i2c1
> flx2: uart2, spi2, i2c2
> flx3: uart3, spi3, i2c3
> flx4: uart4, spi4, i2c4
> flx5: uart5, spi5, i2c5
> flx6: uart6, i2c6
> flx7: uart7, i2c7
> flx8: uart8, i2c8
> flx9: uart9, i2c9
> flx10: uart10, i2c10
> flx11: uart11, i2c11
> flx12: uart12, i2c12
>
> Signed-off-by: Manikandan M <manikandan.m@microchip.com>
Also you SoB should go here.
> ---
> arch/arm/boot/dts/at91-sam9x60ek.dts | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm/boot/dts/at91-sam9x60ek.dts b/arch/arm/boot/dts/at91-sam9x60ek.dts
> index 4ba52ba11dc6..265978514dcf 100644
> --- a/arch/arm/boot/dts/at91-sam9x60ek.dts
> +++ b/arch/arm/boot/dts/at91-sam9x60ek.dts
> @@ -16,8 +16,8 @@ / {
>
> aliases {
> i2c0 = &i2c0;
> - i2c1 = &i2c1;
> - serial1 = &uart1;
> + i2c1 = &i2c6;
> + serial1 = &uart5;
> };
>
> chosen {
> @@ -238,7 +238,7 @@ &flx4 {
> atmel,flexcom-mode = <ATMEL_FLEXCOM_MODE_SPI>;
> status = "disabled";
>
> - spi0: spi@400 {
> + spi4: spi@400 {
> compatible = "microchip,sam9x60-spi", "atmel,at91rm9200-spi";
> reg = <0x400 0x200>;
> interrupts = <13 IRQ_TYPE_LEVEL_HIGH 7>;
> @@ -257,7 +257,7 @@ &flx5 {
> atmel,flexcom-mode = <ATMEL_FLEXCOM_MODE_USART>;
> status = "okay";
>
> - uart1: serial@200 {
> + uart5: serial@200 {
> compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
> reg = <0x200 0x200>;
> atmel,usart-mode = <AT91_USART_MODE_SERIAL>;
> @@ -283,7 +283,7 @@ &flx6 {
> atmel,flexcom-mode = <ATMEL_FLEXCOM_MODE_TWI>;
> status = "okay";
>
> - i2c1: i2c@600 {
> + i2c6: i2c@600 {
> compatible = "microchip,sam9x60-i2c";
> reg = <0x600 0x200>;
> interrupts = <9 IRQ_TYPE_LEVEL_HIGH 7>;
> @@ -443,7 +443,7 @@ AT91_PIOA 13 AT91_PERIPH_A AT91_PINCTRL_NONE
> AT91_PIOA 14 AT91_PERIPH_A AT91_PINCTRL_NONE>;
> };
>
> - pinctrl_flx5_default: flx_uart {
> + pinctrl_flx5_default: flx5_uart {
> atmel,pins =
> <AT91_PIOA 7 AT91_PERIPH_C AT91_PINCTRL_NONE
> AT91_PIOA 8 AT91_PERIPH_B AT91_PINCTRL_NONE
next prev parent reply other threads:[~2022-10-31 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221031033653.43269-1-durai.manickamkr@microchip.com>
2022-10-31 10:20 ` [PATCHv1 0/8] Add support for sam9x60 curiosity board Claudiu.Beznea
2022-11-02 20:18 ` Krzysztof Kozlowski
2022-11-03 5:12 ` Durai.ManickamKR
[not found] ` <20221031033653.43269-3-durai.manickamkr@microchip.com>
2022-10-31 10:23 ` [PATCHv1 2/8] ARM: dts: at91: sam9x60: remove flexcom definitions Claudiu.Beznea
[not found] ` <20221031033653.43269-4-durai.manickamkr@microchip.com>
2022-10-31 10:24 ` [PATCHv1 3/8] ARM: dts: at91: sam9x60: Add " Claudiu.Beznea
2022-10-31 10:27 ` Claudiu.Beznea
2022-11-08 13:37 ` Nicolas Ferre
2022-11-15 5:33 ` Durai.ManickamKR
[not found] ` <20221031033653.43269-2-durai.manickamkr@microchip.com>
2022-10-31 10:22 ` [PATCHv1 1/8] ARM: dts: at91: sam9x60: Fix the label numbering for the flexcom functions Claudiu.Beznea
2022-10-31 10:25 ` Claudiu.Beznea [this message]
[not found] ` <20221031033653.43269-7-durai.manickamkr@microchip.com>
2022-10-31 10:28 ` [PATCHv1 6/8] ARM: dts: at91: sam9x60: Add missing flexcom definitions Claudiu.Beznea
2022-11-15 5:40 ` Durai.ManickamKR
[not found] ` <20221031033653.43269-8-durai.manickamkr@microchip.com>
2022-10-31 10:29 ` [PATCHv1 7/8] dt-bindings: arm: at91: Add info on SAM9X60-CURIOSITY Claudiu.Beznea
[not found] ` <20221031033653.43269-9-durai.manickamkr@microchip.com>
2022-10-31 10:29 ` [PATCHv1 8/8] ARM: dts: at91: sam9x60_curiosity: Add device tree for sam9x60_curiosity board Claudiu.Beznea
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=52ed373d-24a6-fb8f-a70e-4345188e7739@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Cristian.Birsan@microchip.com \
--cc=Durai.ManickamKR@microchip.com \
--cc=Hari.PrasathGE@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Manikandan.M@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
/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).