The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 updates for v6.13
Date: Thu, 26 Dec 2024 19:12:32 +0530	[thread overview]
Message-ID: <Z21dSH5rNYKrPPcD@vaman> (raw)

[-- Attachment #1: Type: text/plain, Size: 2636 bytes --]

Hello Linus,

Here is the 6.13 fixes for Generic phy subsystem. A few core API fixes
for devm calls and bunch of driver fixes as usual

The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:

  Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git tags/phy-fixes-6.13

for you to fetch changes up to 17194c2998d39ab366a2ecbc4d1f3281e00d6a05:

  phy: mediatek: phy-mtk-hdmi: add regulator dependency (2024-12-24 20:38:53 +0530)

----------------------------------------------------------------
phy fixes for 6.13

 - devm_phy_xxx fixes for few APIs in the phy core
 - qmp driver register name config
 - init sequence fix for usb driver
 - rockchip driver setting drvdata correctly in samsung hdptx and reset
   fix for naneng combophy
 - regulator dependency fix for mediatek hdmi driver
 - overflow assertion fix for stm32 driver

----------------------------------------------------------------
Adam Ford (1):
      phy: freescale: fsl-samsung-hdmi: Fix 64-by-32 division cocci warnings

Arnd Bergmann (2):
      phy: stm32: work around constant-value overflow assertion
      phy: mediatek: phy-mtk-hdmi: add regulator dependency

Chukun Pan (1):
      phy: rockchip: naneng-combphy: fix phy reset

Cristian Ciocaltea (1):
      phy: rockchip: samsung-hdptx: Set drvdata before enabling runtime PM

Justin Chen (1):
      phy: usb: Toggle the PHY power during init

Krishna Kurapati (1):
      phy: qcom-qmp: Fix register name in RX Lane config of SC8280XP

Zijun Hu (5):
      phy: core: Fix that API devm_phy_put() fails to release the phy
      phy: core: Fix that API devm_of_phy_provider_unregister() fails to unregister the phy provider
      phy: core: Fix that API devm_phy_destroy() fails to destroy the phy
      phy: core: Fix an OF node refcount leakage in _of_phy_get()
      phy: core: Fix an OF node refcount leakage in of_phy_provider_lookup()

 drivers/phy/broadcom/phy-brcm-usb-init-synopsys.c  |  6 ++++++
 drivers/phy/freescale/phy-fsl-samsung-hdmi.c       |  3 +--
 drivers/phy/mediatek/Kconfig                       |  1 +
 drivers/phy/phy-core.c                             | 21 +++++++++++++--------
 drivers/phy/qualcomm/phy-qcom-qmp-usb.c            |  2 +-
 drivers/phy/rockchip/phy-rockchip-naneng-combphy.c |  2 +-
 drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c  |  3 ++-
 drivers/phy/st/phy-stm32-combophy.c                | 21 +++++++++++++++------
 8 files changed, 40 insertions(+), 19 deletions(-)

-- 
~Vinod

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2024-12-26 13:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26 13:42 Vinod Koul [this message]
2024-12-26 21:24 ` [GIT PULL]: Generic phy updates for v6.13 pr-tracker-bot

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=Z21dSH5rNYKrPPcD@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