All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
	Eddie Hung <eddie.hung@mediatek.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v6 1/4] dt-bindings: nvmem: convert mtk-efuse.txt to YAML schema
Date: Mon, 20 Jun 2022 15:11:44 +0800	[thread overview]
Message-ID: <0050627cdd64c02bb84f4694fc8994a5cb27d0f2.camel@mediatek.com> (raw)
In-Reply-To: <46ec62eb-00da-defb-219f-92121fd35d7e@linaro.org>

Hi Matthias,

On Fri, 2022-06-17 at 12:41 -0700, Srinivas Kandagatla wrote:
> 
> On 17/06/2022 02:31, Chunfeng Yun wrote:
> > Convert mtk-efuse.txt to YAML schema mediatek,efuse.yaml
> > 
> > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Reviewed-by: Rob Herring <robh@kernel.org>
> > Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> > ---
> 
> Applied 1/4 and 2/4, dts patches need to go via SoC maintainer.
Could you please help to pick up 3/4, 4/4?

thanks

> 
> 
> thanks,
> -srini
> 
> 
> > v6: no changes, based on kernel 5.19-rc1
> > 
> > v5:
> > sync with the series:
> > 
https://patchwork.kernel.org/project/linux-mediatek/list/?series=640196
> >     1. change title suggested by Krzysztof;
> >     2. No need drop 'reviewed-by Rob' suggested by Krzysztof
> >     3. add maintainer Lala who maintain efuse driver now;
> > 
> > v4: fix duplicated unit-address in example;
> >      drop reviewed-by Rob, due to changes;
> > 
> > v3: add reviewed-by Rob
> > 
> > v2:
> >     1. remove description of subnodes which is covered by
> > nvmem.yaml
> > suggested by Rob
> >     2. change the example which is commoner than mt8173's
> > ---
> >   .../bindings/nvmem/mediatek,efuse.yaml        | 87
> > +++++++++++++++++++
> >   .../devicetree/bindings/nvmem/mtk-efuse.txt   | 43 ---------
> >   2 files changed, 87 insertions(+), 43 deletions(-)
> >   create mode 100644
> > Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> >   delete mode 100644 Documentation/devicetree/bindings/nvmem/mtk-
> > efuse.txt
> > 
> > diff --git
> > a/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> > b/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> > new file mode 100644
> > index 000000000000..f6e01ddb7499
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> > @@ -0,0 +1,87 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/nvmem/mediatek,efuse.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: MediaTek efuse
> > +
> > +description: |
> > +  MediaTek's efuse is used for storing calibration data, it can be
> > accessed
> > +  on ARM devices usiong I/O mapped memory.
> > +
> > +maintainers:
> > +  - Andrew-CT Chen <andrew-ct.chen@mediatek.com>
> > +  - Lala Lin <lala.lin@mediatek.com>
> > +
> > +allOf:
> > +  - $ref: "nvmem.yaml#"
> > +
> > +properties:
> > +  $nodename:
> > +    pattern: "^efuse@[0-9a-f]+$"
> > +
> > +  compatible:
> > +    oneOf:
> > +      - items:
> > +          - enum:
> > +              - mediatek,mt7622-efuse
> > +              - mediatek,mt7623-efuse
> > +              - mediatek,mt8173-efuse
> > +              - mediatek,mt8192-efuse
> > +              - mediatek,mt8195-efuse
> > +              - mediatek,mt8516-efuse
> > +          - const: mediatek,efuse
> > +      - const: mediatek,mt8173-efuse
> > +        deprecated: true
> > +
> > +  reg:
> > +    maxItems: 1
> > +
> > +required:
> > +  - compatible
> > +  - reg
> > +
> > +unevaluatedProperties: false
> > +
> > +examples:
> > +  - |
> > +    efuse@11c10000 {
> > +        compatible = "mediatek,mt8195-efuse", "mediatek,efuse";
> > +        reg = <0x11c10000 0x1000>;
> > +        #address-cells = <1>;
> > +        #size-cells = <1>;
> > +
> > +        u3_tx_imp_p0: usb3-tx-imp@184,1 {
> > +            reg = <0x184 0x1>;
> > +            bits = <0 5>;
> > +        };
> > +        u3_rx_imp_p0: usb3-rx-imp@184,2 {
> > +            reg = <0x184 0x2>;
> > +            bits = <5 5>;
> > +        };
> > +        u3_intr_p0: usb3-intr@185 {
> > +            reg = <0x185 0x1>;
> > +            bits = <2 6>;
> > +        };
> > +        comb_tx_imp_p1: usb3-tx-imp@186,1 {
> > +            reg = <0x186 0x1>;
> > +            bits = <0 5>;
> > +        };
> > +        comb_rx_imp_p1: usb3-rx-imp@186,2 {
> > +            reg = <0x186 0x2>;
> > +            bits = <5 5>;
> > +        };
> > +        comb_intr_p1: usb3-intr@187 {
> > +            reg = <0x187 0x1>;
> > +            bits = <2 6>;
> > +        };
> > +        u2_intr_p0: usb2-intr-p0@188,1 {
> > +            reg = <0x188 0x1>;
> > +            bits = <0 5>;
> > +        };
> > +        u2_intr_p1: usb2-intr-p1@188,2 {
> > +            reg = <0x188 0x2>;
> > +            bits = <5 5>;
> > +        };
> > +    };
> > diff --git a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> > b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> > deleted file mode 100644
> > index 39d529599444..000000000000
> > --- a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> > +++ /dev/null
> > @@ -1,43 +0,0 @@
> > -= Mediatek MTK-EFUSE device tree bindings =
> > -
> > -This binding is intended to represent MTK-EFUSE which is found in
> > most Mediatek SOCs.
> > -
> > -Required properties:
> > -- 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
> > -	      "mediatek,mt8192-efuse", "mediatek,efuse": for MT8192
> > -	      "mediatek,mt8195-efuse", "mediatek,efuse": for MT8195
> > -	      "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
> > -bindings/nvmem/nvmem.txt
> > -
> > -Example:
> > -
> > -	efuse: efuse@10206000 {
> > -		compatible = "mediatek,mt8173-efuse";
> > -		reg	   = <0 0x10206000 0 0x1000>;
> > -		#address-cells = <1>;
> > -		#size-cells = <1>;
> > -
> > -		/* Data cells */
> > -		thermal_calibration: calib@528 {
> > -			reg = <0x528 0xc>;
> > -		};
> > -	};
> > -
> > -= Data consumers =
> > -Are device nodes which consume nvmem data cells.
> > -
> > -For example:
> > -
> > -	thermal {
> > -		...
> > -		nvmem-cells = <&thermal_calibration>;
> > -		nvmem-cell-names = "calibration";
> > -	};


WARNING: multiple messages have this Message-ID (diff)
From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
	Eddie Hung <eddie.hung@mediatek.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v6 1/4] dt-bindings: nvmem: convert mtk-efuse.txt to YAML schema
Date: Mon, 20 Jun 2022 15:11:44 +0800	[thread overview]
Message-ID: <0050627cdd64c02bb84f4694fc8994a5cb27d0f2.camel@mediatek.com> (raw)
In-Reply-To: <46ec62eb-00da-defb-219f-92121fd35d7e@linaro.org>

Hi Matthias,

On Fri, 2022-06-17 at 12:41 -0700, Srinivas Kandagatla wrote:
> 
> On 17/06/2022 02:31, Chunfeng Yun wrote:
> > Convert mtk-efuse.txt to YAML schema mediatek,efuse.yaml
> > 
> > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Reviewed-by: Rob Herring <robh@kernel.org>
> > Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> > ---
> 
> Applied 1/4 and 2/4, dts patches need to go via SoC maintainer.
Could you please help to pick up 3/4, 4/4?

thanks

> 
> 
> thanks,
> -srini
> 
> 
> > v6: no changes, based on kernel 5.19-rc1
> > 
> > v5:
> > sync with the series:
> > 
https://patchwork.kernel.org/project/linux-mediatek/list/?series=640196
> >     1. change title suggested by Krzysztof;
> >     2. No need drop 'reviewed-by Rob' suggested by Krzysztof
> >     3. add maintainer Lala who maintain efuse driver now;
> > 
> > v4: fix duplicated unit-address in example;
> >      drop reviewed-by Rob, due to changes;
> > 
> > v3: add reviewed-by Rob
> > 
> > v2:
> >     1. remove description of subnodes which is covered by
> > nvmem.yaml
> > suggested by Rob
> >     2. change the example which is commoner than mt8173's
> > ---
> >   .../bindings/nvmem/mediatek,efuse.yaml        | 87
> > +++++++++++++++++++
> >   .../devicetree/bindings/nvmem/mtk-efuse.txt   | 43 ---------
> >   2 files changed, 87 insertions(+), 43 deletions(-)
> >   create mode 100644
> > Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> >   delete mode 100644 Documentation/devicetree/bindings/nvmem/mtk-
> > efuse.txt
> > 
> > diff --git
> > a/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> > b/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> > new file mode 100644
> > index 000000000000..f6e01ddb7499
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> > @@ -0,0 +1,87 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/nvmem/mediatek,efuse.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: MediaTek efuse
> > +
> > +description: |
> > +  MediaTek's efuse is used for storing calibration data, it can be
> > accessed
> > +  on ARM devices usiong I/O mapped memory.
> > +
> > +maintainers:
> > +  - Andrew-CT Chen <andrew-ct.chen@mediatek.com>
> > +  - Lala Lin <lala.lin@mediatek.com>
> > +
> > +allOf:
> > +  - $ref: "nvmem.yaml#"
> > +
> > +properties:
> > +  $nodename:
> > +    pattern: "^efuse@[0-9a-f]+$"
> > +
> > +  compatible:
> > +    oneOf:
> > +      - items:
> > +          - enum:
> > +              - mediatek,mt7622-efuse
> > +              - mediatek,mt7623-efuse
> > +              - mediatek,mt8173-efuse
> > +              - mediatek,mt8192-efuse
> > +              - mediatek,mt8195-efuse
> > +              - mediatek,mt8516-efuse
> > +          - const: mediatek,efuse
> > +      - const: mediatek,mt8173-efuse
> > +        deprecated: true
> > +
> > +  reg:
> > +    maxItems: 1
> > +
> > +required:
> > +  - compatible
> > +  - reg
> > +
> > +unevaluatedProperties: false
> > +
> > +examples:
> > +  - |
> > +    efuse@11c10000 {
> > +        compatible = "mediatek,mt8195-efuse", "mediatek,efuse";
> > +        reg = <0x11c10000 0x1000>;
> > +        #address-cells = <1>;
> > +        #size-cells = <1>;
> > +
> > +        u3_tx_imp_p0: usb3-tx-imp@184,1 {
> > +            reg = <0x184 0x1>;
> > +            bits = <0 5>;
> > +        };
> > +        u3_rx_imp_p0: usb3-rx-imp@184,2 {
> > +            reg = <0x184 0x2>;
> > +            bits = <5 5>;
> > +        };
> > +        u3_intr_p0: usb3-intr@185 {
> > +            reg = <0x185 0x1>;
> > +            bits = <2 6>;
> > +        };
> > +        comb_tx_imp_p1: usb3-tx-imp@186,1 {
> > +            reg = <0x186 0x1>;
> > +            bits = <0 5>;
> > +        };
> > +        comb_rx_imp_p1: usb3-rx-imp@186,2 {
> > +            reg = <0x186 0x2>;
> > +            bits = <5 5>;
> > +        };
> > +        comb_intr_p1: usb3-intr@187 {
> > +            reg = <0x187 0x1>;
> > +            bits = <2 6>;
> > +        };
> > +        u2_intr_p0: usb2-intr-p0@188,1 {
> > +            reg = <0x188 0x1>;
> > +            bits = <0 5>;
> > +        };
> > +        u2_intr_p1: usb2-intr-p1@188,2 {
> > +            reg = <0x188 0x2>;
> > +            bits = <5 5>;
> > +        };
> > +    };
> > diff --git a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> > b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> > deleted file mode 100644
> > index 39d529599444..000000000000
> > --- a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
> > +++ /dev/null
> > @@ -1,43 +0,0 @@
> > -= Mediatek MTK-EFUSE device tree bindings =
> > -
> > -This binding is intended to represent MTK-EFUSE which is found in
> > most Mediatek SOCs.
> > -
> > -Required properties:
> > -- 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
> > -	      "mediatek,mt8192-efuse", "mediatek,efuse": for MT8192
> > -	      "mediatek,mt8195-efuse", "mediatek,efuse": for MT8195
> > -	      "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
> > -bindings/nvmem/nvmem.txt
> > -
> > -Example:
> > -
> > -	efuse: efuse@10206000 {
> > -		compatible = "mediatek,mt8173-efuse";
> > -		reg	   = <0 0x10206000 0 0x1000>;
> > -		#address-cells = <1>;
> > -		#size-cells = <1>;
> > -
> > -		/* Data cells */
> > -		thermal_calibration: calib@528 {
> > -			reg = <0x528 0xc>;
> > -		};
> > -	};
> > -
> > -= Data consumers =
> > -Are device nodes which consume nvmem data cells.
> > -
> > -For example:
> > -
> > -	thermal {
> > -		...
> > -		nvmem-cells = <&thermal_calibration>;
> > -		nvmem-cell-names = "calibration";
> > -	};
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-20  7:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  9:31 [PATCH v6 1/4] dt-bindings: nvmem: convert mtk-efuse.txt to YAML schema Chunfeng Yun
2022-06-17  9:31 ` Chunfeng Yun
2022-06-17  9:31 ` [PATCH v6 2/4] dt-bindings: nvmem: mediatek: efuse: add support mt8183 Chunfeng Yun
2022-06-17  9:31   ` Chunfeng Yun
2022-06-17  9:31 ` [PATCH v6 3/4] arm64: dts: mediatek: mt8192: fix dtbs check warning of efuse Chunfeng Yun
2022-06-17  9:31   ` Chunfeng Yun
2022-06-17  9:31 ` [PATCH v6 4/4] arm64: dts: mediatek: mt8183: change efuse node name Chunfeng Yun
2022-06-17  9:31   ` Chunfeng Yun
2022-06-17 19:41 ` [PATCH v6 1/4] dt-bindings: nvmem: convert mtk-efuse.txt to YAML schema Srinivas Kandagatla
2022-06-17 19:41   ` Srinivas Kandagatla
2022-06-20  7:11   ` Chunfeng Yun [this message]
2022-06-20  7:11     ` Chunfeng Yun
2022-06-22 14:10     ` Matthias Brugger
2022-06-22 14:10       ` Matthias Brugger

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=0050627cdd64c02bb84f4694fc8994a5cb27d0f2.camel@mediatek.com \
    --to=chunfeng.yun@mediatek.com \
    --cc=allen-kh.cheng@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eddie.hung@mediatek.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=srinivas.kandagatla@linaro.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.