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: [v4 0/4] drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail
Date: Mon, 30 Aug 2021 10:38:45 +0800 [thread overview]
Message-ID: <20210830023849.258839-1-yangcong5@huaqin.corp-partner.google.com> (raw)
Compared to v3, remove the "//9A" and modify boe_panel_prepare timing in
drm/panel: boe-tv101wum-nl6
- _INIT_DCS_CMD(0x5A, 0xBA), //9A
+ _INIT_DCS_CMD(0x5A, 0xBA),
...
...
...
- usleep_range(10000, 15000);
+ usleep_range(10000, 11000);
Update commit message.
yangcong (4):
drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail
dt-bindings: drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail
drm/panel: support for BOE and INX video mode panel
dt-bindngs: display: panel: Add BOE and INX panel bindings
.../display/panel/boe,tv101wum-nl6.yaml | 7 +
.../gpu/drm/panel/panel-boe-tv101wum-nl6.c | 926 +++++++++++++++++-
2 files changed, 930 insertions(+), 3 deletions(-)
--
2.25.1
next reply other threads:[~2021-08-30 2:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 2:38 yangcong [this message]
2021-08-30 2:38 ` [v4 1/4] drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail yangcong
2021-08-30 2:38 ` [v4 2/4] dt-bindings: " yangcong
2021-08-30 2:38 ` [v4 3/4] drm/panel: support for BOE and INX video mode panel yangcong
2021-08-30 16:17 ` Doug Anderson
2021-08-30 16:17 ` Doug Anderson
2021-08-30 2:38 ` [v4 4/4] dt-bindngs: display: panel: Add BOE and INX panel bindings yangcong
2021-08-31 22:32 ` Rob Herring
2021-09-08 14:45 ` Doug Anderson
2021-09-08 14:45 ` Doug Anderson
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=20210830023849.258839-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.