From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] mv64xxx i2c bus lock w/ commit eda6bee6c7
Date: Tue, 25 Jun 2013 23:09:26 +0200 [thread overview]
Message-ID: <87mwqdnbi1.fsf@natisbad.org> (raw)
In-Reply-To: 87wqpjkxfz.fsf@natisbad.org
Hi Wolfram,
arno at natisbad.org (Arnaud Ebalard) writes:
> Wolfram Sang <wsa@the-dreams.de> writes:
>
>>> does nothing fancy either. While debugging I ended up on Debian bug
>>> #622325 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622325) which
>>> made the driver a little less suspect when a revert of commit eda6bee6c7
>>> fixed the issue for me.
>>
>> Either wait for 3.11 or pick 4243fa0bad551b8c8d4ff7104e8fd557ae848845
>> "(I2C: mv64xxx: fix race between FSM/interrupt and process context")
>> from my for-next branch. (Note the other patches from Russell, probably
>> all worth to pick).
>
> Thanks for the tip. Will try it tomorrow.
Done. It works as expected, i.e. no i2c lock at boot on my ReadynNAS
102 once applied. Note that I had to also apply other patches from
Russel on which this specific commit somewhat depends.
>> Would be nice if you could pass the info to the Debian bug as well.
Done as well. I put you in the Cc: list.
Thanks for your work,
Cheers,
a+
prev parent reply other threads:[~2013-06-25 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 20:21 [PATCHv8 1/1] Add support for GMT G762/G763 PWM fan controllers Arnaud Ebalard
2013-06-21 17:03 ` Guenter Roeck
2013-06-23 15:39 ` Simon Guinot
2013-06-23 16:06 ` Guenter Roeck
2013-06-23 18:07 ` Arnaud Ebalard
[not found] ` <87fvw8ehne.fsf@natisbad.org>
2013-06-24 18:30 ` [BUG] mv64xxx i2c bus lock w/ commit eda6bee6c7 Wolfram Sang
2013-06-24 21:31 ` Arnaud Ebalard
2013-06-25 21:09 ` Arnaud Ebalard [this message]
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=87mwqdnbi1.fsf@natisbad.org \
--to=arno@natisbad.org \
--cc=linux-arm-kernel@lists.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