mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Radu Rendec <radu@rendec.net>
To: Eliav Farber <farbere@amazon.com>,
	Thomas Gleixner <tglx@kernel.org>,
	 Talel Shenhar <talel@amazon.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 7/8] irqchip/al-fic: add support for FIC v3
Date: Sun, 04 Oct 2026 21:04:00 -0400	[thread overview]
Message-ID: <4eac1b35110b7e642d4a4c6f4856ac4db428170a.camel@rendec.net> (raw)
In-Reply-To: <20260927080637.27285-8-farbere@amazon.com>

On Sun, 2026-09-27 at 08:06 +0000, Eliav Farber wrote:
> FIC v3 reports version id 2 in the control register version field. It
> exposes the same info/error/fatal groups as v2, so add the version to
> enum al_fic_version; the existing "version_id > V1" handling masks the
> error and fatal groups at init as for v2.
> 
> Unlike v2, the v3 error and fatal mask registers read back correctly, so
> v3 does not need the v2 mask_cache workaround: the workaround is gated on
> AL_FIC_VERSION_V2 and v3 keeps the register-seeded mask_cache.
> 
> Signed-off-by: Eliav Farber <farbere@amazon.com>
> ---
> v2: the "erratum fixed from v3 onwards" code comment moved here (where
>     AL_FIC_VERSION_V3 is introduced) from the FIC v2 patch, so the claim
>     that v3 keeps the register-seeded mask_cache has its code in the same
>     commit.
> 
>  drivers/irqchip/irq-al-fic.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/irqchip/irq-al-fic.c b/drivers/irqchip/irq-al-fic.c
> index 35e366b4da30..322e41ffa2fa 100644
> --- a/drivers/irqchip/irq-al-fic.c
> +++ b/drivers/irqchip/irq-al-fic.c
> @@ -44,6 +44,7 @@ enum al_fic_state {
>  enum al_fic_version {
>  	AL_FIC_VERSION_V1,
>  	AL_FIC_VERSION_V2,
> +	AL_FIC_VERSION_V3,
>  };
>  
>  enum al_fic_id {
> @@ -177,8 +178,8 @@ static int al_fic_register(struct device_node *node,
>  	 * register. Suppress the seeding there and set mask_cache below to
>  	 * match what al_fic_wire_init() programmed.
>  	 *
> -	 * The info mask register is not affected, so the info output keeps the
> -	 * register-seeded mask_cache.
> +	 * The info mask register is not affected, and the erratum is fixed
> +	 * from v3 onwards, so those paths keep the register-seeded mask_cache.
>  	 */
>  	if (version == AL_FIC_VERSION_V2 &&
>  	    (fic_id == AL_FIC_ID_ERROR || fic_id == AL_FIC_ID_FATAL))

Reviewed-by: Radu Rendec <radu@rendec.net>

  reply	other threads:[~2026-10-05  1:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27  8:06 [PATCH v2 0/8] irqchip/al-fic: shared parent IRQ, error/fatal outputs and affinity Eliav Farber
2026-09-27  8:06 ` [PATCH v2 1/8] irqchip/al-fic: fix argument alignment and a repeated word Eliav Farber
2026-10-04 16:15   ` Radu Rendec
2026-09-27  8:06 ` [PATCH v2 2/8] irqchip/al-fic: use %pOF and raise init log level Eliav Farber
2026-10-04 16:25   ` Radu Rendec
2026-09-27  8:06 ` [PATCH v2 3/8] irqchip/al-fic: keep the device_node instead of a cached name string Eliav Farber
2026-10-04 17:40   ` Radu Rendec
2026-10-05 11:17     ` Farber, Eliav
2026-09-27  8:06 ` [PATCH v2 4/8] irqchip/al-fic: switch to shared parent interrupt Eliav Farber
2026-10-04 19:30   ` Radu Rendec
2026-10-05 11:18     ` Farber, Eliav
2026-09-27  8:06 ` [PATCH v2 5/8] dt-bindings: interrupt-controller: amazon,al-fic: add mask selection Eliav Farber
2026-09-28 16:50   ` Conor Dooley
2026-10-04 21:06   ` Radu Rendec
2026-09-27  8:06 ` [PATCH v2 6/8] irqchip/al-fic: support error and fatal outputs and FIC v2 Eliav Farber
2026-10-05  1:01   ` Radu Rendec
2026-10-05 11:19     ` Farber, Eliav
2026-09-27  8:06 ` [PATCH v2 7/8] irqchip/al-fic: add support for FIC v3 Eliav Farber
2026-10-05  1:04   ` Radu Rendec [this message]
2026-09-27  8:06 ` [PATCH v2 8/8] irqchip/al-fic: add irq_set_affinity callback Eliav Farber
2026-10-05  1:25   ` Radu Rendec
2026-10-05 11:20     ` Farber, Eliav

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=4eac1b35110b7e642d4a4c6f4856ac4db428170a.camel@rendec.net \
    --to=radu@rendec.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=farbere@amazon.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=talel@amazon.com \
    --cc=tglx@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

all inboxes | Powered by JetHome®