[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176192142805.427883.17050945919190775595.b4-ty@ti.com>
Date: Fri, 31 Oct 2025 20:10:56 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>, Rob Herring
<robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Michael Walle <mwalle@...nel.org>
CC: Vignesh Raghavendra <vigneshr@...com>,
<linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/3] Initial Kontron SMARC-sAM67 support
Hi Michael Walle,
On Fri, 17 Oct 2025 15:50:43 +0200, Michael Walle wrote:
> This series contains the remaining (device tree) patches for the
> Kontron SMARC-sAM67 module.
>
> v3:
> - dropped all patches which were already applied
> - add 'bootph-all' to the usb ctrl node to support DFU boot
> - as all MFD bits are now merged, combine the patch which added the
> system controller node into the main one again
> - drop duplicate RTC node. This one was a left over before the rtc
> node moved into it's own overlay
> - add a new overlay for the Kontron SMARC 2.2 evaluation carrier
> - add a new SMARC gpio overlay to configure the pinmux correct.
> This is not integrated into the default device tree because it
> will conflict with any device tree which will use the pins for
> different purposes (they are multi function pins)
>
> [...]
I have applied the following to branch ti-next on [1].
Thank you!
[1/3] dt-bindings: arm: ti: Add Kontron SMARC-sAM67 module
commit: 22e1d0d8cda783bee95de578cbda3ad0da8a3eb4
[2/3] arm64: dts: ti: Add support for Kontron SMARC-sAM67
commit: 1c3c4df06f9dee41bff60b93d9f0e67500f798f7
[3/3] arm64: dts: ti: sa67: add overlay for the ADS2 carrier
commit: 0114330e7f92ae4f643fca62e6004631018f48d0
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh
Powered by blists - more mailing lists