...@wdc.com; Sagar Kadam
>; r...@andestech.com; Lukas Auer
>
>Subject: Re: [PATCH v7 16/22] riscv: Enable cpu clock if it is present
>
>[External Email] Do not click links or attachments unless you recognize the
>sender and know the content is safe
>
>On 5/3/20 3:12 AM, Pragne
bmeng...@gmail.com; Paul Walmsley ;
>> ja...@amarulasolutions.com; Troy Benjegerdes
>> ; anup.pa...@wdc.com; Sagar Kadam
>> ; r...@andestech.com; Lukas Auer
>>
>> Subject: Re: [PATCH v7 16/22] riscv: Enable cpu clock if it is present
>>
>> [External Email] Do not click
...@wdc.com; Sagar Kadam
>; r...@andestech.com; Lukas Auer
>
>Subject: Re: [PATCH v7 16/22] riscv: Enable cpu clock if it is present
>
>[External Email] Do not click links or attachments unless you recognize the
>sender and know the content is safe
>
>On 5/2/20 6:06 AM, Pr
On 5/2/20 6:06 AM, Pragnesh Patel wrote:
> The cpu clock is probably already enabled if we are executing code (though
> we could be executing from a different core). This patch prevents the cpu
> clock or its parents from being disabled.
>
> Signed-off-by: Sean Anderson
If you make substantial c
On Sat, May 2, 2020 at 6:08 PM Pragnesh Patel wrote:
>
> The cpu clock is probably already enabled if we are executing code (though
> we could be executing from a different core). This patch prevents the cpu
> clock or its parents from being disabled.
>
> Signed-off-by: Sean Anderson
> Signed-off
5 matches
Mail list logo