From: <ye.xingchen@zte.com.cn>
To: <vkoul@kernel.org>
Cc: <nandhini.srikandan@intel.com>, <rashmi.a@intel.com>,
<kishon@kernel.org>, <linux-phy@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH] phy: intel: Use devm_platform_get_and_ioremap_resource()
Date: Wed, 15 Feb 2023 11:25:07 +0800 (CST) [thread overview]
Message-ID: <202302151125076179524@zte.com.cn> (raw)
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/phy/intel/phy-intel-thunderbay-emmc.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/phy/intel/phy-intel-thunderbay-emmc.c b/drivers/phy/intel/phy-intel-thunderbay-emmc.c
index 593f6970b81e..4fe63240779f 100644
--- a/drivers/phy/intel/phy-intel-thunderbay-emmc.c
+++ b/drivers/phy/intel/phy-intel-thunderbay-emmc.c
@@ -461,7 +461,6 @@ static int thunderbay_emmc_phy_probe(struct platform_device *pdev)
struct device *dev = &pdev->dev;
const struct of_device_id *id;
struct phy *generic_phy;
- struct resource *res;
if (!dev->of_node)
return -ENODEV;
@@ -470,8 +469,7 @@ static int thunderbay_emmc_phy_probe(struct platform_device *pdev)
if (!tbh_phy)
return -ENOMEM;
- res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
- tbh_phy->reg_base = devm_ioremap_resource(&pdev->dev, res);
+ tbh_phy->reg_base = devm_platform_get_and_ioremap_resource(pdev, 0, NULL);
if (IS_ERR(tbh_phy->reg_base))
return PTR_ERR(tbh_phy->reg_base);
--
2.25.1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
reply other threads:[~2023-02-15 3:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202302151125076179524@zte.com.cn \
--to=ye.xingchen@zte.com.cn \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=nandhini.srikandan@intel.com \
--cc=rashmi.a@intel.com \
--cc=vkoul@kernel.org \
/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).