From: Rob Herring <robh@kernel.org>
To: yangcong <yangcong5@huaqin.corp-partner.google.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
sam@ravnborg.org, thierry.reding@gmail.com, daniel@ffwll.ch,
airlied@linux.ie, devicetree@vger.kernel.org,
dianders@google.com
Subject: Re: [v1 2/2] dt-bindings: drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail
Date: Thu, 19 Aug 2021 16:19:11 -0500 [thread overview]
Message-ID: <1629407951.445122.1418772.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20210819124844.12424-3-yangcong5@huaqin.corp-partner.google.com>
On Thu, 19 Aug 2021 20:48:44 +0800, yangcong wrote:
> 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.
>
> Signed-off-by: yangcong <yangcong5@huaqin.corp-partner.google.com>
> ---
> .../devicetree/bindings/display/panel/boe,tv101wum-nl6.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/panel/boe,tv101wum-nl6.example.dt.yaml: panel@0: 'pp3300-supply' is a required property
From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/panel/boe,tv101wum-nl6.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1518662
This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit.
next prev parent reply other threads:[~2021-08-19 21:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 12:48 [v1 0/2] drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail yangcong
2021-08-19 12:48 ` [v1 1/2] " yangcong
2021-08-19 12:48 ` [v1 2/2] dt-bindings: " yangcong
2021-08-19 21:19 ` Rob Herring [this message]
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 9:29 ` [v1 2/2] dt-bindings: " yangcong
2021-08-19 12:49 ` Rob Herring
2021-08-19 14:00 ` Doug Anderson
2021-08-19 8:41 [v1 0/2] " yangcong
2021-08-19 8:41 ` [v1 2/2] dt-bindings: " yangcong
2021-08-19 8:28 [v1 0/2] " yangcong
2021-08-19 8:28 ` [v1 2/2] dt-bindings: " 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=1629407951.445122.1418772.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--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 \
--cc=yangcong5@huaqin.corp-partner.google.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).