Re: [PATCH v1 0/7] Initial Kontron SMARC-sAM67 support

["Michael Walle" <mwalle@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 2306 bytes --]

On Fri Aug 22, 2025 at 5:23 PM CEST, Nishanth Menon wrote:
> 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?

Not sure, if this needs an IB anyway or if the DTS can be pulled by
the corresponding SoC subsys and the DT binding can go through
another tree in the same cycle. If not, I can certainly split the
device tree (to my knowledge, it was said that it should be a
complete description :).

I'd expect that Lee is picking up the first 6 patches after they got
an ACK. Please correct me if I'm wrong, Lee.

In any case, I'd give this v1 some time to get some feedback on the
patches.

-michael

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]