From: Josua Mayer <josua@solid-run.com>
To: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Yazan Shhady <yazan.shhady@solid-run.com>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, Josua Mayer <josua@solid-run.com>
Subject: [PATCH RFC v2 0/4] phy: mvebu-cp110-utmi: add support for armada-380 utmi phys
Date: Tue, 16 Jul 2024 22:52:36 +0200 [thread overview]
Message-ID: <20240716-a38x-utmi-phy-v2-0-dae3a9c6ca3e@solid-run.com> (raw)
Armada 380 has smilar USB-2.0 PHYs as CP-110 (Armada 8K).
Add support for Armada 380 to cp110 utmi phy driver.
Signed-off-by: Josua Mayer <josua@solid-run.com>
---
Changes in v2:
- add support for optional regs / make syscon use optional
- add device-tree changes for armada-388-clearfog
- attempted to fix warning reported by krobot (untested)
- tested on actual hardware
- drafted dt-bindings
- Link to v1: https://lore.kernel.org/r/20240715-a38x-utmi-phy-v1-0-d57250f53cf2@solid-run.com
---
Josua Mayer (4):
dt-bindings: phy: cp110-utmi-phy: add compatible string for armada-38x
arm: dts: marvell: armada-38x: add description for usb phys
phy: mvebu-cp110-utmi: add support for armada-380 utmi phys
arm: dts: marvell: armada-388-clearfog: add description for usb phys
.../phy/marvell,armada-cp110-utmi-phy.yaml | 15 +-
.../boot/dts/marvell/armada-388-clearfog-base.dts | 8 +
arch/arm/boot/dts/marvell/armada-388-clearfog.dts | 8 +
arch/arm/boot/dts/marvell/armada-388-clearfog.dtsi | 30 ++-
arch/arm/boot/dts/marvell/armada-38x.dtsi | 29 +++
drivers/phy/marvell/phy-mvebu-cp110-utmi.c | 209 ++++++++++++++++-----
6 files changed, 244 insertions(+), 55 deletions(-)
---
base-commit: 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0
change-id: 20240715-a38x-utmi-phy-02e8059afe35
Sincerely,
--
Josua Mayer <josua@solid-run.com>
next reply other threads:[~2024-07-16 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 20:52 Josua Mayer [this message]
2024-07-16 20:52 ` [PATCH RFC v2 1/4] dt-bindings: phy: cp110-utmi-phy: add compatible string for armada-38x Josua Mayer
2024-07-16 22:45 ` Rob Herring (Arm)
2024-07-16 20:52 ` [PATCH RFC v2 2/4] arm: dts: marvell: armada-38x: add description for usb phys Josua Mayer
2024-07-17 12:04 ` Krzysztof Kozlowski
2024-07-20 13:19 ` Josua Mayer
2024-07-20 18:23 ` Krzysztof Kozlowski
2024-07-20 19:04 ` Andrew Lunn
2024-07-16 20:52 ` [PATCH RFC v2 3/4] phy: mvebu-cp110-utmi: add support for armada-380 utmi phys Josua Mayer
2024-07-16 20:52 ` [PATCH RFC v2 4/4] arm: dts: marvell: armada-388-clearfog: add description for usb phys Josua Mayer
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=20240716-a38x-utmi-phy-v2-0-dae3a9c6ca3e@solid-run.com \
--to=josua@solid-run.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kishon@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=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=vkoul@kernel.org \
--cc=yazan.shhady@solid-run.com \
/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).