From: Minda Chen <minda.chen@starfivetech.com>
To: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
linux-phy@lists.infradead.org
Cc: Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Rob Herring <robh+dt@kernel.org>, Conor Dooley <conor@kernel.org>,
linux-kernel@vger.kernel.org,
Minda Chen <minda.chen@starfivetech.com>
Subject: [PATCH v3 0/1] Fix configuration for on-chip USB 2.0 support
Date: Mon, 2 Sep 2024 19:11:26 +0800 [thread overview]
Message-ID: <20240902111127.15155-1-minda.chen@starfivetech.com> (raw)
While mainline has support for the USB controller of the JH7110 since 6.5,
this never really worked, even not with latest downstream kernels by Starfive -
unless you were also using an old downstream U-Boot version. The reason for
that was a missing syscon setting that prevented the connection between USB
2.0 PHY and the controller. This series finally fixes the issue.
Changes in v2:
- fix copy&paste mistake in error patch found by kernel test robot and Dan Carpenter
Change in v3:
- Using syscon_regmap_lookup_by_compatible() to lookup regmap. So dts
with no changed. Delete v2 patch1 and patch 2.
base on v6.11-rc5
Jan Kiszka (1):
phy: starfive: jh7110-usb: Fix link configuration to controller
drivers/phy/starfive/phy-jh7110-usb.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
base-commit: 5be63fc19fcaa4c236b307420483578a56986a37
--
2.17.1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next reply other threads:[~2024-09-02 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 11:11 Minda Chen [this message]
2024-09-02 11:11 ` [PATCH v3 1/1] phy: starfive: jh7110-usb: Fix link configuration to controller Minda Chen
2024-09-09 11:02 ` Conor Dooley
2024-09-14 6:49 ` Minda Chen
2024-10-29 11:26 ` Emil Renner Berthing
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=20240902111127.15155-1-minda.chen@starfivetech.com \
--to=minda.chen@starfivetech.com \
--cc=conor@kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=jan.kiszka@siemens.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).