From: Yangtao Li <frank.li@vivo.com>
To: Daniele Alessandrelli <daniele.alessandrelli@intel.com>,
Declan Murphy <declan.murphy@intel.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: Yangtao Li <frank.li@vivo.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/5] crypto: keembay - Convert to devm_platform_ioremap_resource()
Date: Wed, 5 Jul 2023 15:21:55 +0800 [thread overview]
Message-ID: <20230705072159.77221-2-frank.li@vivo.com> (raw)
In-Reply-To: <20230705072159.77221-1-frank.li@vivo.com>
Use devm_platform_ioremap_resource() to simplify code.
Signed-off-by: Yangtao Li <frank.li@vivo.com>
---
drivers/crypto/intel/keembay/keembay-ocs-hcu-core.c | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/crypto/intel/keembay/keembay-ocs-hcu-core.c b/drivers/crypto/intel/keembay/keembay-ocs-hcu-core.c
index d4bcbed1f546..51a6de6294cb 100644
--- a/drivers/crypto/intel/keembay/keembay-ocs-hcu-core.c
+++ b/drivers/crypto/intel/keembay/keembay-ocs-hcu-core.c
@@ -1170,7 +1170,6 @@ static int kmb_ocs_hcu_probe(struct platform_device *pdev)
{
struct device *dev = &pdev->dev;
struct ocs_hcu_dev *hcu_dev;
- struct resource *hcu_mem;
int rc;
hcu_dev = devm_kzalloc(dev, sizeof(*hcu_dev), GFP_KERNEL);
@@ -1184,14 +1183,7 @@ static int kmb_ocs_hcu_probe(struct platform_device *pdev)
if (rc)
return rc;
- /* Get the memory address and remap. */
- hcu_mem = platform_get_resource(pdev, IORESOURCE_MEM, 0);
- if (!hcu_mem) {
- dev_err(dev, "Could not retrieve io mem resource.\n");
- return -ENODEV;
- }
-
- hcu_dev->io_base = devm_ioremap_resource(dev, hcu_mem);
+ hcu_dev->io_base = devm_platform_ioremap_resource(pdev, 0);
if (IS_ERR(hcu_dev->io_base))
return PTR_ERR(hcu_dev->io_base);
--
2.39.0
next prev parent reply other threads:[~2023-07-05 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 7:21 [PATCH 1/5] crypto: omap-des - Use devm_platform_get_and_ioremap_resource() Yangtao Li
2023-07-05 7:21 ` Yangtao Li [this message]
2023-07-05 7:21 ` [PATCH 3/5] crypto: atmel-aes " Yangtao Li
2023-07-05 7:21 ` [PATCH 4/5] crypto: atmel-sha " Yangtao Li
2023-07-05 7:21 ` [PATCH 5/5] crypto: atmel-tdes " Yangtao Li
2023-07-14 8:58 ` [PATCH 1/5] crypto: omap-des " Herbert Xu
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=20230705072159.77221-2-frank.li@vivo.com \
--to=frank.li@vivo.com \
--cc=daniele.alessandrelli@intel.com \
--cc=davem@davemloft.net \
--cc=declan.murphy@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®