From: Linus Walleij <linus.walleij@linaro.org>
To: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"William Zhang" <william.zhang@broadcom.com>,
"Anand Gore" <anand.gore@broadcom.com>,
"Kursad Oney" <kursad.oney@broadcom.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Olivia Mackall" <olivia@selenic.com>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
"Florian Fainelli" <f.fainelli@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH 01/12] ARM: dts: bcm6878: Correct UART0 IRQ number
Date: Fri, 28 Mar 2025 08:43:51 +0100 [thread overview]
Message-ID: <20250328-bcmbca-peripherals-arm-v1-1-e4e515dc9b8c@linaro.org> (raw)
In-Reply-To: <20250328-bcmbca-peripherals-arm-v1-0-e4e515dc9b8c@linaro.org>
According to the vendor file 6878_intr.h the UART0 has IRQ
28, not 32.
Assuming this is a copy-and-paste error.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
arch/arm/boot/dts/broadcom/bcm6878.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/broadcom/bcm6878.dtsi b/arch/arm/boot/dts/broadcom/bcm6878.dtsi
index 70cf23a65fdb5ac7ed9eabc986f4ebb4df263c43..cf378970db08c05c40564a38931417a7be759532 100644
--- a/arch/arm/boot/dts/broadcom/bcm6878.dtsi
+++ b/arch/arm/boot/dts/broadcom/bcm6878.dtsi
@@ -137,7 +137,7 @@ nandcs: nand@0 {
uart0: serial@12000 {
compatible = "arm,pl011", "arm,primecell";
reg = <0x12000 0x1000>;
- interrupts = <GIC_SPI 32 IRQ_TYPE_LEVEL_HIGH>;
+ interrupts = <GIC_SPI 28 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&uart_clk>, <&uart_clk>;
clock-names = "uartclk", "apb_pclk";
status = "disabled";
--
2.48.1
next prev parent reply other threads:[~2025-03-28 7:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 7:43 [PATCH 00/12] ARM: bcm: Add some BCMBCA peripherals Linus Walleij
2025-03-28 7:43 ` Linus Walleij [this message]
2025-03-28 7:43 ` [PATCH 02/12] dt-bindings: rng: r200: Add interrupt property Linus Walleij
2025-03-31 8:00 ` Krzysztof Kozlowski
2025-03-28 7:43 ` [PATCH 03/12] ARM: dts: bcm6846: Add interrupt to RNG Linus Walleij
2025-03-28 7:43 ` [PATCH 04/12] ARM: dts: bcm6855: Add BCMBCA peripherals Linus Walleij
2025-03-28 7:43 ` [PATCH 05/12] ARM: dts: bcm6878: " Linus Walleij
2025-03-28 7:43 ` [PATCH 06/12] ARM: dts: bcm63138: " Linus Walleij
2025-03-28 7:43 ` [PATCH 07/12] ARM: dts: bcm63148: " Linus Walleij
2025-03-28 7:43 ` [PATCH 08/12] ARM: dts: bcm63178: " Linus Walleij
2025-03-28 7:43 ` [PATCH 09/12] ARM64: dts: bcm4908: " Linus Walleij
2025-03-28 7:44 ` [PATCH 10/12] ARM64: dts: bcm6856: " Linus Walleij
2025-03-28 7:44 ` [PATCH 11/12] ARM64: dts: bcm6858: " Linus Walleij
2025-03-28 7:44 ` [PATCH 12/12] ARM64: dts: bcm63158: " Linus Walleij
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=20250328-bcmbca-peripherals-arm-v1-1-e4e515dc9b8c@linaro.org \
--to=linus.walleij@linaro.org \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=olivia@selenic.com \
--cc=rafal@milecki.pl \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=william.zhang@broadcom.com \
/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