On Wed, Jul 29, 2020 at 10:59:07AM +0300, Maxim Kochetkov wrote: > To stop conversion ads1015_set_power_state function use unimplemented > function pm_runtime_put_autosuspend if CONFIG_PM is not set. > If CONFIG_PM is disabled, there is no need to start/stop conversion. > Fix it by adding return 0 function variant if CONFIG_PM is not set. I'm wondering if you check the real code (assembly) for any difference. All calls AFAICS are statically defined in !CONFIG_PM case and compiler/linker should be clever enough to drop this completely. Isn't it the case? -- With Best Regards, Andy Shevchenko
