From: naim.dahnoun@googlemail.com
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: Kumar Gala <galak@codeaurora.org>,
DLOS <davinci-linux-open-source@linux.davincidsp.com>,
"<linux-doc@vger.kernel.org>" <linux-doc@vger.kernel.org>,
"<devicetree-discuss@lists.ozlabs.org>"
<devicetree-discuss@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>,
LMML <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: [PATCH v5] media: i2c: tvp7002: add OF support
Date: Sun, 25 Aug 2013 16:23:41 +0100 [thread overview]
Message-ID: <07E2F059-EB81-47F7-814E-C55073144FD2@gmail.com> (raw)
In-Reply-To: <52179B03.8090402@samsung.com>
Sent from my iPhone
On 23 Aug 2013, at 18:25, Sylwester Nawrocki <s.nawrocki@samsung.com> wrote:
> On 08/13/2013 03:00 AM, Kumar Gala wrote:
>> On Aug 11, 2013, at 1:25 AM, Lad, Prabhakar wrote:
>>
>>> From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
>>>
>>> add OF support for the tvp7002 driver.
>>>
>>> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com>
>>> ---
> [...]
>>> .../devicetree/bindings/media/i2c/tvp7002.txt | 53 ++++++++++++++++
>>> drivers/media/i2c/tvp7002.c | 67 ++++++++++++++++++--
>>> 2 files changed, 113 insertions(+), 7 deletions(-)
>>> create mode 100644 Documentation/devicetree/bindings/media/i2c/tvp7002.txt
>>>
>>> diff --git a/Documentation/devicetree/bindings/media/i2c/tvp7002.txt b/Documentation/devicetree/bindings/media/i2c/tvp7002.txt
>>> new file mode 100644
>>> index 0000000..5f28b5d
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/media/i2c/tvp7002.txt
>>> @@ -0,0 +1,53 @@
>>> +* Texas Instruments TV7002 video decoder
>>> +
>>> +The TVP7002 device supports digitizing of video and graphics signal in RGB and
>>> +YPbPr color space.
>>> +
>>> +Required Properties :
>>> +- compatible : Must be "ti,tvp7002"
>>> +
>>> +Optional Properties:
>>
>>
>>> +- hsync-active: HSYNC Polarity configuration for the bus. Default value when
>>> + this property is not specified is <0>.
>>> +
>>> +- vsync-active: VSYNC Polarity configuration for the bus. Default value when
>>> + this property is not specified is <0>.
>>> +
>>> +- pclk-sample: Clock polarity of the bus. Default value when this property is
>>> + not specified is <0>.
>>> +
>>> +- sync-on-green-active: Active state of Sync-on-green signal property of the
>>> + endpoint.
>>> + 0 = Normal Operation (Active Low, Default)
>>> + 1 = Inverted operation
>>
>> These seems better than what you have in video-interfaces.txt
>
> We probably should specify default values in in the common binding description.
> Then duplication could be avoided. Not sure if it's not too late for this, all
> drivers would need to have same default values.
>
> What's normal and what's inverted depends on a particular device.
>
>>> +- field-even-active: Active-high Field ID output polarity control of the bus.
>>> + Under normal operation, the field ID output is set to logic 1 for an odd field
>>> + (field 1) and set to logic 0 for an even field (field 0).
>>> + 0 = Normal Operation (Active Low, Default)
>>> + 1 = FID output polarity inverted
>>> +
>>
>> Why the duplication if this is covered in video-interfaces.txt?
>
> Yes, it would be better to avoid redefining these properties in each specific
> device's binding. Presumably, for easier matching of DT properties with the
> hardware's description, we could only say in device specific document which
> value of a property corresponds to "normal" and which to "inverted" operation ?
>
>>> +For further reading of port node refer Documentation/devicetree/bindings/media/
>>> +video-interfaces.txt.
>
> --
> Sylwester Nawrocki
> Samsung R&D Institute Poland
> _______________________________________________
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
prev parent reply other threads:[~2013-08-25 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 6:25 Lad, Prabhakar
2013-08-13 1:00 ` Kumar Gala
2013-08-13 2:46 ` Prabhakar Lad
2013-08-23 17:25 ` Sylwester Nawrocki
2013-08-25 15:23 ` naim.dahnoun [this message]
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=07E2F059-EB81-47F7-814E-C55073144FD2@gmail.com \
--to=naim.dahnoun@googlemail.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=galak@codeaurora.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=s.nawrocki@samsung.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®