From: Philippe CORNU <philippe.cornu@st.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Archit Taneja <architt@codeaurora.org>,
Andrzej Hajda <a.hajda@samsung.com>,
David Airlie <airlied@linux.ie>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yannick FERTRE <yannick.fertre@st.com>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Alexandre TORGUE <alexandre.torgue@st.com>
Subject: Re: [PATCH v2 1/2] dt-bindings/display/bridge: sii902x: add optional power supplies
Date: Wed, 25 Apr 2018 12:20:04 +0000 [thread overview]
Message-ID: <e18d1a3b-a2eb-74f2-ab88-7bf01af0754b@st.com> (raw)
In-Reply-To: <16954794.QiYqgNKfkn@avalon>
Hi Laurent & Rob :-)
On 04/25/2018 11:01 AM, Laurent Pinchart wrote:
> 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 ?
>
Laurent,
Many thanks Laurent for your comment, I understood the merge of the two
1v2 power supplies but missed the "mandatory" part... maybe because this
patch (with optional power supplies) already got the reviewed-by from
Rob, I thought the discussion thread you pointed out was applicable
"only" to totally new driver documentation.
So, on my side, as a "new user" of sii902x IC, no problem to put these
power supplies as mandatory instead of optional properties but I would
like to be sure this is applicable to both old and new bindings doc : )
Rob,
could you please confirm these power supply properties should be
"mandatory"?
if yes, should we then modify other optional properties like the
reset-gpios too in the future?
Big thanks to both of you,
Philippe :-)
>> 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
>
next prev parent reply other threads:[~2018-04-25 12:20 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: " Philippe Cornu
2018-04-25 7:53 ` [PATCH v2 1/2] dt-bindings/display/bridge: " Philippe Cornu
2018-04-25 9:01 ` Laurent Pinchart
2018-04-25 12:20 ` Philippe CORNU [this message]
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=e18d1a3b-a2eb-74f2-ab88-7bf01af0754b@st.com \
--to=philippe.cornu@st.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=alexandre.torgue@st.com \
--cc=architt@codeaurora.org \
--cc=benjamin.gaignard@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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
all inboxes | Powered by JetHome®