From: Henrik Grimler <henrik@grimler.se>
To: krzysztof.kozlowski@canonical.com, chanho61.park@samsung.com,
semen.protsenko@linaro.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Henrik Grimler <henrik@grimler.se>
Subject: [PATCH 2/2] soc: samsung: exynos-chipid: be more informative when soc is unknown
Date: Sun, 31 Oct 2021 17:56:45 +0100 [thread overview]
Message-ID: <20211031165645.1182368-2-henrik@grimler.se> (raw)
In-Reply-To: <20211031165645.1182368-1-henrik@grimler.se>
Print the obtained product id that is incompatible.
Signed-off-by: Henrik Grimler <henrik@grimler.se>
---
drivers/soc/samsung/exynos-chipid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/soc/samsung/exynos-chipid.c b/drivers/soc/samsung/exynos-chipid.c
index 7fe44f71920d..885d578fd005 100644
--- a/drivers/soc/samsung/exynos-chipid.c
+++ b/drivers/soc/samsung/exynos-chipid.c
@@ -132,7 +132,7 @@ static int exynos_chipid_probe(struct platform_device *pdev)
"%x", soc_info.revision);
soc_dev_attr->soc_id = product_id_to_soc_id(soc_info.product_id);
if (!soc_dev_attr->soc_id) {
- pr_err("Unknown SoC\n");
+ pr_err("Exynos: Unknown SoC: 0x%x\n", soc_info.product_id);
return -ENODEV;
}
--
2.33.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-31 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 16:56 [PATCH 1/2] soc: samsung: exynos-chipid: print entire PRO_ID reg when probing Henrik Grimler
2021-10-31 16:56 ` Henrik Grimler [this message]
2021-10-31 20:35 ` [PATCH 2/2] soc: samsung: exynos-chipid: be more informative when soc is unknown Krzysztof Kozlowski
2021-10-31 20:35 ` [PATCH 1/2] soc: samsung: exynos-chipid: print entire PRO_ID reg when probing Krzysztof Kozlowski
2021-10-31 21:29 ` Henrik Grimler
2021-11-01 7:43 ` Krzysztof Kozlowski
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=20211031165645.1182368-2-henrik@grimler.se \
--to=henrik@grimler.se \
--cc=chanho61.park@samsung.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=semen.protsenko@linaro.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