mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kartik <kkartik@nvidia.com>
To: <thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
	<digetx@gmail.com>, <kkartik@nvidia.com>, <windhl@126.com>,
	<ndesaulniers@google.com>, <nathan@kernel.org>,
	<skamble@nvidia.com>, <linux-tegra@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] Tegra Fuse Nvmem Interface Update
Date: Fri, 7 Oct 2022 15:21:05 +0530	[thread overview]
Message-ID: <1665136268-29494-1-git-send-email-kkartik@nvidia.com> (raw)

This series of patches make various enhancements and updates to Tegra
Fuse nvmem interface, that includes:
 1. Using per SOC nvmem cells. As, tegra fuse availability and size
    can vary from once SOC to another.
 2. Fixes an issue with nvmem binary interface which could result in RAS
    errors.
 3. Add opt-dla-disable nvmem cell for Tegra234 SOC, this is used by
    Tegra Deep Learning Accelerator driver to correctly identify internal
    and production boards.

NOTE: Patch "soc/tegra: fuse: use soc specific nvmem cells" had already
been sent out for review. Please ignore the previous patch.

Kartik (3):
  soc/tegra: fuse: use soc specific nvmem cells
  soc/tegra: fuse: add fuse nvmem keepout list
  soc/tegra: fuse: add opt-dla-disable nvmem cell

 drivers/soc/tegra/fuse/fuse-tegra.c   | 112 +---------
 drivers/soc/tegra/fuse/fuse-tegra30.c | 294 +++++++++++++++++++++++++-
 drivers/soc/tegra/fuse/fuse.h         |   4 +
 3 files changed, 299 insertions(+), 111 deletions(-)

-- 
2.17.1


             reply	other threads:[~2022-10-07  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07  9:51 Kartik [this message]
2022-10-07  9:51 ` [PATCH 1/3] soc/tegra: fuse: use soc specific nvmem cells Kartik
2022-10-07  9:51 ` [PATCH 2/3] soc/tegra: fuse: add fuse nvmem keepout list Kartik
2022-10-07  9:51 ` [PATCH 3/3] soc/tegra: fuse: add opt-dla-disable nvmem cell Kartik

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=1665136268-29494-1-git-send-email-kkartik@nvidia.com \
    --to=kkartik@nvidia.com \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=skamble@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

all inboxes | Powered by JetHome®