All of lore.kernel.org
 help / color / mirror / Atom feed
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, wmills@ti.com
Subject: Re: [PATCHv3 5/6] irqchip/irq-pruss-intc: Add support for ICSSG INTC on K3 SoCs
Date: Thu, 02 Jul 2020 18:59:01 +0100	[thread overview]
Message-ID: <d1b232c6f33a629117a2ecbd440622d0@kernel.org> (raw)
In-Reply-To: <1593699479-1445-6-git-send-email-grzegorz.jaszczyk@linaro.org>

On 2020-07-02 15:17, Grzegorz Jaszczyk wrote:
> From: Suman Anna <s-anna@ti.com>
> 
> The K3 AM65x and J721E SoCs have the next generation of the PRU-ICSS 
> IP,
> commonly called ICSSG. The PRUSS INTC present within the ICSSG supports
> more System Events (160 vs 64), more Interrupt Channels and Host 
> Interrupts
> (20 vs 10) compared to the previous generation PRUSS INTC instances. 
> The
> first 2 and the last 10 of these host interrupt lines are used by the
> PRU and other auxiliary cores and sub-modules within the ICSSG, with 8
> host interrupts connected to MPU. The host interrupts 5, 6, 7 are also
> connected to the other ICSSG instances within the SoC and can be
> partitioned as per system integration through the board dts files.
> 
> Enhance the PRUSS INTC driver to add support for this ICSSG INTC
> instance. This support is added using specific compatible and match
> data and updating the code to use this data instead of the current
> hard-coded macros. The INTC config structure is updated to use the
> higher events and channels on all SoCs, while limiting the actual
> processing to only the relevant number of events/channels/interrupts.
> 
> Signed-off-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
> ---
> v2->v3:
> - Change patch order: use it directly after "irqchip/irq-pruss-intc:
>   Implement irq_{get,set}_irqchip_state ops" and before new
>   "irqchip/irq-pruss-intc: Add event mapping support" in order to 
> reduce
>   diff.

The diff would be even smaller if you introduced a variable number of
inputs the first place, i.e. in patch #2. Most if this patch just
retrofits it. Please squash these changes into that initial patch,
and only add the platform stuff here.

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
	jason@lakedaemon.net, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org, tglx@linutronix.de, lee.jones@linaro.org,
	wmills@ti.com, linux-arm-kernel@lists.infradead.org,
	david@lechnology.com
Subject: Re: [PATCHv3 5/6] irqchip/irq-pruss-intc: Add support for ICSSG INTC on K3 SoCs
Date: Thu, 02 Jul 2020 18:59:01 +0100	[thread overview]
Message-ID: <d1b232c6f33a629117a2ecbd440622d0@kernel.org> (raw)
In-Reply-To: <1593699479-1445-6-git-send-email-grzegorz.jaszczyk@linaro.org>

On 2020-07-02 15:17, Grzegorz Jaszczyk wrote:
> From: Suman Anna <s-anna@ti.com>
> 
> The K3 AM65x and J721E SoCs have the next generation of the PRU-ICSS 
> IP,
> commonly called ICSSG. The PRUSS INTC present within the ICSSG supports
> more System Events (160 vs 64), more Interrupt Channels and Host 
> Interrupts
> (20 vs 10) compared to the previous generation PRUSS INTC instances. 
> The
> first 2 and the last 10 of these host interrupt lines are used by the
> PRU and other auxiliary cores and sub-modules within the ICSSG, with 8
> host interrupts connected to MPU. The host interrupts 5, 6, 7 are also
> connected to the other ICSSG instances within the SoC and can be
> partitioned as per system integration through the board dts files.
> 
> Enhance the PRUSS INTC driver to add support for this ICSSG INTC
> instance. This support is added using specific compatible and match
> data and updating the code to use this data instead of the current
> hard-coded macros. The INTC config structure is updated to use the
> higher events and channels on all SoCs, while limiting the actual
> processing to only the relevant number of events/channels/interrupts.
> 
> Signed-off-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
> ---
> v2->v3:
> - Change patch order: use it directly after "irqchip/irq-pruss-intc:
>   Implement irq_{get,set}_irqchip_state ops" and before new
>   "irqchip/irq-pruss-intc: Add event mapping support" in order to 
> reduce
>   diff.

The diff would be even smaller if you introduced a variable number of
inputs the first place, i.e. in patch #2. Most if this patch just
retrofits it. Please squash these changes into that initial patch,
and only add the platform stuff here.

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-07-02 17:59 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 14:17 [PATCHv3 0/6] Add TI PRUSS Local Interrupt Controller IRQChip driver Grzegorz Jaszczyk
2020-07-02 14:17 ` Grzegorz Jaszczyk
2020-07-02 14:17 ` [PATCHv3 1/6] dt-bindings: irqchip: Add PRU-ICSS interrupt controller bindings Grzegorz Jaszczyk
2020-07-02 14:17   ` Grzegorz Jaszczyk
2020-07-13 21:25   ` Rob Herring
2020-07-13 21:25     ` Rob Herring
2020-07-16  9:25     ` Grzegorz Jaszczyk
2020-07-16  9:25       ` Grzegorz Jaszczyk
2020-07-02 14:17 ` [PATCHv3 2/6] irqchip/irq-pruss-intc: Add a PRUSS irqchip driver for PRUSS interrupts Grzegorz Jaszczyk
2020-07-02 14:17   ` Grzegorz Jaszczyk
2020-07-02 17:24   ` Marc Zyngier
2020-07-02 17:24     ` Marc Zyngier
2020-07-03 14:28     ` Grzegorz Jaszczyk
2020-07-03 14:28       ` Grzegorz Jaszczyk
2020-07-04  9:39       ` Marc Zyngier
2020-07-04  9:39         ` Marc Zyngier
2020-07-05 13:26         ` Grzegorz Jaszczyk
2020-07-05 13:26           ` Grzegorz Jaszczyk
2020-07-05 20:45           ` Marc Zyngier
2020-07-05 20:45             ` Marc Zyngier
2020-07-08  7:04             ` Grzegorz Jaszczyk
2020-07-08  7:04               ` Grzegorz Jaszczyk
2020-07-08 10:47               ` Marc Zyngier
2020-07-08 10:47                 ` Marc Zyngier
2020-07-10 23:03                 ` Suman Anna
2020-07-10 23:03                   ` Suman Anna
2020-07-15 13:38                   ` Grzegorz Jaszczyk
2020-07-15 13:38                     ` Grzegorz Jaszczyk
2020-07-17 12:36                     ` Marc Zyngier
2020-07-17 12:36                       ` Marc Zyngier
2020-07-21  9:27                       ` Grzegorz Jaszczyk
2020-07-21  9:27                         ` Grzegorz Jaszczyk
2020-07-21 10:10                         ` Marc Zyngier
2020-07-21 10:10                           ` Marc Zyngier
2020-07-21 13:59                           ` Grzegorz Jaszczyk
2020-07-21 13:59                             ` Grzegorz Jaszczyk
2020-07-02 14:17 ` [PATCHv3 3/6] irqchip/irq-pruss-intc: Add support for shared and invalid interrupts Grzegorz Jaszczyk
2020-07-02 14:17   ` Grzegorz Jaszczyk
2020-07-02 17:44   ` Marc Zyngier
2020-07-02 17:44     ` Marc Zyngier
2020-07-10 20:59     ` Suman Anna
2020-07-10 20:59       ` Suman Anna
2020-07-17 11:02       ` Marc Zyngier
2020-07-17 11:02         ` Marc Zyngier
2020-07-25 15:57         ` Suman Anna
2020-07-25 15:57           ` Suman Anna
2020-07-25 16:27           ` Marc Zyngier
2020-07-25 16:27             ` Marc Zyngier
2020-07-25 16:39             ` Suman Anna
2020-07-25 16:39               ` Suman Anna
2020-07-02 14:17 ` [PATCHv3 4/6] irqchip/irq-pruss-intc: Implement irq_{get,set}_irqchip_state ops Grzegorz Jaszczyk
2020-07-02 14:17   ` [PATCHv3 4/6] irqchip/irq-pruss-intc: Implement irq_{get, set}_irqchip_state ops Grzegorz Jaszczyk
2020-07-02 17:54   ` [PATCHv3 4/6] irqchip/irq-pruss-intc: Implement irq_{get,set}_irqchip_state ops Marc Zyngier
2020-07-02 17:54     ` Marc Zyngier
2020-07-03 17:04     ` Grzegorz Jaszczyk
2020-07-03 17:04       ` Grzegorz Jaszczyk
2020-07-10 21:04       ` Suman Anna
2020-07-10 21:04         ` Suman Anna
2020-07-02 14:17 ` [PATCHv3 5/6] irqchip/irq-pruss-intc: Add support for ICSSG INTC on K3 SoCs Grzegorz Jaszczyk
2020-07-02 14:17   ` Grzegorz Jaszczyk
2020-07-02 17:59   ` Marc Zyngier [this message]
2020-07-02 17:59     ` Marc Zyngier
2020-07-03 17:05     ` Grzegorz Jaszczyk
2020-07-03 17:05       ` Grzegorz Jaszczyk
2020-07-10 21:13       ` Suman Anna
2020-07-10 21:13         ` Suman Anna
2020-07-02 14:17 ` [PATCHv3 6/6] irqchip/irq-pruss-intc: Add event mapping support Grzegorz Jaszczyk
2020-07-02 14:17   ` Grzegorz Jaszczyk
2020-07-02 16:24   ` Suman Anna
2020-07-02 16:24     ` Suman Anna
2020-07-05 13:39     ` Grzegorz Jaszczyk
2020-07-05 13:39       ` 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=d1b232c6f33a629117a2ecbd440622d0@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=robh+dt@kernel.org \
    --cc=s-anna@ti.com \
    --cc=tglx@linutronix.de \
    --cc=wmills@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.