Message ID | 20240515121634.23945-1-dmt.yashin@gmail.com |
---|---|
Headers | show |
Series | pinctrl: rockchip: add rk3308b SoC support | expand |
Am Dienstag, 28. Mai 2024, 14:18:35 CEST schrieb Dmitry Yashin: > Hi Heiko, > > On 5/28/24 4:52 PM, Heiko Stübner wrote: > > Hi Linus, > > > > Am Dienstag, 28. Mai 2024, 13:29:12 CEST schrieb Linus Walleij: > >> On Wed, May 15, 2024 at 2:17 PM Dmitry Yashin <dmt.yashin@gmail.com> wrote: > >> > >>> Some of the rk3308 iomux routes in rk3308_mux_route_data belong to > >>> the rk3308b SoC. Remove them and correct i2c3 routes. > >>> > >>> Fixes: 7825aeb7b208 ("pinctrl: rockchip: add rk3308 SoC support") > >>> Signed-off-by: Dmitry Yashin <dmt.yashin@gmail.com> > >> While you guys are thinking about the RK3308B support, is this fix > >> something I can just apply? > > I'd think so. I've detailed stuff in my Review mail I just sent. > > Both the soc itself and also the affected pin functions are niche > > enough that this should not cause breakage. > > > > > > Heiko > > > > > > > > Should i just drop 1/3 from V2 then? I guess just check the state of affairs once your v2 is ready ;-) . I.e. if LinusW grabs patch1 before you post v2, just drop it, otherwise send it along. > Thanks everyone for the feedback on this series. I'll prepare V2 based > on runtime chip detection with use of GRF_CHIP_ID.