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" <hsin-hsiung.w...@mediatek.com> > An: "Frank Wunderlich" <fran...@public-files.de>, "Matthias Brugger" > <matthias....@gmail.com> > Cc: linux-media...@lists.infradead.org, "Mark Rutland" > <mark.rutl...@arm.com>, "Alessandro Zummo" <a.zu...@towertech.it>, "Alexandre > Belloni" <alexandre.bell...@bootlin.com>, srv_heupstr...@mediatek.com, > devicet...@vger.kernel.org, "Greg Kroah-Hartman" > <gre...@linuxfoundation.org>, "Sean Wang" <sean.w...@mediatek.com>, "Liam > Girdwood" <lgirdw...@gmail.com>, "Rob Herring" <robh...@kernel.org>, > linux-kernel@vger.kernel.org, "Richard Fontana" <rfont...@redhat.com>, "Mark > Brown" <broo...@kernel.org>, linux-arm-ker...@lists.infradead.org, "René van > Dorst" <opensou...@vdorst.com>, "Thomas Gleixner" <t...@linutronix.de>, > "Eddie Huang" <eddie.hu...@mediatek.com>, "Lee Jones" <lee.jo...@linaro.org>, > "Kate Stewart" <kstew...@linuxfoundation.org>, linux-...@vger.kernel.org > 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" <matthias....@gmail.com> > > > > > 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. > >
