From: Harini Katakam <harini.katakam@amd.com>
To: <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>, <simon.horman@corigine.com>,
<mkl@pengutronix.de>
Cc: <netdev@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 v3 0/3] Add support for VSC8531_02 PHY and DT RGMII tuning
Date: Thu, 11 May 2023 17:38:05 +0530 [thread overview]
Message-ID: <20230511120808.28646-1-harini.katakam@amd.com> (raw)
Add support for VSC8531_02 PHY ID.
Also provide an option to change RGMII delay value via devicetree.
v3 changes:
- Remove patch 2/3 from v2 as custom mscc properties dont need to be
defined. rx-internal-delay-ps and tx-internal-delay-ps can be used.
- Change RGMII delay precedence as advised by Vladimir:
phy-mode rgmii rgmii-rxid/rgmii-id
--------------------------------------------------------------------------------------------
rx-internal-delay-ps absent 0.2 ns 2 ns
rx-internal-delay-ps present follow rx-internal-delay-ps follow rx-internal-delay-ps
- Split VSC8531-02 and RGMII delay config into separate patches.
- Correct vendor ID
- Update commit description and subject everywhere to say RGMII delays
instead of RGMII tuning.
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
Harini Katakam (3):
phy: mscc: Use PHY_ID_MATCH_VENDOR to minimize PHY ID table
phy: mscc: Add support for RGMII delay configuration
phy: mscc: Add support for VSC8531_02
drivers/net/phy/mscc/mscc.h | 4 ++
drivers/net/phy/mscc/mscc_main.c | 75 ++++++++++++++++++++++----------
2 files changed, 57 insertions(+), 22 deletions(-)
--
2.17.1
next reply other threads:[~2023-05-11 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 12:08 Harini Katakam [this message]
2023-05-11 12:08 ` [PATCH net-next v3 1/3] phy: mscc: Use PHY_ID_MATCH_VENDOR to minimize PHY ID table Harini Katakam
2023-05-11 14:05 ` Andrew Lunn
2023-05-11 12:08 ` [PATCH net-next v3 2/3] phy: mscc: Add support for RGMII delay configuration Harini Katakam
2023-05-11 14:00 ` Simon Horman
2023-05-13 18:23 ` kernel test robot
2023-05-11 12:08 ` [PATCH net-next v3 3/3] phy: mscc: Add support for VSC8531_02 Harini Katakam
2023-05-11 14:11 ` Andrew Lunn
2023-05-11 16:17 ` Katakam, Harini
2023-05-11 14:16 ` 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=20230511120808.28646-1-harini.katakam@amd.com \
--to=harini.katakam@amd.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harinikatakamlinux@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michal.simek@amd.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--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).