From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
vadym.kochan@plvision.eu
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Re: [PATCH] arm64: dts: marvell: Add UART1-3 for AC5/AC5X
Date: Fri, 02 Sep 2022 16:06:01 +0200 [thread overview]
Message-ID: <878rn1g9bq.fsf@BL-laptop> (raw)
In-Reply-To: <20220803011623.3607642-1-chris.packham@alliedtelesis.co.nz>
Chris Packham <chris.packham@alliedtelesis.co.nz> writes:
> The AC5/AC5X SoC has 4 UART blocks. Add the additional UART1-3 blocks to
> the base dtsi file.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
Applied on mvebu/dt64
Thanks,
Gregory
> ---
>
> Notes:
> This applies on top of the series adding the AC5/AC5X SoC which is in
> Gregory's mvebu/dt64 tree but hasn't made it to Linus's (yet).
>
> arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi | 30 +++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi b/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
> index 80b44c7df56a..914fcf9e2c24 100644
> --- a/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
> +++ b/arch/arm64/boot/dts/marvell/ac5-98dx25xx.dtsi
> @@ -95,6 +95,36 @@ uart0: serial@12000 {
> status = "okay";
> };
>
> + uart1: serial@12100 {
> + compatible = "snps,dw-apb-uart";
> + reg = <0x11000 0x100>;
> + reg-shift = <2>;
> + interrupts = <GIC_SPI 84 IRQ_TYPE_LEVEL_HIGH>;
> + reg-io-width = <1>;
> + clocks = <&cnm_clock>;
> + status = "disabled";
> + };
> +
> + uart2: serial@12200 {
> + compatible = "snps,dw-apb-uart";
> + reg = <0x12200 0x100>;
> + reg-shift = <2>;
> + interrupts = <GIC_SPI 85 IRQ_TYPE_LEVEL_HIGH>;
> + reg-io-width = <1>;
> + clocks = <&cnm_clock>;
> + status = "disabled";
> + };
> +
> + uart3: serial@12300 {
> + compatible = "snps,dw-apb-uart";
> + reg = <0x12300 0x100>;
> + reg-shift = <2>;
> + interrupts = <GIC_SPI 86 IRQ_TYPE_LEVEL_HIGH>;
> + reg-io-width = <1>;
> + clocks = <&cnm_clock>;
> + status = "disabled";
> + };
> +
> mdio: mdio@22004 {
> #address-cells = <1>;
> #size-cells = <0>;
> --
> 2.37.1
>
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2022-09-02 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 1:16 [PATCH] arm64: dts: marvell: Add UART1-3 for AC5/AC5X Chris Packham
2022-09-02 14:06 ` Gregory CLEMENT [this message]
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=878rn1g9bq.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vadym.kochan@plvision.eu \
/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