public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Yu-Chun Lin <eleanor.lin@realtek•com>
To: <robh@kernel•org>, <krzk+dt@kernel•org>, <conor+dt@kernel•org>,
	<tychang@realtek•com>
Cc: <eleanor.lin@realtek•com>, <cy.huang@realtek•com>,
	<stanley_chang@realtek•com>, <james.tai@realtek•com>,
	<afaerber@suse•com>, <devicetree@vger•kernel.org>,
	<linux-kernel@vger•kernel.org>,
	<linux-arm-kernel@lists•infradead.org>,
	<linux-realtek-soc@lists•infradead.org>
Subject: [PATCH 0/3] soc: realtek: Add Realtek DHC I/O level detector support
Date: Thu, 4 Jun 2026 19:18:17 +0800	[thread overview]
Message-ID: <20260604111821.975624-1-eleanor.lin@realtek.com> (raw)

Hi all,

This patch series introduces support for the Realtek DHC I/O level detector.

The Realtek DHC I/O level detector is a hardware block responsible for
detecting the I/O signaling levels (1.8V or 3.3V) of various IP blocks
such as RGMII, SDIO, eMMC, CSI, SD, UART1, and AIO.

The driver reads the hardware registers to determine the current I/O voltage
levels. Based on these detection results, it dynamically selects and applies
the appropriate pinctrl states to ensure the correct pad configurations are
used for each interface.

Thanks,
Yu-Chun

Tzuyi Chang (2):
  dt-bindings: soc: realtek: Add Realtek DHC I/O level detector
  soc: realtek: Add driver for DHC I/O level detector

Yu-Chun Lin (1):
  arm64: dts: realtek: Add I/O level detector

 .../realtek/realtek,rtd1625-io-detect.yaml    |  77 +++++++++
 MAINTAINERS                                   |   1 +
 arch/arm64/boot/dts/realtek/kent-pinctrl.dtsi | 108 +++++++++++++
 arch/arm64/boot/dts/realtek/kent.dtsi         |  28 ++++
 drivers/soc/Kconfig                           |   1 +
 drivers/soc/Makefile                          |   1 +
 drivers/soc/realtek/Kconfig                   |  21 +++
 drivers/soc/realtek/Makefile                  |   2 +
 drivers/soc/realtek/rtd-io-detect.c           | 152 ++++++++++++++++++
 9 files changed, 391 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/soc/realtek/realtek,rtd1625-io-detect.yaml
 create mode 100644 arch/arm64/boot/dts/realtek/kent-pinctrl.dtsi
 create mode 100644 drivers/soc/realtek/Kconfig
 create mode 100644 drivers/soc/realtek/Makefile
 create mode 100644 drivers/soc/realtek/rtd-io-detect.c

-- 
2.43.0



             reply	other threads:[~2026-06-04 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 11:18 Yu-Chun Lin [this message]
2026-06-04 11:18 ` [PATCH 1/3] dt-bindings: soc: realtek: Add Realtek DHC I/O level detector Yu-Chun Lin
2026-06-04 12:49   ` Krzysztof Kozlowski
2026-06-04 11:18 ` [PATCH 2/3] soc: realtek: Add driver for " Yu-Chun Lin
2026-06-04 11:18 ` [PATCH 3/3] arm64: dts: realtek: Add " Yu-Chun Lin

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=20260604111821.975624-1-eleanor.lin@realtek.com \
    --to=eleanor.lin@realtek$(echo .)com \
    --cc=afaerber@suse$(echo .)com \
    --cc=conor+dt@kernel$(echo .)org \
    --cc=cy.huang@realtek$(echo .)com \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=james.tai@realtek$(echo .)com \
    --cc=krzk+dt@kernel$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-realtek-soc@lists$(echo .)infradead.org \
    --cc=robh@kernel$(echo .)org \
    --cc=stanley_chang@realtek$(echo .)com \
    --cc=tychang@realtek$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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