From: Peter Korsgaard <peter@korsgaard.com>
To: Stefan Roese <sr@denx.de>
Cc: linux-i2c@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH] i2c: ocores: Add missing wake_up() call upon state change to STATE_DONE
Date: Fri, 16 Jun 2017 15:26:43 +0200 [thread overview]
Message-ID: <871sqkhxm4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <7319c512-4301-8a33-5fc3-62486557a883@denx.de> (Stefan Roese's message of "Fri, 16 Jun 2017 15:04:14 +0200")
>>>>> "Stefan" == Stefan Roese <sr@denx.de> writes:
Hi,
>> It is close to 10 years ago since I last had access to any boards with
>> the ocores controller, but the logic in ocores_process() indicates that
>> the controller would generate another interrupt once the stop condition
>> has been sent:
>>
>> if ((i2c->state == STATE_DONE) || (i2c->state == STATE_ERROR)) {
>> /* stop has been sent */
>> oc_setreg(i2c, OCI2C_CMD, OCI2C_CMD_IACK);
>> wake_up(&i2c->wait);
>> return;
>> }
>>
>> Do you not see this interrupt?
> No. It took me quite some time last week, to notice this misbehavior
> in this I2C driver. As the client (Goodix I2C touchscreen) always
> returned only after more than 1 second from reading one I2C frame.
Funky. On what kind of platform / what VHDL source version is this? The
driver has now existed for more than 10 years and has had contributions
from a number of people, but this is the first time I hear about this
missing interrupt.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-06-16 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 9:23 [PATCH] i2c: ocores: Add missing wake_up() call upon state change to STATE_DONE Stefan Roese
2017-06-16 12:52 ` Peter Korsgaard
2017-06-16 13:04 ` Stefan Roese
2017-06-16 13:26 ` Peter Korsgaard [this message]
2017-06-22 10:53 ` Stefan Roese
2017-06-23 18:29 ` Wolfram Sang
2017-06-26 21:30 ` Peter Korsgaard
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=871sqkhxm4.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=sr@denx.de \
--cc=wsa@the-dreams.de \
/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