All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: E Shattow <e@freeshell.de>
Cc: Yixun Lan <dlan@kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	"Martin K. Petersen" <mkp@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@sandisk.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Bean Huo <beanhuo@micron.com>,
	Stanley Jhu <stanleyjhu@google.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	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>,
	Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>,
	Jennifer Berringer <jberring@redhat.com>,
	Trevor Gamblin <tgamblin@baylibre.com>,
	linux-scsi@vger.kernel.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v8 0/2] Add UFS Host driver support for SpacemiT K3 SoC
Date: Thu, 19 Nov 2026 17:55:45 +0100	[thread overview]
Message-ID: <av8qEXk68wsy7pNe@aurel32.net> (raw)
In-Reply-To: <053b55fe-47d0-4cc7-ba53-c560fc9c1d1b@freeshell.de>

Hi,

On 2026-11-18 23:38, E Shattow wrote:
> I was missing this detail previously. For testing again of v8 I have now
> inserted a sed pipe to change this as suggested for the dts application
> step of the build procedure:
> 
> b4 am -v5 -P3 -o- \
>  https://lore.kernel.org/all/20260916-08-k3-ufs-support-v5-0-1f5d71f1027d@kernel.org/ \
>  | sed -z 's%\(clock-names = "axi", "\)ref\(";\)%\1ref_clk\2%' \
>  | patch -p1
> 
> Additionally to the build procedure, since Debian testing now features
> linux-config-7.3 and no longer linux-config-7.2, I now substitute
> accordingly from linux-config-7.2 to linux-config-7.3

[...]

> $ journalctl --dmesg | grep ufshcd
> ufshcd-spacemit c0e00000.ufshc: freq-table-hz property not specified
> ufshcd-spacemit c0e00000.ufshc: ufshcd_populate_vreg: Unable to find
> vdd-hba-supply regulator, assuming enabled
> ufshcd-spacemit c0e00000.ufshc: ufshcd_populate_vreg: Unable to find
> vcc-supply regulator, assuming enabled
> ufshcd-spacemit c0e00000.ufshc: ufshcd_populate_vreg: Unable to find
> vccq-supply regulator, assuming enabled
> ufshcd-spacemit c0e00000.ufshc: ufshcd_populate_vreg: Unable to find
> vccq2-supply regulator, assuming enabled
> scsi host0: ufshcd
> ufshcd-spacemit c0e00000.ufshc: ufshcd_scsi_add_wlus: BOOT WLUN not found

All those are expected, so it's great that the issue you reported is 
fixed.

> I did not again see the DL error event. However, the first attempt to
> build Linux does fail:
> 
> make[7]: *** [scripts/Makefile.build:572: drivers/gpu/drm] Error 2
> make[6]: *** [scripts/Makefile.build:572: drivers/gpu] Error 2
> ...
> make[5]: *** [scripts/Makefile.build:572: drivers] Error 2
> make[4]: *** [Makefile:2244: .] Error 2
> make[3]: *** [debian/rules:80: build-arch] Error 2
> dpkg-buildpackage: error: make -f debian/rules binary subprocess failed
> with exit status 2
> make[2]: *** [scripts/Makefile.package:126: bindeb-pkg] Error 2
> make[1]: *** [/home/es/linux-7.4-rc3/Makefile:1852: bindeb-pkg] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
> 
> real    188m48.844s
> user    1415m17.363s
> sys     66m11.932s

I guess the error is some GCC ICE.

> Linux is running on the K3 SoC here without clocks preparation from the
> bootloader; it is quite slow by comparison to a Linux kernel that
> follows clock preparations by the vendor BSP bootloader. Simply
> re-running the same "make ..." build command is successful in the same
> system without any changes:
> 
>   DEPMOD  debian/linux-image-7.4.0-rc3-k3ufs/lib/modules/7.4.0-rc3-k3ufs
> ...
> dpkg-deb: building package 'linux-image-7.4.0-rc3-k3ufs' in
> '../linux-image-7.4.0-rc3-k3ufs_7.4.0~rc3-2_riscv64.deb'.
> ...
> real    34m56.794s
> user    241m15.511s
> sys     18m4.532s
> 
> Similar build failures occasionally happen when the root filesystem is
> on USB microSD adapter-connected microSD storage. I assume the build
> failures with default clocks configuration are not constrained to just
> the UFS support series here.

Yes, this is a known issue, unfortunately the K3 does not run stable 
under load. See this thread (although it seems at the end the K1 and K3 
issues are different ones):
https://lore.kernel.org/linux-riscv/apSYF5x1Tu7PlyL1@aurel32.net/

Also see this Fedora issue:
https://forge.fedoraproject.org/riscv/planning/issues/36

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

WARNING: multiple messages have this Message-ID (diff)
From: Aurelien Jarno <aurelien@aurel32.net>
To: E Shattow <e@freeshell.de>
Cc: Yixun Lan <dlan@kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	"Martin K. Petersen" <mkp@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@sandisk.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Bean Huo <beanhuo@micron.com>,
	Stanley Jhu <stanleyjhu@google.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	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>,
	Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>,
	Jennifer Berringer <jberring@redhat.com>,
	Trevor Gamblin <tgamblin@baylibre.com>,
	linux-scsi@vger.kernel.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v8 0/2] Add UFS Host driver support for SpacemiT K3 SoC
Date: Thu, 19 Nov 2026 17:55:45 +0100	[thread overview]
Message-ID: <av8qEXk68wsy7pNe@aurel32.net> (raw)
In-Reply-To: <053b55fe-47d0-4cc7-ba53-c560fc9c1d1b@freeshell.de>

Hi,

On 2026-11-18 23:38, E Shattow wrote:
> I was missing this detail previously. For testing again of v8 I have now
> inserted a sed pipe to change this as suggested for the dts application
> step of the build procedure:
> 
> b4 am -v5 -P3 -o- \
>  https://lore.kernel.org/all/20260916-08-k3-ufs-support-v5-0-1f5d71f1027d@kernel.org/ \
>  | sed -z 's%\(clock-names = "axi", "\)ref\(";\)%\1ref_clk\2%' \
>  | patch -p1
> 
> Additionally to the build procedure, since Debian testing now features
> linux-config-7.3 and no longer linux-config-7.2, I now substitute
> accordingly from linux-config-7.2 to linux-config-7.3

[...]

> $ journalctl --dmesg | grep ufshcd
> ufshcd-spacemit c0e00000.ufshc: freq-table-hz property not specified
> ufshcd-spacemit c0e00000.ufshc: ufshcd_populate_vreg: Unable to find
> vdd-hba-supply regulator, assuming enabled
> ufshcd-spacemit c0e00000.ufshc: ufshcd_populate_vreg: Unable to find
> vcc-supply regulator, assuming enabled
> ufshcd-spacemit c0e00000.ufshc: ufshcd_populate_vreg: Unable to find
> vccq-supply regulator, assuming enabled
> ufshcd-spacemit c0e00000.ufshc: ufshcd_populate_vreg: Unable to find
> vccq2-supply regulator, assuming enabled
> scsi host0: ufshcd
> ufshcd-spacemit c0e00000.ufshc: ufshcd_scsi_add_wlus: BOOT WLUN not found

All those are expected, so it's great that the issue you reported is 
fixed.

> I did not again see the DL error event. However, the first attempt to
> build Linux does fail:
> 
> make[7]: *** [scripts/Makefile.build:572: drivers/gpu/drm] Error 2
> make[6]: *** [scripts/Makefile.build:572: drivers/gpu] Error 2
> ...
> make[5]: *** [scripts/Makefile.build:572: drivers] Error 2
> make[4]: *** [Makefile:2244: .] Error 2
> make[3]: *** [debian/rules:80: build-arch] Error 2
> dpkg-buildpackage: error: make -f debian/rules binary subprocess failed
> with exit status 2
> make[2]: *** [scripts/Makefile.package:126: bindeb-pkg] Error 2
> make[1]: *** [/home/es/linux-7.4-rc3/Makefile:1852: bindeb-pkg] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
> 
> real    188m48.844s
> user    1415m17.363s
> sys     66m11.932s

I guess the error is some GCC ICE.

> Linux is running on the K3 SoC here without clocks preparation from the
> bootloader; it is quite slow by comparison to a Linux kernel that
> follows clock preparations by the vendor BSP bootloader. Simply
> re-running the same "make ..." build command is successful in the same
> system without any changes:
> 
>   DEPMOD  debian/linux-image-7.4.0-rc3-k3ufs/lib/modules/7.4.0-rc3-k3ufs
> ...
> dpkg-deb: building package 'linux-image-7.4.0-rc3-k3ufs' in
> '../linux-image-7.4.0-rc3-k3ufs_7.4.0~rc3-2_riscv64.deb'.
> ...
> real    34m56.794s
> user    241m15.511s
> sys     18m4.532s
> 
> Similar build failures occasionally happen when the root filesystem is
> on USB microSD adapter-connected microSD storage. I assume the build
> failures with default clocks configuration are not constrained to just
> the UFS support series here.

Yes, this is a known issue, unfortunately the K3 does not run stable 
under load. See this thread (although it seems at the end the K1 and K3 
issues are different ones):
https://lore.kernel.org/linux-riscv/apSYF5x1Tu7PlyL1@aurel32.net/

Also see this Fedora issue:
https://forge.fedoraproject.org/riscv/planning/issues/36

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

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

  reply	other threads:[~2026-11-19 16:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16  3:46 [PATCH v8 0/2] Add UFS Host driver support for SpacemiT K3 SoC Yixun Lan
2026-11-16  3:46 ` Yixun Lan
2026-11-16  3:46 ` [PATCH v8 1/2] scsi: ufs: spacemit: dt-bindings: Add UFS controller for " Yixun Lan
2026-11-16  3:46   ` Yixun Lan
2026-11-16  3:46 ` [PATCH v8 2/2] scsi: ufs: spacemit: k3: Add UFS Host Controller driver Yixun Lan
2026-11-16  3:46   ` Yixun Lan
2026-11-16  4:16   ` sashiko-bot
2026-11-17 19:44   ` Aurelien Jarno
2026-11-17 19:44     ` Aurelien Jarno
2026-11-17  1:15 ` [PATCH v8 0/2] Add UFS Host driver support for SpacemiT K3 SoC E Shattow
2026-11-17  1:15   ` E Shattow
2026-11-17  3:17   ` Yixun Lan
2026-11-17  3:17     ` Yixun Lan
2026-11-17 19:44   ` Aurelien Jarno
2026-11-17 19:44     ` Aurelien Jarno
2026-11-19  7:38     ` E Shattow
2026-11-19  7:38       ` E Shattow
2026-11-19 16:55       ` Aurelien Jarno [this message]
2026-11-19 16:55         ` Aurelien Jarno

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=av8qEXk68wsy7pNe@aurel32.net \
    --to=aurelien@aurel32.net \
    --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=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@kernel.org \
    --cc=e@freeshell.de \
    --cc=jberring@redhat.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mkp@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=spacemit@lists.linux.dev \
    --cc=stanleyjhu@google.com \
    --cc=tgamblin@baylibre.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 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.