From: yangcong <yangcong5@huaqin.corp-partner.google.com>
To: thierry.reding@gmail.com, sam@ravnborg.org, airlied@linux.ie,
daniel@ffwll.ch, dianders@google.com
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
yangcong <yangcong5@huaqin.corp-partner.google.com>
Subject: [v1 0/2] drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail
Date: Thu, 19 Aug 2021 20:48:42 +0800 [thread overview]
Message-ID: <20210819124844.12424-1-yangcong5@huaqin.corp-partner.google.com> (raw)
The auo,b101uan08.3 panel (already supported by this driver) has
a 3.3V rail that needs to be turned on. For previous users of
this panel this voltage was directly output by pmic. On a new
user (the not-yet-upstream sc7180-trogdor-mrbland board) we need
to turn the 3.3V rail on. Add support in the driver for this.
yangcong (2):
drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail
dt-bindings: drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail
.../bindings/display/panel/boe,tv101wum-nl6.yaml | 4 ++++
drivers/gpu/drm/panel/panel-boe-tv101wum-nl6.c | 11 +++++++++++
2 files changed, 15 insertions(+)
--
2.25.1
next reply other threads:[~2021-08-19 12:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 12:48 yangcong [this message]
2021-08-19 12:48 ` [v1 1/2] drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail yangcong
2021-08-19 12:48 ` [v1 2/2] dt-bindings: " yangcong
2021-08-19 21:19 ` Rob Herring
2021-08-20 6:33 ` [v2 0/2] " yangcong
2021-08-20 6:33 ` [v2 1/2] " yangcong
2021-08-20 6:33 ` [v2 2/2] dt-bindings: " yangcong
2021-08-20 7:01 ` [v2 0/2] " yangcong
2021-08-20 7:01 ` [v2 1/2] " yangcong
2021-08-20 15:46 ` Doug Anderson
2021-08-20 7:01 ` [v2 2/2] dt-bindings: " yangcong
2021-08-20 15:45 ` Doug Anderson
2021-08-24 14:42 ` Rob Herring
2021-08-26 19:48 ` [v2 0/2] " Doug Anderson
-- strict thread matches above, loose matches on Subject: below --
2021-08-19 9:29 [v1 " yangcong
2021-08-19 8:41 yangcong
2021-08-19 8:28 yangcong
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=20210819124844.12424-1-yangcong5@huaqin.corp-partner.google.com \
--to=yangcong5@huaqin.corp-partner.google.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).