From: heiko.stuebner@bq.com (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/6] dt-bindings: add mtk-timer bindings
Date: Wed, 21 May 2014 18:54:20 +0200 [thread overview]
Message-ID: <1948139.7c1AZ80ZQt@phil> (raw)
In-Reply-To: <63a3ee29-aa23-4137-9c0c-5b2bdd75a68f@BN1BFFO11FD014.protection.gbl>
Am Mittwoch, 21. Mai 2014, 09:34:10 schrieb S?ren Brinkmann:
> Hi Matthias,
>
> On Wed, 2014-05-21 at 06:26PM +0200, Matthias Brugger wrote:
> > Add binding documentation for the General Porpose Timer driver of
>
> Typo: Purpose
>
> > the Mediatek SoCs.
> >
> > Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
> > ---
> >
> > .../devicetree/bindings/timer/mediatek,mtk-timer.txt | 18
> > ++++++++++++++++++ 1 file changed, 18 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/timer/mediatek,mtk-timer.txt>
> > diff --git
> > a/Documentation/devicetree/bindings/timer/mediatek,mtk-timer.txt
> > b/Documentation/devicetree/bindings/timer/mediatek,mtk-timer.txt new file
> > mode 100644
> > index 0000000..7d909f7
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/timer/mediatek,mtk-timer.txt
> > @@ -0,0 +1,18 @@
> > +Mediatek MT6577, MT6572 and MT6589 Timers
> > +---------------------------------------
> > +
> > +Required properties:
> > +- compatible: Should be "mediatek,mtk6577-timer"
> > +- reg: Should contain location and length for timers register.
> > +- clocks: Clocks driving the timer hardware. This list shoud include two
> > + clocks. The order is system clock and as second clock the RTC clock.
> > +
> > +Examples:
> > +
> > + timer {
>
> The node name should be timer at 0x10008000
I think the more commonly used variant is
timer at 10008000
without the 0x. While some dts files really use @0x they are in the minority.
>
> > + compatible = "mediatek,mtk6577-timer";
> > + reg = <0x10008000 0x80>;
> > + interrupts = <GIC_SPI 113 IRQ_TYPE_LEVEL_LOW>;
> > + clocks = <&system_clk>, <&rtc_clk>;
> > + clock-names = "system-clk", "rtc-clk";
>
> I'm still not convinced that the timer IP calls its clock inputs this
> way, but well.
Maybe this might convince you ;-)
"The GPT includes 5 32-bit timers and one 64-bit timer. Each timer has 4
operation modes, which are ONE-SHOT, REPEAT, KEEP-GO and FREERUN, and can
operate on one of the 2 clock sources, RTC clock (32.768kHz) and system clock
(13MHz)."
Heiko
next prev parent reply other threads:[~2014-05-21 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 16:26 [PATCH v5 0/6] arm: Add basic support for Mediatek Cortex-A7 SoCs Matthias Brugger
2014-05-21 16:26 ` [PATCH v5 1/6] clocksource: Add support for the Mediatek SoCs Matthias Brugger
2014-05-23 17:39 ` Daniel Lezcano
2014-05-21 16:26 ` [PATCH v5 2/6] dt-bindings: add mtk-timer bindings Matthias Brugger
2014-05-21 16:34 ` Sören Brinkmann
2014-05-21 16:54 ` Heiko Stübner [this message]
2014-05-21 16:53 ` Sören Brinkmann
2014-05-21 17:18 ` Heiko Stübner
2014-05-21 17:21 ` Sören Brinkmann
2014-05-21 16:26 ` [PATCH v5 3/6] vendor-prefixes: add prefix for Mediaktek Inc Matthias Brugger
2014-05-21 16:26 ` [PATCH v5 4/6] arm: add basic support for Mediatek MT6589 boards Matthias Brugger
2014-05-21 16:26 ` [PATCH v5 5/6] dt-bindings: add documentation for Mediatek SoC Matthias Brugger
2014-05-21 16:26 ` [PATCH v5 6/6] arm: mediatek: add dts for Aquaris5 mobile phone Matthias Brugger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1948139.7c1AZ80ZQt@phil \
--to=heiko.stuebner@bq.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).