From: robh@kernel.org (Rob Herring)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 1/4] dt-bindings: nvmem: Describe the Amlogic Meson6/Meson8/Meson8b efuse
Date: Tue, 10 Oct 2017 13:56:56 -0500 [thread overview]
Message-ID: <20171010185656.pf4jybiohcywp7wj@rob-hp-laptop> (raw)
In-Reply-To: <20171002232804.20042-2-martin.blumenstingl@googlemail.com>
On Tue, Oct 03, 2017 at 01:28:01AM +0200, Martin Blumenstingl wrote:
> Amlogic Meson6, Meson8 and Meson8b SoCs have an efuse which contains
> calibration data from the factory (for the internal temperature sensor
> and some CVBS connector settings). Some manufacturers also store the MAC
> address or serial number in the efuse.
>
> This documents the devicetree bindings for the efuse on these SoCs.
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
> .../bindings/nvmem/amlogic-meson-mx-efuse.txt | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/amlogic-meson-mx-efuse.txt
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-10-10 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 23:28 [PATCH v2 0/4] Amlogic Meson6/Meson8/Meson8b efuse support Martin Blumenstingl
2017-10-02 23:28 ` [PATCH v2 1/4] dt-bindings: nvmem: Describe the Amlogic Meson6/Meson8/Meson8b efuse Martin Blumenstingl
2017-10-10 18:56 ` Rob Herring [this message]
2017-10-02 23:28 ` [PATCH v2 2/4] nvmem: meson-efuse: indicate that this driver is only for Meson GX SoCs Martin Blumenstingl
2017-10-10 18:57 ` Rob Herring
2017-10-02 23:28 ` [PATCH v2 3/4] nvmem: add a driver for the Amlogic Meson6/Meson8/Meson8b SoCs Martin Blumenstingl
2017-10-02 23:28 ` [PATCH v2 4/4] ARM: dts: meson: add the efuse node Martin Blumenstingl
2017-10-20 22:04 ` Martin Blumenstingl
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=20171010185656.pf4jybiohcywp7wj@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linus-amlogic@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
all inboxes | Powered by JetHome®