linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Michael Walle <mwalle@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
	linux-watchdog@vger.kernel.org, Andrew Davis <afd@ti.com>,
	Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Srinivas Kandagatla <srini@kernel.org>,
	Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: Re: [PATCH v2 0/7] Initial Kontron SMARC-sAM67 support
Date: Thu, 25 Sep 2025 12:34:15 +0100	[thread overview]
Message-ID: <20250925113415.GD8757@google.com> (raw)
In-Reply-To: <DD1PD807DBY9.2FY81JFZ6EDAE@kernel.org>

On Thu, 25 Sep 2025, Michael Walle wrote:

> Hi Lee,
> 
> On Fri Sep 12, 2025 at 2:07 PM CEST, Michael Walle wrote:
> > Now that the PMIC support is there, we can finally, upstream the
> > support for this board. Besides the usual device tree, this
> > patchset contains the support for the on-board house keeping MCU. It
> > make extensive reuse of the drivers for the former SMARC-sAL28
> > board. Besides different hwmon sensors, all the dt binding patches
> > will just add a board specific compatible (in addition to the old
> > sl28 compatible) to make any future board specific quirks possible.
> >
> > I'm aware that there is a patch [1] which moves the sl28cpld MFD
> > schema to a different directory. Once that patch is merged, I'll
> > repost this series. But I already want to get some early feedback.
> >
> > v2:
> >  - dropped patches which were already picked up
> >  - new patch "dt-bindings: mfd: tps6594: allow gpio-line-names"
> >  - separate driver for the hwmon, add missing hwmon documentation,
> >    thanks Guenter
> >  - split the DT as suggested by the SoC maintainers
> >  - add missing copyright and license to the overlays, thanks Andrew
> >
> > Michael Walle (7):
> >   dt-bindings: arm: ti: Add Kontron SMARC-sAM67 module
> >   dt-bindings: mfd: tps6594: allow gpio-line-names
> >   arm64: dts: ti: Add support for Kontron SMARC-sAM67
> >   dt-bindings: hwmon: sl28cpld: add sa67mcu compatible
> >   dt-bindings: watchdog: add SMARC-sAM67 support
> >   hwmon: add SMARC-sAM67 support
> >   arm64: dts: ti: sa67: add on-board management controller node
> 
> Would you take these two patches
>     dt-bindings: mfd: tps6594: allow gpio-line-names
>     dt-bindings: watchdog: add SMARC-sAM67 support
> 
> through the MFD tree this cycle? If they make it in, there wouldn't
> be any more dependencies for the next cycle for the actual device
> tree.

Applied both, thanks.

-- 
Lee Jones [李琼斯]

      reply	other threads:[~2025-09-25 11:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 12:07 [PATCH v2 0/7] Initial Kontron SMARC-sAM67 support Michael Walle
2025-09-12 12:07 ` [PATCH v2 1/7] dt-bindings: arm: ti: Add Kontron SMARC-sAM67 module Michael Walle
2025-09-12 12:07 ` [PATCH v2 2/7] dt-bindings: mfd: tps6594: allow gpio-line-names Michael Walle
2025-09-15 21:34   ` Rob Herring (Arm)
2025-09-12 12:07 ` [PATCH v2 3/7] arm64: dts: ti: Add support for Kontron SMARC-sAM67 Michael Walle
2025-09-12 12:07 ` [PATCH v2 4/7] dt-bindings: hwmon: sl28cpld: add sa67mcu compatible Michael Walle
2025-09-24 16:00   ` Guenter Roeck
2025-09-12 12:07 ` [PATCH v2 5/7] dt-bindings: watchdog: add SMARC-sAM67 support Michael Walle
2025-09-24 15:59   ` Guenter Roeck
2025-09-12 12:07 ` [PATCH v2 6/7] hwmon: " Michael Walle
2025-09-24 16:01   ` Guenter Roeck
2025-09-12 12:07 ` [PATCH v2 7/7] arm64: dts: ti: sa67: add on-board management controller node Michael Walle
2025-09-25  7:28 ` [PATCH v2 0/7] Initial Kontron SMARC-sAM67 support Michael Walle
2025-09-25 11:34   ` Lee Jones [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=20250925113415.GD8757@google.com \
    --to=lee@kernel.org \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mwalle@kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=srini@kernel.org \
    --cc=vigneshr@ti.com \
    --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).