summaryrefslogtreecommitdiff
path: root/scripts/bpf_helpers_doc.py
diff options
context:
space:
mode:
authorStephen Boyd <swboyd@chromium.org>2020-01-24 08:58:46 +0300
committerThomas Gleixner <tglx@linutronix.de>2020-01-24 23:00:20 +0300
commitc79108bd19a8490315847e0c95ac6526fcd8e770 (patch)
treecf4e052720b13762b461e2e287eaa3d1d86256d8 /scripts/bpf_helpers_doc.py
parent6b088cefbeaa87ba48bf838edfc1e19c9ff3976b (diff)
downloadlinux-c79108bd19a8490315847e0c95ac6526fcd8e770.tar.xz
alarmtimer: Make alarmtimer platform device child of RTC device
The alarmtimer_suspend() function will fail if an RTC device is on a bus such as SPI or i2c and that RTC device registers and probes after alarmtimer_init() registers and probes the 'alarmtimer' platform device. This is because system wide suspend suspends devices in the reverse order of their probe. When alarmtimer_suspend() attempts to program the RTC for a wakeup it will try to program an RTC device on a bus that has already been suspended. Move the alarmtimer device registration to happen when the RTC which is used for wakeup is registered. Register the 'alarmtimer' platform device as a child of the RTC device too, so that it can be guaranteed that the RTC device won't be suspended when alarmtimer_suspend() is called. Reported-by: Douglas Anderson <dianders@chromium.org> Signed-off-by: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Douglas Anderson <dianders@chromium.org> Link: https://lore.kernel.org/r/20200124055849.154411-2-swboyd@chromium.org
Diffstat (limited to 'scripts/bpf_helpers_doc.py')
0 files changed, 0 insertions, 0 deletions