Re: [PATCH v2 1/4] dt-bindings: Correct RISC-V's timebase-frequency

2019-01-07 Thread Daniel Lezcano
On 04/01/2019 01:36, Palmer Dabbelt wrote: > On Fri, 14 Dec 2018 01:17:24 PST (-0800), daniel.lezc...@linaro.org wrote: >> On 14/12/2018 00:14, Atish Patra wrote: >>> From: Palmer Dabbelt >>> >>> In RISC-V systems, timebase-frequency is per cpu instead of one >>> instance for entire SOC as there i

Re: [PATCH v2 1/4] dt-bindings: Correct RISC-V's timebase-frequency

2019-01-03 Thread Palmer Dabbelt
On Fri, 14 Dec 2018 01:17:24 PST (-0800), daniel.lezc...@linaro.org wrote: On 14/12/2018 00:14, Atish Patra wrote: From: Palmer Dabbelt In RISC-V systems, timebase-frequency is per cpu instead of one instance for entire SOC as there is a individual timer per each CPU. Fix the DT binding accord

Re: [PATCH v2 1/4] dt-bindings: Correct RISC-V's timebase-frequency

2018-12-14 Thread Daniel Lezcano
On 14/12/2018 00:14, Atish Patra wrote: > From: Palmer Dabbelt > > In RISC-V systems, timebase-frequency is per cpu instead of one > instance for entire SOC as there is a individual timer per each CPU. > Fix the DT binding accordingly. Why not use a fixed-clock instead of this timebase property

[PATCH v2 1/4] dt-bindings: Correct RISC-V's timebase-frequency

2018-12-13 Thread Atish Patra
From: Palmer Dabbelt In RISC-V systems, timebase-frequency is per cpu instead of one instance for entire SOC as there is a individual timer per each CPU. Fix the DT binding accordingly. Signed-off-by: Palmer Dabbelt Signed-off-by: Christoph Hellwig [Atish: Update the commit text] Signed-off-by