From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: <linux-tegra@vger.kernel.org>,
Petlozu Pravareshwar <petlozup@nvidia.com>,
Kartik <kkartik@nvidia.com>, Jon Hunter <jonathanh@nvidia.com>
Subject: [PATCH 3/3] soc/tegra: fuse: Fix Tegra234 fuse size
Date: Tue, 6 Jun 2023 16:36:08 +0100 [thread overview]
Message-ID: <20230606153608.94289-3-jonathanh@nvidia.com> (raw)
In-Reply-To: <20230606153608.94289-1-jonathanh@nvidia.com>
From: Kartik <kkartik@nvidia.com>
The Tegra234 fuse size is incorrectly defined as 0x98c. The actual size
of the Tegra234 fuses is 0xf8c and so update the size of the Tegra234
fuses to fix this.
Signed-off-by: Kartik <kkartik@nvidia.com>
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
---
drivers/soc/tegra/fuse/fuse-tegra30.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/soc/tegra/fuse/fuse-tegra30.c b/drivers/soc/tegra/fuse/fuse-tegra30.c
index 932a03c64534..c759fb7c8adc 100644
--- a/drivers/soc/tegra/fuse/fuse-tegra30.c
+++ b/drivers/soc/tegra/fuse/fuse-tegra30.c
@@ -663,7 +663,7 @@ static const struct nvmem_keepout tegra234_fuse_keepouts[] = {
static const struct tegra_fuse_info tegra234_fuse_info = {
.read = tegra30_fuse_read,
- .size = 0x98c,
+ .size = 0xf90,
.spare = 0x280,
};
--
2.34.1
next prev parent reply other threads:[~2023-06-06 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 15:36 [PATCH 1/3] soc/tegra: pmc: Use debugfs_initialized() Jon Hunter
2023-06-06 15:36 ` [PATCH 2/3] soc/tegra: pmc: Add AON SW Wake support for Tegra234 Jon Hunter
2023-06-06 15:36 ` Jon Hunter [this message]
2023-06-08 16:33 ` [PATCH 1/3] soc/tegra: pmc: Use debugfs_initialized() Thierry Reding
2023-06-08 16:36 ` (subset) " 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=20230606153608.94289-3-jonathanh@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=kkartik@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=petlozup@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.