From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] doc/devicetree: Add Aspeed VIC bindings
Date: Tue, 10 May 2016 08:04:40 +1000 [thread overview]
Message-ID: <1462831480.20290.120.camel@kernel.crashing.org> (raw)
In-Reply-To: <20160509152003.GA13842@leverpostej>
On Mon, 2016-05-09 at 16:20 +0100, Mark Rutland wrote:
>?
> Generally we steer clear of this kind of bitmap encoding in DT.
>
> Is this actually necessary? What does htis gain us?
>
> Why can we not just register with the full set of possible
> interrupts?
Trying to remember why I did that ... I think it has to do with
supporting multiple SoCs that have different possible sources...
There might also be a case of some sources routed to the internal
coldfire microcontroller or the LPC bus instead of the ARM but I'm not
100% certain.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Mark Rutland <mark.rutland-5wv7dgnIgG8@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
Subject: Re: [PATCH 1/2] doc/devicetree: Add Aspeed VIC bindings
Date: Tue, 10 May 2016 08:04:40 +1000 [thread overview]
Message-ID: <1462831480.20290.120.camel@kernel.crashing.org> (raw)
In-Reply-To: <20160509152003.GA13842@leverpostej>
On Mon, 2016-05-09 at 16:20 +0100, Mark Rutland wrote:
>
> Generally we steer clear of this kind of bitmap encoding in DT.
>
> Is this actually necessary? What does htis gain us?
>
> Why can we not just register with the full set of possible
> interrupts?
Trying to remember why I did that ... I think it has to do with
supporting multiple SoCs that have different possible sources...
There might also be a case of some sources routed to the internal
coldfire microcontroller or the LPC bus instead of the ARM but I'm not
100% certain.
Cheers,
Ben.
--
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-09 22:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 12:33 [PATCH 0/2] irqchip: Support Aspeed IRQ controller Joel Stanley
2016-05-09 12:33 ` Joel Stanley
2016-05-09 12:33 ` [PATCH 1/2] doc/devicetree: Add Aspeed VIC bindings Joel Stanley
2016-05-09 12:33 ` Joel Stanley
2016-05-09 12:50 ` Baruch Siach
2016-05-09 12:50 ` Baruch Siach
2016-05-09 12:55 ` Arnd Bergmann
2016-05-09 12:55 ` Arnd Bergmann
2016-05-09 15:20 ` Mark Rutland
2016-05-09 15:20 ` Mark Rutland
2016-05-09 22:04 ` Benjamin Herrenschmidt [this message]
2016-05-09 22:04 ` Benjamin Herrenschmidt
2016-05-09 12:33 ` [PATCH 2/2] irqchip: Add irq controller for Aspeed Joel Stanley
2016-05-09 12:33 ` Joel Stanley
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=1462831480.20290.120.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.