public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Luca Santini <luca.santini-wNesuFfO2Ajz1n+OaKNE4w@public.gmane.org>
Cc: Linux I2C <i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>
Subject: Re: tvp5150 new style i2c driver
Date: Sat, 20 Sep 2008 10:16:23 +0200	[thread overview]
Message-ID: <20080920101623.791ed72f@hyperion.delvare> (raw)
In-Reply-To: <48D41902.9020804-wNesuFfO2Ajz1n+OaKNE4w@public.gmane.org>

Hi Luca,

Please keep the i2c list Cc'd.

On Fri, 19 Sep 2008 23:26:26 +0200, Luca Santini wrote:
> My board is a custom board based on a Renesas SH4 cpu (sh7760). 
> This uP has 2 i2c channels where i have a tvp5150 video codec, a
> wm8731 audio codec , a realtime clock and a renesas h8  connected
> to; so my i2c bus is drivers/i2c/busses/i2c-sh7760.c .
> 
> my goal - regarding tvp5150 - is to initialize it and set it's
> input (to composite, for the moment).
> The digital video output is 'directly' (there's only a mux
> controlled by H8 beetween) connected to GPU (fujitsu lime).
> (...)
> "SMBus Quick command not supported, " in drivers/i2c/i2c-core.c
> sorry for previous imprecision.

Indeed, the i2c-sh7760 driver doesn't support the SMBus Quick command.
This means that devices on that bus can't be probed. You can still use
legacy i2c drivers on that bus; all you have to do is load them with
the "force" parameter:

modprobe tvp5150 force=0,0x5c

(Adjust for the actual bus number and device address on your system.)

Admittedly, with a new-style i2c driver you would no longer have to do
that. That being said, that's only a small part of your problem. The
other part is that you need some glue code to register a video device
through which you can control your TVP5150 chip.

> (...)
> http://lists.lm-sensors.org/pipermail/i2c/2007-June/001462.html

Ah, right. Well, did you try contacting Jorge Luis Zapata Muga about
this? If someone did some work on the tvp5150 driver, that would be
him. I plan to convert all i2c drivers in the kernel tree to new-style
drivers eventually, but I have no plan to work on the tvp5150 driver in
a near future.

> so my interface will be something like /dev/video ?

Yes.

> I'll be able to change i.e. sources by this?

I do not understand your question, sorry.

-- 
Jean Delvare

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

  parent reply	other threads:[~2008-09-20  8:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 15:30 tvp5150 new style i2c driver Luca Santini
     [not found] ` <48D3C5A3.3080802-wNesuFfO2Ajz1n+OaKNE4w@public.gmane.org>
2008-09-19 20:26   ` Jean Delvare
     [not found]     ` <48D41902.9020804@spesonline.com>
     [not found]       ` <48D41902.9020804-wNesuFfO2Ajz1n+OaKNE4w@public.gmane.org>
2008-09-20  8:16         ` Jean Delvare [this message]
     [not found]           ` <20080920101623.791ed72f-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-09-20  9:10             ` Luca Santini
     [not found]               ` <48D4BDF9.8050003-wNesuFfO2Ajz1n+OaKNE4w@public.gmane.org>
2008-09-20  9:36                 ` Jean Delvare
  -- strict thread matches above, loose matches on Subject: below --
2008-09-19  6:33 need soem help realter to I2C client kalhan trisal
2008-09-19 12:42 ` Jean Delvare
     [not found]   ` <20080919144231.780fb37a-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-09-19 13:04     ` tvp5150 new style i2c driver Luca Santini
     [not found]       ` <48D3A36D.1090001-wNesuFfO2Ajz1n+OaKNE4w@public.gmane.org>
2008-09-19 13:23         ` Jean Delvare
2008-09-19 15:04     ` Luca Santini
     [not found]       ` <48D3BF65.1020201-wNesuFfO2Ajz1n+OaKNE4w@public.gmane.org>
2008-09-19 15:25         ` Jean Delvare
2008-09-19 15:27     ` Luca Santini

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=20080920101623.791ed72f@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=luca.santini-wNesuFfO2Ajz1n+OaKNE4w@public.gmane.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