From: Axe Yang <axe.yang@mediatek.com>
To: Chaotian Jing <chaotian.jing@mediatek.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Wenbin Mei <wenbin.mei@mediatek.com>
Cc: <yong.mao@mediatek.com>, <qingliang.li@mediatek.com>,
<andy-ld.lu@mediatek.com>, <linux-mmc@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
Axe Yang <axe.yang@mediatek.com>
Subject: [PATCH 1/2] dt-bindings: mmc: mtk-sd: add single burst switch
Date: Thu, 6 Mar 2025 16:48:05 +0800 [thread overview]
Message-ID: <20250306085028.5024-2-axe.yang@mediatek.com> (raw)
In-Reply-To: <20250306085028.5024-1-axe.yang@mediatek.com>
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>
---
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:
--
2.46.0
next prev parent reply other threads:[~2025-03-06 8:53 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 ` Axe Yang [this message]
2025-03-06 9:19 ` [PATCH 1/2] dt-bindings: mmc: mtk-sd: add single burst switch AngeloGioacchino Del Regno
2025-03-07 6:59 ` Axe Yang (杨磊)
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=20250306085028.5024-2-axe.yang@mediatek.com \
--to=axe.yang@mediatek.com \
--cc=andy-ld.lu@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chaotian.jing@mediatek.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=qingliang.li@mediatek.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wenbin.mei@mediatek.com \
--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