From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: dts: add initial dts for Samsung GH7 SoC and SSDK-GH7 board
Date: Wed, 12 Feb 2014 11:40:33 +0000 [thread overview]
Message-ID: <52FB5DB1.4090609@arm.com> (raw)
In-Reply-To: <20140212112946.GD21992@e106331-lin.cambridge.arm.com>
On 12/02/14 11:29, Mark Rutland wrote:
>>>> + gic: interrupt-controller at 1C000000 {
>>>> + compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic";
>>>
>>> This looks incorrect -- you should at the very least have a more
>>> specific one than a15-gic? Marc?
>>
>> "arm,cortex-a9-gic" is definitely wrong (the A9 GIC doesn't have the
>> virt extensions). This binding matches what the A15 GIC has, so
>> "arm,cortex-a15-gic" is probably fine. Main issue here is that the GICv2
>> driver has no compatible string for anything else.
>>
>> Should we define something more generic (like "arm,gic-v2")? Or carry on
>> adding more compatible strings?
>
> It's been proposed repeatedly, and it probably makes sense to add the
> generic versions to the driver, and allow for more specific ones in the
> binding which DTs can use. That way we don't get an explosion of strings
> in the driver, but if we need to handle any particular GIC specially in
> future we can do so.
>
> I guess for Linux we'd want to add "arm,gic-v1" and "arm,gic-v2" to the
> driver. We could just add "arm,gic-v1" and expect it later in the
> compatible list if v2 is a strict superset of v1; I think it is but I'm
> not a GIC expert.
Sounds good to me.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2014-02-12 11:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 6:29 [PATCH 0/3] arm64: add new support Samsung GH7 SoC and SSDK board Kukjin Kim
2014-02-11 6:29 ` [PATCH 1/3] arm64: dts: add initial dts for Samsung GH7 SoC and SSDK-GH7 board Kukjin Kim
2014-02-11 18:15 ` Mark Rutland
2014-02-11 3:16 ` Kukjin Kim
2014-02-18 10:30 ` Mark Rutland
2014-02-24 23:56 ` Kukjin Kim
2014-02-11 23:36 ` Olof Johansson
2014-02-11 3:25 ` Kukjin Kim
2014-02-12 11:13 ` Marc Zyngier
2014-02-12 11:29 ` Mark Rutland
2014-02-12 11:40 ` Marc Zyngier [this message]
2014-02-11 3:03 ` Kukjin Kim
2014-02-11 6:29 ` [PATCH 2/3] arm64: Add Kconfig option for Samsung GH7 SoC family Kukjin Kim
2014-02-11 23:39 ` Olof Johansson
2014-02-12 10:38 ` Catalin Marinas
2014-02-12 16:25 ` Kumar Gala
2014-02-12 18:12 ` Catalin Marinas
2014-02-12 19:04 ` Kumar Gala
2014-02-12 19:14 ` Arnd Bergmann
2014-02-11 2:52 ` Kukjin Kim
2014-02-13 19:26 ` Olof Johansson
2014-02-14 17:06 ` Arnd Bergmann
2014-02-18 1:10 ` Kukjin Kim
2014-02-18 10:53 ` Arnd Bergmann
2014-02-18 16:16 ` Olof Johansson
2014-02-18 18:13 ` Arnd Bergmann
2014-02-18 19:52 ` John Stultz
2014-02-18 20:00 ` Olof Johansson
2014-02-18 20:06 ` John Stultz
2014-02-20 9:03 ` Olof Johansson
2014-02-20 11:22 ` Catalin Marinas
2014-02-20 12:07 ` Arnd Bergmann
2014-02-20 17:09 ` Olof Johansson
2014-02-20 18:58 ` Catalin Marinas
2014-02-25 0:19 ` Kukjin Kim
2014-02-25 0:20 ` Kukjin Kim
2014-02-25 0:10 ` Kukjin Kim
2014-02-18 16:40 ` Catalin Marinas
2014-02-13 20:08 ` Rob Herring
2014-02-13 20:19 ` Olof Johansson
2014-02-11 6:29 ` [PATCH 3/3] Documentation: DT: add new entry for Samsung GH7 SoC and SSDK board Kukjin Kim
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=52FB5DB1.4090609@arm.com \
--to=marc.zyngier@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).