From: Yixun Lan <dlan@kernel.org>
To: Yao Zi <me@ziyao.cc>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@sandisk.com>,
Bart Van Assche <bvanassche@acm.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-scsi@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] scsi: ufs: spacemit: k3: Add UFS Host Controller driver
Date: Fri, 3 Jul 2026 01:28:00 +0000 [thread overview]
Message-ID: <20260703012800-GKC35811@kernel.org> (raw)
In-Reply-To: <akaeBJv5T3YmlfpC@pie>
Hi Yao,
On 17:21 Thu 02 Jul , Yao Zi wrote:
> On Thu, Jul 02, 2026 at 02:31:36AM +0000, Yixun Lan wrote:
> > SpacemiT K3 SoC consist of UFS (Universal Flash Storage) Host Controller
> > which has features compatible with JEDEC UFS 2.2, MIPI UniPro v1.61 and
> > M-PHY v3.0 standard.
> >
> > Signed-off-by: Yixun Lan <dlan@kernel.org>
> > ---
> > drivers/ufs/host/Kconfig | 12 +
> > drivers/ufs/host/Makefile | 1 +
> > drivers/ufs/host/ufs-spacemit.c | 931 ++++++++++++++++++++++++++++++++++++++++
> > drivers/ufs/host/ufs-spacemit.h | 90 ++++
> > 4 files changed, 1034 insertions(+)
>
> ...
>
> > +static int ufs_spacemit_wait_mphy_pll_lock(struct ufs_hba *hba)
> > +{
> > + int timeout = MPHY_PLL_LOCK_TIMEOUT_US;
> > + u32 val;
> > +
> > + while (timeout-- > 0) {
> > + val = ufshcd_readl(hba, UFS_PHY_MNG_BASE + UFS_MPHY_PU_CTRL);
> > + if (val & MPHY_PLL_LOCK_BIT)
> > + return 0;
> > +
> > + udelay(1);
> > + }
> > +
> > + dev_err(hba->dev, "M-PHY PLL lock timeout\n");
> > + return -ETIMEDOUT;
> > +}
>
> Could this loop be replaced by read_poll_timeout() like
>
> read_poll_timeout(ufshcd_readl, val, val & MPHY_PLL_LOCK_BIT,
> 1, MPHY_PLL_LOCK_TIMEOUT_US, false, hba,
> UFS_PHY_MSG_BASE + UFS_MPHY_PU_CTRL);
>
I think so, thanks for the suggestion
>
> ...
>
> > +/**
> > + * ufs_spacemit_init - init phy and prepare clk
> > + * @hba: host controller instance
> > + */
> > +static int ufs_spacemit_init(struct ufs_hba *hba)
> > +{
> > + int err = 0;
> > + struct device *dev = hba->dev;
> > + struct ufs_spacemit_host *host;
> > +
> > + host = devm_kzalloc(dev, sizeof(*host), GFP_KERNEL);
> > + if (!host)
> > + return -ENOMEM;
> > +
> > + host->rst = devm_reset_control_get_optional_exclusive_deasserted(dev, NULL);
>
> "resets" property is marked as required in the binding, but the optional
> API is used here. Is this expected?
>
Ok, I will switch to non-optional API and check return value
> ...
>
> > +/**
> > + * ufs_spacemit_hce_enable_notify - Configure HCE enable sequence
> > + * @hba: host controller instance
> > + * @status: notification status (PRE_CHANGE or POST_CHANGE)
> > + *
> > + * Configures host controller enable with proper sequencing.
> > + * Handles crypto enable if supported.
> > + *
> > + * Returns: 0 on success
> > + */
> > +static int ufs_spacemit_hce_enable_notify(struct ufs_hba *hba,
> > + enum ufs_notify_change_status status)
> > +{
> > + struct ufs_spacemit_host *host = ufshcd_get_variant(hba);
> > + u32 enable_val, val;
> > +
> > + if (status == PRE_CHANGE) {
> > + enable_val = CONTROLLER_ENABLE;
> > +
> > + if (hba->caps & UFSHCD_CAP_CRYPTO)
> > + enable_val = CRYPTO_GENERAL_ENABLE | CONTROLLER_ENABLE;
> > +
> > + if (!host->first_hce_done) {
> > + host->first_hce_done = true;
> > + dev_dbg(hba->dev, "First HCE enable\n");
> > + } else {
> > + val = ufshcd_readl(hba, REG_CONTROLLER_ENABLE);
> > + if (val == enable_val) {
> > + ufshcd_writel(hba, enable_val & (1 << CONTROLLER_ENABLE),
> > + REG_CONTROLLER_ENABLE);
> > +
> > + while (ufshcd_readl(hba, REG_CONTROLLER_ENABLE) ==
> > + (enable_val & (1 << CONTROLLER_ENABLE)))
> > + ;
>
> Shouldn't we set a timeout for the polling loop?
>
Yes, good idea and will do in next version
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2026-07-03 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 2:31 [PATCH 0/3] Add UFS Host driver support for SpacemiT K3 SoC Yixun Lan
2026-07-02 2:31 ` [PATCH 1/3] scsi: ufs: spacemit: dt-bindings: Add UFS controller for " Yixun Lan
2026-07-02 2:31 ` [PATCH 2/3] scsi: ufs: spacemit: k3: Add UFS Host Controller driver Yixun Lan
2026-07-02 7:53 ` Philipp Zabel
2026-07-03 0:16 ` Yixun Lan
2026-07-02 17:21 ` Yao Zi
2026-07-03 1:28 ` Yixun Lan [this message]
2026-07-02 2:31 ` [PATCH 3/3] riscv: dts: spacemit: k3: Add UFS support Yixun Lan
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=20260703012800-GKC35811@kernel.org \
--to=dlan@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alex@ghiti.fr \
--cc=alim.akhtar@samsung.com \
--cc=aou@eecs.berkeley.edu \
--cc=avri.altman@sandisk.com \
--cc=bvanassche@acm.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=me@ziyao.cc \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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