On Fri, May 03, 2019 at 07:43:08PM +0200, Philippe Reynes wrote:
> The watchdog should use a clock at 50 Mhz, so
> instead of using the clock osc (200 Mhz), we
> define a reference clock at 50Mhz and use it
> for both watchdog.
>
> Signed-off-by: Philippe Reynes
> Reviewed-by: Stefan Roese
App
Hi Stefan,
> Hi Philippe,
>
> On 06.05.19 14:38, Philippe REYNES wrote:
>> Hi Stefan,
>>
>>> On 03.05.19 19:43, Philippe Reynes wrote:
The watchdog should use a clock at 50 Mhz, so
instead of using the clock osc (200 Mhz), we
define a reference clock at 50Mhz and use it
for b
Hi Philippe,
On 06.05.19 14:38, Philippe REYNES wrote:
Hi Stefan,
On 03.05.19 19:43, Philippe Reynes wrote:
The watchdog should use a clock at 50 Mhz, so
instead of using the clock osc (200 Mhz), we
define a reference clock at 50Mhz and use it
for both watchdog.
Signed-off-by: Philippe Reyne
Hi Stefan,
> On 03.05.19 19:43, Philippe Reynes wrote:
>> The watchdog should use a clock at 50 Mhz, so
>> instead of using the clock osc (200 Mhz), we
>> define a reference clock at 50Mhz and use it
>> for both watchdog.
>>
>> Signed-off-by: Philippe Reynes
>
> Just curious: Why is this the ca
On 03.05.19 19:43, Philippe Reynes wrote:
The watchdog should use a clock at 50 Mhz, so
instead of using the clock osc (200 Mhz), we
define a reference clock at 50Mhz and use it
for both watchdog.
Signed-off-by: Philippe Reynes
Just curious: Why is this the case? Is this also what's done in
t
The watchdog should use a clock at 50 Mhz, so
instead of using the clock osc (200 Mhz), we
define a reference clock at 50Mhz and use it
for both watchdog.
Signed-off-by: Philippe Reynes
---
arch/arm/dts/bcm63158.dtsi | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/
6 matches
Mail list logo