From: Axe Yang <axe.yang@mediatek.com>
To: Chaotian Jing <chaotian.jing@mediatek.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.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: <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>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Axe Yang <axe.yang@mediatek.com>
Subject: [PATCH v3 0/2] mmc: mediatek: add support for 64-steps tuning
Date: Thu, 30 Nov 2023 14:15:11 +0800 [thread overview]
Message-ID: <20231130061513.1296-1-axe.yang@mediatek.com> (raw)
Change in v3:
- use BIT_ULL() instead of BIT() to avoid potential left shift operations
that could cause exceed boundary problem on 32-bit platforms
Change in v2:
- move the change made to document to the front
- change mediatek,tune-step dts property type to enum for better scalability
Axe Yang (2):
dt-bindings: mmc: mtk-sd: add tuning steps related property
mmc: mediatek: extend number of tuning steps
.../devicetree/bindings/mmc/mtk-sd.yaml | 9 +
drivers/mmc/host/mtk-sd.c | 155 ++++++++++++------
2 files changed, 116 insertions(+), 48 deletions(-)
--
2.25.1
next reply other threads:[~2023-11-30 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 6:15 Axe Yang [this message]
2023-11-30 6:15 ` [PATCH v3 1/2] dt-bindings: mmc: mtk-sd: add tuning steps related property Axe Yang
2023-11-30 6:15 ` [PATCH v3 2/2] mmc: mediatek: extend number of tuning steps Axe Yang
2023-12-01 9:02 ` AngeloGioacchino Del Regno
2023-12-05 2:02 ` Axe Yang (杨磊)
2023-12-05 13:24 ` AngeloGioacchino Del Regno
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=20231130061513.1296-1-axe.yang@mediatek.com \
--to=axe.yang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chaotian.jing@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wenbin.mei@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