[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250822152313.vjzjtzik2q5ek5kq@sadly>
Date: Fri, 22 Aug 2025 10:23:13 -0500
From: Nishanth Menon <nm@...com>
To: Michael Walle <mwalle@...nel.org>
CC: Vignesh Raghavendra <vigneshr@...com>, Tero Kristo <kristo@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Jean Delvare <jdelvare@...e.com>,
Guenter
Roeck <linux@...ck-us.net>, Lee Jones <lee@...nel.org>,
Srinivas Kandagatla
<srini@...nel.org>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
<linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-hwmon@...r.kernel.org>,
<linux-watchdog@...r.kernel.org>
Subject: Re: [PATCH v1 0/7] Initial Kontron SMARC-sAM67 support
On 15:15-20250822, 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.
>
> [1] https://lore.kernel.org/r/20250822075712.27314-2-krzysztof.kozlowski@linaro.org/
>
> Michael Walle (7):
> dt-bindings: arm: ti: Add bindings for Kontron SMARC-sAM67 module
> dt-bindings: mfd: sl28cpld: add sa67mcu compatible
> dt-bindings: hwmon: sl28cpld: add sa67mcu compatible
> dt-bindings: watchdog: add SMARC-sAM67 support
> dt-bindings: nvmem: sl28cpld: add sa67mcu compatible
> hwmon: sl28cpld: add SMARC-sAM67 support
> arm64: dts: ti: Add support for Kontron SMARC-sAM67
Since this goes through multiple maintainers, may I suggest the
following strategy?
for this window:
* send dts and board binding changes dropping the nodes that are yet to
be upstream
* send the compatible changes to each of the maintainers
Next window:
* add the nodes based on acceptance of the driver bindings
This removes multiple maintainers needing to give me immutable tags etc.
What do you think?
>
> .../devicetree/bindings/arm/ti/k3.yaml | 1 +
> .../hwmon/kontron,sl28cpld-hwmon.yaml | 1 +
> .../bindings/mfd/kontron,sl28cpld.yaml | 7 +-
> .../nvmem/layouts/kontron,sl28-vpd.yaml | 7 +-
> .../watchdog/kontron,sl28cpld-wdt.yaml | 7 +-
> arch/arm64/boot/dts/ti/Makefile | 6 +
> .../dts/ti/k3-am67a-kontron-sa67-base.dts | 1092 +++++++++++++++++
> .../dts/ti/k3-am67a-kontron-sa67-gbe1.dtso | 19 +
> .../ti/k3-am67a-kontron-sa67-rtc-rv8263.dtso | 24 +
> drivers/hwmon/sl28cpld-hwmon.c | 76 +-
> 10 files changed, 1234 insertions(+), 6 deletions(-)
> create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-base.dts
> create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-gbe1.dtso
> create mode 100644 arch/arm64/boot/dts/ti/k3-am67a-kontron-sa67-rtc-rv8263.dtso
>
> --
> 2.39.5
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
https://ti.com/opensource
Powered by blists - more mailing lists