Am 19.06.2017 um 15:53 schrieb Daniel Lezcano: > On 18/06/2017 22:43, Andreas Färber wrote: >> Am 06.06.2017 um 18:33 schrieb Daniel Lezcano: >>> On Tue, Jun 06, 2017 at 02:54:02AM +0200, Andreas Färber wrote: >>>> The Actions Semi S500 SoC provides four timers, 2Hz0/1 and 32-bit TIMER0/1. >>>> >>>> Use TIMER0 as clocksource and TIMER1 as clockevents. >>>> >>>> Based on LeMaker linux-actions tree. >>>> >>>> An S500 datasheet can be found on the LeMaker Guitar pages: >>>> http://www.lemaker.org/product-guitar-download-29.html >>>> >>>> Signed-off-by: Andreas Färber <[email protected]> >>> >>> Acked-by: Daniel Lezcano <[email protected]> >> >> Thanks. It seems this is not going through a central clocksource tree, >> so I'm applying it to a new linux-actions.git v4.13/soc branch: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/afaerber/linux-actions.git/log/?h=v4.13/soc >> >> Let me know if you intend to take it through some other tree instead. > > No, it is ok. In the future, submit for the clocksource tree > (tip/timers/core).
Hm, I did see that tree in MAINTAINERS, but it specifically said "CLOCKSOURCE CORE" and it does not have any F: drivers/clocksource/ or F: Documentation/devicetree/bindings/timer/ entries, therefore I added the files to Actions like other SoCs did... I can easily unqueue the patches - what does submit for the clocksource tree mean? Just CC the two maintainers on resend or anything else? I intend to rename my branch to v4.13/drivers on Olof's feedback anyway. Sorry, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)
