public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Walls <awalls@radix.net>
To: "Igor M. Liplianin" <liplianin@me.by>
Cc: linux-media@vger.kernel.org,
	Matthias Fechner <idefix@fechner.net>,
	Jarod Wilson <jarod@wilsonet.com>,
	Jean Delvare <khali@linux-fr.org>
Subject: Re: IR Receiver on an Tevii S470
Date: Sun, 22 Nov 2009 18:40:24 -0500	[thread overview]
Message-ID: <1258933224.1896.5.camel@localhost> (raw)
In-Reply-To: <200911230029.38693.liplianin@me.by>

On Mon, 2009-11-23 at 00:29 +0200, Igor M. Liplianin wrote:
> On 22 ноября 2009 22:11:47 Andy Walls wrote:
> > On Sun, 2009-11-22 at 19:08 +0100, Matthias Fechner wrote:
> > > Hi Andy,
> > >
> > > Andy Walls wrote:
> > > > Thank you.  I will probably need you for testing when ready.
> > > >
> > > >
> > > > I was planning to do step 1 above for HVR-1800 IR anyway.
> > > >
> > > > I will estimate that I may have something ready by about Christmas (25
> > > > December 2009), unless work becomes very busy.
> > >
> > > thanks a lot for your answer.
> > > I uploaded two pictures I did from the card, you can find it here:
> > > http://fechner.net/tevii-s470/
> > >
> > > It is a CX23885.
> > > The driver I use is the ds3000.
> > > lspci says:
> >
> > [snip]
> >
> > Matthias,
> >
> > Thanks for the pictures.  OK so of the two other interesting chips on
> > the S470:
> >
> > U4 is an I2C connected EEPROM - we don't care about that for IR.
> >
> > U10 appears to perhaps be a Silicon Labs C8051F300 microcontroller or
> > similar:
> >
> > http://www.silabs.com/products/mcu/smallmcu/Pages/C8051F30x.aspx
> >
> > Since the 'F300 has an A/D convertor and has an SMBus interface
> > (compatable with the I2C bus), I suspect this chip could be the IR
> > controller on the TeVii S470.
> >
> > Could you as root:
> >
> > # modprobe cx23885
> > # modprobe i2c-dev
> > # i2c-detect -l
> > (to list all the i2c buses, including cx23885 mastered i2c buses)
> > # i2c-detect -y N
> > (to show the addresses in use on bus # N: only query the cx23885 buses)
> >
> >
> > i2c-detect was in the lm-sensors package last I checked.  (Jean can
> > correct me if I'm wrong.)
> >
> > With that information, I should be able to figure out what I2C address
> > that microcontroller is listening to.
> >
> > Then we can work out how to read and decode it's data and add it to
> > ir-kbd-i2c at least.  Depending on how your kernel and LIRC versions
> > LIRC might still work with I2C IR chips too.
> >
> >
> > All presupposing of course that that 'F300 chip is for IR...
> Receiver connected to cx23885 IR_RX(pin 106). It is not difficult to track.

Igor,

Thank you.  I did not have a board to trace.  I will then stick with my
original plan since the F300 doesn't do the IR.

> F300 is for LNB power control.
> It connected to cx23885 GPIO pins:
> GPIO0 - data - P0.3 F300
> GPIO1 - reset - P0.2 F300
> GPIO2 - clk - P0.1 F300
> GPIO3 - busy - P0.0 F300
> 
> Interface seems not I2C/SMBUS.
>  
> Source code from TeVii:
> http://mercurial.intuxication.org/hg/s2-
> liplianin/file/d0dfe416e0f6/linux/drivers/media/video/cx23885/tevii_pwr.c

Interesting....

   static void Delay1mS(void)
   {
	   udelay(800);
   }

:D

Regards,
Andy

> BR
> Igor



  reply	other threads:[~2009-11-22 23:42 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 20:31 IR Receiver on an Tevii S470 Matthias Fechner
2009-11-21 17:10 ` Matthias Fechner
2009-11-21 20:41   ` Andy Walls
2009-11-21 22:19     ` Jonas Kvinge
2009-11-22  1:03     ` Igor M. Liplianin
2009-11-22  2:48       ` Andy Walls
2009-11-22 18:08         ` Matthias Fechner
2009-11-22 20:11           ` Andy Walls
2009-11-22 20:25             ` Matthias Fechner
2009-11-22 20:32               ` Jean Delvare
2009-11-23  0:17                 ` Andy Walls
2009-11-23  8:54                   ` Jean Delvare
2009-11-25  0:25                     ` Andy Walls
2009-11-26 16:43                       ` Matthias Fechner
2009-11-29 14:22                         ` Andy Walls
2009-11-22 20:26             ` Jean Delvare
2009-11-22 22:29             ` Igor M. Liplianin
2009-11-22 23:40               ` Andy Walls [this message]
2009-12-06 21:40       ` Andy Walls
2009-12-06 22:36         ` Matthias Fechner
2009-12-07  1:23         ` Igor M. Liplianin
2009-12-07  3:35           ` Andy Walls
2009-12-08 17:59             ` Igor M. Liplianin
2009-12-09 11:47               ` Andy Walls
2009-12-09 15:54                 ` Igor M. Liplianin
2009-12-10  1:12                   ` Andy Walls
2009-12-10 16:16                     ` Igor M. Liplianin
2009-12-11  2:32                       ` Andy Walls
  -- strict thread matches above, loose matches on Subject: below --
2009-11-23  0:15 Igor M. Liplianin
2009-12-12  0:30 Igor M. Liplianin
2009-12-12  1:00 ` Andy Walls
2009-12-12  1:42   ` Igor M. Liplianin
2009-12-12  2:58     ` Andy Walls
2009-12-12 11:49       ` Igor M. Liplianin
2009-12-12 14:15         ` Andy Walls
2009-12-12 16:01           ` Igor M. Liplianin
2009-12-12 16:22           ` Igor M. Liplianin
2009-12-12 16:59             ` Andy Walls
2009-12-31 12:46               ` Guillem Solà Aranda
2009-12-31 15:23                 ` Igor M. Liplianin
2010-01-06 21:21   ` Andreas Tschirpke
2010-01-07  0:44     ` Andy Walls

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=1258933224.1896.5.camel@localhost \
    --to=awalls@radix.net \
    --cc=idefix@fechner.net \
    --cc=jarod@wilsonet.com \
    --cc=khali@linux-fr.org \
    --cc=linux-media@vger.kernel.org \
    --cc=liplianin@me.by \
    /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