From: Marc Zyngier <maz@kernel.org>
To: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Cc: tglx@linutronix.de, jason@lakedaemon.net, s-anna@ti.com,
robh+dt@kernel.org, lee.jones@linaro.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
david@lechnology.com, praneeth@ti.com
Subject: Re: [PATCH v7 0/5] Add TI PRUSS Local Interrupt Controller IRQChip driver
Date: Thu, 17 Sep 2020 11:45:08 +0100 [thread overview]
Message-ID: <9797030dd2c11b24ae0f7ef760f12ffa@kernel.org> (raw)
In-Reply-To: <1600274110-30384-1-git-send-email-grzegorz.jaszczyk@linaro.org>
On 2020-09-16 17:35, Grzegorz Jaszczyk wrote:
> Hi All,
>
> The following is a v7 version of the series [1-6] that adds an IRQChip
> driver for the local interrupt controller present within a Programmable
> Real-Time Unit and Industrial Communication Subsystem (PRU-ICSS)
> present on a
> number of TI SoCs including OMAP architecture based AM335x, AM437x,
> AM57xx SoCs,
> Keystone 2 architecture based 66AK2G SoCs, Davinci architecture based
> OMAP-L138/DA850 SoCs and the latest K3 architecture based AM65x and
> J721E SoCs.
> Please see the v1 cover-letter [1] for details about the features of
> this
> interrupt controller. More details can be found in any of the
> supported SoC
> TRMs. Eg: Chapter 30.1.6 of AM5728 TRM [7]
>
> Please see the individual patches for exact changes in each patch,
> following are
> the main changes from v5:
> - Add Co-developed-by tags.
> - Change the irq type to IRQ_TYPE_LEVEL_HIGH in patch #2.
Applied to irq/irqchip-next.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-09-17 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 16:35 [PATCH v7 0/5] Add TI PRUSS Local Interrupt Controller IRQChip driver Grzegorz Jaszczyk
2020-09-17 10:45 ` Marc Zyngier [this message]
2020-09-17 14:20 ` Grzegorz Jaszczyk
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=9797030dd2c11b24ae0f7ef760f12ffa@kernel.org \
--to=maz@kernel.org \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=grzegorz.jaszczyk@linaro.org \
--cc=jason@lakedaemon.net \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--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).