From: <Claudiu.Beznea@microchip.com>
To: <tglx@linutronix.de>, <maz@kernel.org>, <robh+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/2] irqchip/mchp-eic: add driver for Microchip EIC
Date: Fri, 24 Sep 2021 16:32:32 +0000 [thread overview]
Message-ID: <68755c28-946a-a526-21b1-e40dd4fc5722@microchip.com> (raw)
In-Reply-To: <20210924162817.2135056-1-claudiu.beznea@microchip.com>
Sorry, this had to be v4. I'll fix the versioning and re-post.
Thank you,
Claudiu Beznea
On 24.09.2021 19:28, Claudiu Beznea wrote:
> Hi,
>
> This series adds support for Microchip External Interrupt Controller
> present on SAMA7G5. The controller supports for 2 external interrupt
> lines and is connected to GIC as follows:
>
> pinX +------+ EXT_IRQ0 +------+ int 153 (for pinX) +------+
> ------>| |--------->| |------------------->| |
> pinY | PIO | EXT_IRQ1 | EIC | int 154 (for pinY) | GIC |
> ------>| |--------->| |------------------->| |
> +------+ +------+ +------+
>
> where PIO is the pin controller.
>
> Thank you,
> Claudiu Beznea
>
> Changes in v3:
> - use irq_domain_translate_twocell() instead of mchp_eic_domain_translate()
> from v2
> - use IRQCHIP_PLATFORM_DRIVER_BEGIN(), IRQCHIP_MATCH(),
> IRQCHIP_PLATFORM_DRIVER_END() instead of builtin_platform_driver()
> - register suspend/resume functins via syscore_ops; along with this
> driver private data structure (of type struct mchp_eic has been declared
> as static: struct mchp_eic *eic;)
> - collected tags
>
> Changes in v2:
> - fix compilation warning on bindings
>
> Changes in v2:
> - s/mchp/microchip in bindings
> - get rid of glitch filter settings
> - use s/eic@/interrupt-controller@ in bindings
> - removed '' around interrupts in bindings as proposed by Rob
> - removed glitch filter settings
> - switched to hierarchical irqchip driver
> - addressed review comments
> - use builtin_platform_driver instead of module_platform_driver
>
> Claudiu Beznea (2):
> dt-bindings: microchip,eic: add bindings
> irqchip/mchp-eic: add support
>
> .../interrupt-controller/microchip,eic.yaml | 73 +++++
> MAINTAINERS | 6 +
> drivers/irqchip/Kconfig | 8 +
> drivers/irqchip/Makefile | 1 +
> drivers/irqchip/irq-mchp-eic.c | 280 ++++++++++++++++++
> 5 files changed, 368 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/microchip,eic.yaml
> create mode 100644 drivers/irqchip/irq-mchp-eic.c
>
next prev parent reply other threads:[~2021-09-24 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 16:28 [PATCH v3 0/2] irqchip/mchp-eic: add driver for Microchip EIC Claudiu Beznea
2021-09-24 16:28 ` [PATCH v3 1/2] dt-bindings: microchip,eic: add bindings Claudiu Beznea
2021-09-24 16:28 ` [PATCH v3 2/2] irqchip/mchp-eic: add support Claudiu Beznea
2021-09-24 16:32 ` Claudiu.Beznea [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-10 6:06 [PATCH v3 0/2] irqchip/mchp-eic: add driver for Microchip EIC Claudiu Beznea
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=68755c28-946a-a526-21b1-e40dd4fc5722@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).