From: Jiri Slaby <jirislaby@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: aspeed: Switch to irq_domain_create_linear()
Date: Wed, 8 Jul 2026 12:09:52 +0200 [thread overview]
Message-ID: <bf103637-67ee-4821-ac77-60d8cb997027@kernel.org> (raw)
In-Reply-To: <20260708100454.00A621F000E9@smtp.kernel.org>
On 08. 07. 26, 12:04, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The commit message claims to use `of_fwnode_handle()`, but the code actually uses `dev_fwnode()`.
> --
>
> --- Patch [1]: [PATCH] PCI: aspeed: Switch to irq_domain_create_linear() ---
> commit aee46b37ad2da511a238368770cbd10115b36171
> Author: Jiri Slaby (SUSE) <jirislaby@kernel.org>
>
> PCI: aspeed: Switch to irq_domain_create_linear()
>
> This commit updates the driver to use the modern irq_domain_create_linear()
> function instead of the obsolete irq_domain_add_linear(). It adjusts the
> first parameter to pass a fwnode_handle rather than a device_node.
>
>> irq_domain_add_linear() is going away as being obsolete now. Switch to
>> the preferred irq_domain_create_linear(). That differs in the first
>> parameter: It takes more generic struct fwnode_handle instead of struct
>> device_node. Therefore, of_fwnode_handle() is added around the
>> parameter.
>>
>> Note some of the users can likely use dev->fwnode directly instead of
>> indirect of_fwnode_handle(dev->of_node). But dev->fwnode is not
>> guaranteed to be set for all, so this has to be investigated on case to
>> case basis (by people who can actually test with the HW).
>
>> diff --git a/drivers/pci/controller/pcie-aspeed.c b/drivers/pci/controller/pcie-aspeed.c
>> index 9aa9e14c61484..74b03a55643fa 100644
>> --- a/drivers/pci/controller/pcie-aspeed.c
>> +++ b/drivers/pci/controller/pcie-aspeed.c
>> @@ -725,10 +725,10 @@ static int aspeed_pcie_init_irq_domain(struct aspeed_pcie *pcie)
>> {
>> int ret;
>>
>> - pcie->intx_domain = irq_domain_add_linear(pcie->dev->of_node,
>> - PCI_NUM_INTX,
>> - &aspeed_intx_domain_ops,
>> - pcie);
>> + pcie->intx_domain = irq_domain_create_linear(dev_fwnode(pcie->dev),
>> + PCI_NUM_INTX,
>> + &aspeed_intx_domain_ops,
>> + pcie);
>
> [Severity: Medium]
> Does this code change contradict the commit message?
>
> The commit message explicitly mentions adding of_fwnode_handle() around the
> parameter and warns against using dev->fwnode directly since it is not
> guaranteed to be set.
Sashiko is right, I used a template for more patches...
> The patch uses dev_fwnode(pcie->dev) here, which fetches dev->fwnode, rather
> than using of_fwnode_handle(pcie->dev->of_node) as described. Should the
> implementation be updated to use of_fwnode_handle(), or does the commit
> message need to be revised to match this dev_fwnode() approach?
In this very case, dev_fwnode(pcie->dev) is used in
aspeed_pcie_msi_init(), called few lines below, so this is all right.
The commit log is obsolete in this case though. Do you want me to resubmit?
thanks,
--
js
suse labs
prev parent reply other threads:[~2026-07-08 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 9:58 [PATCH] PCI: aspeed: Switch to irq_domain_create_linear() Jiri Slaby (SUSE)
2026-07-08 10:04 ` sashiko-bot
2026-07-08 10:09 ` Jiri Slaby [this message]
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=bf103637-67ee-4821-ac77-60d8cb997027@kernel.org \
--to=jirislaby@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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