From: Wei Ni <wni@nvidia.com>
To: <thierry.reding@gmail.com>, <swarren@wwwdotorg.org>
Cc: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Wei Ni <wni@nvidia.com>
Subject: [PATCH] soc/tegra: fuse: enable nvidia,tegra114-efuse entry for Tegra132
Date: Thu, 5 May 2016 14:12:07 +0800 [thread overview]
Message-ID: <1462428727-28080-1-git-send-email-wni@nvidia.com> (raw)
In the Tegra132 DTS file, the compatible of fuse node was
set as "nvidia,tegra124-efuse", because the fuse in Tegra132
is same as Tegra124, they are compatible.
But the fuse driver only defined this entry under the
CONFIG_ARCH_TEGRA_124_SOC, so the Tegra132 builds can't find
this entry.
Define this entry under
"CONFIG_ARCH_TEGRA_124_SOC || CONFIG_ARCH_TEGRA_132_SOC"
to fix this problem.
Signed-off-by: Wei Ni <wni@nvidia.com>
---
drivers/soc/tegra/fuse/fuse-tegra.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/soc/tegra/fuse/fuse-tegra.c b/drivers/soc/tegra/fuse/fuse-tegra.c
index de2c1bfe28b5..1b0a1e13577e 100644
--- a/drivers/soc/tegra/fuse/fuse-tegra.c
+++ b/drivers/soc/tegra/fuse/fuse-tegra.c
@@ -104,10 +104,8 @@ static const struct of_device_id tegra_fuse_match[] = {
#ifdef CONFIG_ARCH_TEGRA_210_SOC
{ .compatible = "nvidia,tegra210-efuse", .data = &tegra210_fuse_soc },
#endif
-#ifdef CONFIG_ARCH_TEGRA_132_SOC
+#if defined CONFIG_ARCH_TEGRA_124_SOC || defined CONFIG_ARCH_TEGRA_132_SOC
{ .compatible = "nvidia,tegra132-efuse", .data = &tegra124_fuse_soc },
-#endif
-#ifdef CONFIG_ARCH_TEGRA_124_SOC
{ .compatible = "nvidia,tegra124-efuse", .data = &tegra124_fuse_soc },
#endif
#ifdef CONFIG_ARCH_TEGRA_114_SOC
--
1.9.1
reply other threads:[~2016-05-05 6:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1462428727-28080-1-git-send-email-wni@nvidia.com \
--to=wni@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®