From: Claudiu Beznea <claudiu.beznea@microchip.com>
To: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <nicolas.ferre@microchip.com>,
<alexandre.belloni@bootlin.com>, <daniel.lezcano@linaro.org>,
<tglx@linutronix.de>, <wim@linux-watchdog.org>,
<linux@roeck-us.net>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-watchdog@vger.kernel.org>,
"Claudiu Beznea" <claudiu.beznea@microchip.com>
Subject: [PATCH v2 1/4] ARM: dts: at91: sama7g5: keep only microchip,sam9x60-pit64b compatible for pit64b
Date: Mon, 29 May 2023 09:26:01 +0300 [thread overview]
Message-ID: <20230529062604.1498052-2-claudiu.beznea@microchip.com> (raw)
In-Reply-To: <20230529062604.1498052-1-claudiu.beznea@microchip.com>
SAM9X60 and SAMA7G5 PIT64Bs are 1 to 1 compatible. Thus, there is no
need for specific compatible string on SAMA7G5.
Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
---
arch/arm/boot/dts/sama7g5.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/sama7g5.dtsi b/arch/arm/boot/dts/sama7g5.dtsi
index 886b6209a71e..500b00508621 100644
--- a/arch/arm/boot/dts/sama7g5.dtsi
+++ b/arch/arm/boot/dts/sama7g5.dtsi
@@ -610,7 +610,7 @@ eic: interrupt-controller@e1628000 {
};
pit64b0: timer@e1800000 {
- compatible = "microchip,sama7g5-pit64b", "microchip,sam9x60-pit64b";
+ compatible = "microchip,sam9x60-pit64b";
reg = <0xe1800000 0x4000>;
interrupts = <GIC_SPI 70 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&pmc PMC_TYPE_PERIPHERAL 70>, <&pmc PMC_TYPE_GCK 70>;
@@ -618,7 +618,7 @@ pit64b0: timer@e1800000 {
};
pit64b1: timer@e1804000 {
- compatible = "microchip,sama7g5-pit64b", "microchip,sam9x60-pit64b";
+ compatible = "microchip,sam9x60-pit64b";
reg = <0xe1804000 0x4000>;
interrupts = <GIC_SPI 71 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&pmc PMC_TYPE_PERIPHERAL 71>, <&pmc PMC_TYPE_GCK 71>;
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-29 6:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 6:26 [PATCH v2 0/4] dt-bindings: timer: Microchip AT91 convert to YAML Claudiu Beznea
2023-05-29 6:26 ` Claudiu Beznea [this message]
2023-05-29 12:12 ` [PATCH v2 1/4] ARM: dts: at91: sama7g5: keep only microchip,sam9x60-pit64b compatible for pit64b Conor Dooley
2023-05-29 6:26 ` [PATCH v2 2/4] dt-bindings: timer: atmel,at91sam9260-pit: convert to yaml Claudiu Beznea
2023-05-29 12:17 ` Conor Dooley
2023-05-29 12:32 ` Claudiu.Beznea
2023-05-29 12:48 ` Conor Dooley
2023-05-29 6:26 ` [PATCH v2 3/4] dt-bindings: watchdog: atmel,at91rm9200-wdt: " Claudiu Beznea
2023-05-29 12:21 ` Conor Dooley
2023-05-29 6:26 ` [PATCH v2 4/4] dt-bindings: timer: atmel,at91rm9200-st: " Claudiu Beznea
2023-05-29 12:24 ` Conor Dooley
2023-05-29 12:34 ` 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=20230529062604.1498052-2-claudiu.beznea@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--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=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=wim@linux-watchdog.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