From: <michael.mei-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: orz811017-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
Michael Mei <michael.mei-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
Subject: [PATCH 0/2] Add Mediatek Efuse Device Node
Date: Tue, 16 Apr 2019 16:19:18 +0800 [thread overview]
Message-ID: <20190416081922.21711-1-michael.mei@mediatek.com> (raw)
From: Michael Mei <michael.mei-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
This patch adds efuse and soc_data device nodes to read via NVMEM.
These device nodes store data including thermal calibration, chip ID,
and drivers like thermal sensor will read out theses data to configure
dirver.
Michael Mei (2):
arm64: dts: mt8183: add efuse and Mediatek Chip id node to read
dt-bindings: nvmem: mediatek: add support for MediaTek mt8183 SoC
.../devicetree/bindings/nvmem/mtk-efuse.txt | 1 +
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 15 +++++++++++++++
2 files changed, 16 insertions(+)
--
2.18.0
next reply other threads:[~2019-04-16 8:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 8:19 michael.mei-NuS5LvNUpcJWk0Htik3J/w [this message]
[not found] ` <20190416081922.21711-1-michael.mei-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-04-16 8:19 ` [PATCH 1/2] arm64: dts: mt8183: add efuse and Mediatek Chip id node to read michael.mei-NuS5LvNUpcJWk0Htik3J/w
[not found] ` <20190416081922.21711-2-michael.mei-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-04-16 9:07 ` Matthias Brugger
2019-04-16 8:19 ` [PATCH 2/2] dt-bindings: nvmem: mediatek: add support for MediaTek mt8183 SoC michael.mei-NuS5LvNUpcJWk0Htik3J/w
2020-05-21 14:40 ` Matthias Brugger
2020-05-21 14:40 ` Matthias Brugger
2019-04-16 8:19 ` [PATCH 1/2] arm64: dts: mt8183: add efuse and Mediatek Chip id node to read michael.mei-NuS5LvNUpcJWk0Htik3J/w
2019-04-16 8:19 ` [PATCH 2/2] dt-bindings: nvmem: mediatek: add support for MediaTek mt8183 SoC michael.mei-NuS5LvNUpcJWk0Htik3J/w
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=20190416081922.21711-1-michael.mei@mediatek.com \
--to=michael.mei-nus5lvnupcjwk0htik3j/w@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=orz811017-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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 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.