public inbox for linux-phy@lists.infradead.org
 help / color / mirror / Atom feed
From: "Arthur Fabre" <arthur@arthurfabre.com>
To: "Heiko Stuebner" <heiko@sntech.de>, "Chukun Pan" <amadeus@jmu.edu.cn>
Cc: <linux-phy@lists.infradead.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-rockchip@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, "FUKAUMI Naoki" <naoki@radxa.com>
Subject: PROBLEM: Raxda Rock 5 ITX shared SATA broken by "phy: rockchip: naneng-combphy: fix phy reset"
Date: Sat, 21 Feb 2026 14:28:53 +0100	[thread overview]
Message-ID: <DGKOC0Y8UWRH.3TVFOP2ND9W9J@arthurfabre.com> (raw)

Hello,

I have a Raxda Rock 5 ITX, with a device-tree overlay to enable
the shared SATA port:

// ROCK 5 ITX M.2 E-Key Sata
/dts-v1/;
/plugin/;

/ {
	fragment@0 {
		target = <&pcie2x1l0>;

		__overlay__ {
			status = "disabled";
		};
	};

	fragment@1 {
		target = <&sata1>;

		__overlay__ {
			status = "okay";
		};
	};
};

This worked fine, with the kernel normally logging:

[    0.754425] ata1: SATA max UDMA/133 abar m8192@0xf1282000 port 0xf1282100 irq 70 lpm-pol 0
[    1.692424] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

However this stopped working after a kernel update:

[    2.687755] ata1: SATA max UDMA/133 mmio [mem 0xfe220000-0xfe220fff] port 0x100 irq 79 lpm-pol 0
[    4.893204] ata1: SATA link down (SStatus 1 SControl 300)
[    7.111503] ata1: SATA link down (SStatus 1 SControl 300)
[    7.111993] ata1: limiting SATA link speed to 1.5 Gbps

I've reliably bisected it to commit:
fbcbffbac994 "phy: rockchip: naneng-combphy: fix phy reset".

Unfortunately coming up with a patch is out of my depth.
Happy to test any suggestions.

If it matters I'm using the EDK2 UEFI firmware v1.1:
https://github.com/edk2-porting/edk2-rk3588

Thank you,

Arthur

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

                 reply	other threads:[~2026-02-21 13:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DGKOC0Y8UWRH.3TVFOP2ND9W9J@arthurfabre.com \
    --to=arthur@arthurfabre.com \
    --cc=amadeus@jmu.edu.cn \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=naoki@radxa.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox