From: <Parthiban.Veerasooran@microchip.com>
To: <Horatiu.Vultur@microchip.com>, <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>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2 2/2] net: phy: micrel: Add PTP support for lan8842
Date: Mon, 25 Aug 2025 09:03:35 +0000 [thread overview]
Message-ID: <0b754e84-45d0-4d3e-aa14-564ab5528b98@microchip.com> (raw)
In-Reply-To: <20250825063136.2884640-3-horatiu.vultur@microchip.com>
Hi Horatiu,
On 25/08/25 12:01 pm, Horatiu Vultur wrote:
> + /* As the lan8814 and lan8842 has the same IP for the PTP block, the
> + * only difference is the number of the GPIOs, then make sure that the
> + * lan8842 initialized also the shared data pointer as this is used in
> + * all the PTP functions for lan8814. The lan8842 doesn't have multiple
> + * PHYs in the same package.
> + */
> + addr = lanphy_read_page_reg(phydev, LAN8814_PAGE_COMMON_REGS,
> + LAN8842_STRAP_REG);
> + addr &= LAN8842_STRAP_REG_PHYADDR_MASK;
> + if (addr < 0)
> + return addr;
> +
> + devm_phy_package_join(&phydev->mdio.dev, phydev, addr,
> + sizeof(struct lan8814_shared_priv));
Shouldn't you check the return value of devm_phy_package_join()?
Apologies — I missed to comment in my previous review.
Best regards,
Parthiban V
> + if (phy_package_init_once(phydev)) {
> + ret = lan8842_ptp_probe_once(phydev);
> + if (ret)
> + return ret;
> + }
> +
> + lan8814_ptp_init(phydev);
> +
> return 0;
> }
next prev parent reply other threads:[~2025-08-25 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 6:31 [PATCH net-next v2 0/2] " Horatiu Vultur
2025-08-25 6:31 ` [PATCH net-next v2 1/2] net: phy: micrel: Introduce function __lan8814_ptp_probe_once Horatiu Vultur
2025-08-25 6:31 ` [PATCH net-next v2 2/2] net: phy: micrel: Add PTP support for lan8842 Horatiu Vultur
2025-08-25 9:03 ` Parthiban.Veerasooran [this message]
2025-08-26 6:49 ` Horatiu Vultur - M31836
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=0b754e84-45d0-4d3e-aa14-564ab5528b98@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=Horatiu.Vultur@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®