Hi, On 2025-03-13 10:01, Chukun Pan wrote: > Hi, > >> I have not seen any issue with PWM using the merged patch having >> pinctrl-names=default. >> >> Please see my Linux tree [1] and U-Boot tree [2], those are little ahead >> of what has been posted on ML, e.g. it has working USB2.0 host, CPU opp, >> Hantro VPU, GPU + opp, arm and logic pwm regulators for E20C, ROCK 2A/2F >> and Sige1. >> >> Please see my Linux tree [1] and U-Boot tree [2], those are little ahead >> of what has been posted on ML, e.g. it has working USB2.0 host, CPU opp, >> Hantro VPU, GPU + opp, arm and logic pwm regulators for E20C, ROCK 2A/2F >> and Sige1. >> ... >> [1] https://github.com/Kwiboo/linux-rockchip/commits/next-20250311-rk3528/ >> [2] https://source.denx.de/u-boot/contributors/kwiboo/u-boot/-/commits/rk3528 > > I tested your kernel device tree on E20C earlier today and still have > the same issue. But if I replace u-boot with the link [2] you provided, > it will work fine. For reference, I was using v2025.01 plus this series > of patches [3]. So it looks like u-boot does something and kernel doesn't? Interesting, good that it works with the updated U-Boot. Main change compared to v1 is that it now use clock/reset id and DT closer to what has been merged in mainline Linux. It also has DT params to help initialize the two pwm regulators used by these boards. I will try with the old v1 U-Boot series and see if I can replicated your issue. Regards, Jonas > > [3] https://lore.kernel.org/u-boot/20250123224844.3104592-1-jonas@xxxxxxxxx/ > > Thanks, > Chukun > > -- > 2.25.1 >
