[lkml]   [2018]   [Nov]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH 0/2] Link consumer with clock driver

While working on suspend to RAM feature, I ran into troubles multiple
times when clocks where not suspending/resuming at the desired time. I
had a look at the core and I think the same logic as in the
regulator's core may be applied here to (very easily) fix this issue:
using device links.

The only additional change I had to do was to always (when available)
populate the device entry of the core clock structure so that it could
be used later. This is the purpose of patch 1. Patch 2 actually adds
support for device links.

As I am not used to hack into the clock subsystem I might have missed
something big preventing such change but so far I could not see
anything wrong with it. As this touches core code, I am of course
entirely open to suggestions.


Miquel Raynal (2):
clk: core: clarify the check for runtime PM
clk: core: link consumer with clock driver

drivers/clk/clk.c | 31 +++++++++++++++++++++++++------
drivers/clk/clkdev.c | 13 ++++++++++---
include/linux/clk-provider.h | 2 ++
3 files changed, 37 insertions(+), 9 deletions(-)


 \ /
  Last update: 2018-11-22 22:22    [W:0.099 / U:0.556 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site