Hi Wolfram,
On Thu, Jun 25, 2020 at 9:06 AM Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote:
> ...
>
> > After removing that check, it starts complaining:
> >
> > BUG: sleeping function called from invalid context at
> > kernel/locking/mutex.c:281
> > in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 1, name:
> > systemd-shutdow
> >
> > In general, pm_runtime_get_sync() is not safe to call from atomic
> > context.
> > For Renesas SoCs, I think both the power and clock domains are safe, as
> > the respective drivers don't sleep. The PM core might, though.
>
> Still, that sounds to me like we should protect these calls as in V1?
And talk to the i2c controller while it is disabled?
That does seem to work on R-Car Gen2 (similar to SMP bringup accessing
registers of a disabled WDT?), though.
Needs testing on R-Mobile A1....
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
