linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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 3/8] ARM: dts: at91: sam9x60: Add flexcom definitions
Date: Mon, 31 Oct 2022 10:27:15 +0000	[thread overview]
Message-ID: <e3876fd8-e5e0-d7af-252c-8bba5ec9e7e0@microchip.com> (raw)
In-Reply-To: <20221031033653.43269-4-durai.manickamkr@microchip.com>

On 31.10.2022 05:36, Durai Manickam KR wrote:
> Add the flexcom definitions to the SoC specifc DTSI file.
> 
> Signed-off-by: Durai Manickam KR <durai.manickamkr@microchip.com>
> Signed-off-by: Hari Prasath <Hari.PrasathGE@microchip.com>
> Signed-off-by: Manikandan M <manikandan.m@microchip.com>

For a cleaner view you can use [] to specify each ones contribution. See
https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html#developer-s-certificate-of-origin-1-1

> ---
>  arch/arm/boot/dts/sam9x60.dtsi | 52 ++++++++++++++++++++++++++++++++--
>  1 file changed, 50 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/sam9x60.dtsi b/arch/arm/boot/dts/sam9x60.dtsi
> index ef07d281a3db..fd4f5d43f7bb 100644
> --- a/arch/arm/boot/dts/sam9x60.dtsi
> +++ b/arch/arm/boot/dts/sam9x60.dtsi
> @@ -170,6 +170,16 @@ flx4: flexcom@f0000000 {
>  				#size-cells = <1>;
>  				ranges = <0x0 0xf0000000 0x800>;
>  				status = "disabled";
> +
> +				spi4: spi@400 {
> +					compatible = "microchip,sam9x60-spi", "atmel,at91rm9200-spi";
> +					reg = <0x400 0x200>;
> +					interrupts = <13 IRQ_TYPE_LEVEL_HIGH 7>;
> +					clocks = <&pmc PMC_TYPE_PERIPHERAL 13>;
> +					clock-names = "spi_clk";
> +					atmel,fifo-size = <16>;
> +					status = "disabled";
> +				};
>  			};
>  
>  			flx5: flexcom@f0004000 {
> @@ -180,6 +190,26 @@ flx5: flexcom@f0004000 {
>  				#size-cells = <1>;
>  				ranges = <0x0 0xf0004000 0x800>;
>  				status = "disabled";
> +
> +				uart5: serial@200 {
> +					compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";
> +					reg = <0x200 0x200>;
> +					interrupts = <14 IRQ_TYPE_LEVEL_HIGH 7>;
> +					dmas = <&dma0
> +						(AT91_XDMAC_DT_MEM_IF(0) |
> +						 AT91_XDMAC_DT_PER_IF(1) |
> +						 AT91_XDMAC_DT_PERID(10))>,
> +						<&dma0
> +						(AT91_XDMAC_DT_MEM_IF(0) |
> +						 AT91_XDMAC_DT_PER_IF(1) |
> +						 AT91_XDMAC_DT_PERID(11))>;
> +					dma-names = "tx", "rx";
> +					clocks = <&pmc PMC_TYPE_PERIPHERAL 14>;
> +					clock-names = "usart";
> +					atmel,use-dma-rx;
> +					atmel,use-dma-tx;
> +					status = "disabled";
> +				};
>  			};
>  
>  			dma0: dma-controller@f0008000 {
> @@ -390,6 +420,15 @@ flx6: flexcom@f8010000 {
>  				#size-cells = <1>;
>  				ranges = <0x0 0xf8010000 0x800>;
>  				status = "disabled";
> +
> +				i2c6: i2c@600 {
> +					compatible = "microchip,sam9x60-i2c";
> +					reg = <0x600 0x200>;
> +					interrupts = <9 IRQ_TYPE_LEVEL_HIGH 7>;
> +					clocks = <&pmc PMC_TYPE_PERIPHERAL 9>;
> +					atmel,fifo-size = <16>;
> +					status = "disabled";
> +				};
>  			};
>  
>  			flx7: flexcom@f8014000 {
> @@ -416,10 +455,19 @@ flx0: flexcom@f801c000 {
>  				compatible = "atmel,sama5d2-flexcom";
>  				reg = <0xf801c000 0x200>;
>  				clocks = <&pmc PMC_TYPE_PERIPHERAL 5>;
> -				#address-cells = <1>;
> -				#size-cells = <1>;
>  				ranges = <0x0 0xf801c000 0x800>;
>  				status = "disabled";
> +
> +				i2c0: i2c@600 {
> +					compatible = "microchip,sam9x60-i2c";
> +					reg = <0x600 0x200>;
> +					interrupts = <5 IRQ_TYPE_LEVEL_HIGH 7>;
> +					#address-cells = <1>;
> +					#size-cells = <0>;
> +					clocks = <&pmc PMC_TYPE_PERIPHERAL 5>;
> +					atmel,fifo-size = <16>;
> +					status = "disabled";
> +				};
>  			};
>  
>  			flx1: flexcom@f8020000 {

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-10-31 10:28 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 [this message]
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
     [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=e3876fd8-e5e0-d7af-252c-8bba5ec9e7e0@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).