devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hansverk@cisco.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
	Archit Taneja <architt@codeaurora.org>,
	linux-renesas-soc@vger.kernel.org,
	Lars-Peter Clausen <lars@metafoo.de>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCHv2 1/2] dt-bindings: adi,adv7511.txt: document cec clock
Date: Tue, 19 Sep 2017 12:59:13 +0200	[thread overview]
Message-ID: <aa9c5c0e-c2c8-7913-0e6c-4b150ff09a9b@cisco.com> (raw)
In-Reply-To: <5c8f3625-26f3-8c6e-d42a-def8251a9ac6@cogentembedded.com>

On 09/19/17 12:42, Sergei Shtylyov wrote:
> On 9/19/2017 1:35 PM, Hans Verkuil wrote:
> 
>>>>>>>> From: Hans Verkuil <hans.verkuil@cisco.com>
>>>>>>>>
>>>>>>>> Document the cec clock binding.
>>>>>>>>
>>>>>>>> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
>>>>>>>> Acked-by: Rob Herring <robh@kernel.org>
>>>>>>>> ---
>>>>>>>>      Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt | 4 ++++
>>>>>>>>      1 file changed, 4 insertions(+)
>>>>>>>>
>>>>>>>> diff --git a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt
>>>>>>>> index 06668bca7ffc..4497ae054d49 100644
>>>>>>>> --- a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt
>>>>>>>> +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt
>>>>>>>> @@ -68,6 +68,8 @@ Optional properties:
>>>>>>>>      - adi,disable-timing-generator: Only for ADV7533. Disables the internal timing
>>>>>>>>        generator. The chip will rely on the sync signals in the DSI data lanes,
>>>>>>>>        rather than generate its own timings for HDMI output.
>>>>>>>> +- clocks: from common clock binding: handle to CEC clock.
>>>>>>>
>>>>>>>        It's called "phandle" in the DT speak. :-)
>>>>>>>        Are you sure the clock specifier would always be absent?
>>>>>>
>>>>>> Sorry? I don't understand the question. Did you mean: "can be absent?"?
>>>>>
>>>>>       No, you only say that there'll be the clock phandle only. The clock
>>>>> specifier may follow the phandle for the clock devices that have
>>>>> "#clock-cells" prop != 0.
>>>>
>>>> I have to say that I just copy-and-pasted this from other bindings.
>>>
>>>      :-)
>>>
>>>> Would this be better?
>>>>
>>>> - clocks: list of clock specifiers, corresponding to entries in
>>>>     the clock-names property;
>>>
>>>      Didn't you say that there'll be only one clock, "cec"? If so, there's
>>> gonna  be a single clock phandle+specifier pair. They always go in pairs. :-)
>>>
>>>> - clock-names: from common clock binding: must be "cec".
>>
>> - clocks: cec clock phandle, corresponding to the clock-names entry.
> 
>     The clock phandle and specifier.
> 
>> - clock-names: from common clock binding: must be "cec".
>>
>> This OK?
> 
>     Well, you seem to be going in circles, the above was almost the same as 
> the original prop description...

- clocks: from common clock binding: reference to the CEC clock.
- clock-names: from common clock binding: must be "cec".

This avoids the whole issue of having just a phandle or a phandle + specifier.

Regards,

	Hans

  reply	other threads:[~2017-09-19 10:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170919073331.29007-1-hverkuil@xs4all.nl>
     [not found] ` <20170919073331.29007-2-hverkuil@xs4all.nl>
     [not found]   ` <505bc74f-6563-ab1d-9aab-7893410aef7e@cogentembedded.com>
     [not found]     ` <74b252c8-c1eb-8498-7b9b-54604fe2806a@cisco.com>
     [not found]       ` <e68cffb1-346c-2018-9048-3f8523903809@cogentembedded.com>
     [not found]         ` <e68cffb1-346c-2018-9048-3f8523903809-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2017-09-19 10:07           ` [PATCHv2 1/2] dt-bindings: adi,adv7511.txt: document cec clock Hans Verkuil
2017-09-19 10:15             ` Sergei Shtylyov
2017-09-19 10:35               ` Hans Verkuil
2017-09-19 10:42                 ` Sergei Shtylyov
2017-09-19 10:59                   ` Hans Verkuil [this message]
2017-09-19 12:27                     ` Sergei Shtylyov

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=aa9c5c0e-c2c8-7913-0e6c-4b150ff09a9b@cisco.com \
    --to=hansverk@cisco.com \
    --cc=architt@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hans.verkuil@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=lars@metafoo.de \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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).