On 07/24/2015 09:30 AM, Lee Jones wrote:
> On Tue, 07 Jul 2015, Eric Anholt wrote:
>
>> Lee Jones writes:
>>
>>> If I were the Clock Maintainer, I would have probably missed this
>>> patch. You _must_ intimate which subsystem you are submitting to.
>>>
The hardware clocks are not controllab
On Tue, 07 Jul 2015, Eric Anholt wrote:
> Lee Jones writes:
>
> > If I were the Clock Maintainer, I would have probably missed this
> > patch. You _must_ intimate which subsystem you are submitting to.
> >
> >> The hardware clocks are not controllable by the ARM, so we have to
> >> make request
Lee Jones writes:
> If I were the Clock Maintainer, I would have probably missed this
> patch. You _must_ intimate which subsystem you are submitting to.
>
>> 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 wil
If I were the Clock Maintainer, I would have probably missed this
patch. You _must_ intimate which subsystem you are submitting to.
> 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 cl
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).
>
> v2: Include the dt-bindings
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).
v2: Include the dt-bindings header in this commit instead of
6 matches
Mail list logo
