Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
* Update: I2C bus driver TIMEDOUT because of PM autosuspend
@ 2019-11-28  9:32 Primoz Beltram
  2019-11-28 10:37 ` Greg KH
  0 siblings, 1 reply; 2+ messages in thread
From: Primoz Beltram @ 2019-11-28  9:32 UTC (permalink / raw)
  To: kernelnewbies

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Update: I2C bus driver TIMEDOUT because of PM autosuspend
  2019-11-28  9:32 Update: I2C bus driver TIMEDOUT because of PM autosuspend Primoz Beltram
@ 2019-11-28 10:37 ` Greg KH
  0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2019-11-28 10:37 UTC (permalink / raw)
  To: Primoz Beltram; +Cc: kernelnewbies

On Thu, Nov 28, 2019 at 10:32:42AM +0100, Primoz Beltram wrote:
> 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.

Then email them, and not some other random mailing list :)

good luck!

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-28  9:32 Update: I2C bus driver TIMEDOUT because of PM autosuspend Primoz Beltram
2019-11-28 10:37 ` Greg KH

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git