From: "Otto Pflüger" <otto.pflueger@abscue.de>
To: "Noralf Trønnes" <noralf@tronnes.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Sam Ravnborg" <sam@ravnborg.org>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Otto Pflüger" <otto.pflueger@abscue.de>
Subject: [PATCH 0/4] drm/tiny: panel-mipi-dbi: Support separate I/O voltage supply
Date: Sun, 27 Nov 2022 19:59:44 +0100 [thread overview]
Message-ID: <20221127185948.1361083-1-otto.pflueger@abscue.de> (raw)
As stated in Documentation/devicetree/bindings/display/panel/panel-mipi-dbi-spi.yml,
the MIPI DBI specification defines two power supplies, one for powering
the panel and one for the I/O voltage. The panel-mipi-dbi driver
currently only supports specifying a single "power-supply" in the
device tree.
Add support for a second power supply defined in a new "io-supply"
device tree property to make the driver properly configure the voltage
regulators on platforms where separate supplies are used.
(Resent from a new email address with proper formatting)
Otto Pflüger (4):
drm/mipi-dbi: Support separate I/O regulator
drm/tiny: panel-mipi-dbi: Read I/O supply from DT
dt-bindings: display: panel: mipi-dbi-spi: Add missing power-supply
dt-bindings: display: panel: mipi-dbi-spi: Add io-supply
.../bindings/display/panel/panel-mipi-dbi-spi.yaml | 11 ++++++++++-
drivers/gpu/drm/drm_mipi_dbi.c | 14 ++++++++++++++
drivers/gpu/drm/tiny/panel-mipi-dbi.c | 5 +++++
include/drm/drm_mipi_dbi.h | 7 ++++++-
4 files changed, 35 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2022-11-27 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 18:59 Otto Pflüger [this message]
2022-11-27 20:43 ` Krzysztof Kozlowski
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=20221127185948.1361083-1-otto.pflueger@abscue.de \
--to=otto.pflueger@abscue.de \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=noralf@tronnes.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
/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®