From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <richardcochran@gmail.com>,
<Parthiban.Veerasooran@microchip.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net-next v5 0/2] net: phy: micrel: Add PTP support for lan8842
Date: Fri, 29 Aug 2025 15:48:34 +0200 [thread overview]
Message-ID: <20250829134836.1024588-1-horatiu.vultur@microchip.com> (raw)
The PTP block in lan8842 is the same as lan8814 so reuse all these
functions. The first patch of the series just does cosmetic changes such
that lan8842 can reuse the function lan8814_ptp_probe. There should not be
any functional changes here. While the second patch adds the PTP support
to lan8842.
v4->v5:
- remove phydev from lan8842_priv as is not used
- change type for rev to be u16 and fix holes in the struct
- assign ret to priv->rev only after it is checked
v3->v4:
- when reading PHY addr first check return value and then mask it
- change the type of gpios in the declration of __lan8814_ptp_probe_once
v2->v3:
- check return value of function devm_phy_package_join
v1->v2:
- use reverse x-mas notation
- replace hardcoded value with define
Horatiu Vultur (2):
net: phy: micrel: Introduce function __lan8814_ptp_probe_once
net: phy: micrel: Add PTP support for lan8842
drivers/net/phy/micrel.c | 114 +++++++++++++++++++++++++++++++++++++--
1 file changed, 109 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2025-08-29 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 13:48 Horatiu Vultur [this message]
2025-08-29 13:48 ` [PATCH net-next v5 1/2] net: phy: micrel: Introduce function __lan8814_ptp_probe_once Horatiu Vultur
2025-08-29 14:33 ` Kory Maincent
2025-09-01 6:16 ` Horatiu Vultur
2025-08-29 13:48 ` [PATCH net-next v5 2/2] net: phy: micrel: Add PTP support for lan8842 Horatiu Vultur
2025-08-29 14:53 ` Kory Maincent
2025-09-01 6:21 ` Horatiu Vultur
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=20250829134836.1024588-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--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=richardcochran@gmail.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
all inboxes | Powered by JetHome®