From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "Linus Walleij" <linusw@kernel.org>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Andrew Lunn" <andrew@lunn.ch>,
"Conor Dooley" <conor+dt@kernel.org>,
"Vladimir Oltean" <olteanv@gmail.com>,
"Rob Herring" <robh@kernel.org>,
netdev@vger.kernel.org,
"Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
linux-kernel@vger.kernel.org,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Eric Dumazet" <edumazet@google.com>,
kernel@pengutronix.de, "Jakub Kicinski" <kuba@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Alvin Šipraga" <alvin.sipraga@analog.com>,
"David S. Miller" <davem@davemloft.net>,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v1 2/2] net: dsa: realtek: rtl83xx: add support for enabling supplies
Date: Fri, 7 Aug 2026 16:05:36 +0200 [thread overview]
Message-ID: <270c4bc9-469d-4c30-b76c-0fba569abbd9@pengutronix.de> (raw)
In-Reply-To: <113c8afb-0266-470e-a985-f60a7cdf6852@sirena.org.uk>
Hello Mark,
On 8/7/26 2:19 PM, Mark Brown wrote:
> On Fri, Aug 07, 2026 at 10:27:31AM +0200, Ahmad Fatoum wrote:
>
>> Anyways, circling back to the patch: Any objections to leave it as-is
>> and suppress the warnings in this particular driver?
>
> Yes, that is a buggy use of regulator_get_optional() so you should not
> do that.
If the DT binding documents a regulator as optional, it makes no sense
to me that the driver implementing the binding triggers a warning when
the optional regulator is omitted.
> Unless the supply may be physically absent it should not be
> used. If you have ideas for how to safely improve the implementation of
> the normal regulator_get() then it'd be better to do that, bearing in
> mind that it's an API where getting things wrong can easily result in
> physical damange to the system.
How about demoting the dummy supply warning to notice? I think this
better reflects the severity of the message.
Cheers,
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2026-08-07 14:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 14:02 [PATCH net-next v1 0/2] net: dsa: realtek: enable RTL8365MB power supplies Oleksij Rempel
2026-08-06 14:02 ` [PATCH net-next v1 1/2] dt-bindings: net: dsa: realtek: add " Oleksij Rempel
2026-08-06 14:02 ` [PATCH net-next v1 2/2] net: dsa: realtek: rtl83xx: add support for enabling supplies Oleksij Rempel
2026-08-06 14:12 ` Andrew Lunn
2026-08-06 15:10 ` Oleksij Rempel
2026-08-06 15:35 ` Andrew Lunn
2026-08-06 15:56 ` Ahmad Fatoum
2026-08-06 17:40 ` Linus Walleij
2026-08-07 4:26 ` Oleksij Rempel
2026-08-07 6:51 ` Linus Walleij
2026-08-07 7:10 ` Oleksij Rempel
2026-08-07 7:49 ` Ahmad Fatoum
2026-08-07 8:20 ` Linus Walleij
2026-08-07 8:27 ` Ahmad Fatoum
2026-08-07 12:19 ` Mark Brown
2026-08-07 14:05 ` Ahmad Fatoum [this message]
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=270c4bc9-469d-4c30-b76c-0fba569abbd9@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=alvin.sipraga@analog.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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