linux-kernel - Re: [PATCH V2] i2c-designware: Mask all interrupts during i2c controller enable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140411092956.GE19349@intel.com>
Date:	Fri, 11 Apr 2014 12:29:56 +0300
From:	"Westerberg, Mika" <mika.westerberg@...el.com>
To:	"Du, Wenkai" <wenkai.du@...el.com>
Cc:	"'linux-i2c@...r.kernel.org'" <linux-i2c@...r.kernel.org>,
	'Wolfram Sang' <wsa@...-dreams.de>,
	"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2] i2c-designware: Mask all interrupts during i2c
 controller enable

On Fri, Apr 11, 2014 at 02:03:19AM +0300, Du, Wenkai wrote:
> Hi all,
> 
> Updated problem descriptions from Mika's feedback and new test data: 
> 
> There have been "i2c_designware 80860F41:00: controller timed out" errors
> on a number of Baytrail platforms. The issue is caused by incorrect value in
> Interrupt Mask Register (DW_IC_INTR_MASK)  when i2c core is being enabled. 
> This causes call to __i2c_dw_enable() to immediately start the transfer which
> leads to timeout. There are 3 failure modes observed:
> 
> 1. Failure in S0 to S3 resume path
> 
> The default value after reset for DW_IC_INTR_MASK is 0x8ff. When we start 
> the first transaction after resuming from system sleep, TX_EMPTY interrupt 
> is already unmasked because of the hardware default.
> 
> 2. Failure in normal operational path
> 
> This failure happens rarely and is hard to reproduce. Debug trace showed that
> DW_IC_INTR_MASK had value of 0x254 when failure occurred, which meant 
> TX_EMPTY was unmasked.
> 
> 2. Failure in S3 to S0 suspend path

This should probably be 3.

> This failure also happens rarely and is hard to reproduce. Adding debug trace
> that read DW_IC_INTR_MASK made this failure not reproducible. But from ISR 
> call trace we could conclude TX_EMPTY was unmasked when problem occurred.
> 
> 
> The patch masks all interrupts before the controller is enabled to resolve the
> faulty DW_IC_INTR_MASK conditions.
> 
> Signed-off-by: Wenkai Du <wenkai.du@...el.com>

Acked-by: Mika Westerberg <mika.westerberg@...ux.intel.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/