From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>,
Rob Herring <robh+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-phy@lists.infradead.org,
Eddie Hung <eddie.hung@mediatek.com>,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
Yz Wu <yz.wu@mediatek.com>
Subject: Re: [PATCH 1/6] dt-bindings: nvmem: mediatek: add support bits property
Date: Fri, 19 Nov 2021 17:18:27 +0000 [thread overview]
Message-ID: <9a730cf5-7f92-470a-633d-70d06bb66a0b@linaro.org> (raw)
In-Reply-To: <20211107075646.4366-1-chunfeng.yun@mediatek.com>
On 07/11/2021 07:56, Chunfeng Yun wrote:
> Add support bits property, will satisfy more consumers.
>
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
Applied thanks,
--srini
> ---
> Need convert mtk-efuse.txt into yaml first?
> ---
> Documentation/devicetree/bindings/nvmem/mtk-efuse.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> index b6791702bcfc..ec70c5b7a340 100644
> --- a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> +++ b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> @@ -10,6 +10,7 @@ Required properties:
> "mediatek,mt8192-efuse", "mediatek,efuse": for MT8192
> "mediatek,mt8516-efuse", "mediatek,efuse": for MT8516
> - reg: Should contain registers location and length
> +- bits: contain the bits range by offset and size
>
> = Data cells =
> Are child nodes of MTK-EFUSE, bindings of which as described in
>
prev parent reply other threads:[~2021-11-19 17:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 7:56 [PATCH 1/6] dt-bindings: nvmem: mediatek: add support bits property Chunfeng Yun
2021-11-07 7:56 ` [PATCH 2/6] dt-bindings: nvmem: mediatek: add support for mt8195 Chunfeng Yun
2021-11-12 22:41 ` Rob Herring
2021-11-19 17:18 ` Srinivas Kandagatla
2021-11-07 7:56 ` [PATCH 3/6] nvmem: mtk-efuse: support minimum one byte access stride and granularity Chunfeng Yun
2021-11-19 17:18 ` Srinivas Kandagatla
2021-11-07 7:56 ` [PATCH 4/6] dt-bindings: phy: mediatek: tphy: support software efuse load Chunfeng Yun
2021-11-12 22:42 ` Rob Herring
2021-11-19 17:18 ` Srinivas Kandagatla
2021-11-22 4:05 ` Chen-Yu Tsai
2021-11-22 9:21 ` Srinivas Kandagatla
2021-11-24 7:48 ` Chunfeng Yun
2021-11-07 7:56 ` [PATCH 5/6] phy: phy-mtk-tphy: add support efuse setting Chunfeng Yun
2021-11-22 11:35 ` Vinod Koul
2021-11-24 6:54 ` Chunfeng Yun
2021-11-25 5:12 ` Vinod Koul
2021-12-02 8:48 ` Chunfeng Yun
2021-11-07 7:56 ` [PATCH 6/6] arm64: dts: mediatek: mt8195: add efuse node and cells Chunfeng Yun
2021-11-12 22:41 ` [PATCH 1/6] dt-bindings: nvmem: mediatek: add support bits property Rob Herring
2021-11-19 17:18 ` Srinivas Kandagatla [this message]
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=9a730cf5-7f92-470a-633d-70d06bb66a0b@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=chunfeng.yun@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.hung@mediatek.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=yz.wu@mediatek.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;
as well as URLs for NNTP newsgroup(s).