Devicetree
 help / color / mirror / Atom feed
From: Jan Paszkowski <jan.m.paszkowski@gmail.com>
To: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Cc: marijn.suijten@somainline.org,
	Jan Paszkowski <jan.m.paszkowski@gmail.com>
Subject: [PATCH 0/1] arm64: dts: qcom: sm8350-sagami: UFS
Date: Wed,  9 Sep 2026 19:13:11 +0200	[thread overview]
Message-ID: <20260909172421.33593-1-jan.m.paszkowski@gmail.com> (raw)

This patch is about turning on the UFS for the sony xperia sagami
platform.

The patch is small, but due to the grave risk of the patch combined with
my inexperience I wanted to write this cover letter.

While digging through the reasons for the UFS bug in sony devices, I
stumbled upon a downstream workaround in the initial commit for
sm8250-sony-xperia devices [1]. The workaround did not mention the
sagami platform. Looking through android patches for UFS for the sony
sagami copyleft kernel, they seemed to be minor compared to previous
generations[2].

With that I got a spare pdx215 to try this on. I compiled a kernel with
postmarketOS tools. Normal flashing of pmOS on a single partition seemed
to not work, though the UFS device was visible when booting on the sd
card. That said both split flashing of pmOS onto two partitions and
formating partitions worked, at least for super and userdata with ext4.
The booted device detected the partitions and even worked without the sd
card. With that I wanted to send it to the mailing lists in case the bug
is gone this generation.

I guess that most likely I am missing something. If so please respond to
this series. I am happy to test  further to make sure it won't brick
anybody's device.

[1] https://github.com/kholk/kernel/commit/2e7a9ee1c91a016baa0b826a7752ec45663a0561
[2] https://github.com/sonyxperiadev/kernel-copyleft/tree/61.0.A.11.xxx


Jan Paszkowski (1):
  arm64: dts: qcom: sm8350-sony-xperia-sagami: enable UFS

 .../dts/qcom/sm8350-sony-xperia-sagami.dtsi     | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-09-09 17:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 17:13 Jan Paszkowski [this message]
2026-09-09 17:13 ` [PATCH 1/1] arm64: dts: qcom: sm8350-sony-xperia-sagami: enable UFS Jan Paszkowski
2026-09-09 17:30   ` sashiko-bot
2026-09-09 17:44     ` Jan Paszkowski
2026-09-09 19:07   ` Dmitry Baryshkov

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=20260909172421.33593-1-jan.m.paszkowski@gmail.com \
    --to=jan.m.paszkowski@gmail.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=robh@kernel.org \
    /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