Thread (66 messages) flat view 66 messages, 7 authors, 3d ago

Re: [PATCH 10/21] net: phy: add X-Powers AC200 EPHY control driver

From: Andrew Lunn <andrew@lunn.ch>
Date: 2026-08-03 17:48:42
Also in: linux-arm-kernel, linux-devicetree, linux-rockchip, linux-sunxi, lkml

On Mon, Aug 03, 2026 at 10:09:01AM -0600, James Hilliard wrote:
On Mon, Aug 3, 2026 at 7:51 AM Andrew Lunn [off-list ref] wrote:
quoted
quoted
+static int
+ac200_ephy_ctl_set_led_outputs(struct acx00_ephy_control *control,
+                            unsigned long outputs)
+{
+}
quoted
+static int
+ac200_ephy_ctl_set_led_polarity(struct acx00_ephy_control *control,
+                             bool active_low)
+{
+}
I've not looked into the details, but these look like pinmux. Does
this I2C device have a GPIO controller? Can these pins be used for
other things than LEDs? Maybe you should be implementing a GPIO and
pinmux driver. The Ethernet PHY driver can then just select the
correct pinmux configuration.
These do not appear to be GPIO or muxable pins. The AC200
documentation describes them as three dedicated EPHY LED
outputs: link/activity, speed, and duplex. The bits in SYS_EPHY_CTL1
enable those output pads, while EPHY_CTL provides their shared
polarity setting. I have not found any documented GPIO data
registers or alternative functions for these pins.
So what i'm trying to do with both of these is make it look more like
standard Linux building blocks.

If that is not possible, i would actually put all this code into the
PHY driver. You then have a regmap property to gain access to the I2C
registers.

       Andrew
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help