| 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
| ||
|
Message-ID: <20130617103336.354022c2@endymion.delvare> Date: Mon, 17 Jun 2013 10:33:36 +0200 From: Jean Delvare <khali@...ux-fr.org> To: Christian Ruppert <christian.ruppert@...lis.com> Cc: Wolfram Sang <wsa@...-dreams.de>, Mika Westerberg <mika.westerberg@...ux.intel.com>, Pierrick Hascoet <pierrick.hascoet@...lis.com>, linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH V2] i2c: designware: fix race between subsequent xfers On Mon, 17 Jun 2013 10:19:33 +0200, Christian Ruppert wrote: > On Fri, Jun 14, 2013 at 04:37:41PM +0200, Wolfram Sang wrote: > > BTW since I am currently here: i2c-designware-core should be in the > > 'algos' directory, no? > > At the risk of passing for a complete moron: What exactly is the > difference between I2C algos and I2C bus drivers? The i2c/algos directory contains abstracted code which is common to multiple hardware implementations. The most popular of these is i2c-algo-bit which implements software-only I2C over virtually any pair of controllable pins (parallel port, GPIOs, etc.) As a general rule, i2c/algos should only contain reusable, architecture and platform independent code. All the actual hardware access should be delegated to the bus drivers, through callbacks. If this can't be done easily then i2c/algos is not the right place. -- Jean Delvare -- 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/
Powered by blists - more mailing lists