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 2/8] irqchip/al-fic: use %pOF and raise init log level
Date: Sun, 04 Oct 2026 12:25:47 -0400	[thread overview]
Message-ID: <4d4ec34125df2f2b3efc6adcbe9dc45f66b822e8.camel@rendec.net> (raw)
In-Reply-To: <20260927080637.27285-3-farbere@amazon.com>

On Sun, 2026-09-27 at 08:06 +0000, Eliav Farber wrote:
> Use %pOF in the driver's log messages, so that both the success and the
> error paths identify the specific FIC instance by its full devicetree
> path rather than by its bare node name, e.g.:
> 
>   /soc/interrupt-controller@fd803000 initialized successfully in Legacy mode (parent-irq=3)
> 
> A single controller is described by several FIC nodes that share the same
> bare node name (e.g. "interrupt-controller"), so the bare name cannot tell
> one instance from another. The full path includes the unit address and
> keeps the instances distinguishable.
> 
> While converting the parent-missing message, fix a grammar typo in it
> ("device require a parent" -> "device requires a parent").
> 
> Raise the successful-initialization message from pr_debug to pr_info, as
> this single boot-time printout is useful when dynamic debug is not enabled
> at this stage of boot.
> 
> Signed-off-by: Eliav Farber <farbere@amazon.com>
> ---
> v2: reworded to explain why %pOF matters (several nodes of one controller
>     share the same bare node name, so only the full path with the unit
>     address distinguishes them). Also switched from full_name string to
>     %pOF. No functional change from v1's "use full node name" patch beyond
>     the log level and the grammar fix.
> 
>  drivers/irqchip/irq-al-fic.c | 16 +++++++---------
>  1 file changed, 7 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/irqchip/irq-al-fic.c b/drivers/irqchip/irq-al-fic.c
> index 35581332b40e..760bd08dcff4 100644
> --- a/drivers/irqchip/irq-al-fic.c
> +++ b/drivers/irqchip/irq-al-fic.c
> @@ -216,8 +216,8 @@ static struct al_fic *al_fic_wire_init(struct device_node *node,
>  		goto err_free;
>  	}
>  
> -	pr_debug("%s initialized successfully in Legacy mode (parent-irq=%u)\n",
> -		 fic->name, parent_irq);
> +	pr_info("%pOF initialized successfully in Legacy mode (parent-irq=%u)\n",
> +		node, parent_irq);
>  
>  	return fic;
>  
> @@ -235,20 +235,19 @@ static int __init al_fic_init_dt(struct device_node *node,
>  	struct al_fic *fic;
>  
>  	if (!parent) {
> -		pr_err("%s: unsupported - device require a parent\n",
> -		       node->name);
> +		pr_err("%pOF: unsupported - device requires a parent\n", node);
>  		return -EINVAL;
>  	}
>  
>  	base = of_iomap(node, 0);
>  	if (!base) {
> -		pr_err("%s: fail to map memory\n", node->name);
> +		pr_err("%pOF: fail to map memory\n", node);
>  		return -ENOMEM;
>  	}
>  
>  	parent_irq = irq_of_parse_and_map(node, 0);
>  	if (!parent_irq) {
> -		pr_err("%s: fail to map irq\n", node->name);
> +		pr_err("%pOF: fail to map irq\n", node);
>  		ret = -EINVAL;
>  		goto err_unmap;
>  	}
> @@ -258,9 +257,8 @@ static int __init al_fic_init_dt(struct device_node *node,
>  			       node->name,
>  			       parent_irq);
>  	if (IS_ERR(fic)) {
> -		pr_err("%s: fail to initialize irqchip (%lu)\n",
> -		       node->name,
> -		       PTR_ERR(fic));
> +		pr_err("%pOF: fail to initialize irqchip (%lu)\n",
> +		       node, PTR_ERR(fic));
>  		ret = PTR_ERR(fic);
>  		goto err_irq_dispose;
>  	}

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

  reply	other threads:[~2026-10-04 16:25 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 [this message]
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
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=4d4ec34125df2f2b3efc6adcbe9dc45f66b822e8.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®