All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@kernel.org>
To: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>
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 0/3] Add UFS Host driver support for SpacemiT K3 SoC
Date: Mon, 13 Jul 2026 12:37:59 +0000	[thread overview]
Message-ID: <20260713123759-GKD106000@kernel.org> (raw)
In-Reply-To: <wjbz5tp7vjrsjwjaiu3n7du5ksbrlsduuxhwg2wriyxshkrqd5@t3sdxr6ua2sg>

Hi Anirudh,

On 22:40 Sun 12 Jul     , Anirudh Srinivasan wrote:
> Hi Yixun,
> 
> On Thu, Jul 02, 2026 at 02:31:34AM +0000, Yixun Lan wrote:
> > This series try to add UFS support for SpacemiT K3 SoC, the controller
> > components consists of System Bus Interface Unit, UFS Host Controller
> > Interface, UFS Transport Protocol Layer, UFS Host Registers, Device
> > Management Entity (DME), Transport Layer, Network Layer, Data Link
> > Layer, PHY Adapter Layer, and M-PHY Interface. A more detail functional
> > block diagram can be found in SpacemiT website, chapter 9.7.3 [1]
> > 
> > Please note, in order to test this driver, the UFS clock driver[2] here
> > should be applied first as a prerequisite patch.
> > 
> > One known issue is that the device will occasionally raise BKOPS interrupt
> > when doing some high load test, log from dmesg shows
> > 
> > [  806.710763] ufshcd-spacemit c0e00000.ufshc: ufshcd_bkops_exception_event_handler: device raised urgent BKOPS exception for bkops status 1
> > 
> > Link: https://spacemit.com/community/document/info?nodepath=hardware/key_stone/k3/k3_docs/k3_usermanual/09_memory_storage.md&lang=en [1]
> > Link: https://lore.kernel.org/all/20260630-06-clk-ufs-support-v1-0-cf7521d1d0fe@kernel.org/ [2]
> > Signed-off-by: Yixun Lan <dlan@kernel.org>
> 
> I see this during probe on a k3-pico-itx. Does the UFS chip on board
> have an RPMB block on it? Is this error of any concern.
> 
It's probably true of having a RPMB block, but not used in K3 platform, so can ignore

> [    5.957864] ufshcd-spacemit c0e00000.ufshc: ufshcd_scsi_add_wlus: BOOT WLUN not found
> [    5.963319] bus_add_device: cannot add device 'ufs_rpmb0' to unregistered bus 'ufs_rpmb'
> [    5.971155] ufshcd-spacemit c0e00000.ufshc: Failed to register UFS RPMB device 0
> 
Maybe disable CONFIG_RPMB to silent this? I've not tested this option locally

-- 
Yixun Lan (dlan)

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Yixun Lan <dlan@kernel.org>
To: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>
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 0/3] Add UFS Host driver support for SpacemiT K3 SoC
Date: Mon, 13 Jul 2026 12:37:59 +0000	[thread overview]
Message-ID: <20260713123759-GKD106000@kernel.org> (raw)
In-Reply-To: <wjbz5tp7vjrsjwjaiu3n7du5ksbrlsduuxhwg2wriyxshkrqd5@t3sdxr6ua2sg>

Hi Anirudh,

On 22:40 Sun 12 Jul     , Anirudh Srinivasan wrote:
> Hi Yixun,
> 
> On Thu, Jul 02, 2026 at 02:31:34AM +0000, Yixun Lan wrote:
> > This series try to add UFS support for SpacemiT K3 SoC, the controller
> > components consists of System Bus Interface Unit, UFS Host Controller
> > Interface, UFS Transport Protocol Layer, UFS Host Registers, Device
> > Management Entity (DME), Transport Layer, Network Layer, Data Link
> > Layer, PHY Adapter Layer, and M-PHY Interface. A more detail functional
> > block diagram can be found in SpacemiT website, chapter 9.7.3 [1]
> > 
> > Please note, in order to test this driver, the UFS clock driver[2] here
> > should be applied first as a prerequisite patch.
> > 
> > One known issue is that the device will occasionally raise BKOPS interrupt
> > when doing some high load test, log from dmesg shows
> > 
> > [  806.710763] ufshcd-spacemit c0e00000.ufshc: ufshcd_bkops_exception_event_handler: device raised urgent BKOPS exception for bkops status 1
> > 
> > Link: https://spacemit.com/community/document/info?nodepath=hardware/key_stone/k3/k3_docs/k3_usermanual/09_memory_storage.md&lang=en [1]
> > Link: https://lore.kernel.org/all/20260630-06-clk-ufs-support-v1-0-cf7521d1d0fe@kernel.org/ [2]
> > Signed-off-by: Yixun Lan <dlan@kernel.org>
> 
> I see this during probe on a k3-pico-itx. Does the UFS chip on board
> have an RPMB block on it? Is this error of any concern.
> 
It's probably true of having a RPMB block, but not used in K3 platform, so can ignore

> [    5.957864] ufshcd-spacemit c0e00000.ufshc: ufshcd_scsi_add_wlus: BOOT WLUN not found
> [    5.963319] bus_add_device: cannot add device 'ufs_rpmb0' to unregistered bus 'ufs_rpmb'
> [    5.971155] ufshcd-spacemit c0e00000.ufshc: Failed to register UFS RPMB device 0
> 
Maybe disable CONFIG_RPMB to silent this? I've not tested this option locally

-- 
Yixun Lan (dlan)

  reply	other threads:[~2026-07-13 12:38 UTC|newest]

Thread overview: 38+ 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 ` 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   ` Yixun Lan
2026-07-02  2:38   ` sashiko-bot
2026-07-02  6:43     ` Yixun Lan
2026-07-02  2:31 ` [PATCH 2/3] scsi: ufs: spacemit: k3: Add UFS Host Controller driver Yixun Lan
2026-07-02  2:31   ` Yixun Lan
2026-07-02  2:46   ` sashiko-bot
2026-07-02  7:53   ` Philipp Zabel
2026-07-02  7:53     ` Philipp Zabel
2026-07-03  0:16     ` Yixun Lan
2026-07-03  0:16       ` Yixun Lan
2026-07-02 17:21   ` Yao Zi
2026-07-02 17:21     ` Yao Zi
2026-07-03  1:28     ` Yixun Lan
2026-07-03  1:28       ` Yixun Lan
2026-07-06 14:01   ` Bart Van Assche
2026-07-06 14:01     ` Bart Van Assche
2026-07-08  7:10     ` Yixun Lan
2026-07-08  7:10       ` Yixun Lan
2026-07-12 20:16   ` Anirudh Srinivasan
2026-07-12 20:16     ` Anirudh Srinivasan
2026-07-02  2:31 ` [PATCH 3/3] riscv: dts: spacemit: k3: Add UFS support Yixun Lan
2026-07-02  2:31   ` Yixun Lan
2026-07-02  2:44   ` sashiko-bot
2026-07-04 14:01   ` Jennifer Berringer
2026-07-04 14:01     ` Jennifer Berringer
2026-07-08  2:17     ` Yixun Lan
2026-07-08  2:17       ` Yixun Lan
2026-07-13  3:40 ` [PATCH 0/3] Add UFS Host driver support for SpacemiT K3 SoC Anirudh Srinivasan
2026-07-13  3:40   ` Anirudh Srinivasan
2026-07-13 12:37   ` Yixun Lan [this message]
2026-07-13 12:37     ` Yixun Lan
2026-07-13 14:56     ` Anirudh Srinivasan
2026-07-13 14:56       ` Anirudh Srinivasan
2026-07-13 23:57       ` Yixun Lan
2026-07-13 23:57         ` 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=20260713123759-GKD106000@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=asrinivasan@oss.tenstorrent.com \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.