From: "Aleksandr V. Piskunov" <aleksandr.v.piskunov@gmail.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Aleksandr V. Piskunov" <aleksandr.v.piskunov@gmail.com>,
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 13:02:48 +0300 [thread overview]
Message-ID: <20091005100248.GA15806@moon> (raw)
In-Reply-To: <20091005110402.059e9830@hyperion.delvare>
On Mon, Oct 05, 2009 at 11:04:02AM +0200, Jean Delvare wrote:
> 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.
>
Yup, also tried udelay=4, IR controller handles it without problems,
though cx25840 and xc2028 doesn't seem to like the 125 KHz frequency,
refusing to communicate. xc2028 even stopped responding, requiring a cold
reboot.
So for M116 board, the most stable combination seems to be 100 KHz i2c bus
and 150ms polling delay (up from 100 default). With this combination
I can quickly press 1234567890 on remote and driver gets the combination
without any losses.
next prev parent reply other threads:[~2009-10-05 10: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
2009-10-05 10:02 ` Aleksandr V. Piskunov [this message]
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=20091005100248.GA15806@moon \
--to=aleksandr.v.piskunov@gmail.com \
--cc=awalls@radix.net \
--cc=hverkuil@xs4all.nl \
--cc=jarod@wilsonet.com \
--cc=khali@linux-fr.org \
--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.