From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL]: Generic phy fixes for v7.2
Date: Sun, 2 Aug 2026 10:27:32 +0530 [thread overview]
Message-ID: <am7OPDaTANNI9yPk@vaman> (raw)
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
Hey Linus,
Please consider this pull request for couple of driver fixes for Generic
phy subsystem.
The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:
Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git tags/phy-fixes-7.2
for you to fetch changes up to 7eb61caf45607e1e1270f51f8f93f0ded53146da:
phy: zynqmp: keep SERDES scrambler and 8b/10b enabled for USB (2026-07-22 20:52:59 +0530)
----------------------------------------------------------------
phy fixes for 7.2
Couple of driver fixes
- Couple of zynqmp clock and pm error handling and SERDES scrambler
register handling
- Rockchip SSC spread fix
- Qualcomm musb return call fix
----------------------------------------------------------------
Alexey Charkov (1):
phy: rockchip: naneng-combphy: Always configure SSC spread direction
Krishna Kurapati (1):
phy: qcom: m31-eusb2: Fix return value of init call
Nava kishore Manne (3):
phy: zynqmp: fix L0_TM_DISABLE_SCRAMBLE_ENCODER mask
phy: zynqmp: use read-modify-write for SERDES scrambler bypass
phy: zynqmp: keep SERDES scrambler and 8b/10b enabled for USB
Radhey Shyam Pandey (2):
phy: zynqmp: fix clock error handling in xpsgtr_phy_init()
phy: zynqmp: fix runtime PM leak on probe allocation failure
drivers/phy/qualcomm/phy-qcom-m31-eusb2.c | 2 +-
drivers/phy/rockchip/phy-rockchip-naneng-combphy.c | 6 +--
drivers/phy/xilinx/phy-zynqmp.c | 62 ++++++++++++++++------
3 files changed, 49 insertions(+), 21 deletions(-)
Thanks
--
~Vinod
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2026-08-02 4:57 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=am7OPDaTANNI9yPk@vaman \
--to=vkoul@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).