From: Simon Horman <horms@kernel.org>
To: Parvathi Pudi <parvathi@couthit.com>
Cc: nm@ti.com, vigneshr@ti.com, tony@atomide.com,
edumazet@google.com, glaroque@baylibre.com, pmohan@couthit.com,
diogo.ivo@siemens.com, robh@kernel.org,
javier.carrasco.cruz@gmail.com, praneeth@ti.com,
m-karicheri2@ti.com, basharath@couthit.com, kuba@kernel.org,
pabeni@redhat.com, richardcochran@gmail.com,
devicetree@vger.kernel.org, conor+dt@kernel.org,
schnelle@linux.ibm.com, mohan@couthit.com,
s.hauer@pengutronix.de, prajith@ti.com, rogerq@kernel.org,
jacob.e.keller@intel.com, ssantosh@kernel.org,
linux-arm-kernel@lists.infradead.org, rogerq@ti.com, srk@ti.com,
pratheesh@ti.com, m-malladi@ti.com, netdev@vger.kernel.org,
rdunlap@infradead.org, linux-kernel@vger.kernel.org,
danishanwar@ti.com, afd@ti.com, andrew+netdev@lunn.ch,
krishna@couthit.com, krzk+dt@kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next v5 02/11] net: ti: prueth: Adds ICSSM Ethernet driver
Date: Wed, 16 Apr 2025 10:16:32 +0100 [thread overview]
Message-ID: <20250416091632.GM395307@horms.kernel.org> (raw)
In-Reply-To: <20250414113458.1913823-3-parvathi@couthit.com>
On Mon, Apr 14, 2025 at 05:04:49PM +0530, Parvathi Pudi wrote:
> From: Roger Quadros <rogerq@ti.com>
>
> Updates Kernel configuration to enable PRUETH driver and its dependencies
> along with makefile changes to add the new PRUETH driver.
>
> Changes includes init and deinit of ICSSM PRU Ethernet driver including
> net dev registration and firmware loading for DUAL-MAC mode running on
> PRU-ICSS2 instance.
>
> Changes also includes link handling, PRU booting, default firmware loading
> and PRU stopping using existing remoteproc driver APIs.
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> Signed-off-by: Andrew F. Davis <afd@ti.com>
> Signed-off-by: Basharath Hussain Khaja <basharath@couthit.com>
> Signed-off-by: Parvathi Pudi <parvathi@couthit.com>
...
> diff --git a/drivers/net/ethernet/ti/icssm/icssm_prueth.c b/drivers/net/ethernet/ti/icssm/icssm_prueth.c
...
> +static int icssm_prueth_probe(struct platform_device *pdev)
> +{
> + struct device_node *eth0_node = NULL, *eth1_node = NULL;
> + struct device_node *eth_node, *eth_ports_node;
> + enum pruss_pru_id pruss_id0, pruss_id1;
> + struct device *dev = &pdev->dev;
> + struct device_node *np;
> + struct prueth *prueth;
> + int i, ret;
> +
> + np = dev->of_node;
> + if (!np)
> + return -ENODEV; /* we don't support non DT */
> +
> + prueth = devm_kzalloc(dev, sizeof(*prueth), GFP_KERNEL);
> + if (!prueth)
> + return -ENOMEM;
> +
> + platform_set_drvdata(pdev, prueth);
> + prueth->dev = dev;
> + prueth->fw_data = device_get_match_data(dev);
> +
> + eth_ports_node = of_get_child_by_name(np, "ethernet-ports");
> + if (!eth_ports_node)
> + return -ENOENT;
> +
> + for_each_child_of_node(eth_ports_node, eth_node) {
> + u32 reg;
> +
> + if (strcmp(eth_node->name, "ethernet-port"))
> + continue;
> + ret = of_property_read_u32(eth_node, "reg", ®);
> + if (ret < 0) {
> + dev_err(dev, "%pOF error reading port_id %d\n",
> + eth_node, ret);
> + }
> +
> + of_node_get(eth_node);
Hi Roger, Parvathi, all,
I feel that I'm missing something obvious here.
But I have some questions about the reference to eth_node
taken on the line above.
> +
> + if (reg == 0) {
> + eth0_node = eth_node;
If, while iterating through the for loop above, we reach this point more
than once, then will the reference to the previously node assigned to
eth0_node be leaked?
> + if (!of_device_is_available(eth0_node)) {
> + of_node_put(eth0_node);
> + eth0_node = NULL;
> + }
> + } else if (reg == 1) {
> + eth1_node = eth_node;
Likewise here for eth1_node.
> + if (!of_device_is_available(eth1_node)) {
> + of_node_put(eth1_node);
> + eth1_node = NULL;
> + }
> + } else {
> + dev_err(dev, "port reg should be 0 or 1\n");
And, perhaps more to the point, is the reference to eth_node leaked if
we reach this line?
> + }
> + }
> +
> + of_node_put(eth_ports_node);
> +
> + /* At least one node must be present and available else we fail */
> + if (!eth0_node && !eth1_node) {
> + dev_err(dev, "neither port0 nor port1 node available\n");
> + return -ENODEV;
> + }
> +
> + if (eth0_node == eth1_node) {
Given the if / else if condition in the for loop above,
I'm not sure this can ever occur.
> + dev_err(dev, "port0 and port1 can't have same reg\n");
> + of_node_put(eth0_node);
> + return -ENODEV;
> + }
> +
> + prueth->eth_node[PRUETH_MAC0] = eth0_node;
> + prueth->eth_node[PRUETH_MAC1] = eth1_node;
> +
> + if (eth0_node) {
> + prueth->pru0 = pru_rproc_get(np, 0, &pruss_id0);
> + if (IS_ERR(prueth->pru0)) {
> + ret = PTR_ERR(prueth->pru0);
> + if (ret != -EPROBE_DEFER)
> + dev_err(dev, "unable to get PRU0: %d\n", ret);
> + goto put_pru;
> + }
> + }
> +
> + if (eth1_node) {
> + prueth->pru1 = pru_rproc_get(np, 1, &pruss_id1);
> + if (IS_ERR(prueth->pru1)) {
> + ret = PTR_ERR(prueth->pru1);
> + if (ret != -EPROBE_DEFER)
> + dev_err(dev, "unable to get PRU1: %d\n", ret);
> + goto put_pru;
> + }
> + }
> +
> + /* setup netdev interfaces */
> + if (eth0_node) {
> + ret = icssm_prueth_netdev_init(prueth, eth0_node);
> + if (ret) {
> + if (ret != -EPROBE_DEFER) {
> + dev_err(dev, "netdev init %s failed: %d\n",
> + eth0_node->name, ret);
> + }
> + goto put_pru;
> + }
> + }
> +
> + if (eth1_node) {
> + ret = icssm_prueth_netdev_init(prueth, eth1_node);
> + if (ret) {
> + if (ret != -EPROBE_DEFER) {
> + dev_err(dev, "netdev init %s failed: %d\n",
> + eth1_node->name, ret);
> + }
> + goto netdev_exit;
> + }
> + }
> +
> + /* register the network devices */
> + if (eth0_node) {
> + ret = register_netdev(prueth->emac[PRUETH_MAC0]->ndev);
> + if (ret) {
> + dev_err(dev, "can't register netdev for port MII0");
> + goto netdev_exit;
> + }
> +
> + prueth->registered_netdevs[PRUETH_MAC0] =
> + prueth->emac[PRUETH_MAC0]->ndev;
> + }
> +
> + if (eth1_node) {
> + ret = register_netdev(prueth->emac[PRUETH_MAC1]->ndev);
> + if (ret) {
> + dev_err(dev, "can't register netdev for port MII1");
> + goto netdev_unregister;
> + }
> +
> + prueth->registered_netdevs[PRUETH_MAC1] =
> + prueth->emac[PRUETH_MAC1]->ndev;
> + }
> +
> + if (eth1_node)
> + of_node_put(eth1_node);
> + if (eth0_node)
> + of_node_put(eth0_node);
> + return 0;
> +
> +netdev_unregister:
> + for (i = 0; i < PRUETH_NUM_MACS; i++) {
> + if (!prueth->registered_netdevs[i])
> + continue;
> + unregister_netdev(prueth->registered_netdevs[i]);
> + }
> +
> +netdev_exit:
> + for (i = 0; i < PRUETH_NUM_MACS; i++) {
> + eth_node = prueth->eth_node[i];
> + if (!eth_node)
> + continue;
> +
> + icssm_prueth_netdev_exit(prueth, eth_node);
> + }
> +
> +put_pru:
> + if (eth1_node) {
> + if (prueth->pru1)
> + pru_rproc_put(prueth->pru1);
> + of_node_put(eth1_node);
> + }
> +
> + if (eth0_node) {
> + if (prueth->pru0)
> + pru_rproc_put(prueth->pru0);
> + of_node_put(eth0_node);
> + }
> +
> + return ret;
> +}
> +
> +static void icssm_prueth_remove(struct platform_device *pdev)
> +{
> + struct prueth *prueth = platform_get_drvdata(pdev);
> + struct device_node *eth_node;
> + int i;
> +
> + for (i = 0; i < PRUETH_NUM_MACS; i++) {
> + if (!prueth->registered_netdevs[i])
> + continue;
> + unregister_netdev(prueth->registered_netdevs[i]);
> + }
> +
> + for (i = 0; i < PRUETH_NUM_MACS; i++) {
> + eth_node = prueth->eth_node[i];
> + if (!eth_node)
> + continue;
> +
> + icssm_prueth_netdev_exit(prueth, eth_node);
> + of_node_put(eth_node);
> + }
> +
> + pruss_put(prueth->pruss);
> +
> + if (prueth->eth_node[PRUETH_MAC0])
> + pru_rproc_put(prueth->pru0);
> + if (prueth->eth_node[PRUETH_MAC1])
> + pru_rproc_put(prueth->pru1);
> +}
...
next prev parent reply other threads:[~2025-04-16 10:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 11:34 [PATCH net-next v5 00/11] PRU-ICSSM Ethernet Driver Parvathi Pudi
2025-04-14 11:34 ` [PATCH net-next v5 01/11] dt-bindings: net: ti: Adds DUAL-EMAC mode support on PRU-ICSS2 for AM57xx, AM43xx and AM33xx SOCs Parvathi Pudi
2025-04-14 11:34 ` [PATCH net-next v5 02/11] net: ti: prueth: Adds ICSSM Ethernet driver Parvathi Pudi
2025-04-16 9:16 ` Simon Horman [this message]
2025-04-18 12:23 ` Parvathi Pudi
2025-04-14 11:34 ` [PATCH net-next v5 03/11] net: ti: prueth: Adds PRUETH HW and SW configuration Parvathi Pudi
2025-04-14 13:02 ` [PATCH net-next v5 04/11] net: ti: prueth: Adds link detection, RX and TX support Parvathi Pudi
2025-04-14 13:02 ` [PATCH net-next v5 05/11] net: ti: prueth: Adds ethtool support for ICSSM PRUETH Driver Parvathi Pudi
2025-04-14 13:34 ` Andrew Lunn
2025-04-16 11:59 ` Parvathi Pudi
2025-04-23 16:28 ` Simon Horman
2025-04-23 16:34 ` Simon Horman
2025-04-14 13:02 ` [PATCH net-next v5 06/11] net: ti: prueth: Adds HW timestamping support for PTP using PRU-ICSS IEP module Parvathi Pudi
2025-04-14 13:02 ` [PATCH net-next v5 07/11] net: ti: prueth: Adds support for network filters for traffic control supported by PRU-ICSS Parvathi Pudi
2025-04-15 19:57 ` Simon Horman
2025-04-18 12:25 ` Parvathi Pudi
2025-04-14 14:07 ` [PATCH net-next v5 08/11] net: ti: prueth: Adds support for RX interrupt coalescing/pacing Parvathi Pudi
2025-04-14 14:07 ` [PATCH net-next v5 09/11] net: ti: prueth: Adds power management support for PRU-ICSS Parvathi Pudi
2025-04-14 14:07 ` [PATCH net-next v5 10/11] net: ti: prueth: Adds support for PRUETH on AM33x and AM43x SOCs Parvathi Pudi
2025-04-14 14:07 ` [PATCH net-next v5 11/11] net: ti: prueth: Adds PTP OC Support for AM335x and AM437x Parvathi Pudi
2025-04-15 20:15 ` Simon Horman
2025-04-16 12:03 ` Parvathi Pudi
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=20250416091632.GM395307@horms.kernel.org \
--to=horms@kernel.org \
--cc=afd@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=basharath@couthit.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=glaroque@baylibre.com \
--cc=jacob.e.keller@intel.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=krishna@couthit.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=m-malladi@ti.com \
--cc=mohan@couthit.com \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=pabeni@redhat.com \
--cc=parvathi@couthit.com \
--cc=pmohan@couthit.com \
--cc=prajith@ti.com \
--cc=praneeth@ti.com \
--cc=pratheesh@ti.com \
--cc=rdunlap@infradead.org \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=rogerq@ti.com \
--cc=s.hauer@pengutronix.de \
--cc=schnelle@linux.ibm.com \
--cc=srk@ti.com \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).