From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Yanteng Si <siyanteng@loongson.cn>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, peppe.cavallaro@st.com,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
fancer.lancer@gmail.com, Jose.Abreu@synopsys.com,
chenhuacai@loongson.cn, guyinggang@loongson.cn,
netdev@vger.kernel.org, chris.chenfeiyang@gmail.com
Subject: Re: [PATCH net-next v7 2/9] net: stmmac: dwmac-loongson: Refactor code for loongson_dwmac_probe()
Date: Tue, 2 Jan 2024 10:37:31 +0000 [thread overview]
Message-ID: <ZZPnaziDZEcv5GGw@shell.armlinux.org.uk> (raw)
In-Reply-To: <aee820a3c4293c8172edda27ad4eb9cf5eaead5e.1702990507.git.siyanteng@loongson.cn>
On Tue, Dec 19, 2023 at 10:17:05PM +0800, Yanteng Si wrote:
> Add a setup() function to initialize data, and simplify code for
> loongson_dwmac_probe().
Not all changes in this patch are described.
> +static int loongson_gmac_data(struct pci_dev *pdev,
> + struct plat_stmmacenet_data *plat)
> +{
> + loongson_default_data(pdev, plat);
> +
> + plat->multicast_filter_bins = 256;
> +
> + plat->mdio_bus_data->phy_mask = 0;
>
> - /* Default to phy auto-detection */
> plat->phy_addr = -1;
> + plat->phy_interface = PHY_INTERFACE_MODE_RGMII_ID;
This presumably sets the default phy_interface mode?
> - plat->bus_id = of_alias_get_id(np, "ethernet");
> - if (plat->bus_id < 0)
> - plat->bus_id = pci_dev_id(pdev);
> + pci_set_master(pdev);
> +
> + info = (struct stmmac_pci_info *)id->driver_data;
> + ret = info->setup(pdev, plat);
> + if (ret)
> + goto err_disable_device;
loongson_gmac_data() gets called from here...
> +
> + bus_id = of_alias_get_id(np, "ethernet");
> + if (bus_id >= 0)
> + plat->bus_id = bus_id;
>
> phy_mode = device_get_phy_mode(&pdev->dev);
> if (phy_mode < 0) {
This gets the PHY interface mode, and errors out if it can't be found in
firmware.
> @@ -110,11 +137,7 @@ static int loongson_dwmac_probe(struct pci_dev *pdev, const struct pci_device_id
> }
>
> plat->phy_interface = phy_mode;
So this ends up always overwriting the value written in
loongson_gmac_data(). So it seems to be that initialising
plat->phy_interface in loongson_gmac_data() is just patch noise and
serves no real purpose.
> - plat->mac_interface = PHY_INTERFACE_MODE_GMII;
This has now gone - and is not described, and I'm left wondering what
the implication of that is on the driver. It also makes me wonder
whether loongson_gmac_data() should've been setting mac_interface
rather than phy_interface.
> res.wol_irq = of_irq_get_byname(np, "eth_wake_irq");
> if (res.wol_irq < 0) {
> - dev_info(&pdev->dev, "IRQ eth_wake_irq not found, using macirq\n");
> + dev_info(&pdev->dev,
> + "IRQ eth_wake_irq not found, using macirq\n");
Whitespace cleanups should be a separate patch.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-01-02 10:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 14:17 [PATCH net-next v7 0/9] stmmac: Add Loongson platform support Yanteng Si
2023-12-19 14:17 ` [PATCH net-next v7 1/9] net: stmmac: Pass stmmac_priv and chan in some callbacks Yanteng Si
2023-12-20 15:08 ` Simon Horman
2023-12-21 9:40 ` Yanteng Si
2023-12-20 18:18 ` Serge Semin
2023-12-21 11:50 ` Yanteng Si
2023-12-21 12:53 ` Serge Semin
2023-12-21 13:21 ` Yanteng Si
2023-12-19 14:17 ` [PATCH net-next v7 2/9] net: stmmac: dwmac-loongson: Refactor code for loongson_dwmac_probe() Yanteng Si
2024-01-02 10:37 ` Russell King (Oracle) [this message]
2024-01-18 12:53 ` Yanteng Si
2023-12-19 14:17 ` [PATCH net-next v7 3/9] net: stmmac: dwmac-loongson: Add full PCI support Yanteng Si
2024-01-02 10:40 ` Russell King (Oracle)
2024-01-12 9:42 ` Yanteng Si
2024-01-18 12:56 ` Yanteng Si
2023-12-19 14:17 ` [PATCH net-next v7 4/9] net: stmmac: Add multi-channel supports Yanteng Si
2023-12-20 22:36 ` Serge Semin
2023-12-29 10:33 ` Yanteng Si
2023-12-30 11:25 ` Serge Semin
2024-01-01 6:57 ` Yanteng Si
2024-01-02 1:04 ` Serge Semin
2023-12-19 14:26 ` [PATCH net-next v7 5/9] net: stmmac: Add Loongson-specific register definitions Yanteng Si
2023-12-21 2:14 ` Serge Semin
2024-01-01 8:31 ` Yanteng Si
2024-01-01 12:26 ` Serge Semin
2024-01-12 10:08 ` Yanteng Si
2024-01-23 13:08 ` Yanteng Si
2024-01-24 13:59 ` Serge Semin
2023-12-19 14:26 ` [PATCH net-next v7 6/9] net: stmmac: dwmac-loongson: Add MSI support Yanteng Si
2023-12-19 14:26 ` [PATCH net-next v7 7/9] net: stmmac: dwmac-loongson: Add GNET support Yanteng Si
2023-12-21 2:34 ` Serge Semin
2024-01-01 7:27 ` Yanteng Si
2024-01-02 1:22 ` Serge Semin
2024-01-25 6:57 ` Yanteng Si
2024-01-29 11:45 ` Yanteng Si
2024-01-24 9:21 ` Yanteng Si
2024-01-24 13:51 ` Serge Semin
2024-01-25 8:36 ` Yanteng Si
2024-01-25 18:38 ` Serge Semin
2024-01-25 18:41 ` Russell King (Oracle)
2024-01-25 20:12 ` Serge Semin
2024-01-29 11:18 ` Yanteng Si
2023-12-19 14:28 ` [PATCH net-next v7 8/9] net: stmmac: dwmac-loongson: Disable flow control for GMAC Yanteng Si
2023-12-21 2:35 ` Serge Semin
2024-01-24 10:54 ` Yanteng Si
2023-12-19 14:28 ` [PATCH net-next v7 9/9] net: stmmac: Disable coe for some Loongson GNET Yanteng Si
2023-12-21 2:36 ` Serge Semin
2024-01-23 12:47 ` Yanteng Si
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=ZZPnaziDZEcv5GGw@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Jose.Abreu@synopsys.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=chenhuacai@loongson.cn \
--cc=chris.chenfeiyang@gmail.com \
--cc=fancer.lancer@gmail.com \
--cc=guyinggang@loongson.cn \
--cc=hkallweit1@gmail.com \
--cc=joabreu@synopsys.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=siyanteng@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.