Message ID | 20240408181429.3676856-1-jonas@kwiboo.se |
---|---|
Headers | show |
Series | rockchip: rk3308: Sync DT with linux v6.8 and update defconfigs | expand |
On Mon, Apr 08, 2024 at 06:13:57PM +0000, Jonas Karlman wrote: > This series adds support for new clocks used in linux v6.8 device trees, > enables use of FIT signature check for checksum validation and fixes > loading FIT from SD-card when loading FIT from eMMC fails. > > It should be possible to move RK3308 boards to use OF_UPSTREAM in a > future series after this has been applied. > > I have runtime tested this series on a Radxa ROCK Pi S v1.3 having a > RK3308B SoC. Following was tested and now working after this: SD-card, > eMMC (SD NAND), Ethernet, USB host and USB gadget (RockUSB and UMS). > > Changes in v2: > - Add clocks and resets props to otp node > - Add bootph-some-ram to emmc and sdmmc pinctrl nodes > - Sort bootph-all prop after compatible and reg props > - Fix rk3308-evb debug uart > - New patch to move cru and grf include files to arch-rockchip Sorry if I missed the answer in v1, but why aren't we switching to OF_UPSTREAM here, which is also on v6.8 currently? Thanks.
Hi Tom, On 2024-04-08 21:38, Tom Rini wrote: > On Mon, Apr 08, 2024 at 06:13:57PM +0000, Jonas Karlman wrote: >> This series adds support for new clocks used in linux v6.8 device trees, >> enables use of FIT signature check for checksum validation and fixes >> loading FIT from SD-card when loading FIT from eMMC fails. >> >> It should be possible to move RK3308 boards to use OF_UPSTREAM in a >> future series after this has been applied. >> >> I have runtime tested this series on a Radxa ROCK Pi S v1.3 having a >> RK3308B SoC. Following was tested and now working after this: SD-card, >> eMMC (SD NAND), Ethernet, USB host and USB gadget (RockUSB and UMS). >> >> Changes in v2: >> - Add clocks and resets props to otp node >> - Add bootph-some-ram to emmc and sdmmc pinctrl nodes >> - Sort bootph-all prop after compatible and reg props >> - Fix rk3308-evb debug uart >> - New patch to move cru and grf include files to arch-rockchip > > Sorry if I missed the answer in v1, but why aren't we switching to > OF_UPSTREAM here, which is also on v6.8 currently? Thanks. > I would like to keep the switch to OF_UPSTREAM in a separate series because of reviewability, some of the device tree files has not been updated since v5.5-rc1, also I would like to have the option of cherry-picking these patches to e.g. a 2024.04 branch. What is the expected update cadence on OF_UPSTREAM, will there be an update to v6.9 before v2024.07 or will U-Boot be one version behind linux at release time? Regards, Jonas
On Mon, Apr 08, 2024 at 09:55:59PM +0200, Jonas Karlman wrote: > Hi Tom, > > On 2024-04-08 21:38, Tom Rini wrote: > > On Mon, Apr 08, 2024 at 06:13:57PM +0000, Jonas Karlman wrote: > >> This series adds support for new clocks used in linux v6.8 device trees, > >> enables use of FIT signature check for checksum validation and fixes > >> loading FIT from SD-card when loading FIT from eMMC fails. > >> > >> It should be possible to move RK3308 boards to use OF_UPSTREAM in a > >> future series after this has been applied. > >> > >> I have runtime tested this series on a Radxa ROCK Pi S v1.3 having a > >> RK3308B SoC. Following was tested and now working after this: SD-card, > >> eMMC (SD NAND), Ethernet, USB host and USB gadget (RockUSB and UMS). > >> > >> Changes in v2: > >> - Add clocks and resets props to otp node > >> - Add bootph-some-ram to emmc and sdmmc pinctrl nodes > >> - Sort bootph-all prop after compatible and reg props > >> - Fix rk3308-evb debug uart > >> - New patch to move cru and grf include files to arch-rockchip > > > > Sorry if I missed the answer in v1, but why aren't we switching to > > OF_UPSTREAM here, which is also on v6.8 currently? Thanks. > > > > I would like to keep the switch to OF_UPSTREAM in a separate series > because of reviewability, some of the device tree files has not been > updated since v5.5-rc1, also I would like to have the option of > cherry-picking these patches to e.g. a 2024.04 branch. > > What is the expected update cadence on OF_UPSTREAM, will there be an > update to v6.9 before v2024.07 or will U-Boot be one version behind > linux at release time? If v6.9 comes out before I open the next branch, yes, it will be in v2024.07 otherwise no. I have to double check my emails before repeating if it's rc2 or rc3 I'm trying to regularly do that with, and then update doc/develop/release_cycle.rst to list it clearly.