On 14/01/19 10:09 PM, Bartosz Golaszewski wrote: > pon., 14 sty 2019 o 13:20 Sekhar Nori <nsekhar@xxxxxx> napisał(a): >> >> Hi Bartosz, >> >> On 11/01/19 10:51 PM, Bartosz Golaszewski wrote: >>> From: Bartosz Golaszewski <bgolaszewski@xxxxxxxxxxxx> >>> >>> Currently the clocksource and clockevent support for davinci platforms >>> lives in mach-davinci. It hard-codes many things, used global variables, >>> implements functionalities unused by any platform and has code fragments >>> scattered across many (often unrelated) files. >>> >>> Implement a new, modern and simplified timer driver and put it into >>> drivers/clocksource. We still need to support legacy board files so >>> export a config structure and a function that allows machine code to >>> register the timer. >>> >>> We don't check the return values of regmap reads and writes since with >>> mmio it's only likely to fail due to programmer's errors. >>> >>> We also don't bother freeing resources on errors in >>> davinci_timer_register() as the system won't boot without a timer anyway. >>> >>> Signed-off-by: Bartosz Golaszewski <bgolaszewski@xxxxxxxxxxxx> >> >> With this series, DA830 fails to boot. Rest of the devices are okay from >> boot perspective. >> >> DA830 is pretty unique because it uses the same timer-half for both >> clocksource and clockevent. May be you can set the same configuration on >> your DA850 to see the same issue? Else, I will enable low-level debug >> and try to provide more debug data. >> > > I can't boot da850 with the same config as da830 (0x60 compare > register, compare irq 74) even with the old timer code. Just to make > sure: does da830 boot fine with mainline v5.0-rc2? Yeah, I did check that without the patch DA830 does boot. Thanks, Sekhar
