From: "Andy-ld Lu (卢东)" <Andy-ld.Lu@mediatek.com>
To: "robh@kernel.org" <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Wenbin Mei (梅文彬)" <Wenbin.Mei@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>
Subject: Re: [PATCH 2/2] dt-bindings: mmc: mtk-sd: Add support for MT8196
Date: Sat, 28 Sep 2024 13:14:03 +0000 [thread overview]
Message-ID: <10ce6e9af6daa69735f46b45028ec1b2d25ee66a.camel@mediatek.com> (raw)
In-Reply-To: <20240926175409.GA2644361-robh@kernel.org>
On Thu, 2024-09-26 at 12:54 -0500, Rob Herring wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> On Thu, Sep 26, 2024 at 03:03:18PM +0800, Andy-ld Lu wrote:
> > Extend the devicetree bindings to include the MT8196 mmc controller
> > by adding the compatible string 'mediatek,msdc-v2', which could be
> > also used for future compatible SoCs that support new tx/rx.
>
> Generally, every SoC ends up changing at least slightly. So we don't
> do
> version numbers except when there's a well defined versioning scheme
> of
> the h/w (e.g. FPGA IP blocks). So, use SoC for compatible string.
Thanks for your review.
The new tx/rx represents a significant update for mmc controller of
mediatek from the MT8196 chipset, and the dependent settings remain
consistent for MT8196 and subsequent SoCs. Therefore, It is proposed to
use a unified compatible string for these SoCs that support new tx/rx,
and name it as 'IP(msdc) version two'.
>
> >
> > Add three properties for MT8196 settings:
> > - 'mediatek,prohibit-gate-cg', indicate if the source clock CG
> could
> > be disabled when CPU access IP registers.
> >
> > - 'mediatek,stop-dly-sel', configure read data clock stops at block
> gap.
> >
> > - 'mediatek,pop-en-cnt', configure the margins of write and read
> > pointers while begin to pop data transfer.
> >
> > Signed-off-by: Andy-ld Lu <andy-ld.lu@mediatek.com>
> > ---
> > .../devicetree/bindings/mmc/mtk-sd.yaml | 26
> +++++++++++++++++++
> > 1 file changed, 26 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/mmc/mtk-sd.yaml
> b/Documentation/devicetree/bindings/mmc/mtk-sd.yaml
> > index c532ec92d2d9..82d1a9fac67c 100644
> > --- a/Documentation/devicetree/bindings/mmc/mtk-sd.yaml
> > +++ b/Documentation/devicetree/bindings/mmc/mtk-sd.yaml
> > @@ -25,6 +25,7 @@ properties:
> > - mediatek,mt8173-mmc
> > - mediatek,mt8183-mmc
> > - mediatek,mt8516-mmc
> > + - mediatek,msdc-v2
> > - items:
> > - const: mediatek,mt7623-mmc
> > - const: mediatek,mt2701-mmc
> > @@ -154,6 +155,30 @@ properties:
> > enum: [32, 64]
> > default: 32
> >
> > + mediatek,stop-dly-sel:
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + description:
> > + Some SoCs need to set appropriate stop-dly-sel to configure
> read data clock
> > + stops at block gap. The valid range is from 0 to 0xf.
>
> SoC dependent or board dependent? Imply from the compatible for the
> former. A property is fine for the latter case.
Yes, it is SoC dependent in principle, but we would like to use a
unified compatible string for MT8196 and subsequent SoCs as mentioned
above, and this register setting(not relavant with new tx/rx) may be
variant. Therefore, want to use the property of device tree to set
individually.
>
> > + minimum: 0
> > + maximum: 0xf
> > +
> > + mediatek,pop-en-cnt:
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + description:
> > + Some SoCs need to set appropriate pop-en-cnt to configure
> the margins of write
> > + and read pointers while begin to pop data transfer. The
> valid range is from 0
> > + to 0xf.
> > + minimum: 0
> > + maximum: 0xf
>
> Same question.
Same as the reply above.
>
> > +
> > + mediatek,prohibit-gate-cg:
> > + $ref: /schemas/types.yaml#/definitions/flag
> > + description:
> > + Decide if source clock CG could be disabled when CPU access
> IP registers.
> > + If present, source clock CG could not be disabled.
> > + If not present, source clock CG could be disabled.
>
>
> Sounds like you need to describe the clock in "clocks".
It is not with clock itself, but rather with the bus design that would
check the 'source_cg' status bit to decide whether to prevent the CPU
from accessing the IP registers. And there have been no changes to the
'source_cg'(already been descirbed before) for MT8196.
>
> > +
> > resets:
> > maxItems: 1
> >
> > @@ -191,6 +216,7 @@ allOf:
> > - mediatek,mt8188-mmc
> > - mediatek,mt8195-mmc
> > - mediatek,mt8516-mmc
> > + - mediatek,msdc-v2
> > then:
> > properties:
> > clocks:
> > --
> > 2.46.0
> >
next prev parent reply other threads:[~2024-09-28 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 7:03 [PATCH 0/2] Add mtk-sd support for MT8196 Andy-ld Lu
2024-09-26 7:03 ` [PATCH 1/2] mmc: mtk-sd: Add " Andy-ld Lu
2024-09-26 7:03 ` [PATCH 2/2] dt-bindings: " Andy-ld Lu
2024-09-26 16:13 ` Conor Dooley
2024-09-29 5:44 ` Andy-ld Lu (卢东)
2024-09-26 17:54 ` Rob Herring
2024-09-28 13:14 ` Andy-ld Lu (卢东) [this message]
2024-09-28 13:39 ` Krzysztof Kozlowski
2024-09-29 5:50 ` Andy-ld Lu (卢东)
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=10ce6e9af6daa69735f46b45028ec1b2d25ee66a.camel@mediatek.com \
--to=andy-ld.lu@mediatek.com \
--cc=Wenbin.Mei@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@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 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).