linux-kernel - Re: [PATCH 1/3] i2c: append hardware lock with bus lock

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] [day] [month] [year] [list]

Message-ID: <20110510230832.GE634@freya.fluff.org>
Date:	Wed, 11 May 2011 00:08:32 +0100
From:	Ben Dooks <ben-i2c@...ff.org>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Ben Dooks <ben-i2c@...ff.org>, linux@....linux.org.uk,
	linux-kernel@...r.kernel.org,
	Haojian Zhuang <haojian.zhuang@...il.com>,
	Haojian Zhuang <haojian.zhuang@...vell.com>,
	linux-i2c@...r.kernel.org, ben-linux@...ff.org,
	eric.y.miao@...il.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/3] i2c: append hardware lock with bus lock

On Mon, May 02, 2011 at 11:46:16AM +0200, Jean Delvare wrote:
> On Mon, 2 May 2011 10:27:34 +0100, Ben Dooks wrote:
> > On Thu, Apr 28, 2011 at 11:15:44PM +0800, Haojian Zhuang wrote:
> > > Both AP and CP are contained in Marvell PXA910 silicon. These two ARM
> > > cores are sharing one pair of I2C pins.
> > > 
> > > In order to keep I2C transaction operated with atomic, hardware lock
> > > (RIPC) is required. Because of this, bus lock in AP side can't afford
> > > this requirement. Now hardware lock is appended.
> > > 
> > > Signed-off-by: Haojian Zhuang <haojian.zhuang@...vell.com>
> > > Cc: Ben Dooks <ben-linux@...ff.org>
> > > Cc: Jean Delvare <khali@...ux-fr.org>
> > 
> > Right, this looks like a reasonable explanation of what is going on here
> > and if Jean is happy with the core changes I'll look at where the driver
> > change can go.
> 
> Yes I am!
> 
> Let me know if you want me to take the core change in my tree or if you
> prefer to have it in yours to avoid a dependency.

if it'll go in my tree ok, then yes.
Will publish a new tree soon.
--
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/