Martin Sperl writes:
>> On 02.05.2016, at 17:29, Eric Anholt wrote:
>>
>> Martin Sperl writes:
>>
On 26.04.2016, at 21:39, Eric Anholt wrote:
If the firmware had set up a clock to source from PLLC, go along with
it. But if we're looking for a new parent, we don't want t
> On 02.05.2016, at 17:29, Eric Anholt wrote:
>
> Martin Sperl writes:
>
>>> On 26.04.2016, at 21:39, Eric Anholt wrote:
>>>
>>> If the firmware had set up a clock to source from PLLC, go along with
>>> it. But if we're looking for a new parent, we don't want to switch it
>>> to PLLC becaus
Martin Sperl writes:
>> On 26.04.2016, at 21:39, Eric Anholt wrote:
>>
>> If the firmware had set up a clock to source from PLLC, go along with
>> it. But if we're looking for a new parent, we don't want to switch it
>> to PLLC because the firmware will force PLLC (and thus the AXI bus
>> cloc
On 30.04.2016 11:28, Martin Sperl wrote:
On 26.04.2016, at 21:39, Eric Anholt wrote:
If the firmware had set up a clock to source from PLLC, go along with
it. But if we're looking for a new parent, we don't want to switch it
to PLLC because the firmware will force PLLC (and thus the AXI bus
c
> On 26.04.2016, at 21:39, Eric Anholt wrote:
>
> If the firmware had set up a clock to source from PLLC, go along with
> it. But if we're looking for a new parent, we don't want to switch it
> to PLLC because the firmware will force PLLC (and thus the AXI bus
> clock) to different frequencies
If the firmware had set up a clock to source from PLLC, go along with
it. But if we're looking for a new parent, we don't want to switch it
to PLLC because the firmware will force PLLC (and thus the AXI bus
clock) to different frequencies during over-temp/under-voltage,
without notification to Lin
6 matches
Mail list logo