From: "Noralf Trønnes" <noralf@tronnes.org>
To: "Otto Pflüger" <otto.pflueger@abscue.de>,
"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: "Noralf Trønnes" <noralf@tronnes.org>
Subject: Re: [PATCH v2 2/3] drm/tiny: panel-mipi-dbi: Read I/O supply from DT
Date: Sat, 3 Dec 2022 17:20:28 +0100 [thread overview]
Message-ID: <9d0815fb-141d-91dc-2ca3-a827bed62b3e@tronnes.org> (raw)
In-Reply-To: <20221201160245.2093816-3-otto.pflueger@abscue.de>
Den 01.12.2022 17.02, skrev Otto Pflüger:
> To support platforms with a separate I/O voltage supply, set the new
> io_regulator property along with the regulator property of the DBI
> device. Read the I/O supply from a new "io-supply" device tree
> property.
>
> Signed-off-by: Otto Pflüger <otto.pflueger@abscue.de>
> ---
Reviewed-by: Noralf Trønnes <noralf@tronnes.org>
next prev parent reply other threads:[~2022-12-03 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 16:02 [PATCH v2 0/3] drm/tiny: panel-mipi-dbi: Support separate I/O voltage supply Otto Pflüger
2022-12-01 16:02 ` [PATCH v2 1/3] drm/mipi-dbi: Support separate I/O regulator Otto Pflüger
2022-12-03 16:19 ` Noralf Trønnes
2022-12-01 16:02 ` [PATCH v2 2/3] drm/tiny: panel-mipi-dbi: Read I/O supply from DT Otto Pflüger
2022-12-03 16:20 ` Noralf Trønnes [this message]
2022-12-01 16:02 ` [PATCH v2 3/3] dt-bindings: display: panel: mipi-dbi-spi: Add io-supply Otto Pflüger
2022-12-03 16:21 ` Noralf Trønnes
2022-12-14 14:07 ` [PATCH v2 0/3] drm/tiny: panel-mipi-dbi: Support separate I/O voltage supply Noralf Trønnes
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=9d0815fb-141d-91dc-2ca3-a827bed62b3e@tronnes.org \
--to=noralf@tronnes.org \
--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=otto.pflueger@abscue.de \
--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;
as well as URLs for NNTP newsgroup(s).