[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdafAWgt9A8km1zLZF9UawXkdqBOEVnMHiRjaF=2SeyhgA@mail.gmail.com>
Date: Mon, 7 Aug 2023 15:37:43 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Huqiang Qin <huqiang.qin@...ogic.com>
Cc: robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, neil.armstrong@...aro.org,
khilman@...libre.com, jbrunet@...libre.com,
martin.blumenstingl@...glemail.com, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org
Subject: Re: [PATCH V2 0/3] Add binding header file for GPIO interrupt of
Amlogic Meson-G12A
On Mon, Jul 24, 2023 at 8:02 AM Huqiang Qin <huqiang.qin@...ogic.com> wrote:
> After adding this binding header file, you can intuitively find
> the interrupt number corresponding to each GPIO, and apply it
> in the format of IRQID_XXX where it needs to be used.
(...)
> Huqiang Qin (3):
> dt-bindings: interrupt-controller: Add header file for Amlogic
> Meson-G12A SoCs
> pinctrl: Replace the IRQ number in the driver with the IRQID macro
> definition
> arm64: dts: Replace the IRQ number with the IRQID macro definition
Neil wrote:
> What's the best way to apply this patchset ?
I just applied all three to the pin control tree.
I could have applied just the two first and then offered an
immutable branch. But eh... too much work for too low risk.
Better to just apply it and hope all works out. If it explodes
I just back out and figure something like the above.
Yours,
Linus Walleij
Powered by blists - more mailing lists