From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Philippe Cornu <philippe.cornu@st.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@st.com>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Yannick Fertre <yannick.fertre@st.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings/display/bridge: sii902x: add optional power supplies
Date: Wed, 25 Apr 2018 12:01:35 +0300 [thread overview]
Message-ID: <16954794.QiYqgNKfkn@avalon> (raw)
In-Reply-To: <20180425075314.19137-2-philippe.cornu@st.com>
Hi Philippe,
Thank you for the patch.
On Wednesday, 25 April 2018 10:53:13 EEST Philippe Cornu wrote:
> Add optional power supplies using the description found in
> "SiI9022A/SiI9024A HDMI Transmitter Data Sheet (August 2016)".
>
> There is a single 1v2 supply voltage named vcc12 from which cvcc12
> (digital core) and avcc12 (TMDS analog) are derived because according
> to this data sheet:
> "cvcc12 and avcc12 can be derived from the same power source"
Shouldn't the power supplies be mandatory, as explained by Mark in https://
lists.freedesktop.org/archives/dri-devel/2018-April/172400.html ?
> Signed-off-by: Philippe Cornu <philippe.cornu@st.com>
> ---
> Documentation/devicetree/bindings/display/bridge/sii902x.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/sii902x.txt
> b/Documentation/devicetree/bindings/display/bridge/sii902x.txt index
> 56a3e68ccb80..9fb41fc9af51 100644
> --- a/Documentation/devicetree/bindings/display/bridge/sii902x.txt
> +++ b/Documentation/devicetree/bindings/display/bridge/sii902x.txt
> @@ -8,6 +8,8 @@ Optional properties:
> - interrupts-extended or interrupt-parent + interrupts: describe
> the interrupt line used to inform the host about hotplug events.
> - reset-gpios: OF device-tree gpio specification for RST_N pin.
> + - iovcc-supply: I/O supply voltage (1.8V or 3.3V, host-dependent).
> + - vcc12-supply: TMDS analog & digital core supply voltage (1.2V).
>
> Optional subnodes:
> - video input: this subnode can contain a video input port node
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-25 9:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 7:53 [PATCH v2 0/2] drm/bridge: sii902x: add optional power supplies Philippe Cornu
2018-04-25 7:53 ` [PATCH v2 1/2] dt-bindings/display/bridge: " Philippe Cornu
2018-04-25 9:01 ` Laurent Pinchart [this message]
2018-04-25 12:20 ` Philippe CORNU
2018-04-25 13:17 ` Laurent Pinchart
2018-04-25 17:11 ` Rob Herring
2018-04-25 22:05 ` Laurent Pinchart
2018-05-14 9:22 ` Philippe CORNU
2018-05-14 17:06 ` Laurent Pinchart
2018-04-25 7:53 ` [PATCH v2 2/2] drm/bridge: " Philippe Cornu
2018-05-14 9:38 ` Philippe CORNU
2018-05-14 10:33 ` Andrzej Hajda
2018-05-14 18:58 ` Philippe CORNU
2018-05-15 7:36 ` Laurent Pinchart
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=16954794.QiYqgNKfkn@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=philippe.cornu@st.com \
--cc=robh+dt@kernel.org \
--cc=yannick.fertre@st.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