On Tue, Nov 6, 2018 at 9:44 AM Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > * Grygorii Strashko <grygorii.strashko@xxxxxx> [181031 23:32]: > > > > > > On 10/29/18 5:11 PM, Adam Ford wrote: > > > On Sun, Oct 28, 2018 at 6:15 PM Adam Ford <aford173@xxxxxxxxx> wrote: > > > > > > > > On Sun, Oct 28, 2018 at 6:09 PM Adam Ford <aford173@xxxxxxxxx> wrote: > > > > > > > > > > MMCx_dat1 and serial RX pins can be associated to additional > > > > > interrupts. Enable these on AM3517-evm. > > > > > > > > > > > > > The reason, I made this an RFC, is that I think there might be some > > > > IRQ support missing in AM3517, and I am not sure where to look. > > > > > > > > During boot, I get multiple instances of the following message: > > > > > > > > irq: no irq domain found for pinmux@30 ! > > > > > > > I should also note, that the am3517 is also returning > > > > > > pm: Failed to request pm_wkup irq > > > > most probably padconf IRQs are not initialized properly. > > you could try to check pcs_probe() and PCS_FEAT_IRQ > > Those get passed to the driver in pdata-quirks.c BTW if > something is missing there. >From what I can tell, omap_pcs_legacy_init sets the pcs_pdata. It appears to get called from omap_prcm_register_chain_handler, but I am not seeing a clear different between any of the omap2plus boards. I double checked the addresses of pinmux@30 to see if it's any different between the DM37 and the AM35, and the addresses seem to match, so I don't think it's a device tree issue. adam > > Regards, > > Tony
