[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <568CCCA2.4040004@nvidia.com>
Date: Wed, 6 Jan 2016 13:43:22 +0530
From: Laxman Dewangan <ldewangan@...dia.com>
To: "H. Nikolaus Schaller" <hns@...delico.com>,
Nishanth Menon <nm@...com>
CC: BenoƮt Cousson <bcousson@...libre.com>,
Tony Lindgren <tony@...mide.com>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
"Russell King" <linux@....linux.org.uk>,
linux-omap <linux-omap@...r.kernel.org>,
<devicetree@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
"Marek Belisko" <marek@...delico.com>
Subject: Re: [PATCH 1/3] ARM: dts: omap5-board-common: enable rtc and charging
of backup battery
On Wednesday 06 January 2016 01:12 PM, H. Nikolaus Schaller wrote:
> Hi,
>
> Am 06.01.2016 um 00:40 schrieb Nishanth Menon <nm@...com>:
>
>> On 01/05/2016 06:01 AM, H. Nikolaus Schaller wrote:
>>> + rtc {
>>> + compatible = "ti,palmas-rtc";
>>> + interrupt-parent = <&palmas>;
>>> + interrupts = <8 IRQ_TYPE_NONE>;
>> IRQ_TYPE_NONE is not correct here -> it should have some polarity - if
>> it had none, there'd be no interrupt, right?
> Well, it just translates IRQ_TYPE_NONE through
>
> Linux/include/dt-bindings/interrupt-controller/irq.h
>
> to
>
> interrupts = <8 0>;
>
> which is given as an example in
>
> Documentation//devicetree/bindings/rtc/rtc-palmas.txt
>
> Since I don't know anything about the rtc driver beyond the bindings documentation I assume it is correct...
> I have added Laxman Dewangan because he introduced this interrupts = <8 0>;
>
As this is for palmas interrupt controller, it does not use the second
field for interrupt from RTC.
So there is no really any polarity. It can be set to 0.
The second argument will be used for GPIOs mainly. However, support need
to be added on GPIO driver for rising/falling configuration.
--
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/
Powered by blists - more mailing lists