From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: ye.xingchen@zte.com.cn, lee@kernel.org
Cc: agross@kernel.org, andersson@kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: qcom_rpm: use devm_platform_get_and_ioremap_resource()
Date: Wed, 8 Feb 2023 11:02:02 +0100 [thread overview]
Message-ID: <5d6c0f50-da59-8f4f-a04f-d24e3c0c2992@linaro.org> (raw)
In-Reply-To: <202302081734511884545@zte.com.cn>
On 8.02.2023 10:34, ye.xingchen@zte.com.cn wrote:
> 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: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
> drivers/mfd/qcom_rpm.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/mfd/qcom_rpm.c b/drivers/mfd/qcom_rpm.c
> index 8fea0e511550..086611322874 100644
> --- a/drivers/mfd/qcom_rpm.c
> +++ b/drivers/mfd/qcom_rpm.c
> @@ -530,7 +530,6 @@ static int qcom_rpm_probe(struct platform_device *pdev)
> {
> const struct of_device_id *match;
> struct device_node *syscon_np;
> - struct resource *res;
> struct qcom_rpm *rpm;
> u32 fw_version[3];
> int irq_wakeup;
> @@ -576,8 +575,7 @@ static int qcom_rpm_probe(struct platform_device *pdev)
> return -ENODEV;
> rpm->data = match->data;
>
> - res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> - rpm->status_regs = devm_ioremap_resource(&pdev->dev, res);
> + rpm->status_regs = devm_platform_get_and_ioremap_resource(pdev, 0, NULL);
> if (IS_ERR(rpm->status_regs))
> return PTR_ERR(rpm->status_regs);
> rpm->ctrl_regs = rpm->status_regs + 0x400;
next prev parent reply other threads:[~2023-02-08 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 9:34 ye.xingchen
2023-02-08 10:02 ` Konrad Dybcio [this message]
2023-03-03 8:22 ` Lee Jones
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=5d6c0f50-da59-8f4f-a04f-d24e3c0c2992@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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®