linux-kernel - Re: [PATCH v5 2/6] dt-bindings: add mtk-timer bindings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3a9b6824-e088-4774-b125-7a33b5a895dc@BN1AFFO11FD022.protection.gbl>
Date:	Wed, 21 May 2014 09:53:57 -0700
From:	Sören Brinkmann <soren.brinkmann@...inx.com>
To:	Heiko Stübner <heiko.stuebner@...com>
CC:	Matthias Brugger <matthias.bgg@...il.com>,
	<linux-kernel@...r.kernel.org>, <robh+dt@...nel.org>,
	<pawel.moll@....com>, <mark.rutland@....com>,
	<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
	<rdunlap@...radead.org>, <linux@....linux.org.uk>,
	<daniel.lezcano@...aro.org>, <tglx@...utronix.de>,
	<thierry.reding@...il.com>, <florian.vaussard@...l.ch>,
	<jic23@...nel.org>, <jason@...edaemon.net>, <andrew@...n.ch>,
	<silvio.fricke@...il.com>, <olof@...om.net>,
	<sebastian.hesselbarth@...il.com>, <sboyd@...eaurora.org>,
	<gregory.clement@...e-electrons.com>, <arnd@...db.de>,
	<robherring2@...il.com>, <marc.zyngier@....com>,
	<maxime.ripard@...e-electrons.com>, <devicetree@...r.kernel.org>,
	<linux-doc@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v5 2/6] dt-bindings: add mtk-timer bindings

On Wed, 2014-05-21 at 06:54PM +0200, Heiko Stübner wrote:
> 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@...il.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@...0008000
> 
> I think the more commonly used variant is
> 
> 	timer@...08000
> 
> without the 0x. While some dts files really use @0x they are in the minority.

You're right.

> 
> 
> > 
> > > +		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)."

Is this copied from the timer data sheet or the SOC documentation?

	Sören
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/