From: "Krzysztof Wilczyński" <kw@linux.com>
To: Yangtao Li <frank.li@vivo.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Yang Li <yang.lee@linux.alibaba.com>
Subject: Re: [PATCH 3/4] PCI: v3-semi: Use devm_platform_get_and_ioremap_resource()
Date: Fri, 7 Jul 2023 03:55:11 +0900 [thread overview]
Message-ID: <20230706185511.GA3380331@rocinante> (raw)
In-Reply-To: <20230706092047.18599-3-frank.li@vivo.com>
[+Cc Yang]
Hello,
> Convert platform_get_resource(), devm_ioremap_resource() to a single
> call to devm_platform_get_and_ioremap_resource(), as this is exactly
> what this function does.
A very similar series was posted a while ago. Patches 1, 2 and 4 in this
series are identical, except for this patch, which adds one more very nice
refactoring,
The other series:
https://lore.kernel.org/linux-pci/20230626110226.GA569947@rocinante
What I can do would be to pick this patch and squash it with the other ones
that are already applied. I will then attribute both you and Yang Li as
the authors. Let me know if this is fine with you, Yangtao and Yang.
That said...
> diff --git a/drivers/pci/controller/pci-v3-semi.c b/drivers/pci/controller/pci-v3-semi.c
> index ca44b0c83d1b..0f993328dba2 100644
> --- a/drivers/pci/controller/pci-v3-semi.c
> +++ b/drivers/pci/controller/pci-v3-semi.c
> @@ -736,8 +736,7 @@ static int v3_pci_probe(struct platform_device *pdev)
> return ret;
> }
>
> - regs = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> - v3->base = devm_ioremap_resource(dev, regs);
> + v3->base = devm_platform_get_and_ioremap_resource(pdev, 0, &res);
Are you sure about the variable name here? This might be a small copy-and-paste
mistake that snuck up here. Have a closer look, or better yet, try to compile
and test this. :)
> - regs = platform_get_resource(pdev, IORESOURCE_MEM, 1);
> + v3->config_base = devm_platform_get_and_ioremap_resource(pdev, 1, &res);
Same as above.
> + if (IS_ERR(v3->config_base))
> + return PTR_ERR(v3->config_base);
> if (resource_size(regs) != SZ_16M) {
> dev_err(dev, "config mem is not 16MB!\n");
> return -EINVAL;
> }
> v3->config_mem = regs->start;
> - v3->config_base = devm_ioremap_resource(dev, regs);
> - if (IS_ERR(v3->config_base))
> - return PTR_ERR(v3->config_base);
This could be made such that the assignments are together.
Krzysztof
next prev parent reply other threads:[~2023-07-06 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 9:20 [PATCH 1/4] PCI: imx6: Use devm_platform_get_and_ioremap_resource() Yangtao Li
2023-07-06 9:20 ` [PATCH 2/4] PCI: rcar-gen2: " Yangtao Li
2023-07-06 9:30 ` Geert Uytterhoeven
2023-07-06 9:20 ` [PATCH 3/4] PCI: v3-semi: " Yangtao Li
2023-07-06 18:04 ` Linus Walleij
2023-07-06 18:55 ` Krzysztof Wilczyński [this message]
2023-07-07 7:39 ` Yangtao Li
2023-07-06 9:20 ` [PATCH 4/4] PCI: xgene-msi: " Yangtao Li
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=20230706185511.GA3380331@rocinante \
--to=kw@linux.com \
--cc=bhelgaas@google.com \
--cc=frank.li@vivo.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=yang.lee@linux.alibaba.com \
/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