PXA1908 DT changes for 6.18

Hi SoC maintainers,

Here's the first batch of PXA1908 DT changes for 6.18.

Regards,
Duje

The following changes since commit 76eeb9b8de9880ca38696b2fb56ac45ac0a25c6c:

Linux 6.17-rc5 (2025-09-07 14:22:57 -0700)

are available in the Git repository at:

https://gitlab.com/pxa1908-mainline/linux.git tags/pxa1908-dt-for-6.18

for you to fetch changes up to efab3844c6f18327886c5c2e0e40acccaf976a89:

arm64: dts: marvell: samsung,coreprimevelte: Add USB connector (2025-09-20 14:08:32 +0200)

----------------------------------------------------------------
PXA1908 DT changes for 6.18

Rollup of hardware support which has accumulated since support for the SoC and coreprimevelte board was merged. This most notably includes eMMC, PMIC, backlight and touchscreen. A few QoL fixes are also included.

----------------------------------------------------------------
Duje Mihanović (9):
arm64: dts: marvell: samsung,coreprimevelte: Add backlight
arm64: dts: marvell: samsung,coreprimevelte: Correct CD GPIO
arm64: dts: marvell: samsung,coreprimevelte: Enable eMMC
arm64: dts: marvell: pxa1908: Add PWMs
arm64: dts: marvell: samsung,coreprimevelte: Add vibrator
arm64: dts: marvell: pxa1908: Move ramoops to SoC dtsi
arm64: dts: marvell: samsung,coreprimevelte: Drop some reserved memory
arm64: dts: marvell: samsung,coreprimevelte: Fill in memory node
arm64: dts: marvell: samsung,coreprimevelte: Add USB connector

Karel Balej (3):
arm64: dts: samsung,coreprimevelte: add PMIC
arm64: dts: samsung,coreprimevelte: add touchscreen
arm64: dts: samsung,coreprimevelte: add SDIO

 .../marvell/mmp/pxa1908-samsung-coreprimevelte.dts | 266 ++++++++++++++++++---
 arch/arm64/boot/dts/marvell/mmp/pxa1908.dtsi       |  46 ++++
 2 files changed, 278 insertions(+), 34 deletions(-)

Hi Duje,

It's really late since there are only a few days left before the merge window, and you unfortunately based this on -rc5. Since my branch is based on -rc4, merging your contents would backmerge all of the upstream changes and somewhat mess up the git history, which I try to avoid.

If you can send an updated pull request based on -rc1, I'll try to do find the time to merge that, otherwise please rebase on 6.18-rc1 once that is out.

Arnd

Hi Arnd,

I don't want to rush anything, I'd rather wait until after the v6.18 merge window then unless the merge itself is very trivial.

My only question then would be whether I could still target v6.18 or would that postpone the series for v6.19? I don't really mind the latter, I'd just like to know.

Regards,
--
Duje

I meant sending a pull request for 6.19 based on 6.18-rc1.

Generally speaking, I need pull requests to be based on an -rc release that is no newer than the one I'm already using in the tree, so -rc1 is what you can use to be on the safe side.

You can also send multiple pull requests during a cycle if you either want to add more contents or find bugs in the earlier patches. This way you can ensure that there is enough time to fix up mistakes if you send something at first that for some reason needs a rework.

Arnd