From: pdeschrijver@nvidia.com (Peter De Schrijver)
To: linux-arm-kernel@lists.infradead.org
Subject: a case for a common efuse API?
Date: Wed, 9 Jul 2014 14:49:07 +0300 [thread overview]
Message-ID: <20140709114907.GI23218@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <53BC4DD7.20906@codeaurora.org>
On Tue, Jul 08, 2014 at 10:00:23PM +0200, Stephen Boyd wrote:
>
> I added Tegra folks because I see that on Tegra this hardware is exposed
> via an SoC specific API, tegra_fuse_readl(), and an associated driver in
> drivers/misc/fuse/tegra/. Unfortunately I don't see any users of the API
> outside of the speedo code in the same directory and the sysfs bin
> attribute that may or may not be in use by some userspace code.
>
The SATA driver by Mikko Perttunen uses it. The driver hasn't been merged
though. There's some more upcoming work which makes use of it.
I don't think we can standardize much of an API for this. The data is
SoC specific, so the user will always need to have some SoC specific
knowledge on how to use it. In some cases we need it very early (eg. to
determine the correct Tegra20 revision). On Tegra20 we can't use the CPU
to read the fuses due to a hw bug, we have to use DMA, which means the
transaction becomes blocking and could fail due to lack of resources.
Cheers,
Peter.
next prev parent reply other threads:[~2014-07-09 11:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 20:00 a case for a common efuse API? Stephen Boyd
2014-07-08 20:26 ` Olof Johansson
2014-07-08 21:59 ` Bjorn Andersson
2014-07-09 7:24 ` Uwe Kleine-König
2014-07-09 7:50 ` Srinivas Kandagatla
2014-07-09 8:35 ` Maxime Ripard
2014-07-09 23:32 ` Stephen Boyd
2014-07-10 14:26 ` Maxime Ripard
2014-07-10 15:18 ` Alexandre Belloni
2014-07-10 15:41 ` Grygorii Strashko
2014-07-10 15:09 ` Maxime Ripard
2014-09-11 21:59 ` Stephen Boyd
2014-09-16 10:16 ` Maxime Ripard
2014-07-09 11:49 ` Peter De Schrijver [this message]
2014-07-21 15:51 ` Stephen Warren
2014-07-09 20:42 ` Tomasz Figa
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=20140709114907.GI23218@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).