From: Yan Zhen <yanzhen@vivo.com>
To: matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, opensource.kernel@vivo.com,
Yan Zhen <yanzhen@vivo.com>
Subject: [PATCH v3] soc: mediatek: mtk-mmsys: Simplify with dev_err_probe()
Date: Mon, 2 Sep 2024 13:30:01 +0800 [thread overview]
Message-ID: <20240902053001.930379-1-yanzhen@vivo.com> (raw)
Use dev_err_probe() to simplify the error path and unify a
message template.
Using this helper is totally fine even if err is known to never
be -EPROBE_DEFER.
The benefit compared to a normal dev_err() is the standardized format
of the error code, it being emitted symbolically and the fact that
the error code is returned which allows more compact error paths.
Signed-off-by: Yan Zhen <yanzhen@vivo.com>
---
Changes in v3:
- Modify the message.
- Add the '\n' at the end of the string.
drivers/soc/mediatek/mtk-mmsys.c | 15 ++++++---------
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/drivers/soc/mediatek/mtk-mmsys.c b/drivers/soc/mediatek/mtk-mmsys.c
index 938240714e54..170319163c28 100644
--- a/drivers/soc/mediatek/mtk-mmsys.c
+++ b/drivers/soc/mediatek/mtk-mmsys.c
@@ -397,11 +397,9 @@ static int mtk_mmsys_probe(struct platform_device *pdev)
return -ENOMEM;
mmsys->regs = devm_platform_ioremap_resource(pdev, 0);
- if (IS_ERR(mmsys->regs)) {
- ret = PTR_ERR(mmsys->regs);
- dev_err(dev, "Failed to ioremap mmsys registers: %d\n", ret);
- return ret;
- }
+ if (IS_ERR(mmsys->regs))
+ return dev_err_probe(dev, PTR_ERR(mmsys->regs),
+ "Failed to ioremap mmsys registers\n");
mmsys->data = of_device_get_match_data(&pdev->dev);
@@ -413,10 +411,9 @@ static int mtk_mmsys_probe(struct platform_device *pdev)
mmsys->rcdev.ops = &mtk_mmsys_reset_ops;
mmsys->rcdev.of_node = pdev->dev.of_node;
ret = devm_reset_controller_register(&pdev->dev, &mmsys->rcdev);
- if (ret) {
- dev_err(&pdev->dev, "Couldn't register mmsys reset controller: %d\n", ret);
- return ret;
- }
+ if (ret)
+ dev_err_probe(&pdev->dev, ret,
+ "Couldn't register mmsys reset controller\n");
}
/* CMDQ is optional */
--
2.34.1
next reply other threads:[~2024-09-02 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 5:30 Yan Zhen [this message]
2024-09-02 15:35 ` [PATCH v3] soc: mediatek: mtk-mmsys: Simplify with dev_err_probe() Matthias Brugger
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=20240902053001.930379-1-yanzhen@vivo.com \
--to=yanzhen@vivo.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=opensource.kernel@vivo.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