On Thu, Aug 2, 2018 at 5:50 AM Christoph Hellwig <[email protected]> wrote: > > From: Palmer Dabbelt <[email protected]> > > Someone must have read the device tree specification incorrectly, > because we were putting timebase-frequency in the wrong place. This > corrects the issue, moving it from > > / { > cpus { > timebase-frequency = X; > } > } > > to > > / { > cpus { > cpu@0 { > timebase-frequency = X; > } > } > } > > This is great, because the timer's frequency should really be a per-cpu > quantity on RISC-V systems since there's a timer per CPU. This should > lead to some cleanups in our timer driver. > > Signed-off-by: Palmer Dabbelt <[email protected]> > Signed-off-by: Christoph Hellwig <[email protected]> > --- > Documentation/devicetree/bindings/riscv/cpus.txt | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-)
Reviewed-by: Rob Herring <[email protected]>
