spi: st: fix PM macros to use CONFIG_PM instead of CONFIG_PM_SLEEP
PATCH 1/1 spi: st: fix PM macros to use CONFIG_PM instead of CONFIG_PM_SLEEP
pm_sleep_ptr() depends on CONFIG_PM_SLEEP while pm_ptr() depends on CONFIG_PM. Since ST SSC4 implements runtime PM it makes sense using pm_ptr() here.
For the same reason replace PM macros that use CONFIG_PM. Doing so prevents from using __maybe_unused attribute of runtime PM functions.
--- drivers/spi/spi-st-ssc4.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/spi/spi-st-ssc4.c +5 -5
@@ -378,7 +378,7 @@ static void spi_st_remove(struct platform_device *pdev)pinctrl_pm_select_sleep_state (&pdev->dev); } -static int __maybe_unused spi_st_runtime_suspend (struct device *dev) +static int spi_st_runtime_suspend (struct device *dev) {struct spi_controller *host =dev_get_drvdata (dev);struct spi_st *spi_st =spi_controller_get_devdata (host);
@@ -391,7 +391,7 @@ static int __maybe_unused spi_st_runtime_suspend(struct device *dev)return 0 ; } -static int __maybe_unused spi_st_runtime_resume (struct device *dev) +static int spi_st_runtime_resume (struct device *dev) {struct spi_controller *host =dev_get_drvdata (dev);struct spi_st *spi_st =spi_controller_get_devdata (host);
@@ -428,8 +428,8 @@ static int __maybe_unused spi_st_resume(struct device *dev) }static const struct dev_pm_ops spi_st_pm = { - SET_SYSTEM_SLEEP_PM_OPS(spi_st_suspend, spi_st_resume) -SET_RUNTIME_PM_OPS (spi_st_runtime_suspend, spi_st_runtime_resume,NULL ) + SYSTEM_SLEEP_PM_OPS(spi_st_suspend, spi_st_resume) +RUNTIME_PM_OPS (spi_st_runtime_suspend, spi_st_runtime_resume,NULL ) };static const struct of_device_id stm_spi_match[] = {
@@ -441,7 +441,7 @@ MODULE_DEVICE_TABLE(of, stm_spi_match);static struct platform_driver spi_st_driver = { .driver = { .name ="spi-st" , - .pm =pm_sleep_ptr (&spi_st_pm), + .pm =pm_ptr (&spi_st_pm), .of_match_table =of_match_ptr (stm_spi_match), }, .probe = spi_st_probe,
Signature · 1 line
2.50.1
Quoted 11 lines · Raphael Gallais-Pou
pm_sleep_ptr()depends onCONFIG_PM_SLEEPwhilepm_ptr()depends onCONFIG_PM. Since ST SSC4 implements runtime PM it makes sense usingpm_ptr()here.For the same reason replace PM macros that use
CONFIG_PM. Doing so prevents from using__maybe_unusedattribute of runtime PM functions.Link https://lore.kernel.org/lkml/CAMuHMdX9nkROkAJJ5odv4qOWe0bFTmaFs=Rfxsfuc9+DT-bsEQ@mail.gmail.com open hereFixes 6f8584a4826f ("spi: st: Switch from CONFIG_PM_SLEEP guards to pm_sleep_ptr()")Signed-off-by Raphael Gallais-Pou <[email protected]>
Gr{oetje,eeting}s,
Geert
Signature · 5 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] 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
Mark Brown
maintainerQuoted 8 lines · Raphael Gallais-Pou
pm_sleep_ptr()depends onCONFIG_PM_SLEEPwhilepm_ptr()depends onCONFIG_PM. Since ST SSC4 implements runtime PM it makes sense usingpm_ptr()here.For the same reason replace PM macros that use
CONFIG_PM. Doing so prevents from using__maybe_unusedattribute of runtime PM functions.[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: st: fix PM macros to use CONFIG_PM instead of CONFIG_PM_SLEEP
commit: 7c7cda81159b1abe7d50bcef2ccc6f662e225c8b
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark