diff options
| author | Tony Lindgren <tony@atomide.com> | 2020-07-03 18:07:29 +0200 |
|---|---|---|
| committer | Tony Lindgren <tony@atomide.com> | 2020-08-24 07:38:32 +0200 |
| commit | 2152fbbd47c06c4f50ad265ec1b0c43673bee3e8 (patch) | |
| tree | c5906fa570160bd33c6d16ce46f206882efdbe5c /include | |
| parent | Linux 5.9-rc1 (diff) | |
| download | linux-2152fbbd47c06c4f50ad265ec1b0c43673bee3e8.tar.xz linux-2152fbbd47c06c4f50ad265ec1b0c43673bee3e8.zip | |
soc: ti: pm33xx: Simplify RTC usage to prepare to drop platform data
We must re-enable the RTC module clock enabled in RTC+DDR suspend, and
pm33xx has been using platform data callbacks for that. Looks like for
retention suspend the RTC module clock must not be re-enabled.
To remove the legacy platform data callbacks, and eventually be able to
drop the RTC legacy platform data, let's manage the RTC module clock
and register range directly in pm33xx.
Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'include')
| -rw-r--r-- | include/linux/platform_data/pm33xx.h | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/include/linux/platform_data/pm33xx.h b/include/linux/platform_data/pm33xx.h index 644af1d89cfa..7037ba7a53ca 100644 --- a/include/linux/platform_data/pm33xx.h +++ b/include/linux/platform_data/pm33xx.h @@ -54,11 +54,8 @@ struct am33xx_pm_platform_data { void (*begin_suspend)(void); void (*finish_suspend)(void); struct am33xx_pm_sram_addr *(*get_sram_addrs)(void); - void __iomem *(*get_rtc_base_addr)(void); void (*save_context)(void); void (*restore_context)(void); - void (*prepare_rtc_suspend)(void); - void (*prepare_rtc_resume)(void); int (*check_off_mode_enable)(void); }; |