linux-kernel - Re: [PATCH v7 09/15] i2c: octeon: Add workaround for broken irqs on CN3860

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: <20160427093707.GA2624@hardcore>
Date:	Wed, 27 Apr 2016 11:37:07 +0200
From:	Jan Glauber <jan.glauber@...iumnetworks.com>
To:	Wolfram Sang <wsa@...-dreams.de>
CC:	<linux-kernel@...r.kernel.org>, <linux-i2c@...r.kernel.org>,
	David Daney <ddaney@...iumnetworks.com>,
	David Daney <david.daney@...ium.com>
Subject: Re: [PATCH v7 09/15] i2c: octeon: Add workaround for broken irqs on
 CN3860

On Tue, Apr 26, 2016 at 11:17:59PM +0200, Wolfram Sang wrote:
> On Mon, Apr 25, 2016 at 04:33:38PM +0200, Jan Glauber wrote:
> > From: David Daney <david.daney@...ium.com>
> > 
> > CN3860 does not interrupt the CPU when the i2c status changes. If
> > we get a timeout, and see the status has in fact changed, we know we
> > have this problem, and drop back to polling.
> > 
> > Signed-off-by: David Daney <ddaney@...iumnetworks.com>
> > Signed-off-by: Jan Glauber <jglauber@...ium.com>
> 
> My code checkers say something:
> 
>     CHECKPATCH
> CHECK: usleep_range is preferred over udelay; see Documentation/timers/timers-howto.txt
> #37: FILE: drivers/i2c/busses/i2c-octeon.c:390:
> +			udelay(50);
> 
> CHECK: usleep_range is preferred over udelay; see Documentation/timers/timers-howto.txt
> #70: FILE: drivers/i2c/busses/i2c-octeon.c:529:
> +			udelay(50);
> 
> Dunno if you want to change that? Seems reasonable to me. Also:

Yes, makes sense.

>     SMATCH
> drivers/i2c/busses/i2c-octeon.c:544 octeon_i2c_hlc_wait() warn: inconsistent indenting
> 
> This is true as well.
> 

OK, I'll reply with an updated patch.