public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: vipul kumar samar <vipulkumar.samar@st.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: "Martin Bugge (marbugge)" <marbugge@cisco.com>,
	"hdegoede@redhat.com" <hdegoede@redhat.com>,
	"mchehab@infradead.org" <mchehab@infradead.org>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: About RFC of HDMI-CEC
Date: Thu, 26 May 2011 17:46:58 +0530	[thread overview]
Message-ID: <4DDE44BA.6030808@st.com> (raw)
In-Reply-To: <201105260835.45559.hverkuil@xs4all.nl>

On 05/26/2011 12:05 PM, Hans Verkuil wrote:
> On Thursday, May 26, 2011 07:09:30 vipul kumar samar wrote:
>> Hello,
>>
>> On 05/25/2011 06:13 PM, Martin Bugge (marbugge) wrote:
>>> Hello
>>>
>>> To be honest I became a bit disengaded after all the discussion.
>>>
>>> What caused me a lot of problems was the request for AV link support
>>> (which is used in SCART connectors).
>>> Something I never plan to implement.
>>>
>>> But after the "v4l2 Warsaw Brainstroming meeting" it was sort of approved.
>>>
>>> It only need to be reworked to be a subdev level api.
>>> (for that I need some help from Hans Verkuil)
>>>
>>> But it is great that someone else also need an API for this.
>>> I include the latest version here so you can see if you agree, and
>>> together we will get it in.
>>>
>>
>> Yes, sure.
>>
>>> We currently have two drivers which uses this API for CEC.
>>>
>>> * Analog Devices adv7604
>>>
>>> * TMS320DM8x
>>>
>>
>> i want to see source code of these two drivers.From where i can get
>> source code of these drivers??
>
> The adv7604 driver is here:
>
> http://git.linuxtv.org/hverkuil/cisco.git?a=shortlog;h=refs/heads/cobalt
>
> But this tree hasn't been updated in quite some time and doesn't contain the
> CEC support. I need to work on this anyway today so I'll see if I can get
> this tree in sync with our internal tree.
>
> The other driver we can't release as open source. It will eventually become
> available, though.
>
> Regards,
>
>        Hans

Hello Hans,

Once i go through this driver then we will discuss it in more detail.
Thanks for your support.

Regards
Vipul Kumar Samar

>
>>
>> Thanks and Regards
>> Vipul Kumar Samar
>>
>>> At least the adv7604 is planned to be upstreamed.
>>>
>>> Best regards
>>> Martin Bugge
>>>
>>>
>>> On 05/25/2011 01:52 PM, vipul kumar samar wrote:
>>>> Hello,
>>>>
>>>> I am working on HDMI-CEC and planning to implement it in v4l2
>>>> framework.I came to know that a RFC is going on for the same driver.
>>>>
>>>> I want to know is their any friezed version of that RFC or discussion
>>>> is still going on?? Is it included in kernel??
>>>>
>>>> Thanks and Regards
>>>> Vipul Kumar Samar
>>>
>>>
>>
>>
>>
> .
>

  reply	other threads:[~2011-05-26 12:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DDCED60.3080907@st.com>
     [not found] ` <4DDCF95C.1020705@cisco.com>
2011-05-26  5:09   ` About RFC of HDMI-CEC vipul kumar samar
2011-05-26  6:35     ` Hans Verkuil
2011-05-26 12:16       ` vipul kumar samar [this message]
2011-05-31 17:01         ` Hans Verkuil

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=4DDE44BA.6030808@st.com \
    --to=vipulkumar.samar@st.com \
    --cc=hans.verkuil@cisco.com \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=marbugge@cisco.com \
    --cc=mchehab@infradead.org \
    /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