From: Krzysztof Kozlowski <krzk@kernel.org>
To: Piotr Kubik <piotr.kubik@adtran.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Kory Maincent <kory.maincent@bootlin.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 2/2] net: pse-pd: Add Si3474 PSE controller driver
Date: Tue, 13 May 2025 10:08:39 +0200 [thread overview]
Message-ID: <4783c1aa-d918-4194-90d7-ebc69ddbb789@kernel.org> (raw)
In-Reply-To: <036e6a6c-ba45-4288-bc2a-9fd8d860ade6@adtran.com>
On 13/05/2025 00:06, Piotr Kubik wrote:
> +/* Parse pse-pis subnode into chan array of si3474_priv */
> +static int si3474_get_of_channels(struct si3474_priv *priv)
> +{
> + struct device_node *pse_node, *node;
> + struct pse_pi *pi;
> + u32 pi_no, chan_id;
> + s8 pairset_cnt;
> + s32 ret = 0;
> +
> + pse_node = of_get_child_by_name(priv->np, "pse-pis");
> + if (!pse_node) {
> + dev_warn(&priv->client[0]->dev,
> + "Unable to parse DT PSE power interface matrix, no pse-pis node\n");
> + return -EINVAL;
> + }
> +
> + for_each_child_of_node(pse_node, node) {
Use scoped variant. One cleanup less.
> + if (!of_node_name_eq(node, "pse-pi"))
> + continue;
...
> +
> + ret = i2c_smbus_read_byte_data(client, FIRMWARE_REVISION_REG);
> + if (ret < 0)
> + return ret;
> + fw_version = ret;
> +
> + ret = i2c_smbus_read_byte_data(client, CHIP_REVISION_REG);
> + if (ret < 0)
> + return ret;
> +
> + dev_info(dev, "Chip revision: 0x%x, firmware version: 0x%x\n",
dev_dbg or just drop. Drivers should be silent on success.
> + ret, fw_version);
> +
> + priv->client[0] = client;
> + i2c_set_clientdata(client, priv);
> +
> + priv->client[1] = i2c_new_ancillary_device(priv->client[0], "slave",
> + priv->client[0]->addr + 1);
> + if (IS_ERR(priv->client[1]))
> + return PTR_ERR(priv->client[1]);
> +
> + ret = i2c_smbus_read_byte_data(priv->client[1], VENDOR_IC_ID_REG);
> + if (ret < 0) {
> + dev_err(&priv->client[1]->dev, "Cannot access slave PSE controller\n");
> + goto out_err_slave;
> + }
> +
> + if (ret != SI3474_DEVICE_ID) {
> + dev_err(&priv->client[1]->dev,
> + "Wrong device ID for slave PSE controller: 0x%x\n", ret);
> + ret = -ENXIO;
> + goto out_err_slave;
> + }
> +
> + priv->np = dev->of_node;
> + priv->pcdev.owner = THIS_MODULE;
> + priv->pcdev.ops = &si3474_ops;
> + priv->pcdev.dev = dev;
> + priv->pcdev.types = ETHTOOL_PSE_C33;
> + priv->pcdev.nr_lines = SI3474_MAX_CHANS;
> +
> + ret = devm_pse_controller_register(dev, &priv->pcdev);
> + if (ret) {
No need for {}
> + return dev_err_probe(dev, ret,
> + "Failed to register PSE controller\n");
No cleanup here? That's odd.
> + }
> +
> + return ret;
return 0
> +
> +out_err_slave:
> + i2c_unregister_device(priv->client[1]);
> + return ret;
> +}
> +
> +static void si3474_i2c_remove(struct i2c_client *client)
> +{
> + struct si3474_priv *priv = i2c_get_clientdata(client);
> +
> + i2c_unregister_device(priv->client[1]);
So you first unregister i2c device and then unregister pse controller.
Feels like possible issues, difficult to debug.... Use devm reset
wrapper for that.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-13 8:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 22:02 [PATCH net-next 0/2] " Piotr Kubik
2025-05-12 22:05 ` [PATCH net-next 1/2] dt-bindings: net: pse-pd: Add bindings for Si3474 PSE controller Piotr Kubik
2025-05-13 8:24 ` Krzysztof Kozlowski
2025-05-15 15:20 ` [EXTERNAL]Re: " Piotr Kubik
2025-05-16 13:37 ` Krzysztof Kozlowski
2025-05-16 14:09 ` Piotr Kubik
2025-05-16 22:35 ` [EXTERNAL]Re: " Kory Maincent
2025-05-17 9:44 ` Piotr Kubik
2025-05-12 22:06 ` [PATCH net-next 2/2] net: pse-pd: Add Si3474 PSE controller driver Piotr Kubik
2025-05-13 8:08 ` Krzysztof Kozlowski [this message]
2025-05-15 15:20 ` [EXTERNAL]Re: " Piotr Kubik
2025-05-15 15:32 ` Krzysztof Kozlowski
2025-05-15 15:35 ` Krzysztof Kozlowski
2025-05-15 15:40 ` Krzysztof Kozlowski
2025-05-15 15:58 ` Piotr Kubik
2025-05-16 13:30 ` Krzysztof Kozlowski
2025-05-13 11:48 ` [PATCH net-next 0/2] " Kory Maincent
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=4783c1aa-d918-4194-90d7-ebc69ddbb789@kernel.org \
--to=krzk@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=piotr.kubik@adtran.com \
--cc=robh@kernel.org \
/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®