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-phy@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH RFC 2/2] arm: dts: marvell: armada-38x: add description for usb phys
Date: Tue, 16 Jul 2024 12:55:37 +0000 [thread overview]
Message-ID: <bbb5c223-d75b-4adb-9930-a67126c16605@solid-run.com> (raw)
In-Reply-To: <20240715-a38x-utmi-phy-v1-2-d57250f53cf2@solid-run.com>
Am 15.07.24 um 19:47 schrieb Josua Mayer:
> 3. utmi phy driver access just three registers using syscon: all-ports
> power-up (probably enables clocks), device-mode mux, per-port power-up.
>
> Assign these registers individually to the phy device-node, and
> implement access in driver when syscon is not available.
>
> If this is preferred, which dt property should s[ecify their address?
> reg, ranges, ...?
I think I have my answer, with reg-names it seems manageable -
please see the example below:
utmi: utmi@c0000 {
compatible = "marvell,armada-380-utmi-phy";
reg = <0xc0000 0x6000>, <0x18420 4>, <0x18440 12>;
reg-names = "utmi", "usb-cfg", "utmi-cfg";
#address-cells = <1>;
#size-cells = <0>;
status = "disabled";
utmi0: usb-phy@0 {
reg = <0>;
#phy-cells = <0>;
};
utmi1: usb-phy@1 {
reg = <1>;
#phy-cells = <0>;
};
utmi2: usb-phy@2 {
reg = <2>;
#phy-cells = <0>;
};
};
If registers named "usb-cfg" and "utmi-cfg" are given, the driver can be extended
to optionally use those.
I have tested on armada-388-clearfog-pro,
and will send a v2 after tidying up my changes:
/* USB-2.0 Host, CON3 - nearest power */
&usb0 {
phys = <&utmi0>;
phy-names = "utmi";
status = "okay";
};
/* USB-2.0 Host, CON2 - nearest CPU */
&usb3_0 {
phys = <&utmi1>;
phy-names = "utmi";
status = "okay";
};
/* SRDS #3 - USB-2.0/3.0 Host, Type-A connector */
&usb3_1 {
phys = <&utmi2>;
phy-names = "utmi";
status = "okay";
};
&utmi {
status = "okay";
};
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2024-07-16 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 17:47 [PATCH RFC 0/2] phy: mvebu-cp110-utmi: add support for armada-380 utmi phys Josua Mayer
2024-07-15 17:47 ` [PATCH RFC 1/2] " Josua Mayer
2024-07-15 18:05 ` Andrew Lunn
2024-07-16 8:30 ` Josua Mayer
2024-07-15 17:47 ` [PATCH RFC 2/2] arm: dts: marvell: armada-38x: add description for usb phys Josua Mayer
2024-07-15 18:12 ` Andrew Lunn
2024-07-16 8:16 ` Josua Mayer
2024-07-16 12:55 ` Josua Mayer [this message]
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=bbb5c223-d75b-4adb-9930-a67126c16605@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).