Re: [U-Boot] [PATCH v2 10/11] cpu: Bind timer driver for boot hart

2019-01-21 Thread Bin Meng
On Fri, Jan 18, 2019 at 7:19 PM Anup Patel wrote: > > From: Atish Patra > > Currently, timer driver is bound only for hart0. > > There is no mandatory requirement that hart0 should always > come up. In fact, HiFive Unleashed SoC hart0 doesn't boot > in S-mode because it only has M-mode. > > The

Re: [U-Boot] [PATCH v2 10/11] cpu: Bind timer driver for boot hart

2019-01-20 Thread Auer, Lukas
On Fri, 2019-01-18 at 11:19 +, Anup Patel wrote: > From: Atish Patra > > Currently, timer driver is bound only for hart0. > > There is no mandatory requirement that hart0 should always > come up. In fact, HiFive Unleashed SoC hart0 doesn't boot > in S-mode because it only has M-mode. > >

Re: [U-Boot] [PATCH v2 10/11] cpu: Bind timer driver for boot hart

2019-01-18 Thread Anup Patel
> -Original Message- > From: Alexander Graf [mailto:ag...@suse.de] > Sent: Friday, January 18, 2019 5:22 PM > To: Anup Patel ; Rick Chen ; > Bin Meng ; Joe Hershberger > ; Lukas Auer ; > Masahiro Yamada ; Simon Glass > > Cc: Palmer Dabbelt ; Paul Walmsley > ; Atish Patra ; > Christoph

Re: [U-Boot] [PATCH v2 10/11] cpu: Bind timer driver for boot hart

2019-01-18 Thread Alexander Graf
On 18.01.19 12:19, Anup Patel wrote: > From: Atish Patra > > Currently, timer driver is bound only for hart0. > > There is no mandatory requirement that hart0 should always > come up. In fact, HiFive Unleashed SoC hart0 doesn't boot > in S-mode because it only has M-mode. > > The timer

[U-Boot] [PATCH v2 10/11] cpu: Bind timer driver for boot hart

2019-01-18 Thread Anup Patel
From: Atish Patra Currently, timer driver is bound only for hart0. There is no mandatory requirement that hart0 should always come up. In fact, HiFive Unleashed SoC hart0 doesn't boot in S-mode because it only has M-mode. The timer driver should be bound for boot hart. Signed-off-by: Atish