From: Sudeep Holla <sudeep.holla@arm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
arm-scmi@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: arm_scmi: Simplify printks with pOF format
Date: Fri, 12 Sep 2025 11:31:34 +0100 [thread overview]
Message-ID: <20250912-axiomatic-pumpkin-teal-9c9fbc@sudeepholla> (raw)
In-Reply-To: <c5df4196-b951-4f8e-b2ca-c63fba63d1ee@linaro.org>
On Fri, Sep 12, 2025 at 11:34:53AM +0200, Krzysztof Kozlowski wrote:
> On 12/09/2025 11:24, Krzysztof Kozlowski wrote:
> > Print full device node name with %pOF format, so the code will be a bit
> > simpler.
> >
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > ---
> > drivers/firmware/arm_scmi/bus.c | 13 ++++++-------
> > drivers/firmware/arm_scmi/transports/mailbox.c | 7 +++----
> > 2 files changed, 9 insertions(+), 11 deletions(-)
> >
> > diff --git a/drivers/firmware/arm_scmi/bus.c b/drivers/firmware/arm_scmi/bus.c
> > index 24e59ddf85e7..c7698cfaa4e8 100644
> > --- a/drivers/firmware/arm_scmi/bus.c
> > +++ b/drivers/firmware/arm_scmi/bus.c
> > @@ -401,8 +401,8 @@ static void scmi_device_release(struct device *dev)
> >
> > static void __scmi_device_destroy(struct scmi_device *scmi_dev)
> > {
> > - pr_debug("(%s) Destroying SCMI device '%s' for protocol 0x%x (%s)\n",
> > - of_node_full_name(scmi_dev->dev.parent->of_node),
> > + pr_debug("(%pOF) Destroying SCMI device '%s' for protocol 0x%x (%s)\n",
> > + scmi_dev->dev.parent->of_node,
> > dev_name(&scmi_dev->dev), scmi_dev->protocol_id,
> > scmi_dev->name);
>
> Heh, I misread the docs and see now in the testing that my patch changes
> the behavior. of_node_full_name() is just node name. pOF is full path.
>
> This might be desired or not...
>
That should be fine. I am in the process of changing this but happy to
take this for now. We may have to move to fwnode as we are in process of
adding ACPI support for this. Not finalised yet so it may be a while before
I tinker with it again.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-09-12 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 9:24 [PATCH] firmware: arm_scmi: Simplify printks with pOF format Krzysztof Kozlowski
2025-09-12 9:34 ` Krzysztof Kozlowski
2025-09-12 10:31 ` Sudeep Holla [this message]
2025-09-12 11:19 ` Sudeep Holla
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=20250912-axiomatic-pumpkin-teal-9c9fbc@sudeepholla \
--to=sudeep.holla@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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