From: Paolo Abeni <pabeni@redhat.com>
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>, 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 v4 2/2] net: pse-pd: Add Si3474 PSE controller driver
Date: Thu, 3 Jul 2025 11:13:50 +0200 [thread overview]
Message-ID: <0547d8fd-e6ee-4f59-8a7e-93d2d11cdf5e@redhat.com> (raw)
In-Reply-To: <4e55abda-ba02-4bc9-86e6-97c08e4e4a2d@adtran.com>
On 6/30/25 4:57 PM, Piotr Kubik wrote:
> +static inline void si3474_get_channels(struct si3474_priv *priv, int id,
> + u8 *chan0, u8 *chan1)
> +{
Please don't use 'static inline' in c files. 'static' would do and will
let the compiler do the better choice.
> + *chan0 = priv->pi[id].chan[0];
> + *chan1 = priv->pi[id].chan[1];
> +}
> +
> +static inline struct i2c_client *si3474_get_chan_client(struct si3474_priv *priv,
> + u8 chan)
Same as above.
[...]
> +static int si3474_pi_enable(struct pse_controller_dev *pcdev, int id)
> +{
> + struct si3474_priv *priv = to_si3474_priv(pcdev);
> + struct i2c_client *client;
> + u8 chan0, chan1;
> + u8 val = 0;
> + s32 ret;
> +
> + if (id >= SI3474_MAX_CHANS)
> + return -ERANGE;
> +
> + si3474_get_channels(priv, id, &chan0, &chan1);
> + client = si3474_get_chan_client(priv, chan0);
> +
> + /* Release PI from shutdown */
> + ret = i2c_smbus_read_byte_data(client, PORT_MODE_REG);
> + if (ret < 0)
> + return ret;
> +
> + val = (u8)ret;
> + val |= CHAN_MASK(chan0);
> + val |= CHAN_MASK(chan1);
> +
> + ret = i2c_smbus_write_byte_data(client, PORT_MODE_REG, val);
> + if (ret)
> + return ret;
> +
> + /* DETECT_CLASS_ENABLE must be set when using AUTO mode,
> + * otherwise PI does not power up - datasheet section 2.10.2
> + */
> + val = (CHAN_BIT(chan0) | CHAN_UPPER_BIT(chan0) |
> + CHAN_BIT(chan1) | CHAN_UPPER_BIT(chan1));
Minor nit: brackets not needed above.
> + ret = i2c_smbus_write_byte_data(client, DETECT_CLASS_ENABLE_REG, val);
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
> +
> +static int si3474_pi_disable(struct pse_controller_dev *pcdev, int id)
> +{
> + struct si3474_priv *priv = to_si3474_priv(pcdev);
> + struct i2c_client *client;
> + u8 chan0, chan1;
> + u8 val = 0;
> + s32 ret;
> +
> + if (id >= SI3474_MAX_CHANS)
> + return -ERANGE;
> +
> + si3474_get_channels(priv, id, &chan0, &chan1);
> + client = si3474_get_chan_client(priv, chan0);
> +
> + /* Set PI in shutdown mode */
> + ret = i2c_smbus_read_byte_data(client, PORT_MODE_REG);
> + if (ret < 0)
> + return ret;
> +
> + val = (u8)ret;
> + val &= ~(CHAN_MASK(chan0));
> + val &= ~(CHAN_MASK(chan1));
Brackets not needed here, too and adding them makes the code IMHO less
readable.
> +
> + ret = i2c_smbus_write_byte_data(client, PORT_MODE_REG, val);
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
> +
> +static int si3474_pi_get_chan_current(struct si3474_priv *priv, u8 chan)
> +{
> + struct i2c_client *client;
> + s32 ret;
> + u8 reg;
> + u64 tmp_64;
Please respect the reverse christmass tree order in variable
declaration, here and elsewhere.
/P
next prev parent reply other threads:[~2025-07-03 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 14:55 [PATCH net-next v4 0/2] Add Si3474 PSE controller driver Piotr Kubik
2025-06-30 14:57 ` [PATCH net-next v4 1/2] dt-bindings: net: pse-pd: Add bindings for Si3474 PSE controller Piotr Kubik
2025-06-30 14:57 ` [PATCH net-next v4 2/2] net: pse-pd: Add Si3474 PSE controller driver Piotr Kubik
2025-07-03 9:13 ` Paolo Abeni [this message]
2025-07-07 13:17 ` Kory Maincent
2025-07-10 15:32 ` [EXTERNAL]Re: " Piotr Kubik
2025-07-10 18:05 ` 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=0547d8fd-e6ee-4f59-8a7e-93d2d11cdf5e@redhat.com \
--to=pabeni@redhat.com \
--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=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;
as well as URLs for NNTP newsgroup(s).