[<prev] [next>] [day] [month] [year] [list]
Message-ID: <51be638b-e12d-b9ae-c14b-f51e33d2503e@linaro.org>
Date: Wed, 27 Apr 2022 15:53:52 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: "allen-kh.cheng" <allen-kh.cheng@...iatek.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
Cc: Lala Lin <lala.lin@...iatek.com>,
Project_Global_Chrome_Upstream_Group@...iatek.com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
Chen-Yu Tsai <wenst@...omium.org>,
Ryder Lee <ryder.lee@...nel.org>
Subject: Re: [PATCH v2 1/1] dt-bindings: nvmem: mediatek: Convert mtk-efuse
binding to YAML
On 27/04/2022 12:00, allen-kh.cheng wrote:
> 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?
Indeed, I forgot that mt8173 would also fallback to generic efuse.
Indeed let's go with case 2, so your proposal before was correct.
Best regards,
Krzysztof
Powered by blists - more mailing lists