From: Antti Palosaari <crope@iki.fi>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Luis Alves <ljalvs@gmail.com>,
linux-media@vger.kernel.org, mchehab@infradead.org,
awalls@md.metrocast.net
Subject: Re: [PATCH] cx23885: Fix interrupt storm that happens in some cards when IR is enabled.
Date: Thu, 18 Jul 2013 05:15:11 +0300 [thread overview]
Message-ID: <51E74FAF.2060709@iki.fi> (raw)
In-Reply-To: <CAGoCfizDcOPKiCo54rsoZJyXU3m-_v8jE0aTagxTyjB3QZrZXg@mail.gmail.com>
On 07/18/2013 04:58 AM, Devin Heitmueller wrote:
> On Wed, Jul 17, 2013 at 9:33 PM, Luis Alves <ljalvs@gmail.com> wrote:
>> Hi,
>>
>> This i2c init should stop the interrupt storm that happens in some cards when the IR receiver in enabled.
>> It works perfectly in my TBS6981.
>
> What is at I2C address 0x4c? Might be useful to have a comment in
> there explaining what this patch actually does. This assumes you
> know/understand what it does - if you don't then a comment saying "I
> don't know why this is needed but my board doesn't work right without
> it" is just as valuable.
>
>> It would be good to test in other problematic cards.
>>
>> In this patch I've added the IR init to the TeVii S470/S471 (and some others that fall in the same case statment).
>> Other cards but these that suffer the same issue should also be tested.
>
> Without fully understanding the nature of this patch and what cards
> that it actually effects, it may make sense to move your board into a
> separate case statement. Generally it's bad form to make changes like
> against other cards without any testing against those cards (otherwise
> you can introduce regressions). Stick it in its own case statement,
> and users of the other boards can move their cards into that case
> statement *after* it's actually validated.
>
> Devin
>
hmm, I looked again the cx23885 driver.
0x4c == [0x98 >> 1] = "flatiron" == some internal block of the chip
There is routine which dumps registers out, 0x00 - 0x23
cx23885_flatiron_dump()
There is also existing routine to write those Flatiron registers. So,
that direct I2C access could be shorten to:
cx23885_flatiron_write(dev, 0x1f, 0x80);
cx23885_flatiron_write(dev, 0x23, 0x80);
Unfortunately these two register names are not defined. Something clock
or interrupt related likely.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2013-07-18 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 1:33 [PATCH] cx23885: Fix interrupt storm that happens in some cards when IR is enabled Luis Alves
2013-07-18 1:58 ` Devin Heitmueller
2013-07-18 2:15 ` Antti Palosaari [this message]
2013-07-18 2:41 ` Devin Heitmueller
2013-07-18 10:49 ` Andy Walls
2013-07-18 11:04 ` Konstantin Dimitrov
2013-07-18 12:33 ` Luis Alves
-- strict thread matches above, loose matches on Subject: below --
2013-07-18 10:03 Luis Alves
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=51E74FAF.2060709@iki.fi \
--to=crope@iki.fi \
--cc=awalls@md.metrocast.net \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.org \
--cc=ljalvs@gmail.com \
--cc=mchehab@infradead.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