From: <Ryan.Wanner@microchip.com>
To: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<claudiu.beznea@tuxon.dev>, <vkoul@kernel.org>,
<wim@linux-watchdog.org>, <linux@roeck-us.net>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<linux-watchdog@vger.kernel.org>,
Ryan Wanner <Ryan.Wanner@microchip.com>
Subject: [PATCH 1/8] dt-bindings: atmel-sysreg: Add SAMA7D65 Chip ID
Date: Fri, 14 Feb 2025 11:08:14 -0700 [thread overview]
Message-ID: <008e4e49c9fd315cc96a185662b31eca1a64a614.1739555984.git.Ryan.Wanner@microchip.com> (raw)
In-Reply-To: <cover.1739555984.git.Ryan.Wanner@microchip.com>
From: Ryan Wanner <Ryan.Wanner@microchip.com>
Add compatible string for SAMA7D65 SoC ChipID dt-bindings.
Signed-off-by: Ryan Wanner <Ryan.Wanner@microchip.com>
---
Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
index 1a173e92bb137..d3821f651e728 100644
--- a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
+++ b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
@@ -2,6 +2,7 @@ Atmel system registers
Chipid required properties:
- compatible: Should be "atmel,sama5d2-chipid" or "microchip,sama7g5-chipid"
+ "microchip,sama7d65-chipid"
- reg : Should contain registers location and length
PIT Timer required properties:
--
2.43.0
next prev parent reply other threads:[~2025-02-14 18:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 18:08 [PATCH 0/8] Add System Components for Microchip SAMA7D65 SoC Ryan.Wanner
2025-02-14 18:08 ` Ryan.Wanner [this message]
2025-02-19 22:59 ` [PATCH 1/8] dt-bindings: atmel-sysreg: Add SAMA7D65 Chip ID Rob Herring
2025-02-14 18:08 ` [PATCH 2/8] dt-bindings: watchdog: sama5d4-wdt: Add sama7d65-wdt Ryan.Wanner
2025-02-18 8:42 ` Claudiu Beznea
2025-02-19 22:59 ` Rob Herring
2025-02-14 18:08 ` [PATCH 3/8] dt-bindings: dma: atmel: add microchip,sama7d65-dma Ryan.Wanner
2025-02-19 23:00 ` Rob Herring (Arm)
2025-02-14 18:08 ` [PATCH 4/8] ARM: at91: Add Support in SoC driver for SAMA7D65 Ryan.Wanner
2025-02-14 18:08 ` [PATCH 5/8] ARM: dts: microchip: sama7d65: Add chipID for sama7d65 Ryan.Wanner
2025-02-14 18:08 ` [PATCH 6/8] ARM: dts: microchip: sama7d65: Add watchdog " Ryan.Wanner
2025-02-24 11:43 ` Claudiu Beznea
2025-02-14 18:08 ` [PATCH 7/8] ARM: dts: microchip: sama7d65: Add DMAs to sama7d65 SoC Ryan.Wanner
2025-02-18 8:41 ` Claudiu Beznea
2025-02-14 18:08 ` [PATCH 8/8] ARM: dts: microchip: sama7d65: Enable DMAs Ryan.Wanner
2025-02-18 8:45 ` [PATCH 0/8] Add System Components for Microchip SAMA7D65 SoC Claudiu Beznea
2025-02-19 0:42 ` Rob Herring (Arm)
2025-02-25 16:33 ` Claudiu Beznea
2025-02-27 12:07 ` (subset) " Vinod Koul
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=008e4e49c9fd315cc96a185662b31eca1a64a614.1739555984.git.Ryan.Wanner@microchip.com \
--to=ryan.wanner@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.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@kernel.org \
--cc=vkoul@kernel.org \
--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
all inboxes | Powered by JetHome®