linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Li Zetao <lizetao1@huawei.com>
Cc: airlied@gmail.com, daniel@ffwll.ch, michal.simek@amd.com,
	dri-devel@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next] drm: xlnx: zynqmp_dpsub: Use devm_platform_ioremap_resource_byname()
Date: Wed, 2 Aug 2023 00:47:29 +0300	[thread overview]
Message-ID: <20230801214729.GF8578@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20230801083220.3892883-1-lizetao1@huawei.com>

Hi Li,

Thank you for the patch.

On Tue, Aug 01, 2023 at 04:32:20PM +0800, Li Zetao wrote:
> Convert platform_get_resource_byname() + devm_ioremap_resource() to a
> single call to devm_platform_ioremap_resource_byname(), as this is
> exactly what this function does.
> 
> Signed-off-by: Li Zetao <lizetao1@huawei.com>

Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> ---
>  drivers/gpu/drm/xlnx/zynqmp_disp.c | 10 +++-------
>  1 file changed, 3 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xlnx/zynqmp_disp.c b/drivers/gpu/drm/xlnx/zynqmp_disp.c
> index 3b87eebddc97..2b731f3eea54 100644
> --- a/drivers/gpu/drm/xlnx/zynqmp_disp.c
> +++ b/drivers/gpu/drm/xlnx/zynqmp_disp.c
> @@ -1228,7 +1228,6 @@ int zynqmp_disp_probe(struct zynqmp_dpsub *dpsub)
>  {
>  	struct platform_device *pdev = to_platform_device(dpsub->dev);
>  	struct zynqmp_disp *disp;
> -	struct resource *res;
>  	int ret;
>  
>  	disp = kzalloc(sizeof(*disp), GFP_KERNEL);
> @@ -1238,22 +1237,19 @@ int zynqmp_disp_probe(struct zynqmp_dpsub *dpsub)
>  	disp->dev = &pdev->dev;
>  	disp->dpsub = dpsub;
>  
> -	res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "blend");
> -	disp->blend.base = devm_ioremap_resource(disp->dev, res);
> +	disp->blend.base = devm_platform_ioremap_resource_byname(pdev, "blend");
>  	if (IS_ERR(disp->blend.base)) {
>  		ret = PTR_ERR(disp->blend.base);
>  		goto error;
>  	}
>  
> -	res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "av_buf");
> -	disp->avbuf.base = devm_ioremap_resource(disp->dev, res);
> +	disp->avbuf.base = devm_platform_ioremap_resource_byname(pdev, "av_buf");
>  	if (IS_ERR(disp->avbuf.base)) {
>  		ret = PTR_ERR(disp->avbuf.base);
>  		goto error;
>  	}
>  
> -	res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "aud");
> -	disp->audio.base = devm_ioremap_resource(disp->dev, res);
> +	disp->audio.base = devm_platform_ioremap_resource_byname(pdev, "aud");
>  	if (IS_ERR(disp->audio.base)) {
>  		ret = PTR_ERR(disp->audio.base);
>  		goto error;

-- 
Regards,

Laurent Pinchart

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-08-01 21:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01  8:32 [PATCH -next] drm: xlnx: zynqmp_dpsub: Use devm_platform_ioremap_resource_byname() Li Zetao
2023-08-01 21:47 ` Laurent Pinchart [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=20230801214729.GF8578@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lizetao1@huawei.com \
    --cc=michal.simek@amd.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;
as well as URLs for NNTP newsgroup(s).