From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] of: Add NVIDIA Tegra Legacy Interrupt Controller binding
Date: Mon, 30 Jun 2014 18:43:34 +0100 [thread overview]
Message-ID: <20140630174334.GF28740@leverpostej> (raw)
In-Reply-To: <1403917351-13215-1-git-send-email-thierry.reding@gmail.com>
On Sat, Jun 28, 2014 at 02:02:28AM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The Legacy Interrupt Controller found on NVIDIA Tegra SoCs is used by
> the AVP coprocessor and can also serve as a backup for the ARM Cortex
> CPU's local interrupt controller (GIC).
>
> The LIC is subdivided into multiple identical units, each handling 32
> possible interrupt sources.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v2:
> - new patch
>
> .../interrupt-controller/nvidia,tegra20-ictlr.txt | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt b/Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt
> new file mode 100644
> index 000000000000..c695ec713740
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt
> @@ -0,0 +1,19 @@
> +NVIDIA Tegra Legacy Interrupt Controller
> +
> +The legacy interrupt controller is divided into units that serve 32 interrupts
> +each. Tegra20 implements four units, whereas Tegra30 and later implement five.
> +
> +Required properties:
> +- compatible: "nvidia,tegra<chip>-ictlr"
And valid <chip> values are?
> +- reg: Physical base address and length of the controller's registers. There
> + should be one entry for each unit.
> +
> +Example:
> +
> + interrupt-controller at 60004000 {
> + compatible = "nvidia,tegra20-ictlr";
> + reg = <0x60004000 0x40 /* primary controller */
> + 0x60004100 0x40 /* secondary controller */
> + 0x60004200 0x40 /* tertiary controller */
> + 0x60004300 0x40>; /* quaternary controller */
Could we please bracket the entries individually, e.g.
reg = <0x60004000 0x40>,
<0x60004100 0x40>,
<0x60004200 0x40>,
<0x60004300 0x40>;
How do the interrupt lines correspond to those of the GIC?
Cheers,
Mark.
next prev parent reply other threads:[~2014-06-30 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 1:02 [PATCH v2 1/4] of: Add NVIDIA Tegra Legacy Interrupt Controller binding Thierry Reding
2014-06-28 1:02 ` [PATCH v2 2/4] ARM: tegra: Add legacy interrupt controller nodes Thierry Reding
2014-06-28 1:02 ` [PATCH v2 3/4] soc/tegra: Initialize interrupt controller from DT Thierry Reding
2014-06-30 20:31 ` Stephen Warren
2014-06-28 1:02 ` [PATCH v2 4/4] soc/tegra: Remove unused defines Thierry Reding
2014-06-30 17:43 ` Mark Rutland [this message]
2014-06-30 18:38 ` [PATCH v2 1/4] of: Add NVIDIA Tegra Legacy Interrupt Controller binding Stephen Warren
2014-07-01 13:10 ` Mark Rutland
2014-06-30 20:32 ` Stephen Warren
2014-08-25 17:35 ` Stephen Warren
2014-08-26 6:17 ` Thierry Reding
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=20140630174334.GF28740@leverpostej \
--to=mark.rutland@arm.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).