From: Rob Herring <robh@kernel.org>
To: Tzu-Hao Wei <twei@axiado.com>
Cc: devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
SriNavmani A <srinavmani@axiado.com>,
openbmc@lists.ozlabs.org,
Neil Armstrong <neil.armstrong@linaro.org>,
Prasad Bolisetty <pbolisetty@axiado.com>,
linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH 0/4] Add eMMC PHY support for Axiado AX3000 SoC
Date: Mon, 12 Jan 2026 09:17:30 -0600 [thread overview]
Message-ID: <176822994353.7723.17700786956910310022.robh@kernel.org> (raw)
In-Reply-To: <20260109-axiado-ax3000-add-emmc-phy-driver-support-v1-0-dd43459dbfea@axiado.com>
On Fri, 09 Jan 2026 17:43:28 +0800, Tzu-Hao Wei wrote:
> Axiado AX3000 SoC contains Arasan PHY which provides the interface to the
> HS200 eMMC controller.
>
> This series includes:
> 1. Add bindings for Axiado AX3000 eMMC PHY
> 2. Add Axiado AX3000 eMMC phy driver
> 3. Update MAINTAINERS for the new driver
> 4. Update Axiado AX3000 device tree
>
> Changes: (The previous version was mixed with Host driver, so I separate
> the PHY driver as a new thread)
> - Fix property order in required section to match properties section
> - Fixed example to use lowercase hex and proper node naming
> - Removed wrapper functions, use readl/writel directly
> - Replaced manual polling loops with read_poll_timeout macro
> - Used devm_platform_ioremap_resource instead of separate calls
> - Removed unnecessary of_match_node check
> - Used dev_err_probe for error reporting
> - Added proper Kconfig dependencies (ARCH_AXIADO || COMPILE_TEST)
> - Fixed various coding style issues
> - Link to previous patches: https://lore.kernel.org/all/20251222-axiado-ax3000-add-emmc-host-driver-support-v1-0-5457d0ebcdb4@axiado.com/
>
> Signed-off-by: Tzu-Hao Wei <twei@axiado.com>
> ---
> SriNavmani A (3):
> dt-bindings: phy: axiado,ax3000-emmc-phy: add Axiado eMMC PHY
> phy: axiado: add Axiado eMMC PHY driver
> arm64: dts: axiado: Add eMMC PHY node
>
> Tzu-Hao Wei (1):
> MAINTAINERS: Add Axiado AX3000 eMMC PHY driver
>
> .../bindings/phy/axiado,ax3000-emmc-phy.yaml | 38 ++++
> MAINTAINERS | 10 +
> arch/arm64/boot/dts/axiado/ax3000.dtsi | 7 +
> drivers/phy/Kconfig | 1 +
> drivers/phy/Makefile | 1 +
> drivers/phy/axiado/Kconfig | 11 ++
> drivers/phy/axiado/Makefile | 1 +
> drivers/phy/axiado/phy-axiado-emmc.c | 220 +++++++++++++++++++++
> 8 files changed, 289 insertions(+)
> ---
> base-commit: f0b9d8eb98dfee8d00419aa07543bdc2c1a44fb1
> change-id: 20260108-axiado-ax3000-add-emmc-phy-driver-support-d61aead8f622
>
> Best regards,
> --
> Tzu-Hao Wei <twei@axiado.com>
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
This patch series was applied (using b4) to base:
Deps: looking for dependencies matching 4 patch-ids
Deps: Applying prerequisite patch: [PATCH 1/4] dt-bindings: phy: axiado,ax3000-emmc-phy: add Axiado eMMC PHY
Deps: Applying prerequisite patch: [PATCH 2/4] phy: axiado: add Axiado eMMC PHY driver
Deps: Applying prerequisite patch: [PATCH 3/4] MAINTAINERS: Add Axiado AX3000 eMMC PHY driver
Deps: Applying prerequisite patch: [PATCH 4/4] arm64: dts: axiado: Add eMMC PHY node
Base: f10c325a345fef0a688a2bcdfab1540d1c924148 (use --merge-base to override)
If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)
New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/axiado/' for 20260109-axiado-ax3000-add-emmc-phy-driver-support-v1-0-dd43459dbfea@axiado.com:
arch/arm64/boot/dts/axiado/ax3000-evk.dtb: /soc/phy@80801c00: failed to match any schema with compatible: ['axiado,ax3000-emmc-phy']
next prev parent reply other threads:[~2026-01-12 15:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 9:43 [PATCH 0/4] Add eMMC PHY support for Axiado AX3000 SoC Tzu-Hao Wei
2026-01-09 9:43 ` [PATCH 1/4] dt-bindings: phy: axiado,ax3000-emmc-phy: add Axiado eMMC PHY Tzu-Hao Wei
2026-01-11 10:37 ` Krzysztof Kozlowski
2026-01-12 8:34 ` Krzysztof Kozlowski
2026-01-12 10:27 ` Tzu-Hao Wei
2026-01-09 9:43 ` [PATCH 2/4] phy: axiado: add Axiado eMMC PHY driver Tzu-Hao Wei
2026-01-15 22:22 ` kernel test robot
2026-01-09 9:43 ` [PATCH 3/4] MAINTAINERS: Add Axiado AX3000 " Tzu-Hao Wei
2026-01-11 10:40 ` Krzysztof Kozlowski
2026-01-13 3:38 ` Tzu-Hao Wei
2026-01-12 6:02 ` Prasad Bolisetty
2026-01-09 9:43 ` [PATCH 4/4] arm64: dts: axiado: Add eMMC PHY node Tzu-Hao Wei
2026-01-12 8:32 ` [PATCH 0/4] Add eMMC PHY support for Axiado AX3000 SoC Krzysztof Kozlowski
2026-01-13 6:16 ` Tzu-Hao Wei
2026-01-12 15:17 ` Rob Herring [this message]
2026-02-04 9:19 ` Tzu-Hao Wei
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=176822994353.7723.17700786956910310022.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=openbmc@lists.ozlabs.org \
--cc=pbolisetty@axiado.com \
--cc=srinavmani@axiado.com \
--cc=twei@axiado.com \
--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