From mboxrd@z Thu Jan 1 00:00:00 1970 From: pankaj.dubey@samsung.com (Pankaj Dubey) Date: Tue, 20 Jan 2015 13:17:00 +0530 Subject: [PATCH v4 16/21] DT: exynos: update PMU binding In-Reply-To: <1421660655-21394-17-git-send-email-marc.zyngier@arm.com> References: <1421660655-21394-1-git-send-email-marc.zyngier@arm.com> <1421660655-21394-17-git-send-email-marc.zyngier@arm.com> Message-ID: <54BE07F4.1000106@samsung.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Marc, On Monday 19 January 2015 03:14 PM, Marc Zyngier wrote: > Document the fact that some Exynos PMUs are capable of acting as > an interrupt controller. > > Signed-off-by: Marc Zyngier > --- > Documentation/devicetree/bindings/arm/samsung/pmu.txt | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > diff --git a/Documentation/devicetree/bindings/arm/samsung/pmu.txt b/Documentation/devicetree/bindings/arm/samsung/pmu.txt > index 1e1979b..d698e74 100644 > --- a/Documentation/devicetree/bindings/arm/samsung/pmu.txt > +++ b/Documentation/devicetree/bindings/arm/samsung/pmu.txt > @@ -28,10 +28,23 @@ Properties: > - clocks : list of phandles and specifiers to all input clocks listed in > clock-names property. > > +Optional properties: > + > +Some PMUs are capable of behaving as an interrupt controller (mostly > +to wake up a suspended PMU). In which case, they can have the > +following properties: > + > +- interrupt-controller: indicate that said PMU is an interrupt controller > + Need to add #interrupt-cells property here. > +- interrupt-parent: a phandle indicating which interrupt controller > + this PMU signals interrupts to. > + > Example : > pmu_system_controller: system-controller at 10040000 { > compatible = "samsung,exynos5250-pmu", "syscon"; > reg = <0x10040000 0x5000>; > + interrupt-controller; > + interrupt-parent = <&gic>; > #clock-cells = <1>; > clock-names = "clkout0", "clkout1", "clkout2", "clkout3", > "clkout4", "clkout8", "clkout9"; > Thanks, Pankaj Dubey