linux-kernel - Re: [PATCH v2] tps65910: Work around silicon erratum SWCZ010

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 26 Aug 2014 15:44:08 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	"Arnout Vandecappelle (Essensium/Mind)" <arnout@...d.be>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Lee Jones <lee.jones@...aro.org>,
	Mark Brown <broonie@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	David Brown <davidb@...eaurora.org>
Subject: Re: [PATCH v2] tps65910: Work around silicon erratum SWCZ010

Because this patch is dropped from Mark's tree, here is opportunity to 
revisit patch.

On Friday 22 August 2014 09:00 PM, Arnout Vandecappelle (Essensium/Mind) 
wrote:
>  From http://www.ti.com/lit/pdf/SWCZ010 :
>
>
> Workaround:
> Repeat I2C access.

> A simpler workaround is to make a dummy transfer just before the first
> access to the tps65910 chip. This can be done unconditionally.
> >id = chip_id;
>   
> +	/* Work around silicon erratum SWCZ010: the tps65910 may miss the
> +	 * first I2C transfer. So issue a dummy transfer before the first
> +	 * real transfer.
> +	 */
> +	i2c_master_send(i2c, "", 1);

I think dummy read is more safe operation than dummy write.
Dummy write can create the write on any register which can damage the 
critical settings or it may be possible that it will be incomplete 
calls. Datasheet has not been explained this clearly.


>   	

--
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/