From: Rob Herring <robh@kernel.org>
To: Shashank Maurya <shashank.maurya@oss.qualcomm.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@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
Subject: Re: [PATCH v4 1/2] dt-bindings: regulator: rpi-panel-v2: Add vcc-supply property
Date: Wed, 4 Nov 2026 11:05:26 -0600 [thread overview]
Message-ID: <20261104170526.GA2198175-robh@kernel.org> (raw)
In-Reply-To: <20261104-rpi_reg-v4-1-3578e794ff45@oss.qualcomm.com>
On Wed, Nov 04, 2026 at 01:40:47PM +0530, Shashank Maurya wrote:
> Add an optional vcc-supply property to the Raspberry Pi 7" touchscreen
> panel V2 regulator binding. The panel controller MCU is powered from an
> external power rail, which has to be supplied before any I2C
> communication can take place.
>
> The property is optional so that existing device trees which do not
> describe the supply remain valid.
>
> Signed-off-by: Shashank Maurya <shashank.maurya@oss.qualcomm.com>
Missing Krzysztof's ack.
next prev parent reply other threads:[~2026-11-04 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 8:10 [PATCH v4 0/2] regulator: rpi-panel-v2: Add vcc-supply Shashank Maurya
2026-11-04 8:10 ` [PATCH v4 1/2] dt-bindings: regulator: rpi-panel-v2: Add vcc-supply property Shashank Maurya
2026-11-04 17:05 ` Rob Herring [this message]
2026-11-04 8:10 ` [PATCH v4 2/2] regulator: rpi-panel-v2: Add vcc-supply support Shashank Maurya
2026-11-04 13:23 ` Mark Brown
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=20261104170526.GA2198175-robh@kernel.org \
--to=robh@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=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=shashank.maurya@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
all inboxes | Powered by JetHome®