On 17/07/15 19:13, Stephen Boyd wrote:
On 07/17/2015 04:17 AM, Sudeep Holla wrote:
[...]
determine_rate change shouldn't affect SCPI clock driver but I remember
seeing round_rate change too on the list which returns value using the
argument from Boris. Is that planned for v4.3 ? I would need the stable
branch from this clk_hw_set_rate_range if you decide to push. Let me
know your preferences. I will post the updated version of the patch
accordingly.
We're not going to change round_rate() so it sounds like you don't need
a stable branch. But you would need this new consumer API. So you still
need a branch right?
I am fine either way. If no one else need the stable branch to be shared
with arm-soc, I prefer to use clock consumer API for now to avoid all
the troubles to you guys and switch to provider API later. I will post
it once the both this driver and that provider API is merged, if that's
fine with you ?
Regards,
Sudeep
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
