summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorKoichiro Den <den@valinux.co.jp>2026-09-11 16:30:58 +0900
committerGeert Uytterhoeven <geert+renesas@glider.be>2026-09-14 10:07:09 +0200
commit8dc2615d5702059b2b71fca6f93c0d7d10ae54cb (patch)
treebac1808efa06a9f84c4f2de7b4cd5fafef1c53d7 /tools/perf/scripts/python/stackcollapse.py
parent2ac7bad110be6ebe478d6bd57821f7f5259a1f54 (diff)
downloadlinux-next-8dc2615d5702059b2b71fca6f93c0d7d10ae54cb.tar.gz
linux-next-8dc2615d5702059b2b71fca6f93c0d7d10ae54cb.zip
arm64: dts: renesas: r8a779f0: Set UFS lane count
Since commit e72323f3b09f ("scsi: ufs: core: Configure only active lanes during link"), the following error is observed on R-Car S4: ufshcd-renesas e6860000.ufs: Tx lane mismatch [config,reported] [2,1] ufshcd-renesas e6860000.ufs: link startup failed -67 ufshcd-renesas e6860000.ufs: error -ENOLINK: Initialization failed with error -67 ufshcd-renesas e6860000.ufs: probe with driver ufshcd-renesas failed with error -67 R-Car S4 has one UFS lane per direction, as described in section 152.1 of its hardware manual. Without lanes-per-direction, the UFS platform driver defaults to two lanes. Previously, the core used PA_CONNECTEDRXDATALANES and PA_CONNECTEDTXDATALANES to configure the link without checking them against lanes-per-direction, so the missing property did not prevent initialization. Explicitly set lanes-per-direction to 1, now that the validation is in place. Fixes: 5235d551779d ("arm64: dts: renesas: r8a779f0: Add UFS node") Cc: stable@vger.kernel.org # 7.2+ Signed-off-by: Koichiro Den <den@valinux.co.jp> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be> Link: https://patch.msgid.link/20260911073058.253000-1-den@valinux.co.jp Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions