From: Primoz Beltram <primoz.beltram@kate.si>
To: kernelnewbies@kernelnewbies.org
Subject: Update: I2C bus driver TIMEDOUT because of PM autosuspend
Date: Thu, 28 Nov 2019 10:32:42 +0100 [thread overview]
Message-ID: <7e195624-1bae-194a-a9e9-4f71b1af4abc@kate.si> (raw)
I must update my report. It is not PM autosuspend (void calls do
nothing, no miracle here).
This morning I reproduced the I2C timeout error also with
XIIC_PM_TIMEOUT=10000 delay. For several days some other change was
misleading me to PM autosuspend conclusion.
What looks to me now is that just slight change in driver code (e.g. add
or remove dev_info() call) changes the execution timing pattern of
driver and this then determine if the problem probability window is hit
or not. Probability to hit the problem is very low.
The driver timeout error and its result to I2C bus blocked is still a
problem.
I would still like to let the maintainer aware of this problem.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2019-11-28 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 9:32 Primoz Beltram [this message]
2019-11-28 10:37 ` Update: I2C bus driver TIMEDOUT because of PM autosuspend Greg KH
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=7e195624-1bae-194a-a9e9-4f71b1af4abc@kate.si \
--to=primoz.beltram@kate.si \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).