On 02/12/15 05:58, Javier Martinez Canillas wrote:
The change in the clk API to return a per-user clock instance, moved
the clock state to struct clk_core so now the struct clk_hw .core field
is used instead of .clk for most operations.
So for hardware clocks that needs to share the same
Hello Stephen,
On 02/12/2015 08:55 PM, Stephen Boyd wrote:
On 02/12/15 05:58, Javier Martinez Canillas wrote:
The changes were made using the following cocinelle semantic patch:
@i@
@@
@depends on i@
identifier dst;
@@
- dst-clk = hw-clk;
+ __clk_hw_set_clk(dst, hw);
@depends on i@
The change in the clk API to return a per-user clock instance, moved
the clock state to struct clk_core so now the struct clk_hw .core field
is used instead of .clk for most operations.
So for hardware clocks that needs to share the same clock state, both
the .core and .clk pointers have to be
Javier Martinez Canillas javier.marti...@collabora.co.uk writes:
The change in the clk API to return a per-user clock instance, moved
the clock state to struct clk_core so now the struct clk_hw .core field
is used instead of .clk for most operations.
If the patchset makes it up to acceptance