From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: Cai Huoqing <caihuoqing@baidu.com>
Cc: Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] media: rcar_jpu: Make use of the helper function devm_platform_ioremap_resource()
Date: Thu, 2 Sep 2021 11:54:22 +0100 [thread overview]
Message-ID: <f55b3276-a628-804f-b686-64dd0afcfab4@ideasonboard.com> (raw)
In-Reply-To: <20210901055532.7429-1-caihuoqing@baidu.com>
+Cc linux-renesas-soc
On 01/09/2021 06:55, Cai Huoqing wrote:
> Use the devm_platform_ioremap_resource() helper instead of
> calling platform_get_resource() and devm_ioremap_resource()
> separately
>
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> ---
> drivers/media/platform/rcar_jpu.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/media/platform/rcar_jpu.c b/drivers/media/platform/rcar_jpu.c
> index f57158bf2b11..56bb464629ed 100644
> --- a/drivers/media/platform/rcar_jpu.c
> +++ b/drivers/media/platform/rcar_jpu.c
> @@ -1590,7 +1590,6 @@ MODULE_DEVICE_TABLE(of, jpu_dt_ids);
> static int jpu_probe(struct platform_device *pdev)
> {
> struct jpu *jpu;
> - struct resource *res;
> int ret;
> unsigned int i;
>
> @@ -1603,8 +1602,7 @@ static int jpu_probe(struct platform_device *pdev)
> jpu->dev = &pdev->dev;
>
> /* memory-mapped registers */
> - res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> - jpu->regs = devm_ioremap_resource(&pdev->dev, res);
> + jpu->regs = devm_platform_ioremap_resource(pdev, 0);
> if (IS_ERR(jpu->regs))
> return PTR_ERR(jpu->regs);
>
>
prev parent reply other threads:[~2021-09-02 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 5:55 Cai Huoqing
2021-09-02 10:54 ` Kieran Bingham [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=f55b3276-a628-804f-b686-64dd0afcfab4@ideasonboard.com \
--to=kieran.bingham+renesas@ideasonboard.com \
--cc=caihuoqing@baidu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mikhail.ulyanov@cogentembedded.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
all inboxes | Powered by JetHome®