From: Harini Katakam <harini.katakam@amd.com>
To: <robh+dt@kernel.org>, <andrew@lunn.ch>, <hkallweit1@gmail.com>,
<linux@armlinux.org.uk>, <davem@davemloft.net>, <kuba@kernel.org>,
<edumazet@google.com>, <pabeni@redhat.com>,
<vladimir.oltean@nxp.com>, <wsa+renesas@sang-engineering.com>,
<krzysztof.kozlowski+dt@linaro.org>, <simon.horman@corigine.com>
Cc: <netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <harinikatakamlinux@gmail.com>,
<michal.simek@amd.com>, <harini.katakam@amd.com>,
<radhey.shyam.pandey@amd.com>
Subject: [PATCH net-next v2 0/3] Add support for VSC8531_02 PHY and DT RGMII tuning
Date: Wed, 26 Apr 2023 16:13:10 +0530 [thread overview]
Message-ID: <20230426104313.28950-1-harini.katakam@amd.com> (raw)
Add support for VSC8531_02 PHY ID.
Also provide an option to tune RGMII delay value via devicetree.
The default delays are retained in the driver.
v2 changes:
- Added patch to use a common vendor phy id match
- Removed dt include header patch because delays should be specied in
ps, not register values
- Updated DT binding description and commit for optional delay tuning to
be clearer on the precedence
- Updated dt property name to include vendor instead of phy device name
- Switch both VSC8531 and VSC8531-02 to use exact phy id match as they
share the same model number
- Ensure RCT
- Improve optional property read
RFC link: https://lore.kernel.org/all/20210629094038.18610-1-harini.katakam@xilinx.com/
Harini Katakam (3):
phy: mscc: Use PHY_ID_MATCH_VENDOR to minimize PHY ID table
dt-bindings: mscc: Add RGMII RX and TX delay tuning
phy: mscc: Add support for VSC8531_02 with RGMII tuning
.../bindings/net/mscc-phy-vsc8531.txt | 2 +
drivers/net/phy/mscc/mscc.h | 3 ++
drivers/net/phy/mscc/mscc_main.c | 54 +++++++++++++------
3 files changed, 42 insertions(+), 17 deletions(-)
--
2.17.1
next reply other threads:[~2023-04-26 10:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 10:43 Harini Katakam [this message]
2023-04-26 10:43 ` [PATCH net-next v2 1/3] phy: mscc: Use PHY_ID_MATCH_VENDOR to minimize PHY ID table Harini Katakam
2023-04-26 13:39 ` Andrew Lunn
2023-04-26 17:27 ` Katakam, Harini
2023-04-26 10:43 ` [PATCH net-next v2 2/3] dt-bindings: mscc: Add RGMII RX and TX delay tuning Harini Katakam
2023-04-26 11:10 ` Vladimir Oltean
2023-04-26 13:42 ` Andrew Lunn
2023-04-26 10:43 ` [PATCH net-next v2 3/3] phy: mscc: Add support for VSC8531_02 with RGMII tuning Harini Katakam
2023-04-26 11:18 ` Vladimir Oltean
2023-04-26 12:21 ` Katakam, Harini
2023-04-26 14:18 ` Vladimir Oltean
2023-04-26 17:39 ` Katakam, Harini
2023-04-26 13:48 ` Andrew Lunn
2023-04-26 17:30 ` Katakam, Harini
2023-04-26 15:00 ` Simon Horman
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=20230426104313.28950-1-harini.katakam@amd.com \
--to=harini.katakam@amd.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=harinikatakamlinux@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=robh+dt@kernel.org \
--cc=simon.horman@corigine.com \
--cc=vladimir.oltean@nxp.com \
--cc=wsa+renesas@sang-engineering.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).