From: Andrew Lunn <andrew@lunn.ch>
To: "Marek Behún" <kabel@kernel.org>
Cc: "Pali Rohár" <pali@kernel.org>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] ARM: dts: mvebu: Add definitions for PCIe legacy INTx interrupts
Date: Thu, 7 Jul 2022 18:50:00 +0200 [thread overview]
Message-ID: <YscOuEUws9E9nnmm@lunn.ch> (raw)
In-Reply-To: <20220707163818.620ccb95@dellmb>
On Thu, Jul 07, 2022 at 04:38:18PM +0200, Marek Behún wrote:
> On Wed, 6 Jul 2022 22:53:46 +0200
> Andrew Lunn <andrew@lunn.ch> wrote:
>
> > On Wed, Jul 06, 2022 at 08:31:03PM +0200, Pali Rohár wrote:
> > > This patch series add definitions for PCIe legacy INTx interrupts into
> > > every DTS file used by the pci-mvebu.c controller driver.
> >
> > What you fail to explain in the commit message is Why?
> >
> > Andrew
>
> Hi Andrew,
>
> this is required for example in a scenario where a driver requests only
> one of the legacy interrupts (INTA). Without this change, the driver
> would be notified on events on all 4 (INTA, INTB, INTC, INTD), even if
> it requested only one of them.
O.K, so please add that to the commit message.
Is this purely theoretical, or are there known broken platforms out
there? Should a subset of these patches be added to stable?
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: "Marek Behún" <kabel@kernel.org>
Cc: "Pali Rohár" <pali@kernel.org>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] ARM: dts: mvebu: Add definitions for PCIe legacy INTx interrupts
Date: Thu, 7 Jul 2022 18:50:00 +0200 [thread overview]
Message-ID: <YscOuEUws9E9nnmm@lunn.ch> (raw)
In-Reply-To: <20220707163818.620ccb95@dellmb>
On Thu, Jul 07, 2022 at 04:38:18PM +0200, Marek Behún wrote:
> On Wed, 6 Jul 2022 22:53:46 +0200
> Andrew Lunn <andrew@lunn.ch> wrote:
>
> > On Wed, Jul 06, 2022 at 08:31:03PM +0200, Pali Rohár wrote:
> > > This patch series add definitions for PCIe legacy INTx interrupts into
> > > every DTS file used by the pci-mvebu.c controller driver.
> >
> > What you fail to explain in the commit message is Why?
> >
> > Andrew
>
> Hi Andrew,
>
> this is required for example in a scenario where a driver requests only
> one of the legacy interrupts (INTA). Without this change, the driver
> would be notified on events on all 4 (INTA, INTB, INTC, INTD), even if
> it requested only one of them.
O.K, so please add that to the commit message.
Is this purely theoretical, or are there known broken platforms out
there? Should a subset of these patches be added to stable?
Andrew
next prev parent reply other threads:[~2022-07-07 16:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 18:31 [PATCH 00/11] ARM: dts: mvebu: Add definitions for PCIe legacy INTx interrupts Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 01/11] ARM: dts: kirkwood: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 02/11] ARM: dts: dove: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 03/11] ARM: dts: armada-370.dtsi: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 04/11] ARM: dts: armada-xp-98dx3236.dtsi: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 05/11] ARM: dts: armada-xp-mv78230.dtsi: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 06/11] ARM: dts: armada-xp-mv78260.dtsi: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 07/11] ARM: dts: armada-xp-mv78460.dtsi: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 08/11] ARM: dts: armada-375.dtsi: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 09/11] ARM: dts: armada-380.dtsi: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 10/11] ARM: dts: armada-385.dtsi: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 18:31 ` [PATCH 11/11] ARM: dts: armada-39x.dtsi: " Pali Rohár
2022-07-06 18:31 ` Pali Rohár
2022-07-06 20:53 ` [PATCH 00/11] ARM: dts: mvebu: " Andrew Lunn
2022-07-06 20:53 ` Andrew Lunn
2022-07-07 14:38 ` Marek Behún
2022-07-07 14:38 ` Marek Behún
2022-07-07 16:50 ` Andrew Lunn [this message]
2022-07-07 16:50 ` Andrew Lunn
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=YscOuEUws9E9nnmm@lunn.ch \
--to=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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.