From: <ed.tsai@mediatek.com>
To: <bvanassche@acm.org>, Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <wsd_upstream@mediatek.com>,
<peter.wang@mediatek.com>, <alice.chao@mediatek.com>,
<naomi.chu@mediatek.com>, <chun-hung.wu@mediatek.com>,
Ed Tsai <ed.tsai@mediatek.com>
Subject: [PATCH v2 0/2] ufs: add delay for VCC ramp-up stability
Date: Tue, 10 Mar 2026 08:52:26 +0800 [thread overview]
Message-ID: <20260310005230.4001904-2-ed.tsai@mediatek.com> (raw)
From: Ed Tsai <ed.tsai@mediatek.com>
Hi,
This patch series resolves a link stability issue found on our certain
platforms where the VCC regulator has a slow ramp-up time.
To fix this, a delay is needed after VCC is turned on. The solution is
implemented in two parts:
1. Introduce the new host quirks, UFSHCD_QUIRK_VCC_ON_DELAY.
2. Apply in our new platform with UFS5 device to ensure the VCC is
ready before we enable the clocks.
Changes in v2:
- Fix typos and wording issues.
Ed Tsai (2):
ufs: core: Add quirks for VCC ramp-up delay
ufs: host: mediatek: Add VCC on delay for stability
drivers/ufs/core/ufshcd.c | 12 ++++++++++++
drivers/ufs/host/ufs-mediatek.c | 11 +++++++++++
drivers/ufs/host/ufs-mediatek.h | 4 ++++
include/ufs/ufshcd.h | 6 ++++++
4 files changed, 33 insertions(+)
--
2.45.2
next reply other threads:[~2026-03-10 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 0:52 ed.tsai [this message]
2026-03-10 0:52 ` [PATCH v2 1/2] ufs: core: Add quirks for VCC ramp-up delay ed.tsai
2026-03-11 1:43 ` Martin K. Petersen
2026-03-11 9:23 ` Julian Calaby
2026-03-10 0:52 ` [PATCH v2 2/2] ufs: host: mediatek: Add VCC on delay for stability ed.tsai
2026-03-10 17:43 ` Bart Van Assche
2026-03-16 1:41 ` [PATCH v2 0/2] ufs: add delay for VCC ramp-up stability Martin K. Petersen
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=20260310005230.4001904-2-ed.tsai@mediatek.com \
--to=ed.tsai@mediatek.com \
--cc=alice.chao@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bvanassche@acm.org \
--cc=chun-hung.wu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=naomi.chu@mediatek.com \
--cc=peter.wang@mediatek.com \
--cc=wsd_upstream@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