Re: [PATCH v4 4/4] arm64: dts: S32G3: Introduce device tree for S32G-VNP-RDB3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/25/24 15:26, Wadim Mueller wrote:
> On Mon, Mar 25, 2024 at 11:30:38AM +0200, Ghennadi Procopciuc wrote:
>> On 3/24/24 23:43, Wadim Mueller wrote:
>>> This commit adds device tree support for the NXP S32G3-based
>>> S32G-VNP-RDB3 Board [1].
>>>
>>> The S32G3 features an 8-core ARM Cortex-A53 based SoC developed by NXP.
>>>
>>> The device tree files are derived from the official NXP downstream
>>> Linux tree [2].
>>>
>>> This addition encompasses a limited selection of peripherals that
>>> are upstream-supported. Apart from the ARM System Modules
>>> (GIC, Generic Timer, etc.), the following IPs have been validated:
>>>
>>>     * UART: fsl-linflexuart
>>>     * SDHC: fsl-imx-esdhc
>>>
>>> Clock settings for the chip rely on ATF Firmware [3].
>>> Pin control integration into the device tree is pending and currently
>>> relies on Firmware/U-Boot settings [4].
>>>
>>> These changes were validated using BSP39 Firmware/U-Boot from NXP [5].
>>>
>>> The modifications enable booting the official Ubuntu 22.04 from NXP on
>>> the RDB3 with default settings from the SD card and eMMC.
>>>
>>> [1] https://www.nxp.com/design/design-center/designs/s32g3-vehicle-networking-reference-design:S32G-VNP-RDB3
>>> [2] https://github.com/nxp-auto-linux/linux
>>> [3] https://github.com/nxp-auto-linux/arm-trusted-firmware
>>> [4] https://github.com/nxp-auto-linux/u-boot
>>> [5] https://github.com/nxp-auto-linux/auto_yocto_bsp
>>>
>>> Signed-off-by: Wadim Mueller <wafgo01@xxxxxxxxx>
>>> ---
>>
>> Thank you, Wadim, for bringing up the S32G3RDB3 board! The board boots
>> with all 8 cores. The log is attached below.
>>
> 
> Thanks for testing Ghennadi, much appreciated. 
> 
> According to MAINTAINERS all "dts/freescale/" DTS files
> needs to go through the IMX/MXC tree? 
> Is my understanding correct? Just asking whether I understand the file
> content correctly!
> 

Indeed, everything should go through the IMX tree.
Here [0] you can find a long discussion about this.

[0]
https://lore.kernel.org/linux-arm-kernel/a5f7b53a-6b44-4f0b-83f2-b055b8aa3b2d@xxxxxxxx/

Regards,
Ghennadi





[Index of Archives]     [Linux Memonry Technology]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux