From: Andi Shyti <andi.shyti@kernel.org>
To: ye.xingchen@zte.com.cn
Cc: wsa+renesas@sang-engineering.com,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: wmt: Use devm_platform_get_and_ioremap_resource()
Date: Sat, 10 Jun 2023 15:42:53 +0200 [thread overview]
Message-ID: <20230610134253.jphhhsfgxixtildd@intel.intel> (raw)
In-Reply-To: <202301281451442100100@zte.com.cn>
Hi Ye,
On Sat, Jan 28, 2023 at 02:51:44PM +0800, 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>
> ---
> drivers/i2c/busses/i2c-wmt.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-wmt.c b/drivers/i2c/busses/i2c-wmt.c
> index 7d4bc8736079..4a3e3985e418 100644
> --- a/drivers/i2c/busses/i2c-wmt.c
> +++ b/drivers/i2c/busses/i2c-wmt.c
> @@ -372,7 +372,6 @@ static int wmt_i2c_probe(struct platform_device *pdev)
> struct device_node *np = pdev->dev.of_node;
> struct wmt_i2c_dev *i2c_dev;
> struct i2c_adapter *adap;
> - struct resource *res;
> int err;
> u32 clk_rate;
>
> @@ -380,8 +379,7 @@ static int wmt_i2c_probe(struct platform_device *pdev)
> if (!i2c_dev)
> return -ENOMEM;
>
> - res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> - i2c_dev->base = devm_ioremap_resource(&pdev->dev, res);
> + i2c_dev->base = devm_platform_get_and_ioremap_resource(pdev, 0, NULL);
It's also a cleaner way to handle the error when res is NULL.
Reviewed-by: Andi Shyti <andi.shyti@kernel.org>
Thanks,
Andi
> if (IS_ERR(i2c_dev->base))
> return PTR_ERR(i2c_dev->base);
>
> --
> 2.25.1
next prev parent reply other threads:[~2023-06-10 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 6:51 [PATCH] i2c: wmt: Use devm_platform_get_and_ioremap_resource() ye.xingchen
2023-06-10 13:42 ` Andi Shyti [this message]
2023-06-14 8:41 ` Wolfram Sang
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=20230610134253.jphhhsfgxixtildd@intel.intel \
--to=andi.shyti@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--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