From: Wei Fang <wei.fang@nxp.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andrew@lunn.ch, f.fainelli@gmail.com,
hkallweit1@gmail.com, linux@armlinux.org.uk,
andrei.botila@oss.nxp.com
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev
Subject: [PATCH v3 net-next 0/2] make PHY output RMII reference clock
Date: Mon, 26 Aug 2024 13:26:58 +0800 [thread overview]
Message-ID: <20240826052700.232453-1-wei.fang@nxp.com> (raw)
The TJA11xx PHYs have the capability to provide 50MHz reference clock
in RMII mode and output on REF_CLK pin. Therefore, add the new property
"nxp,phy-output-refclk" to support this feature. This property is only
available for PHYs which use nxp-c45-tja11xx driver, such as TJA1103,
TJA1104, TJA1120 and TJA1121.
---
V3 change:
Removed the patch 2 from the V2 patch set.
v2 Link: https://lore.kernel.org/netdev/20240823-jersey-conducive-70863dd6fd27@spud/T/
---
Wei Fang (2):
dt-bindings: net: tja11xx: add "nxp,phy-output-refclk" property
net: phy: c45-tja11xx: add support for outputing RMII reference clock
.../devicetree/bindings/net/nxp,tja11xx.yaml | 6 ++++
drivers/net/phy/nxp-c45-tja11xx.c | 29 +++++++++++++++++--
drivers/net/phy/nxp-c45-tja11xx.h | 1 +
3 files changed, 34 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2024-08-26 5:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 5:26 Wei Fang [this message]
2024-08-26 5:26 ` [PATCH v3 net-next 1/2] dt-bindings: net: tja11xx: add "nxp,phy-output-refclk" property Wei Fang
2024-08-26 15:49 ` Rob Herring
2024-08-27 3:25 ` Wei Fang
2024-08-27 12:34 ` Andrew Lunn
2024-08-28 7:35 ` Wei Fang
2024-08-27 13:26 ` Krzysztof Kozlowski
2024-08-28 7:37 ` Wei Fang
2024-08-26 5:27 ` [PATCH v3 net-next 2/2] net: phy: c45-tja11xx: add support for outputing RMII reference clock Wei Fang
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=20240826052700.232453-1-wei.fang@nxp.com \
--to=wei.fang@nxp.com \
--cc=andrei.botila@oss.nxp.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@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
all inboxes | Powered by JetHome®