On Wednesday, October 11, 2017, Chris Brandt wrote: > On Wednesday, October 11, 2017, Jacopo Mondi wrote: > > From: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > > > > Currently all OSTM devices are called "ostm", also in kernel messages. > > > > As there can be multiple instances in an SoC, this can confuse the user. > > Hence construct a unique name from the DT node name, like is done for > > platform devices. > > > > On GR-Peach, the boot log changes like: > > > > -clocksource: ostm: mask: 0xffffffff max_cycles: 0xffffffff, > > max_idle_ns: 57352151442 ns > > +clocksource: ostm /timer@fcfec000: mask: 0xffffffff max_cycles: > > 0xffffffff, max_idle_ns: 57352151442 ns > > sched_clock: 32 bits at 33MHz, resolution 30ns, wraps every > > 64440619504ns > > -ostm: used for clocksource > > -ostm: used for clock events > > +ostm /timer@fcfec000: used for clocksource > > +ostm /timer@fcfec400: used for clock events > > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > > Signed-off-by: Jacopo Mondi <jacopo+renesas@xxxxxxxxxx> > > Tested-by: Jacopo Mondi <jacopo+renesas@xxxxxxxxxx> > > --- > > > My results on the RZ/A1H RSK board: > > $ dmesg | grep timer > [ 0.000000] clocksource: ostm /timer@fcfec000: mask: 0xffffffff > max_cycles: 0xffffffff, max_idle_ns: 57352151442 ns > [ 0.008267] ostm /timer@fcfec000: used for clocksource > [ 0.014085] ostm /timer@fcfec400: used for clock events > [ 0.452022] sh_mtu2 fcff0000.timer: ch0: used for clock events > [ 0.475358] sh_mtu2 fcff0000.timer: PM domain cpg_clocks will not be > powered off > [ 0.486528] clocksource: Switched to clocksource ostm /timer@fcfec000 > > > $ cat /proc/interrupts | grep timer > 17: 18721 GIC-0 135 Edge ostm /timer@fcfec400 > 40: 0 GIC-0 139 Level fcff0000.timer > > > Chris Out of curiosity, what ever happened to this patch??? Chris
