public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Stefan Ringel <stefan.ringel@arcor.de>
Cc: Bee Hock Goh <beehock@gmail.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Help needed in understanding v4l2_device_call_all
Date: Fri, 23 Apr 2010 13:52:13 -0300	[thread overview]
Message-ID: <4BD1D03D.6070403@redhat.com> (raw)
In-Reply-To: <4BD1BD78.3050105@arcor.de>

Stefan Ringel wrote:
> Am 23.04.2010 17:28, schrieb Bee Hock Goh:
>> So do you mean its required for tm6010 to set the registers?
>>   
> that is not a register, please see you in lastest git, that this request
> a command is (send start and send stop!).

It is hard to know what it really does, but I suspect that it were meant to
implement manual i2c handling, on a similar way to what other drivers do.
On the logs I have here for tm6000 and tm6010, this is not used. So, I suspect
that this is one of the i2c tricks that were used by the vendor of your board.
Other vendors seem to implement different tricks to make i2c work. We need
to figure out what would work better for the devices supported by the driver.

Cheers,
Mauro

      reply	other threads:[~2010-04-23 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07  6:10 Help needed in understanding v4l2_device_call_all Bee Hock Goh
2010-04-22 20:35 ` Mauro Carvalho Chehab
2010-04-23  2:20   ` Bee Hock Goh
2010-04-23 12:22     ` Mauro Carvalho Chehab
2010-04-23 15:23     ` Stefan Ringel
2010-04-23 15:28       ` Bee Hock Goh
2010-04-23 15:32         ` Stefan Ringel
2010-04-23 16:52           ` Mauro Carvalho Chehab [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=4BD1D03D.6070403@redhat.com \
    --to=mchehab@redhat.com \
    --cc=beehock@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=stefan.ringel@arcor.de \
    /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