From: Conor Dooley <conor@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Shashank Maurya <shashank.maurya@oss.qualcomm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
venkata.valluru@oss.qualcomm.com,
Jessica Zhang <jesszhan0024@gmail.com>
Subject: Re: [PATCH v2 2/2] regulator: rpi-panel-v2: Add required vcc-supply support
Date: Mon, 7 Sep 2026 19:04:21 +0100 [thread overview]
Message-ID: <20260907-showroom-elevation-ba1a0792b7f7@spud> (raw)
In-Reply-To: <27fb1c11-c1eb-4494-ac38-d794baf80814@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On Mon, Sep 07, 2026 at 06:09:57PM +0100, Mark Brown wrote:
> On Mon, Sep 07, 2026 at 06:06:24PM +0100, Conor Dooley wrote:
> > On Mon, Sep 07, 2026 at 11:16:08AM +0530, Shashank Maurya wrote:
>
> > > + vcc = devm_regulator_get(&i2c->dev, "vcc");
> > > + if (IS_ERR(vcc))
> > > + return dev_err_probe(&i2c->dev, PTR_ERR(vcc),
> > > + "Failed to get vcc supply\n");
>
> > This needs to be optional, because without it you'll break existing
> > devicetrees. Unless you can explain how all existing users are
> > nonfunctional (e.g. nothing ever enabled the supply, which seems
> > doubtful given this surely worked when it was added) this must remain
> > optional.
>
> The core will stub in a dummy regulator for mandatory supplies that
> don't have anything mapped by firmware, otherwise essentially all
> regualtors would be optional and our error handling would be a disaster
> zone.
I always forget how this works. Thanks for the reminder.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-07 18:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 5:46 [PATCH v2 0/2] regulator: rpi-panel-v2: Add required vcc-supply Shashank Maurya
2026-09-07 5:46 ` [PATCH v2 1/2] dt-bindings: regulator: rpi-panel-v2: Add required vcc-supply property Shashank Maurya
2026-09-07 5:55 ` sashiko-bot
2026-09-07 13:24 ` Dave Stevenson
2026-09-07 17:10 ` Conor Dooley
2026-09-11 5:42 ` Shashank Maurya
2026-09-07 5:46 ` [PATCH v2 2/2] regulator: rpi-panel-v2: Add required vcc-supply support Shashank Maurya
2026-09-07 5:51 ` sashiko-bot
2026-09-07 6:02 ` Marek Vasut
2026-09-07 13:21 ` Dave Stevenson
2026-09-07 17:06 ` Conor Dooley
2026-09-07 17:09 ` Mark Brown
2026-09-07 18:04 ` Conor Dooley [this message]
2026-09-11 5:16 ` Shashank Maurya
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=20260907-showroom-elevation-ba1a0792b7f7@spud \
--to=conor@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=jesszhan0024@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=robh@kernel.org \
--cc=shashank.maurya@oss.qualcomm.com \
--cc=venkata.valluru@oss.qualcomm.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