From: Bart Van Assche <bvanassche@acm.org>
To: ed.tsai@mediatek.com, 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>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/2] ufs: core: Add quriks for VCC ramp-up delay
Date: Thu, 5 Mar 2026 06:24:38 -0600 [thread overview]
Message-ID: <fd1fb573-6d02-433e-a74a-1a015c64e3be@acm.org> (raw)
In-Reply-To: <20260305083610.2672344-2-ed.tsai@mediatek.com>
On 3/5/26 2:29 AM, ed.tsai@mediatek.com wrote:
> + /*
> + * On platforms with a slow VCC ramp-up, a delay is needed after
> + * turning on VCC to ensure the voltage is stable before the
> + * reference clock is enabled.
> + */
> + if (hba->quirks & UFSHCD_QUIRK_VCC_ON_DELAY && !ret && vcc_on &&
> + hba->vreg_info.vcc && !hba->vreg_info.vcc->always_on)
> + usleep_range(1000, 1100);
Since the value of the delay is platform-dependent, has it been
considered to introduce a new vendor operation (vop)?
Thanks,
Bart.
next prev parent reply other threads:[~2026-03-05 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260305083610.2672344-1-ed.tsai@mediatek.com>
2026-03-05 8:29 ` [PATCH 1/2] ufs: core: Add quriks for VCC ramp-up delay ed.tsai
2026-03-05 12:24 ` Bart Van Assche [this message]
2026-03-06 0:19 ` Ed Tsai (蔡宗軒)
2026-03-06 2:15 ` Bart Van Assche
2026-03-06 2:16 ` Bart Van Assche
2026-03-05 8:29 ` [PATCH 2/2] ufs: host: mediatek: Add VCC on delay for stability ed.tsai
2026-03-05 12:20 ` Bart Van Assche
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=fd1fb573-6d02-433e-a74a-1a015c64e3be@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.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=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.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