Hi, bug is still present in 5.4-rc1
dmesg prints this line and at least switch is not inialized on bananapi-r2 mt6397 1000d000.pwrap:mt6323: unsupported chip: 0x0 regards Frank > Gesendet: Donnerstag, 29. August 2019 um 08:24 Uhr > Von: "Hsin-hsiung Wang" <[email protected]> > An: "Frank Wunderlich" <[email protected]>, "Matthias Brugger" > <[email protected]> > Cc: [email protected], "Mark Rutland" > <[email protected]>, "Alessandro Zummo" <[email protected]>, "Alexandre > Belloni" <[email protected]>, [email protected], > [email protected], "Greg Kroah-Hartman" > <[email protected]>, "Sean Wang" <[email protected]>, "Liam > Girdwood" <[email protected]>, "Rob Herring" <[email protected]>, > [email protected], "Richard Fontana" <[email protected]>, "Mark > Brown" <[email protected]>, [email protected], "René van > Dorst" <[email protected]>, "Thomas Gleixner" <[email protected]>, > "Eddie Huang" <[email protected]>, "Lee Jones" <[email protected]>, > "Kate Stewart" <[email protected]>, [email protected] > Betreff: Re: Aw: Re: [BUG] [PATCH v5 02/10] mfd: mt6397: extract irq related > code from core driver > > Hi Frank/Matthias, > > On Fri, 2019-08-23 at 19:16 +0200, Frank Wunderlich wrote: > > > Gesendet: Freitag, 23. August 2019 um 17:42 Uhr > > > Von: "Matthias Brugger" <[email protected]> > > > > > I suppose that's because 3/10 has code that should be in 2/10 and for some > > > reason 3/10 was not pushed for linux-next inclusion. Although it has the > > > same > > > Acked-for-mfd-by tag. > > > > > > @Frank, can you test if adding 3/10 to your code base fixes the issue? > > > > adding part 3 [1] seems to fix the issue too > > > > [ 4.960051] mt6323-regulator mt6323-regulator: Chip ID = 0x2023 > > > > thanks > > > > [1] https://patchwork.kernel.org/patch/11110509/ > Thanks for your comments. > The root cause seems I didn't split the code well. > I will fix it in the next version. > >
