* Peter Ujfalusi <peter.ujfalusi@xxxxxx> [181210 16:13]: > Tony, > > On 10/12/2018 17.44, Tony Lindgren wrote: > > * Tony Lindgren <tony@xxxxxxxxxxx> [181210 14:49]: > >> * Peter Ujfalusi <peter.ujfalusi@xxxxxx> [181210 09:52]: > >>> On 10/12/2018 9.05, Peter Ujfalusi wrote: > >>>> Works fine on bbb + audio cape. > >>>> For some reason my am335x-evm-sk is not booting up at all w/ linux-next, > >>>> but I believe it is not related to this (disabled audio and still not > >>>> booting). > >>> > >>> bisect on next-20181207 (am335x-evm-sk) points to: > >>> Author: Tony Lindgren <tony@xxxxxxxxxxx> > >>> 87fc89ced3a78f7f0845afab1934d509ef4ad0f2 > >>> ARM: dts: am335x: Move l4 child devices to probe them with ti-sysc > >>> > >>> when looking for the non booting of am335x-evm-sk (nothing printed on > >>> serial after stating kernel). > >> > >> OK I'm pretty sure this is because we now need to move the gpio1 > >> ti,no-reset-on-init up to the module level because of the DDR being > >> GPIO controlled. I'll send a patch out shortly for that. > >> > >> It might be also worth adding a check for having ti,no-reset-on-init > >> at the child level to ti-sysc driver too. > > > > Looks like we have quite a few boards variants with probably > > DDR powered by a gpio1 pin. So let's fix the ti-sysc driver first, > > care to try the following patch? > > am335x-evmsk is still not booting with this patch on top of next-20181210. Oh interesting. > Fwiw 'git grep ti,no-reset-on-idle' yields no results... > Where it should be? Sorry it should be ti,no-reset-on-init. Regards, Tony
