Quoting Maxime Ripard (2020-06-15 01:40:54)
> The driver has really only supported one clock so far and has hardcoded the
> ID used in communications with the firmware in all the functions
> implementing the clock framework hooks. Let's store that in the clock data
> structure so that we can support more clocks later on.
> 
> Cc: Michael Turquette <[email protected]>
> Cc: [email protected]
> Acked-by: Nicolas Saenz Julienne <[email protected]>
> Reviewed-by: Stephen Boyd <[email protected]>
> Tested-by: Nicolas Saenz Julienne <[email protected]>
> Signed-off-by: Maxime Ripard <[email protected]>
> ---

Applied to clk-next

Reply via email to