From: Inochi Amaoto <inochiama@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Yixun Lan <dlan@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Inochi Amaoto <inochiama@gmail.com>
Cc: devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org,
Yixun Lan <dlan@gentoo.org>, Longbin Li <looong.bin@gmail.com>
Subject: [PATCH v2 0/2] riscv: dts: spacemit: Fix phy id check for the phy
Date: Sun, 26 Jul 2026 07:33:48 +0800 [thread overview]
Message-ID: <20260725233351.55004-1-inochiama@gmail.com> (raw)
As reported, the phy framework can not detected the phy id correctly
when re-initialize this. So add the phy id compatible string to the
etherenet phy, so the phy can be reinit successfully.
Note: separate this patchset as two patch for backport if necessary.
Changed from v1:
- https://lore.kernel.org/spacemit/20260725005804.373698-1-inochiama@gmail.com
1. Remove all the c22 fallback compatible.
Inochi Amaoto (2):
riscv: dts: spacemit: Fix phy id check for the phy on pico-itx board
riscv: dts: spacemit: Fix phy id check for the phy on com260 board
arch/riscv/boot/dts/spacemit/k3-com260.dtsi | 2 +-
arch/riscv/boot/dts/spacemit/k3-pico-itx.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.55.0
next reply other threads:[~2026-07-25 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 23:33 Inochi Amaoto [this message]
2026-07-25 23:33 ` [PATCH v2 1/2] riscv: dts: spacemit: Fix phy id check for the phy on pico-itx board Inochi Amaoto
2026-07-25 23:33 ` [PATCH v2 2/2] riscv: dts: spacemit: Fix phy id check for the phy on com260 board Inochi Amaoto
2026-07-26 8:00 ` [PATCH v2 0/2] riscv: dts: spacemit: Fix phy id check for the phy 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=20260725233351.55004-1-inochiama@gmail.com \
--to=inochiama@gmail.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=dlan@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=looong.bin@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox