From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: <ed.tsai@mediatek.com>
Cc: <bvanassche@acm.org>, Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
<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>,
<linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] ufs: core: Add quirks for VCC ramp-up delay
Date: Tue, 10 Mar 2026 21:43:38 -0400 [thread overview]
Message-ID: <yq1jyvjtadh.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260310005230.4001904-4-ed.tsai@mediatek.com> (ed tsai's message of "Tue, 10 Mar 2026 08:52:28 +0800")
Ed,
> On some platforms, the VCC regulator has a slow ramp-up time. Add a
> delay after enabling VCC to ensure voltage has fully stabilized before
> we enable the clocks.
Applied #1 + #2 to 7.1/scsi-staging, thanks!
--
Martin K. Petersen
next prev parent reply other threads:[~2026-03-11 1:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 0:52 [PATCH v2 0/2] ufs: add delay for VCC ramp-up stability ed.tsai
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 [this message]
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=yq1jyvjtadh.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alice.chao@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=chun-hung.wu@mediatek.com \
--cc=ed.tsai@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.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