On 12/02/2015 02:04 PM, Stephen Boyd wrote:
On 12/02, Stephen Boyd wrote:
My only thought there would be to make of_clk_set_defaults() wait
until both clocks are registered before it does any parent
setting. But only in the case where the assigned parents contains
a clock that is provided by the node being processed. I suppose
the simplest thing to do would be to skip it during the device
driver probe and handle it when the clk provider is registered.
Actually it looks like we already have the code for that.
if (clkspec.np == node && !clk_supplier)
return 0;
So assigned parents should "just work"?
I tried using assigned-parents and it works fine.
The issue you mentioned above doesn't apply in our case, because
we have two different devices for "dsi" and "dsi_phy". dsi_phy is the
clock provider here and dsi is the one that wants to assign clocks.
If there was only one dsi device representing both DSI and PHY, then
we'd hit the condition you mentioned.
Thanks,
Archit
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, hosted by The Linux Foundation
--
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
