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
| ||
|
Date: Mon, 8 Dec 2014 14:53:39 +0100 From: Maxime Coquelin <maxime.coquelin@...com> To: Arnd Bergmann <arnd@...db.de>, Lee Jones <lee.jones@...aro.org> Cc: <devicetree@...r.kernel.org>, <kernel@...inux.com>, <linux-kernel@...r.kernel.org>, <linux-spi@...r.kernel.org>, <broonie@...nel.org>, <linux-arm-kernel@...ts.infradead.org> Subject: Re: [STLinux Kernel] [PATCH v3 0/4] spi: st: New driver for ST's SPI Controller On 12/08/2014 02:22 PM, Arnd Bergmann wrote: > On Monday 08 December 2014 12:53:30 Lee Jones wrote: >> This is a new driver which controls the SPI component of ST's >> Synchronous Serial Controller (SSC). >> > How does this related to the i2c driver for drivers/i2c/busses/i2c-st.c? > Could you have the same piece of hardware do one or the other mode > depending on pin configuration, or is each instance hardwired to > a particular mode? This is the same IP, that can be configured either in SPI or I2C. > > Is there any code worth sharing between the two drivers? No, except a couple of registers, they are managed in a ways. The way it is used, a single SSC instance can only be used either in SPI or I2C mode on a board, so I think it wouldn't make sense to create a MFD driver to manage it. Kr, Maxime > > Arnd > > _______________________________________________ > Kernel mailing list > Kernel@...inux.com > http://www.stlinux.com/mailman/listinfo/kernel -- 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