From: "Axe Yang (杨磊)" <Axe.Yang@mediatek.com>
To: "Wenbin Mei (梅文彬)" <Wenbin.Mei@mediatek.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"Chaotian Jing (井朝天)" <Chaotian.Jing@mediatek.com>,
"robh@kernel.org" <robh@kernel.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>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
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>,
"Andy-ld Lu (卢东)" <Andy-ld.Lu@mediatek.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Yong Mao (毛勇)" <yong.mao@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Qingliang Li (黎晴亮)" <Qingliang.Li@mediatek.com>
Subject: Re: [PATCH 1/2] dt-bindings: mmc: mtk-sd: add single burst switch
Date: Fri, 7 Mar 2025 06:59:03 +0000 [thread overview]
Message-ID: <f84800fac589429157cd84034ef2f4541d3486a7.camel@mediatek.com> (raw)
In-Reply-To: <3e84fda8-2566-4f18-8ef9-850c84789c34@collabora.com>
On Thu, 2025-03-06 at 10:19 +0100, AngeloGioacchino Del Regno wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> Il 06/03/25 09:48, Axe Yang ha scritto:
> > Add 'mediatek,disable-single-burst' setting. This property can be
> > used to switch bus burst type, from single burst to INCR, which is
> > determined by the bus type within the IP. Some versions of the IP
> > are using AXI bus, thus this switch is necessary as 'single' is not
> > the burst type supported by the bus.
> >
> > Signed-off-by: Axe Yang <axe.yang@mediatek.com>
>
> I am mostly sure that this is not something to put in devicetree, but
> as
> platform data for specific SoC(s), as much as I'm mostly sure that
> all of
> the instances of the MSDC IP in one SoC will be *all* using either
> single
> or INCR.
No, actually MSDC IPs in one SoC are using different versions.
Usually MSDC1 (index from 1) is used as eMMC host, the left hosts are
used as SD/SDIO hosts. They have similar designs, but there are still
difference.
>
> So, I think I know the answer but I'll still ask just to be extremely
> sure:
>
> is there any MediaTek SoC that has different IP versions for
> different MSDC
> instances, and that hence require single burst on one instance and
> INCR on
> another instance?
Yes. Actually every SoC has different IP versions for eMMC and SD/SDIO
host as I said.
e.g. For MT8168, signel burst bit should be set to 1 for eMMC Host, but
0 for SD/SDIO Host.
>
> And if there is - is there a pattern? Is it always SDIO requiring
> INCR or
> always eMMC/SD requiring it?
>
>
No, there is no pattern. Both eMMC and SD/SDIO hosts need to be
configured base on IP version. There is no binding relationship between
eMMC/SD/SDIO and the burst type. eMMC burst type might be INCR or
single, same as SD/SDIO.
Regards,
Axe
>
> > ---
> > Documentation/devicetree/bindings/mmc/mtk-sd.yaml | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/mmc/mtk-sd.yaml
> > b/Documentation/devicetree/bindings/mmc/mtk-sd.yaml
> > index 0debccbd6519..6076aff0a689 100644
> > --- a/Documentation/devicetree/bindings/mmc/mtk-sd.yaml
> > +++ b/Documentation/devicetree/bindings/mmc/mtk-sd.yaml
> > @@ -100,6 +100,14 @@ properties:
> > minimum: 0
> > maximum: 0xffffffff
> >
> > + mediatek,disable-single-burst:
> > + $ref: /schemas/types.yaml#/definitions/flag
> > + description:
> > + Burst type setting. For some versions of the IP that do not
> > use
> > + AHB bus, the burst type need to be switched to INCR.
> > + If present, use INCR burst type.
> > + If not present, use single burst type.
> > +
> > mediatek,hs200-cmd-int-delay:
> > $ref: /schemas/types.yaml#/definitions/uint32
> > description:
>
>
>
next prev parent reply other threads:[~2025-03-07 7:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 8:48 [PATCH 0/2] mmc: mtk-sd: add support for burst type switch Axe Yang
2025-03-06 8:48 ` [PATCH 1/2] dt-bindings: mmc: mtk-sd: add single burst switch Axe Yang
2025-03-06 9:19 ` AngeloGioacchino Del Regno
2025-03-07 6:59 ` Axe Yang (杨磊) [this message]
2025-03-07 15:48 ` Conor Dooley
2025-03-10 3:31 ` Axe Yang (杨磊)
2025-03-11 9:47 ` AngeloGioacchino Del Regno
2025-03-12 6:30 ` Axe Yang (杨磊)
2025-03-25 2:41 ` Axe Yang (杨磊)
2025-03-25 10:20 ` AngeloGioacchino Del Regno
2025-03-27 2:48 ` Axe Yang (杨磊)
2025-04-03 10:57 ` AngeloGioacchino Del Regno
2025-03-06 8:48 ` [PATCH 2/2] mmc: mtk-sd: add support to disable single burst Axe Yang
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=f84800fac589429157cd84034ef2f4541d3486a7.camel@mediatek.com \
--to=axe.yang@mediatek.com \
--cc=Andy-ld.Lu@mediatek.com \
--cc=Chaotian.Jing@mediatek.com \
--cc=Qingliang.Li@mediatek.com \
--cc=Wenbin.Mei@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--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 \
--cc=yong.mao@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