From: hkallweit1@gmail.com (Heiner Kallweit)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 1/2] soc: amlogic: meson-gx-pwrc-vpu: don't print error message on probe deferral
Date: Wed, 20 Dec 2017 20:07:50 +0100 [thread overview]
Message-ID: <943d2b32-86ad-d1d5-b798-12c3ae54a0fe@gmail.com> (raw)
The error message may be misleading in case of probe deferral
(happens on my Odroid-C2). Therefore don't print it in this case.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
drivers/soc/amlogic/meson-gx-pwrc-vpu.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/soc/amlogic/meson-gx-pwrc-vpu.c b/drivers/soc/amlogic/meson-gx-pwrc-vpu.c
index 2bdeebc48..3adb2f2ec 100644
--- a/drivers/soc/amlogic/meson-gx-pwrc-vpu.c
+++ b/drivers/soc/amlogic/meson-gx-pwrc-vpu.c
@@ -184,7 +184,8 @@ static int meson_gx_pwrc_vpu_probe(struct platform_device *pdev)
rstc = devm_reset_control_array_get(&pdev->dev, false, false);
if (IS_ERR(rstc)) {
- dev_err(&pdev->dev, "failed to get reset lines\n");
+ if (PTR_ERR(rstc) != -EPROBE_DEFER)
+ dev_err(&pdev->dev, "failed to get reset lines\n");
return PTR_ERR(rstc);
}
--
2.15.1
next reply other threads:[~2017-12-20 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 19:07 Heiner Kallweit [this message]
2017-12-20 19:11 ` [PATCH 2/2] soc: amlogic: meson-gx-pwrc-vpu: Heiner Kallweit
2017-12-20 19:15 ` [PATCH 1/2] soc: amlogic: meson-gx-pwrc-vpu: fix error on shutdown when domain is powered off Heiner Kallweit
2017-12-21 13:33 ` [PATCH 1/2] soc: amlogic: meson-gx-pwrc-vpu: don't print error message on probe deferral Neil Armstrong
2017-12-21 19:37 [PATCH 0/2] soc: amlogic: meson-gx-pwrc-vpu: fix two issues Heiner Kallweit
2017-12-21 19:40 ` [PATCH 1/2] soc: amlogic: meson-gx-pwrc-vpu: don't print error message on probe deferral Heiner Kallweit
2018-01-17 8:26 ` Neil Armstrong
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=943d2b32-86ad-d1d5-b798-12c3ae54a0fe@gmail.com \
--to=hkallweit1@gmail.com \
--cc=linus-amlogic@lists.infradead.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®