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: <5509BC1E.8050802@cogentembedded.com>
Date:	Wed, 18 Mar 2015 20:55:42 +0300
From:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To:	Geert Uytterhoeven <geert+renesas@...der.be>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jason Cooper <jason@...edaemon.net>
CC:	linux-sh@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] irqchip: renesas-intc-irqpin: Add optional functional
 clock to bindings

Hello.

On 03/18/2015 07:37 PM, Geert Uytterhoeven wrote:

> This clock is managed since commit 705bc96c2c15313c ("irqchip:
> renesas-intc-irqpin: Add minimal runtime PM support").

> Also add an example while we're at.

> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> ---
>   .../interrupt-controller/renesas,intc-irqpin.txt   | 29 ++++++++++++++++++++++
>   1 file changed, 29 insertions(+)

> diff --git a/Documentation/devicetree/bindings/interrupt-controller/renesas,intc-irqpin.txt b/Documentation/devicetree/bindings/interrupt-controller/renesas,intc-irqpin.txt
> index 4f7946ae8adcdc04..e7cfcec056159b93 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/renesas,intc-irqpin.txt
> +++ b/Documentation/devicetree/bindings/interrupt-controller/renesas,intc-irqpin.txt
> @@ -25,3 +25,32 @@ Optional properties:
>     if different from the default 4 bits
>   - control-parent: disable and enable interrupts on the parent interrupt
>     controller, needed for some broken implementations
> +- clocks: Must contain a reference to the functional clock.  The property is
> +  mandatory if the hardware implements a controllable functional clock for
> +  the irqpin controller instance.
> +
> +
> +Example
> +-------
> +
> +	irqpin1: irqpin@...00004 {

    The node name should be "interrupt-controller@...00004".

> +		compatible = "renesas,intc-irqpin-r8a7740",
> +			     "renesas,intc-irqpin";
> +		#interrupt-cells = <2>;
> +		interrupt-controller;
> +		reg = <0xe6900004 4>,
> +			<0xe6900014 4>,
> +			<0xe6900024 1>,
> +			<0xe6900044 1>,
> +			<0xe6900064 1>;
> +		interrupts = <0 149 IRQ_TYPE_LEVEL_HIGH
> +			      0 149 IRQ_TYPE_LEVEL_HIGH
> +			      0 149 IRQ_TYPE_LEVEL_HIGH
> +			      0 149 IRQ_TYPE_LEVEL_HIGH
> +			      0 149 IRQ_TYPE_LEVEL_HIGH
> +			      0 149 IRQ_TYPE_LEVEL_HIGH
> +			      0 149 IRQ_TYPE_LEVEL_HIGH
> +			      0 149 IRQ_TYPE_LEVEL_HIGH>;

    Hm, 8 similar interrupts?

> +		clocks = <&mstp2_clks R8A7740_CLK_INTCA>;
> +		power-domains = <&pd_a4s>;
> +	};

WBR, Sergei

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ