public inbox for linux-mediatek@lists.infradead.org
 help / color / mirror / Atom feed
From: allen-kh.cheng <allen-kh.cheng@mediatek.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>
Cc: Lala Lin <lala.lin@mediatek.com>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>,
	Chen-Yu Tsai <wenst@chromium.org>,
	Ryder Lee <ryder.lee@kernel.org>
Subject: Re: [PATCH v2 1/1] dt-bindings: nvmem: mediatek: Convert mtk-efuse binding to YAML
Date: Wed, 27 Apr 2022 18:00:37 +0800	[thread overview]
Message-ID: <daca88d63fa844179a3d44affee124584353bec9.camel@mediatek.com> (raw)
In-Reply-To: <0c63c24a-8014-2491-095c-77893d2141d9@linaro.org>

Hi Krzysztof,

On Wed, 2022-04-27 at 11:39 +0200, Krzysztof Kozlowski wrote:
> On 27/04/2022 11:28, allen-kh.cheng wrote:
> > Hi Krzysztof,
> > 
> > On Tue, 2022-04-26 at 12:14 +0200, Krzysztof Kozlowski wrote:
> > > On 26/04/2022 12:02, allen-kh.cheng wrote:
> > > > Hi Krzysztof,
> > > > 
> > > > On Tue, 2022-04-26 at 08:31 +0200, Krzysztof Kozlowski wrote:
> > > > > On 26/04/2022 08:23, allen-kh.cheng wrote:
> > > > > > > > +properties:
> > > > > > > > +  compatible:
> > > > > > > > +    oneOf:
> > > > > > > > +      - enum:
> > > > > > > > +          - mediatek,mt8173-efuse
> > > > > > > > +          - mediatek,efuse
> > > > > > > 
> > > > > > > Still no changes...
> > > > > > > 
> > > > > > 
> > > > > > I just want to confirm again.
> > > > > > 
> > > > > > "Generic compatibles should not be used standalone"
> > > > > > 
> > > > > > It seems we should remove mediatek,efuse and keep
> > > > > > "mediatek,mt8173-
> > > > > > efuse"in binding. have I got that right?
> > > > > 
> > > > > You should comment for which chipsets this compatible is and
> > > > > add
> > > > > a
> > > > > deprecated:true. In such case it cannot be part of enum but
> > > > > separate
> > > > > item in this oneOf.
> > > > > 
> > > > > 
> > > > > Best regards,
> > > > > Krzysztof
> > > > 
> > > > Thanks for your suggestions, I would plan to send PATCHs as
> > > > below,
> > > > 
> > > > We have a PATCH 01 for current accepted dts
> > > > 
> > > > properties:
> > > >   compatible:
> > > >     oneOf:
> > > >       - enum:
> > > >         - mediatek,efuse
> > > > 
> > > >         - mediatek,mt8173-efuse
> > > >         description: Only mt8173-efuse
> > > > with generic fallback should be used
> > > >       - items:
> > > >           - enum:
> > > >     
> > > > - mediatek,mt7622-efuse
> > > > 			  ...
> > > >           - const: mediatek,efuse
> > > > 
> > > > Then add PATCH 02 to deprecate it
> > > > 
> > > > properties:
> > > >   compatible:
> > > >     oneOf:
> > > >       - enum:
> > > >         - mediatek,efuse
> > > >         - mediatek,mt8173-efuse
> > > >         deprecated: true
> > > >         description: The mediatek,efuse is a generic fallback
> > > > for
> > > > other
> > > > Chipset. Do not use the single compatible such as
> > > > mediatek,efuse
> > > > or mediatek,mt8173-efuse. It is deprecated.
> > > >       - items:
> > > >           - enum:
> > > >               - mediatek,mt7622-efuse
> > > >               ...
> > > >           - const: mediatek,efuse
> > > > 
> > > > 
> > > > PATCH 03 for 8173
> > > > 
> > > > update mt8173.dtsi 
> > > > 
> > > > change compatible from "mediatek,mt8173-efuse" to
> > > > "mediatek,mt8173-
> > > > efuse", "mediatek,efuse";
> > > > 
> > > > 
> > > > Do you think it'd be okay ?
> > > 
> > > The idea is correct, but as I said it cannot be part of enum, but
> > > separate item in oneOf. You should see an error when testing your
> > > patch.
> > > 
> > > 
> > > Best regards,
> > > Krzysztof
> > 
> > I have tested 
> > make DT_CHECKER_FLAGS=-m dt_binding_check
> > DT_SCHEMA_FILES=Documentation/devicetree/bindings/nvmem/mtk,efuse.y
> > aml
> > 
> > make ARCH=arm64 dtbs_check
> > DT_SCHEMA_FILES=Documentation/devicetree/bindings/nvmem/mtk,efuse.y
> > aml
> > 
> > Is the following correct as final version ?
> 
> Almost :)
> 
> > 
> > properties:
> >   compatible:
> >     oneOf:
> >       - const: mediatek,mt8173-efuse
> > #Don't use this in new dts files
> 
> This compatible above is correct for mt8173, isn't it?
> 
> >         deprecated: true
> >       - const:
> > mediatek,efuse
> >         deprecated: true
> >         description:
> >          
> > Please use mediatek,efuse as fallback.
> 
> Description does not match. This should be something like:
> "MediaTek efuse for MT8173. Deprecated, use mediatek,mt8173-efuse
> instead"
> 
> 
> 
> Best regards,
> Krzysztof

I think there are two cases in mediatek efuse dirver now.

Case 1, 
const: mediatek,efuse is deprecated.
const: mediatek,mt8173-efuse is remained. All mediatek chipsets will
use mediatek,mt8173-efuse as fallback.

Case 2,
const: mediatek,efuse is deprecated.
const: mediatek,mt8173-efuse is deprecated.

All mediatek chipsets(include ediatek,mt8173-efuse) will use
mediatek,efuse as fallback.

Which one do you think is better?

Best regards,
Allen



_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

  reply	other threads:[~2022-04-27 10:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25  8:47 [PATCH v2 0/1] dt-bindings: nvmem: mediatek: Convert mtk-efuse binding to YAML Allen-KH Cheng
2022-04-25  8:48 ` [PATCH v2 1/1] " Allen-KH Cheng
2022-04-25 16:38   ` Krzysztof Kozlowski
2022-04-26  6:23     ` allen-kh.cheng
2022-04-26  6:31       ` Krzysztof Kozlowski
2022-04-26 10:02         ` allen-kh.cheng
2022-04-26 10:14           ` Krzysztof Kozlowski
2022-04-27  9:28             ` allen-kh.cheng
2022-04-27  9:39               ` Krzysztof Kozlowski
2022-04-27 10:00                 ` allen-kh.cheng [this message]
2022-04-27 13:53                   ` Krzysztof Kozlowski
2022-04-27 14:00                     ` allen-kh.cheng
2022-04-26 10:03         ` allen-kh.cheng

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=daca88d63fa844179a3d44affee124584353bec9.camel@mediatek.com \
    --to=allen-kh.cheng@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lala.lin@mediatek.com \
    --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=ryder.lee@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=wenst@chromium.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