[BUG] 6.2-rc1 spi-mt65xx broken on mt7986

[Ricardo Ribalda]

Hi Thorsten

I replied on my phone, so the mail came out in html and the list did
not pick it up, then Frank also answered in html.

I believe we are good with this:
https://lore.kernel.org/all/Y7WOlkuLaLt1DdY+@sirena.org.uk/

Thanks for headsup anyway

Regards!

On Thu, 5 Jan 2023 at 13:21, Thorsten Leemhuis
<regressions at leemhuis.info> wrote:
>
> [CCing the regression mailing list, as it should be in the loop:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>
> On 27.12.22 11:28, Frank Wunderlich wrote:
> > Hi,
> >
> > the following commit breaks SPIM-NOR on mt7986:
> >
> > c6f7874687f7 2022-11-28 spi: mediatek: Enable irq when pdata is ready
>
> Ricardo, do you have this report on your radar? Just wondering, as it
> was posted a week ago and didn't even get a single reply afaics. This of
> course can happen at this time of the year, but I thought a quick status
> inquiry wouldn't hurt.
>
> >> [    2.145931] pc : mtk_spi_can_dma+0x0/0x34
> >> [    2.155212] lr : mtk_spi_interrupt+0x74/0x360
> >>
> >> [    2.091801] mtk-spi 1100a000.spi: spi-mem transfer timeout
> >> [    2.097310] spi-nor: probe of spi0.0 failed with error -110
> >> [    2.102930] Unable to handle kernel read from unreadable memory at virtual address 0000000000000010
> >
> > after reverting the commit, no trace happens and nor is recognized on my board
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
>
> #regzbot poke



-- 
Ricardo Ribalda