Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Pablo Mazzini <pmazzini@gmail.com>,
	Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Chen-Yu Tsai <wens@kernel.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v3 0/3] pinctrl: sunxi: number the IRQ banks from the first one that has IRQs
Date: Mon, 26 Oct 2026 17:42:50 +0100	[thread overview]
Message-ID: <474d4ed0-b011-49dd-853e-697448382a0e@arm.com> (raw)
In-Reply-To: <20261025142412.112216-1-pmazzini@gmail.com>

Hi Pablo,

just some heads up about process:
- Please do not repost that quickly! The kernel doc says to wait at 
least a day, but that's only the lower limit, in case the series is 
almost ready and there were only minor comments from real(!) reviewers.
I would wait for a couple of days, after you got some proper reviews.
The reason is that reviews (by humans) take time, and it's not like 
people are bored waiting for some patches to look at. So they might be 
interrupted by something or need to do some checks and research. It's 
pretty bad if their effort is ambushed by a new revision, which now 
means they need to start over.
- Please do not repost just because Sashiko said something. Wait for a 
proper review. It's probably a good idea to acknowledge the comment, but 
don't just re-post then.
- Try to avoid posting inside the merge window. Depending on the 
subsystem and maintainer, your posts might just be ignored, because they 
might be busy fixing up conflicts. But more importantly: you are missing 
the correct base: you should always base your patches on an -rc1, unless 
being told otherwise explicitly. And since -rc1 won't be out till 
Sunday, this is not a good timing.

I will comment on the patch set separately.

Cheers,
Andre


On 10/25/26 15:24, Pablo Mazzini wrote:
> The DT pinctrl helper numbers the IRQ banks from PA, even when PA has
> none. The A523 got a DT interrupt for its unimplemented PA bank to work
> around that, the A733 would need the same, and on both PK is written
> past the end of irq_array.
> 
> Number the IRQ banks like the static drivers do, with irq_bank_map for
> the A523 and A733, and drop the PA interrupt from the binding and the
> A523 DT. The B288 (IRQ banks on PB, PD, PF and PG) then needs no
> made-up interrupt.
> 
> v3:
> - apply irq_bank_map to the A733 register layout too (Sashiko)
> 
> v2:
> - give the A523 and A733 an irq_bank_map, and drop the PA interrupt
>    from the binding and the A523 DT
> 
> Pablo Mazzini (3):
>    pinctrl: sunxi: dt: number the IRQ banks from the first one that has
>      IRQs
>    dt-bindings: pinctrl: sun55i-a523: one interrupt per implemented bank
>    arm64: dts: allwinner: a523: drop the PA GPIO interrupt
> 
>   .../bindings/pinctrl/allwinner,sun55i-a523-pinctrl.yaml   | 8 ++++----
>   arch/arm64/boot/dts/allwinner/sun55i-a523.dtsi            | 3 +--
>   drivers/pinctrl/sunxi/pinctrl-sun55i-a523.c               | 2 +-
>   drivers/pinctrl/sunxi/pinctrl-sun60i-a733.c               | 5 ++++-
>   drivers/pinctrl/sunxi/pinctrl-sunxi-dt.c                  | 8 +++-----
>   drivers/pinctrl/sunxi/pinctrl-sunxi.h                     | 7 ++++---
>   6 files changed, 17 insertions(+), 16 deletions(-)
> 
> 
> base-commit: 4f0dbdbdb3ad122e8bbfb1d722fd584bac7124db



  parent reply	other threads:[~2026-10-26 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25 14:24 [PATCH v3 0/3] pinctrl: sunxi: number the IRQ banks from the first one that has IRQs Pablo Mazzini
2026-10-25 14:24 ` [PATCH v3 1/3] pinctrl: sunxi: dt: " Pablo Mazzini
2026-10-25 14:24 ` [PATCH v3 2/3] dt-bindings: pinctrl: sun55i-a523: one interrupt per implemented bank Pablo Mazzini
2026-10-25 14:24 ` [PATCH v3 3/3] arm64: dts: allwinner: a523: drop the PA GPIO interrupt Pablo Mazzini
2026-10-26 16:42 ` Andre Przywara [this message]
2026-10-26 19:22   ` [PATCH v3 0/3] pinctrl: sunxi: number the IRQ banks from the first one that has IRQs Pablo Mazzini

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=474d4ed0-b011-49dd-853e-697448382a0e@arm.com \
    --to=andre.przywara@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=pmazzini@gmail.com \
    --cc=robh@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@kernel.org \
    /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