From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] doc/devicetree: Add Aspeed VIC bindings
Date: Thu, 12 May 2016 11:01:22 +1000 [thread overview]
Message-ID: <1463014882.20290.203.camel@kernel.crashing.org> (raw)
In-Reply-To: <20160511143313.GA7426@rob-hp-laptop>
On Wed, 2016-05-11 at 09:33 -0500, Rob Herring wrote:
> > +- interrupt-controller : Identifies the node as an interrupt controller
> > +- #interrupt-cells : Specifies the number of cells needed to encode an
> > +? interrupt source. The value shall be 1.
>
> No need for level vs. edge flags?
That's an open question. Most interrupts are fixed. A handful of GPIOs
can be configured either way. For now I am relying on uboot setting up
the right config for them and I read it back at boot time, but we could
make it part of the binding I suppose.
> > +- valid-sources : bitmask of valid irq sources
>
> Drop this. Either all interrupt controllers need this or none of?
> them do. The valid sources are the ones described in the DT.
Looking at the code (I wrote that ages ago), this is only used for:
? - Failing map on an unsupported source, so we could drop it
? - Counting the number of sources in order to optimize the
? ? revmap size allocation. We could unconditionally allocate
? ? 64, I don't see a big deal here.
So yes Joel, feel free to just ditch this.
> > +
> > +Example:
> > +
> > + vic: interrupt-controller {
>
> Needs a unit address.
>
> > +????? compatible = "aspeed,ast2400-vic";
> > +????? interrupt-controller;
> > +????? #interrupt-cells = <1>;
> > +????? valid-sources = < 0xffffffff 0x0007ffff>;
> > +????? reg = <0x1e6c0080 0x80>;
> > + };
> > --?
> > 2.8.1
> >?
> > --
> > To unsubscribe from this list: send the line "unsubscribe devicetree" in
> > the body of a message to majordomo at vger.kernel.org
> > More majordomo info at? http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Joel Stanley <joel-U3u1mxZcP9KHXe+LvDLADg@public.gmane.org>
Cc: tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org,
marc.zyngier-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
jk-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org
Subject: Re: [PATCH v2 1/2] doc/devicetree: Add Aspeed VIC bindings
Date: Thu, 12 May 2016 11:01:22 +1000 [thread overview]
Message-ID: <1463014882.20290.203.camel@kernel.crashing.org> (raw)
In-Reply-To: <20160511143313.GA7426@rob-hp-laptop>
On Wed, 2016-05-11 at 09:33 -0500, Rob Herring wrote:
> > +- interrupt-controller : Identifies the node as an interrupt controller
> > +- #interrupt-cells : Specifies the number of cells needed to encode an
> > + interrupt source. The value shall be 1.
>
> No need for level vs. edge flags?
That's an open question. Most interrupts are fixed. A handful of GPIOs
can be configured either way. For now I am relying on uboot setting up
the right config for them and I read it back at boot time, but we could
make it part of the binding I suppose.
> > +- valid-sources : bitmask of valid irq sources
>
> Drop this. Either all interrupt controllers need this or none of
> them do. The valid sources are the ones described in the DT.
Looking at the code (I wrote that ages ago), this is only used for:
- Failing map on an unsupported source, so we could drop it
- Counting the number of sources in order to optimize the
revmap size allocation. We could unconditionally allocate
64, I don't see a big deal here.
So yes Joel, feel free to just ditch this.
> > +
> > +Example:
> > +
> > + vic: interrupt-controller {
>
> Needs a unit address.
>
> > + compatible = "aspeed,ast2400-vic";
> > + interrupt-controller;
> > + #interrupt-cells = <1>;
> > + valid-sources = < 0xffffffff 0x0007ffff>;
> > + reg = <0x1e6c0080 0x80>;
> > + };
> > --
> > 2.8.1
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe devicetree" in
> > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-05-12 1:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <462797239-14765-1-git-send-email-joel@jms.id.au>
2016-05-09 13:58 ` [PATCH v2 0/2] irqchip: Support Aspeed IRQ controller Joel Stanley
2016-05-09 13:58 ` Joel Stanley
2016-05-09 13:58 ` [PATCH v2 1/2] doc/devicetree: Add Aspeed VIC bindings Joel Stanley
2016-05-09 13:58 ` Joel Stanley
2016-05-11 14:33 ` Rob Herring
2016-05-11 14:33 ` Rob Herring
2016-05-12 1:01 ` Benjamin Herrenschmidt [this message]
2016-05-12 1:01 ` Benjamin Herrenschmidt
2016-05-12 17:20 ` Rob Herring
2016-05-12 17:20 ` Rob Herring
2016-05-18 13:50 ` Joel Stanley
2016-05-18 13:50 ` Joel Stanley
2016-05-20 20:13 ` Rob Herring
2016-05-20 20:13 ` Rob Herring
2016-05-09 13:58 ` [PATCH v2 2/2] irqchip: Add irq controller for Aspeed Joel Stanley
2016-05-09 13:58 ` Joel Stanley
2016-05-12 14:43 ` [PATCH v3 0/2] irqchip: Support Aspeed IRQ controller Joel Stanley
2016-05-12 14:43 ` Joel Stanley
2016-05-12 14:43 ` [PATCH v3 1/2] doc/devicetree: Add Aspeed VIC bindings Joel Stanley
2016-05-12 14:43 ` Joel Stanley
2016-05-12 14:43 ` [PATCH v3 2/2] irqchip: Add irq controller for Aspeed Joel Stanley
2016-05-12 14:43 ` Joel Stanley
2016-06-22 18:53 ` [PATCH v3 0/2] irqchip: Support Aspeed IRQ controller Jason Cooper
2016-06-22 18:53 ` Jason Cooper
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=1463014882.20290.203.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.