linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>, <wim@linux-watchdog.org>,
	<linux@roeck-us.net>
Cc: <vkoul@kernel.org>, <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 v2 0/2] Add System Components for Microchip SAMA7D65 SoC
Date: Fri, 28 Feb 2025 08:24:09 -0700	[thread overview]
Message-ID: <cover.1740675317.git.Ryan.Wanner@microchip.com> (raw)

From: Ryan Wanner <Ryan.Wanner@microchip.com>

This patch set adds support for the following systems in the SAMA7D65
SoC:
- DMAs
- Chip ID
- Dual watchdog timer.

Changes v1 -> v2:
- Removed pathes that have been accepted and applied from v1 [1].
- Corrected missing newline in dt-binding.
- Corrected mismatch in watchdog dt node.

1) https://lore.kernel.org/linux-arm-kernel/09eafe54-c262-4db4-b11d-0644a1f90a14@tuxon.dev/

Ryan Wanner (2):
  dt-bindings: watchdog: sama5d4-wdt: Add sama7d65-wdt
  ARM: dts: microchip: sama7d65: Add watchdog for sama7d65

 .../devicetree/bindings/watchdog/atmel,sama5d4-wdt.yaml    | 4 ++++
 arch/arm/boot/dts/microchip/sama7d65.dtsi                  | 7 +++++++
 2 files changed, 11 insertions(+)

-- 
2.43.0


             reply	other threads:[~2025-02-28 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 15:24 Ryan.Wanner [this message]
2025-02-28 15:24 ` [PATCH v2 1/2] dt-bindings: watchdog: sama5d4-wdt: Add sama7d65-wdt Ryan.Wanner
2025-02-28 18:17   ` Conor Dooley
2025-02-28 15:24 ` [PATCH v2 2/2] ARM: dts: microchip: sama7d65: Add watchdog for sama7d65 Ryan.Wanner
2025-03-03 13:14 ` [PATCH v2 0/2] Add System Components for Microchip SAMA7D65 SoC Rob Herring (Arm)
2025-03-03 18:56 ` 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=cover.1740675317.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;
as well as URLs for NNTP newsgroup(s).