devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Nikolay Borisov <Nikolay.Borisov-5wv7dgnIgG8@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH RESEND 1/2] irqchip: Add generic gic-v1/gic-v2 compat strings.
Date: Thu, 22 May 2014 10:07:02 +0100	[thread overview]
Message-ID: <20140522090702.GA23478@leverpostej> (raw)
In-Reply-To: <CAL_JsqKpgWBQ6qFrDHt13wqRx1afPeapEz5z16enUyUX1fgUJg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed, May 21, 2014 at 10:27:33PM +0100, Rob Herring wrote:
> On Wed, May 21, 2014 at 8:48 AM, Nikolay Borisov
> <Nikolay.Borisov-5wv7dgnIgG8@public.gmane.org> wrote:
> > The current set of GIC compatible strings only contains specific
> > implementations (e.g. arm,cortex-a9-gic) rather than revisions of the
> > standard (e.g. arm,gic-v2), so each new implementation must either claim
> > to be an extension of an existing implementation or have a new string
> > added to the driver. This may be problematic when workarounds are
> > required for bugs in particular implementations, as said workaround may
> > end up targeting a wider set of implementations than intended.
> >
> > To prevent these issues, this patch adds compatible strings for the
> > revisions of the GIC spec which all GIC implementations should be able
> > to claim conformance to in addition to any particular implementation
> > specific string, e.g.
> 
> This just encourages not having specific properties which then also
> prevents being able to add work-arounds later. SOCs using the a9 or
> a15 string ONLY that are not an a9 or a15 are wrong. That's what we
> should fix. Adding more generic strings is not going to help that. Do
> you have a specific work-around you need to implement?

AFAIK, we don't have a specific workaround required anywhere that these
strings would help with. It's just that generic GIC strings had been
brought up repeatedly with no particular conclusion.

If we simply ensure that new DTS that feature a GIC have
implementation-specific strings in addition to those we already support
(e.g. "arm,cortex-a9-gic"), then I'm fine with that.

> Given that the GIC specs are obviously meaningless since we now have
> GICv2 with 16 core support as well as the special exynos gics, I'm not
> inclined to accept this.

Arguably neither are "true" GICv2, but your point stands.

Cheers,
Mark.

> 
> Rob
> 
> > compatible = "$VENDOR,specific-gic-variant", "arm,gic-v2";
> >
> > Signed-off-by: Nikolay Borisov <Nikolay.Borisov-5wv7dgnIgG8@public.gmane.org>
> > Acked-by: Mark Rutland <Mark.Rutland-5wv7dgnIgG8@public.gmane.org>
> > ---
> >  drivers/irqchip/irq-gic.c | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
> > index 57d165e..89e9b05 100644
> > --- a/drivers/irqchip/irq-gic.c
> > +++ b/drivers/irqchip/irq-gic.c
> > @@ -1073,6 +1073,8 @@ gic_of_init(struct device_node *node, struct device_node *parent)
> >  }
> >  IRQCHIP_DECLARE(cortex_a15_gic, "arm,cortex-a15-gic", gic_of_init);
> >  IRQCHIP_DECLARE(cortex_a9_gic, "arm,cortex-a9-gic", gic_of_init);
> > +IRQCHIP_DECLARE(gic_v1, "arm,gic-v1", gic_of_init);
> > +IRQCHIP_DECLARE(gic_v2, "arm,gic-v2", gic_of_init);
> >  IRQCHIP_DECLARE(msm_8660_qgic, "qcom,msm-8660-qgic", gic_of_init);
> >  IRQCHIP_DECLARE(msm_qgic2, "qcom,msm-qgic2", gic_of_init);
> >
> > --
> > 1.8.1.5
> >
> >
> > --
> > 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

  parent reply	other threads:[~2014-05-22  9:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 13:48 [PATCH RESEND 0/2] Add generic GIC compat strings Nikolay Borisov
     [not found] ` <1400680085-10430-1-git-send-email-Nikolay.Borisov-5wv7dgnIgG8@public.gmane.org>
2014-05-21 13:48   ` [PATCH RESEND 1/2] irqchip: Add generic gic-v1/gic-v2 " Nikolay Borisov
     [not found]     ` <1400680085-10430-2-git-send-email-Nikolay.Borisov-5wv7dgnIgG8@public.gmane.org>
2014-05-21 21:27       ` Rob Herring
     [not found]         ` <CAL_JsqKpgWBQ6qFrDHt13wqRx1afPeapEz5z16enUyUX1fgUJg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-22  9:07           ` Mark Rutland [this message]
2014-05-22 15:26             ` Christopher Covington
2014-05-21 13:48   ` [PATCH 2/2] documentation/devicetree: Update GIC " Nikolay Borisov

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=20140522090702.GA23478@leverpostej \
    --to=mark.rutland-5wv7dgnigg8@public.gmane.org \
    --cc=Nikolay.Borisov-5wv7dgnIgG8@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.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).