From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dt-bindings: nvmem: mediatek: add support for MediaTek MT7623 and MT7622 SoC
Date: Tue, 4 Jul 2017 23:21:59 +0200 [thread overview]
Message-ID: <7922fc9b-ad4a-fad7-023f-587db484b5aa@gmail.com> (raw)
In-Reply-To: <fc06fbe496ac237b961b73d51bb823e4ac2f8578.1498808678.git.sean.wang@mediatek.com>
On 06/30/2017 09:49 AM, sean.wang at mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> This updates dt-binding documentation for MediaTek MT7622 and
> MT7623 SoC. For the both SoCs supported all rely on the fallback
> binding of the generic case with "mediatek,efuse".
>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> Signed-off-by: Andrew-CT Chen <andrew-ct.chen@mediatek.com>
> ---
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> Documentation/devicetree/bindings/nvmem/mtk-efuse.txt | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> index 74cf529..0668c45 100644
> --- a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> +++ b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> @@ -3,7 +3,10 @@
> This binding is intended to represent MTK-EFUSE which is found in most Mediatek SOCs.
>
> Required properties:
> -- compatible: should be "mediatek,mt8173-efuse" or "mediatek,efuse"
> +- compatible: should be
> + "mediatek,mt7622-efuse", "mediatek,efuse": for MT7622
> + "mediatek,mt7623-efuse", "mediatek,efuse": for MT7623
> + "mediatek,mt8173-efuse" or "mediatek,efuse": for MT8173
> - reg: Should contain registers location and length
>
> = Data cells =
>
next prev parent reply other threads:[~2017-07-04 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 7:49 [PATCH] dt-bindings: nvmem: mediatek: add support for MediaTek MT7623 and MT7622 SoC sean.wang at mediatek.com
2017-07-04 21:21 ` Matthias Brugger [this message]
2017-07-10 0:57 ` Rob Herring
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=7922fc9b-ad4a-fad7-023f-587db484b5aa@gmail.com \
--to=matthias.bgg@gmail.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).