From: Jean Delvare <khali@linux-fr.org>
To: "Aleksandr V. Piskunov" <aleksandr.v.piskunov@gmail.com>
Cc: Andy Walls <awalls@radix.net>, Jarod Wilson <jarod@wilsonet.com>,
linux-media@vger.kernel.org,
Oldrich Jedlicka <oldium.pro@seznam.cz>,
hverkuil@xs4all.nl
Subject: Re: [REVIEW] ivtv, ir-kbd-i2c: Explicit IR support for the AVerTV M116 for newer kernels
Date: Mon, 5 Oct 2009 11:04:02 +0200 [thread overview]
Message-ID: <20091005110402.059e9830@hyperion.delvare> (raw)
In-Reply-To: <20091005085031.GA17431@moon>
On Mon, 5 Oct 2009 11:50:31 +0300, Aleksandr V. Piskunov wrote:
> > Try:
> >
> > # modprobe ivtv newi2c=1
> >
> > to see if that works first.
> >
>
> udelay=10, newi2c=0 => BAD
> udelay=10, newi2c=1 => BAD
> udelay=5, newi2c=0 => OK
> udelay=5, newi2c=1 => BAD
The udelay value is only used by i2c-algo-bit, not newi2c, so the last
test was not needed.
> newi2c=1 also throws some log messages, not sure if its ok or not.
>
> Oct 5 11:41:16 moon kernel: [45430.916449] ivtv: Start initialization, version 1.4.1
> Oct 5 11:41:16 moon kernel: [45430.916618] ivtv0: Initializing card 0
> Oct 5 11:41:16 moon kernel: [45430.916628] ivtv0: Autodetected AVerTV MCE 116 Plus card (cx23416 based)
> Oct 5 11:41:16 moon kernel: [45430.918887] ivtv 0000:03:06.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> Oct 5 11:41:16 moon kernel: [45430.919229] ivtv0: i2c: i2c init
> Oct 5 11:41:16 moon kernel: [45430.919234] ivtv0: i2c: setting scl and sda to 1
> Oct 5 11:41:16 moon kernel: [45430.937745] cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
> Oct 5 11:41:16 moon kernel: [45430.949145] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.951628] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.954191] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.956724] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.959211] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.961749] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.964236] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.966722] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.966786] ivtv0: i2c: i2c write to 43 failed
> Oct 5 11:41:16 moon kernel: [45430.971106] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> Oct 5 11:41:16 moon kernel: [45430.974404] wm8739 0-001a: chip found @ 0x34 (ivtv i2c driver #0)
> Oct 5 11:41:16 moon kernel: [45430.986328] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.988871] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.991355] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.993904] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.996427] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45430.998938] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.001477] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.003968] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.004053] ivtv0: i2c: i2c write to 18 failed
> Oct 5 11:41:16 moon kernel: [45431.011333] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.013883] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.016418] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.018911] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.021463] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.023937] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.026478] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.028998] ivtv0: i2c: Slave did not ack
> Oct 5 11:41:16 moon kernel: [45431.029063] ivtv0: i2c: i2c write to 71 failed
> Oct 5 11:41:16 moon kernel: [45431.031468] ivtv0: i2c: Slave did not ack
> ....
That would be I2C probe attempts such as the ones done by ir-kbd-i2c.
Nothing to be afraid of.
--
Jean Delvare
next prev parent reply other threads:[~2009-10-05 9:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 15:44 [REVIEW] ivtv, ir-kbd-i2c: Explicit IR support for the AVerTV M116 for newer kernels Andy Walls
2009-10-04 8:31 ` Aleksandr V. Piskunov
2009-10-04 8:44 ` Jean Delvare
2009-10-04 9:26 ` Aleksandr V. Piskunov
2009-10-04 20:41 ` Andy Walls
2009-10-04 22:39 ` Aleksandr V. Piskunov
2009-10-04 20:44 ` Andy Walls
2009-10-04 8:54 ` Jean Delvare
2009-10-04 11:33 ` Aleksandr V. Piskunov
2009-10-04 21:07 ` Andy Walls
2009-10-04 20:11 ` Andy Walls
2009-10-05 21:24 ` Jean Delvare
2009-10-04 22:23 ` Aleksandr V. Piskunov
2009-10-05 1:54 ` Andy Walls
2009-10-05 8:29 ` Jean Delvare
2009-10-05 10:36 ` Andy Walls
2009-10-05 8:50 ` Aleksandr V. Piskunov
2009-10-05 9:04 ` Jean Delvare [this message]
2009-10-05 10:02 ` Aleksandr V. Piskunov
2009-10-05 13:56 ` Devin Heitmueller
2009-10-07 17:26 ` Oldrich Jedlicka
2009-10-05 18:45 ` Oldrich Jedlicka
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=20091005110402.059e9830@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=aleksandr.v.piskunov@gmail.com \
--cc=awalls@radix.net \
--cc=hverkuil@xs4all.nl \
--cc=jarod@wilsonet.com \
--cc=linux-media@vger.kernel.org \
--cc=oldium.pro@seznam.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.