From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Andy Walls <awalls@radix.net>
Cc: Jean Delvare <khali@linux-fr.org>,
Dmitri Belimov <d.belimov@gmail.com>,
linux-media@vger.kernel.org, "Timothy D. Lenz" <tlenz@vorgon.com>
Subject: Re: [IR RC, REGRESSION] Didn't work IR RC
Date: Mon, 01 Mar 2010 10:37:54 -0300 [thread overview]
Message-ID: <4B8BC332.6060303@infradead.org> (raw)
In-Reply-To: <1267442919.3110.20.camel@palomino.walls.org>
Andy Walls wrote:
> On Mon, 2010-03-01 at 15:36 +0900, Dmitri Belimov wrote:
>> Hi All
>>
>> After rework of the IR subsystem, IR RC no more work in our TV cards.
>> As I see
>> call saa7134_probe_i2c_ir,
>> configure i2c
>> call i2c_new_device
>>
>> New i2c device not registred.
>>
>> The module kbd-i2c-ir loaded after i2c_new_device.
>
> Jean,
>
> There was also a problem reported with the cx23885 driver's I2C
> connected IR by Timothy Lenz:
>
> http://www.spinics.net/lists/linux-media/msg15122.html
>
> The failure mode sounds similar to Dmitri's, but maybe they are
> unrelated.
>
> I worked a bit with Timothy on IRC and the remote device fails to be
> detected whether ir-kbd-i2c is loaded before the cx23885 driver or after
> the cx23885 driver. I haven't found time to do any folow-up and I don't
> have any of the hardware in question.
>
> Do you have any thoughts or a suggested troubleshooting approach?
Andy/Dmitri,
With the current i2c approach, the bridge driver is responsible for binding
an i2c device into the i2c adapter. In other words, the bridge driver should
have some logic to know what devices use ir-kbd-i2c, loading it at the right
i2c address(es). Manually loading IR shouldn't make any difference.
>From Andy's comment, I suspect that such logic is missing at cx23885 for the board
you're referring. Not sure if this is the same case of the boards Dmitri is
concerned about.
It should be noticed that the i2c redesign happened on 2.6.31 or 2.6.32, so,
if this is the case, a patch should be sent also to -stable.
In the case of saa7134, Jean worked on a fix for some boards:
http://patchwork.kernel.org/patch/75883/
He is currently waiting for someone with the affected boards to test it and
give some return.
--
Cheers,
Mauro
next prev parent reply other threads:[~2010-03-01 13:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 6:36 [IR RC, REGRESSION] Didn't work IR RC Dmitri Belimov
2010-03-01 11:28 ` Andy Walls
2010-03-01 13:37 ` Mauro Carvalho Chehab [this message]
2010-03-02 4:19 ` hermann pitton
2010-03-02 4:43 ` Dmitri Belimov
2010-03-02 7:36 ` Dmitri Belimov
2010-03-02 8:49 ` Mauro Carvalho Chehab
2010-03-09 10:57 ` Jean Delvare
2010-03-10 4:02 ` Dmitri Belimov
2010-03-10 9:00 ` Jean Delvare
2010-03-16 11:05 ` Jean Delvare
2010-03-19 13:42 ` [PATCH] FusionHDTV: Use quick reads for I2C IR device probing Jean Delvare
2010-03-29 15:34 ` Jean Delvare
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=4B8BC332.6060303@infradead.org \
--to=mchehab@infradead.org \
--cc=awalls@radix.net \
--cc=d.belimov@gmail.com \
--cc=khali@linux-fr.org \
--cc=linux-media@vger.kernel.org \
--cc=tlenz@vorgon.com \
/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