On 08/12, Georgi Djakov wrote: > From: Stephen Boyd <sboyd@xxxxxxxxxxxxxx> > > Sometimes clocks can't accept their parent source turning off > while the source is reprogrammed to a different rate. Most > notably CPU clocks require a way to switch away from the current > PLL they're running on, reprogram that PLL to a new rate, and > then switch back to the PLL with the new rate once they're done. > Add a hook that drivers can implement allowing them to return a > 'safe parent' and 'safe frequency' that they can switch their > parent to while the upstream source is reprogrammed to support > this. > > Signed-off-by: Stephen Boyd <sboyd@xxxxxxxxxxxxxx> > Signed-off-by: Georgi Djakov <georgi.djakov@xxxxxxxxxx> Weird to be reviewing my own patch... Anyway, Mike tells me that coordinated clock rates are going to be on the list this month. We should use those patches instead of this safe parent/rate stuff. If the patches don't appear soon, we can look into having the clock provider handle the parent/rate switch itself. That isn't any worse that what we've been doing in other providers. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
