From: Andrew Lunn <andrew@lunn.ch>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Daniel Golle <daniel@makrotopia.org>,
Qingfang Deng <dqfext@gmail.com>,
SkyLake Huang <SkyLake.Huang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Joris Vaisvila <joey@tinyisr.com>,
Ahmed Naseef <naseefkm@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net-next v4 5/6] net: phy: mediatek: add calibration logic for AN7581
Date: Wed, 4 Nov 2026 04:47:09 +0100 [thread overview]
Message-ID: <2b744929-609b-4529-8b6b-30feb3ebbbde@lunn.ch> (raw)
In-Reply-To: <20261103221439.30502-6-ansuelsmth@gmail.com>
> +static int airoha_cal_cycle(struct phy_device *phydev, int devad,
> + u32 regnum, u16 mask, u16 cal_val)
> +{
> + struct airoha_socphy_shared *shared = phy_package_get_priv(phydev);
> + struct phy_device *phydev_p0;
> + int ret;
> +
> + phydev_p0 = shared->phydev_p0;
> +
> + phy_modify_mmd(phydev, devad, regnum, mask, cal_val);
> +
> + ret = mtk_cal_cycle_wait(phydev_p0);
> + phydev_dbg(phydev, "cal_val: 0x%x, ret: %d\n", cal_val, ret);
What is the locking scheme here?
When using PHY packages, the typical usage is:
phy_lock_mdio_bus(phydev);
and then use
val = __phy_package_read(phydev, X, Y);
All the read/write helpers are __ indicating they assume the bus is
locked.
Here you are doing something similar, accessing another PHY in the
same package, but without locking. Is that safe?
Andrew
next prev parent reply other threads:[~2026-11-04 3:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 22:14 [PATCH net-next v4 0/6] net: phy: mediatek: calibration for AN7581/3 Christian Marangi
2026-11-03 22:14 ` [PATCH net-next v4 1/6] net: phy: mediatek: export __mtk_tr_write Christian Marangi
2026-11-04 2:32 ` Andrew Lunn
2026-11-03 22:14 ` [PATCH net-next v4 2/6] net: phy: mediatek: move MTK GE SoC registers define to dedicated header Christian Marangi
2026-11-04 2:33 ` Andrew Lunn
2026-11-03 22:14 ` [PATCH net-next v4 3/6] net: phy: mediatek: generalize cal_cycle function for GE SoC Christian Marangi
2026-11-04 2:34 ` Andrew Lunn
2026-11-03 22:14 ` [PATCH net-next v4 4/6] net: phy: mediatek: split Airoha code to dedicated source Christian Marangi
2026-11-04 2:38 ` Andrew Lunn
2026-11-03 22:14 ` [PATCH net-next v4 5/6] net: phy: mediatek: add calibration logic for AN7581 Christian Marangi
2026-11-04 3:47 ` Andrew Lunn [this message]
2026-11-03 22:14 ` [PATCH net-next v4 6/6] net: phy: mediatek: add calibration logic for AN7583 Christian Marangi
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=2b744929-609b-4529-8b6b-30feb3ebbbde@lunn.ch \
--to=andrew@lunn.ch \
--cc=SkyLake.Huang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ansuelsmth@gmail.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=joey@tinyisr.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=naseefkm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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®