From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>
Cc: Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vladimir Oltean <olteanv@gmail.com>,
"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>, Marek Vasut <marex@denx.de>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Pascal Eberhard <pascal.eberhard@se.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: dsa: microchip: configure strap pins during reset
Date: Wed, 10 Sep 2025 17:38:13 +0200 [thread overview]
Message-ID: <87y0qmb9ne.fsf@bootlin.com> (raw)
In-Reply-To: <20250910-ksz-strap-pins-v1-2-6308bb2e139e@bootlin.com> (Bastien Curutchet's message of "Wed, 10 Sep 2025 16:55:25 +0200")
Hello bastien,
> +static int ksz_configure_strap(struct ksz_device *dev)
> +{
> + struct pinctrl_state *state = NULL;
> + struct pinctrl *pinctrl;
> + int ret;
> +
> + if (of_device_is_compatible(dev->dev->of_node, "microchip,ksz8463")) {
> + struct gpio_desc *rxd0;
> + struct gpio_desc *rxd1;
> +
> + rxd0 = devm_gpiod_get_index_optional(dev->dev, "strap", 0, GPIOD_OUT_LOW);
> + if (IS_ERR(rxd0))
> + return PTR_ERR(rxd0);
> +
> + rxd1 = devm_gpiod_get_index_optional(dev->dev, "strap", 1, GPIOD_OUT_HIGH);
> + if (IS_ERR(rxd1))
> + return PTR_ERR(rxd1);
> +
> + /* If at least one strap definition is missing we don't do anything */
> + if (!rxd0 || !rxd1)
> + return 0;
> +
> + pinctrl = devm_pinctrl_get(dev->dev);
> + if (IS_ERR(pinctrl))
> + return PTR_ERR(pinctrl);
> +
> + state = pinctrl_lookup_state(pinctrl, "reset");
> + if (IS_ERR(state))
> + return PTR_ERR(state);
> +
> + ret = pinctrl_select_state(pinctrl, state);
> + if (ret)
> + return ret;
In order to simplify the pinctrl handling I would propose to replace
these three function calls by:
devm_pinctrl_get_select(dev->dev, "reset")
I do not think in this case we actually require the internal
devm_pinctrl_put() calls from the above helper, but they probably do not
hurt either.
Thanks,
Miquèl
next prev parent reply other threads:[~2025-09-10 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 14:55 [PATCH net-next 0/2] net: dsa: microchip: Add strap configuration during reset Bastien Curutchet
2025-09-10 14:55 ` [PATCH net-next 1/2] dt-bindings: net: dsa: microchip: Add strap description Bastien Curutchet
2025-09-10 14:55 ` [PATCH net-next 2/2] net: dsa: microchip: configure strap pins during reset Bastien Curutchet
2025-09-10 15:38 ` Miquel Raynal [this message]
2025-09-11 11:22 ` Bastien Curutchet
2025-09-10 16:46 ` Andrew Lunn
2025-09-11 8:04 ` Bastien Curutchet
2025-09-11 10:53 ` Parthiban.Veerasooran
2025-09-10 16:27 ` [PATCH net-next 0/2] net: dsa: microchip: Add strap configuration " Andrew Lunn
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=87y0qmb9ne.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bastien.curutchet@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pascal.eberhard@se.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=woojung.huh@microchip.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).