From: Kartik <kkartik@nvidia.com>
To: <thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<windhl@126.com>, <sumitg@nvidia.com>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH] soc/tegra: fuse: Export tegra_get_platform() & tegra_is_silicon()
Date: Mon, 26 Sep 2022 15:35:59 +0530 [thread overview]
Message-ID: <1664186759-9821-1-git-send-email-kkartik@nvidia.com> (raw)
Functions tegra_get_platform() and tegra_is_silicon() are required
for pre-silicon development to correctly identify the platform on
which the software is running.
Export tegra_get_platform() and tegra_is_silicon(), so they can be
used for pre-slicon development of device drivers and kernel space
tests.
Signed-off-by: Kartik <kkartik@nvidia.com>
---
drivers/soc/tegra/fuse/tegra-apbmisc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/soc/tegra/fuse/tegra-apbmisc.c b/drivers/soc/tegra/fuse/tegra-apbmisc.c
index 3351bd872ab2..904797f651a1 100644
--- a/drivers/soc/tegra/fuse/tegra-apbmisc.c
+++ b/drivers/soc/tegra/fuse/tegra-apbmisc.c
@@ -56,6 +56,7 @@ u8 tegra_get_platform(void)
{
return (tegra_read_chipid() >> 20) & 0xf;
}
+EXPORT_SYMBOL(tegra_get_platform);
bool tegra_is_silicon(void)
{
@@ -76,6 +77,7 @@ bool tegra_is_silicon(void)
*/
return true;
}
+EXPORT_SYMBOL(tegra_is_silicon);
u32 tegra_read_straps(void)
{
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-09-26 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 10:05 Kartik [this message]
2022-10-20 9:54 ` [PATCH] soc/tegra: fuse: Export tegra_get_platform() & tegra_is_silicon() Thierry Reding
2022-10-20 9:57 ` Arnd Bergmann
2022-10-20 14:06 ` Thierry Reding
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=1664186759-9821-1-git-send-email-kkartik@nvidia.com \
--to=kkartik@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sumitg@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=windhl@126.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