Re: [PATCH v5 1/3] clk: bcm2835: Add binding docs for the Raspberry Pi clock provider

2015-08-24 Thread Eric Anholt
Eric Anholt writes: > The hardware clocks are not controllable by the ARM, so we have to > make requests to the firmware to do so from the VPU side. This will > let us replace fixed clocks in our DT with actual clock control (and > correct frequency information). Gordon from the Raspberry Pi

Re: [PATCH v5 1/3] clk: bcm2835: Add binding docs for the Raspberry Pi clock provider

2015-08-24 Thread Eric Anholt
Eric Anholt e...@anholt.net writes: The hardware clocks are not controllable by the ARM, so we have to make requests to the firmware to do so from the VPU side. This will let us replace fixed clocks in our DT with actual clock control (and correct frequency information). Gordon from the

[PATCH v5 1/3] clk: bcm2835: Add binding docs for the Raspberry Pi clock provider

2015-08-13 Thread Eric Anholt
The hardware clocks are not controllable by the ARM, so we have to make requests to the firmware to do so from the VPU side. This will let us replace fixed clocks in our DT with actual clock control (and correct frequency information). Signed-off-by: Eric Anholt Acked-by: Stephen Warren

[PATCH v5 1/3] clk: bcm2835: Add binding docs for the Raspberry Pi clock provider

2015-08-13 Thread Eric Anholt
The hardware clocks are not controllable by the ARM, so we have to make requests to the firmware to do so from the VPU side. This will let us replace fixed clocks in our DT with actual clock control (and correct frequency information). Signed-off-by: Eric Anholt e...@anholt.net Acked-by: Stephen