From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
shawnguo@kernel.org, s.hauer@pengutronix.de,
arm-soc <arm@kernel.org>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/3] ARM: dts: imx51: ZII: Add missing phy-mode
Date: Mon, 10 Apr 2023 18:24:34 +0300 [thread overview]
Message-ID: <20230410152434.vafp4t6a3qdo3od7@skbuf> (raw)
In-Reply-To: <ZDPm28C7xXulpG1L@shell.armlinux.org.uk>
On Mon, Apr 10, 2023 at 11:37:15AM +0100, Russell King (Oracle) wrote:
> It is entirely possible that some are wrong, especially as we don't
> document what the various PHY_INTERFACE_MODE_* mean in the kernel
> (remember that I started doing that).
include/linux/phy.h does give a small hint about what is expected:
* @PHY_INTERFACE_MODE_REVRMII: Reduced Media Independent Interface in PHY role
and the commit which added that mode does reference, in its description,
the conversation that led to its creation:
https://lore.kernel.org/netdev/20210201214515.cx6ivvme2tlquge2@skbuf/
next prev parent reply other threads:[~2023-04-10 15:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 15:25 [PATCH 0/3] Add missing DSA properties for marvell switches Andrew Lunn
2023-04-07 15:25 ` [PATCH 1/3] ARM: dts: imx51: ZII: Add missing phy-mode Andrew Lunn
2023-04-07 15:41 ` Vladimir Oltean
2023-04-07 16:10 ` Andrew Lunn
2023-04-07 16:50 ` Vladimir Oltean
2023-04-07 17:06 ` Andrew Lunn
2023-04-10 10:00 ` Vladimir Oltean
2023-04-10 10:37 ` Russell King (Oracle)
2023-04-10 15:24 ` Vladimir Oltean [this message]
2023-04-10 11:59 ` Andrew Lunn
2023-04-10 12:35 ` Andrew Lunn
2023-04-10 13:11 ` Vladimir Oltean
2023-04-10 14:56 ` Andrew Lunn
2023-04-07 15:25 ` [PATCH 2/3] ARM: dts: imx6qdl: Add missing phy-mode and fixed links Andrew Lunn
2023-04-07 15:25 ` [PATCH 3/3] ARM64: dts: freescale: ZII: Add missing phy-mode Andrew Lunn
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=20230410152434.vafp4t6a3qdo3od7@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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