From: <Claudiu.Beznea@microchip.com>
To: <ye.xingchen@zte.com.cn>, <sre@kernel.org>
Cc: <Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<linux-pm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] power: reset: at91-sama5d2_shdwc: Use devm_platform_get_and_ioremap_resource()
Date: Thu, 16 Feb 2023 10:01:41 +0000 [thread overview]
Message-ID: <7ba1360a-74f4-46dc-ad1e-f81c833840ac@microchip.com> (raw)
In-Reply-To: <202302151450594333186@zte.com.cn>
On 15.02.2023 08:50, ye.xingchen@zte.com.cn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> From: Ye Xingchen <ye.xingchen@zte.com.cn>
>
> 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.
>
> Signed-off-by: Ye Xingchen <ye.xingchen@zte.com.cn>
Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> ---
> drivers/power/reset/at91-sama5d2_shdwc.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/power/reset/at91-sama5d2_shdwc.c b/drivers/power/reset/at91-sama5d2_shdwc.c
> index d8ecffe72f16..3142ac53782b 100644
> --- a/drivers/power/reset/at91-sama5d2_shdwc.c
> +++ b/drivers/power/reset/at91-sama5d2_shdwc.c
> @@ -331,7 +331,6 @@ static const struct of_device_id at91_pmc_ids[] = {
>
> static int __init at91_shdwc_probe(struct platform_device *pdev)
> {
> - struct resource *res;
> const struct of_device_id *match;
> struct device_node *np;
> u32 ddr_type;
> @@ -349,8 +348,7 @@ static int __init at91_shdwc_probe(struct platform_device *pdev)
>
> platform_set_drvdata(pdev, at91_shdwc);
>
> - res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> - at91_shdwc->shdwc_base = devm_ioremap_resource(&pdev->dev, res);
> + at91_shdwc->shdwc_base = devm_platform_get_and_ioremap_resource(pdev, 0, NULL);
> if (IS_ERR(at91_shdwc->shdwc_base))
> return PTR_ERR(at91_shdwc->shdwc_base);
>
> --
> 2.25.1
prev parent reply other threads:[~2023-02-16 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 6:50 ye.xingchen
2023-02-16 10:01 ` Claudiu.Beznea [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=7ba1360a-74f4-46dc-ad1e-f81c833840ac@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.org \
--cc=ye.xingchen@zte.com.cn \
/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®