From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/7] irqchip: atmel-aic5: Add sama5d4 support
Date: Thu, 11 Sep 2014 18:28:37 +0200 [thread overview]
Message-ID: <20140911162836.GB3131@piout.net> (raw)
In-Reply-To: <5411CB17.1060608@atmel.com>
On 11/09/2014 at 18:17:27 +0200, Nicolas Ferre wrote :
> On 11/09/2014 17:54, Alexandre Belloni :
> > Add sama5d4 support to irq-atmel-aic5.
> >
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> > ---
> > Cc: Jason Cooper <jason@lakedaemon.net>
>
> Supposed to be before the "---" ;-)
This actually depends on the maintainer preferences, after the ---
marker means that it will not appear in the final commit log which was
my intention.
>
> > drivers/irqchip/irq-atmel-aic5.c | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/drivers/irqchip/irq-atmel-aic5.c b/drivers/irqchip/irq-atmel-aic5.c
> > index dc7d98607a89..a11aae8fb006 100644
> > --- a/drivers/irqchip/irq-atmel-aic5.c
> > +++ b/drivers/irqchip/irq-atmel-aic5.c
> > @@ -295,6 +295,7 @@ static void __init sama5d3_aic_irq_fixup(struct device_node *root)
> >
> > static const struct of_device_id __initdata aic5_irq_fixups[] = {
> > { .compatible = "atmel,sama5d3", .data = sama5d3_aic_irq_fixup },
> > + { .compatible = "atmel,sama5d4", .data = sama5d3_aic_irq_fixup },
> > { /* sentinel */ },
> > };
> >
> > @@ -349,3 +350,12 @@ static int __init sama5d3_aic5_of_init(struct device_node *node,
> > return aic5_of_init(node, parent, NR_SAMA5D3_IRQS);
> > }
> > IRQCHIP_DECLARE(sama5d3_aic5, "atmel,sama5d3-aic", sama5d3_aic5_of_init);
> > +
> > +#define NR_SAMA5D4_IRQS 68
> > +
> > +static int __init sama5d4_aic5_of_init(struct device_node *node,
> > + struct device_node *parent)
> > +{
> > + return aic5_of_init(node, parent, NR_SAMA5D4_IRQS);
> > +}
> > +IRQCHIP_DECLARE(sama5d4_aic5, "atmel,sama5d4-aic", sama5d4_aic5_of_init);
> >
>
>
> --
> Nicolas Ferre
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-11 16:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 15:54 [PATCH 0/7] Initial support for the Atmel SMART sama5d4 Alexandre Belloni
2014-09-11 15:54 ` [PATCH 1/7] irqchip: atmel-aic5: Add sama5d4 support Alexandre Belloni
2014-09-11 16:17 ` Nicolas Ferre
2014-09-11 16:28 ` Alexandre Belloni [this message]
2014-09-11 16:29 ` Nicolas Ferre
2014-09-11 16:34 ` Alexandre Belloni
2014-09-11 16:24 ` Thomas Petazzoni
2014-09-11 16:27 ` Alexandre Belloni
2014-09-11 16:46 ` Thomas Petazzoni
2014-09-11 15:54 ` [PATCH 2/7] clk: at91: add a driver for the h32mx clock Alexandre Belloni
2014-09-11 15:54 ` [PATCH 3/7] ARM: at91: introduce basic SAMA5D4 support Alexandre Belloni
2014-09-11 16:31 ` Thomas Petazzoni
2014-09-11 15:54 ` [PATCH 4/7] ARM: at91: SAMA5D4 SoC detection code and low level routines Alexandre Belloni
2014-09-11 15:54 ` [PATCH 5/7] ARM: at91: dt: add device tree file for SAMA5D4 SoC Alexandre Belloni
2014-09-11 15:54 ` [PATCH 6/7] ARM: at91: dt: add device tree file for SAMA5D4ek board Alexandre Belloni
2014-09-11 15:54 ` [PATCH 7/7] ARM: at91: add sama5d4 support to sama5_defconfig Alexandre Belloni
2014-09-11 16:19 ` Nicolas Ferre
2014-09-11 16:32 ` Thomas Petazzoni
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=20140911162836.GB3131@piout.net \
--to=alexandre.belloni@free-electrons.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).