[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171208102700.g6wy4suhwmwnd4ix@lakrids.cambridge.arm.com>
Date: Fri, 8 Dec 2017 10:27:00 +0000
From: Mark Rutland <mark.rutland@....com>
To: Greentime Hu <green.hu@...il.com>
Cc: greentime@...estech.com, linux-kernel@...r.kernel.org,
arnd@...db.de, linux-arch@...r.kernel.org, tglx@...utronix.de,
jason@...edaemon.net, marc.zyngier@....com, robh+dt@...nel.org,
netdev@...r.kernel.org, deanbo422@...il.com,
devicetree@...r.kernel.org, viro@...iv.linux.org.uk,
dhowells@...hat.com, will.deacon@....com,
daniel.lezcano@...aro.org, linux-serial@...r.kernel.org,
geert.uytterhoeven@...il.com, linus.walleij@...aro.org,
greg@...ah.com, Vincent Chen <vincentc@...estech.com>
Subject: Re: [PATCH v3 24/33] nds32: Device tree support
On Fri, Dec 08, 2017 at 05:12:07PM +0800, Greentime Hu wrote:
> + timer0: timer@...00000 {
> + compatible = "andestech,atftmr010";
> + reg = <0x98400000 0x1000>;
> + interrupts = <19>;
> + clocks = <&clk_pll>;
> + clock-names = "apb_pclk";
> + cycle-count-offset = <0x20>;
> + };
Looking through the series, I can't find a binding or driver for this
timer, either.
Does timekeeping work with this series, or are additional patches
necessary?
Thanks,
Mark.
Powered by blists - more mailing lists