From: "SkyLake Huang (黃啟澤)" <SkyLake.Huang@mediatek.com>
To: "horms@kernel.org" <horms@kernel.org>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"dqfext@gmail.com" <dqfext@gmail.com>,
"Steven Liu (劉人豪)" <steven.liu@mediatek.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"daniel@makrotopia.org" <daniel@makrotopia.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH net-next v9 11/13] net: phy: add driver for built-in 2.5G ethernet PHY on MT7988
Date: Thu, 27 Jun 2024 08:19:30 +0000 [thread overview]
Message-ID: <e3a31911c1e1154dc1989a8f2851ea741a8b1b2f.camel@mediatek.com> (raw)
In-Reply-To: <20240626185221.GC3104@kernel.org>
On Wed, 2024-06-26 at 19:52 +0100, Simon Horman wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> On Wed, Jun 26, 2024 at 06:43:27PM +0800, Sky Huang wrote:
> > From: "SkyLake.Huang" <skylake.huang@mediatek.com>
> >
> > Add support for internal 2.5Gphy on MT7988. This driver will load
> > necessary firmware, add appropriate time delay and figure out LED.
> > Also, certain control registers will be set to fix link-up issues.
> >
> > Signed-off-by: SkyLake.Huang <skylake.huang@mediatek.com>
>
> ...
>
> Hi Sky,
>
> Sorry for not providing this review earlier in the process.
>
It's ok.
> > diff --git a/drivers/net/phy/mediatek/mtk-2p5ge.c
> b/drivers/net/phy/mediatek/mtk-2p5ge.c
>
> ...
>
> > +static int mt798x_2p5ge_phy_load_fw(struct phy_device *phydev)
> > +{
> > +struct mtk_i2p5ge_phy_priv *priv = phydev->priv;
> > +void __iomem *md32_en_cfg_base, *pmb_addr;
> > +struct device *dev = &phydev->mdio.dev;
> > +const struct firmware *fw;
> > +int ret, i;
> > +u16 reg;
> > +
> > +if (priv->fw_loaded)
> > +return 0;
> > +
> > +pmb_addr = ioremap(MT7988_2P5GE_PMB_FW_BASE,
> MT7988_2P5GE_PMB_FW_LEN);
> > +if (!pmb_addr)
> > +return -ENOMEM;
> > +md32_en_cfg_base = ioremap(MT7988_2P5GE_MD32_EN_CFG_BASE,
> > + MT7988_2P5GE_MD32_EN_CFG_LEN);
> > +if (!md32_en_cfg_base) {
> > +ret = -ENOMEM;
> > +goto free_pmb;
> > +}
> > +
> > +ret = request_firmware(&fw, MT7988_2P5GE_PMB_FW, dev);
> > +if (ret) {
> > +dev_err(dev, "failed to load firmware: %s, ret: %d\n",
> > +MT7988_2P5GE_PMB_FW, ret);
> > +goto free;
> > +}
> > +
> > +if (fw->size != MT7988_2P5GE_PMB_FW_SIZE) {
> > +dev_err(dev, "Firmware size 0x%zx != 0x%x\n",
> > +fw->size, MT7988_2P5GE_PMB_FW_SIZE);
> > +ret = -EINVAL;
> > +goto free;
>
> It seems that this leaks any resources allocated by
> request_firmware():
> I think a call to release_firmware() is needed in this unwind path.
>
> Flagged by Smatch.
>
Please see the fix down below.
> > +}
> > +
> > +reg = readw(md32_en_cfg_base);
> > +if (reg & MD32_EN) {
> > +phy_set_bits(phydev, MII_BMCR, BMCR_RESET);
> > +usleep_range(10000, 11000);
> > +}
> > +phy_set_bits(phydev, MII_BMCR, BMCR_PDOWN);
> > +
> > +/* Write magic number to safely stall MCU */
> > +phy_write_mmd(phydev, MDIO_MMD_VEND1, 0x800e, 0x1100);
> > +phy_write_mmd(phydev, MDIO_MMD_VEND1, 0x800f, 0x00df);
> > +
> > +for (i = 0; i < MT7988_2P5GE_PMB_FW_SIZE - 1; i += 4)
> > +writel(*((uint32_t *)(fw->data + i)), pmb_addr + i);
> > +release_firmware(fw);
> > +dev_info(dev, "Firmware date code: %x/%x/%x, version: %x.%x\n",
> > + be16_to_cpu(*((__be16 *)(fw->data +
> > + MT7988_2P5GE_PMB_FW_SIZE - 8))),
> > + *(fw->data + MT7988_2P5GE_PMB_FW_SIZE - 6),
> > + *(fw->data + MT7988_2P5GE_PMB_FW_SIZE - 5),
> > + *(fw->data + MT7988_2P5GE_PMB_FW_SIZE - 2),
> > + *(fw->data + MT7988_2P5GE_PMB_FW_SIZE - 1));
> > +
> > +writew(reg & ~MD32_EN, md32_en_cfg_base);
> > +writew(reg | MD32_EN, md32_en_cfg_base);
> > +phy_set_bits(phydev, MII_BMCR, BMCR_RESET);
> > +/* We need a delay here to stabilize initialization of MCU */
> > +usleep_range(7000, 8000);
> > +dev_info(dev, "Firmware loading/trigger ok.\n");
> > +
> > +priv->fw_loaded = true;
> > +
> > +free:
> > +iounmap(md32_en_cfg_base);
> > +free_pmb:
> > +iounmap(pmb_addr);
> > +
> > +return ret ? ret : 0;
>
> I'm feeling that I'm missing something incredibly obvious,
> but could this simply be:
>
> return ret;
>
> > +}
>
> ...
Thanks. I'll fix like this:
static int mt798x_2p5ge_phy_load_fw(struct phy_device *phydev)
{
int ret, i;
...
if (!md32_en_cfg_base) {
ret = -ENOMEM;
goto free_pmb;
}
ret = request_firmware(&fw, MT7988_2P5GE_PMB_FW, dev);
if (ret) {
dev_err(dev, "failed to load firmware: %s, ret: %d\n",
MT7988_2P5GE_PMB_FW, ret);
goto free;
}
if (fw->size != MT7988_2P5GE_PMB_FW_SIZE) {
dev_err(dev, "Firmware size 0x%zx != 0x%x\n",
fw->size, MT7988_2P5GE_PMB_FW_SIZE);
ret = -EINVAL;
goto release_fw;
}
...
for (i = 0; i < MT7988_2P5GE_PMB_FW_SIZE - 1; i += 4)
writel(*((uint32_t *)(fw->data + i)), pmb_addr + i);
/* Remove original release_firmware(fw) here */
...
release_fw:
release_firmware(fw);
free:
iounmap(md32_en_cfg_base);
free_pmb:
iounmap(pmb_addr);
return ret;
}
BRs,
Sky
next prev parent reply other threads:[~2024-06-27 8:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 10:43 [PATCH net-next v9 00/13] net: phy: mediatek: Introduce mtk-phy-lib and add 2.5Gphy support Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 01/13] net: phy: mediatek: Re-organize MediaTek ethernet phy drivers Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 02/13] net: phy: mediatek: Fix spelling errors and rearrange variables Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 03/13] net: phy: mediatek: Move LED helper functions into mtk phy lib Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 04/13] net: phy: mediatek: Improve readability of mtk-phy-lib.c's mtk_phy_led_hw_ctrl_set() Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 05/13] net: phy: mediatek: Integrate read/write page helper functions Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 06/13] net: phy: mediatek: Hook LED helper functions in mtk-ge.c Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 07/13] net: phy: mediatek: add MT7530 & MT7531's PHY ID macros Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 08/13] net: phy: mediatek: Change mtk-ge-soc.c line wrapping Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 09/13] net: phy: mediatek: Add token ring access helper functions in mtk-phy-lib Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 10/13] net: phy: mediatek: Extend 1G TX/RX link pulse time Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 11/13] net: phy: add driver for built-in 2.5G ethernet PHY on MT7988 Sky Huang
2024-06-26 18:52 ` Simon Horman
2024-06-27 8:19 ` SkyLake Huang (黃啟澤) [this message]
2024-06-26 10:43 ` [PATCH net-next v9 12/13] net: phy: mediatek: Fix alignment in callback functions' hook Sky Huang
2024-06-26 10:43 ` [PATCH net-next v9 13/13] net: phy: mediatek: Remove unnecessary outer parens of "supported_triggers" var Sky Huang
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=e3a31911c1e1154dc1989a8f2851ea741a8b1b2f.camel@mediatek.com \
--to=skylake.huang@mediatek.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steven.liu@mediatek.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®