Re: [PATCH v3 1/4] clk: core: clarify the check for runtime PM

Hi Stephen, Stephen Boyd wrote on Thu, 20 Dec 2018 13:09:19 -0800: > Quoting Miquel Raynal (2018-12-19 00:03:31) > > Hi Stephen, > > > > Stephen Boyd wrote on Tue, 18 Dec 2018 16:03:29 > > -0800: > > > > > Quoting Miquel Raynal (2018-12-04 11:24:37) > > > > Currently, the core->dev entry

Re: [PATCH v3 1/4] clk: core: clarify the check for runtime PM

Quoting Miquel Raynal (2018-12-19 00:03:31) > Hi Stephen, > > Stephen Boyd wrote on Tue, 18 Dec 2018 16:03:29 > -0800: > > > Quoting Miquel Raynal (2018-12-04 11:24:37) > > > Currently, the core->dev entry is populated only if runtime PM is > > > enabled. Doing so prevents accessing the device s

Re: [PATCH v3 1/4] clk: core: clarify the check for runtime PM

Hi Stephen, Stephen Boyd wrote on Tue, 18 Dec 2018 16:03:29 -0800: > Quoting Miquel Raynal (2018-12-04 11:24:37) > > Currently, the core->dev entry is populated only if runtime PM is > > enabled. Doing so prevents accessing the device structure in any > > case. > > > > Keep the same logic but i

Re: [PATCH v3 1/4] clk: core: clarify the check for runtime PM

Quoting Miquel Raynal (2018-12-04 11:24:37) > Currently, the core->dev entry is populated only if runtime PM is > enabled. Doing so prevents accessing the device structure in any > case. > > Keep the same logic but instead of using the presence of core->dev as > the only condition, also check the

[PATCH v3 1/4] clk: core: clarify the check for runtime PM

Currently, the core->dev entry is populated only if runtime PM is enabled. Doing so prevents accessing the device structure in any case. Keep the same logic but instead of using the presence of core->dev as the only condition, also check the status of pm_runtime_enabled(). Then, we can set the cor