| 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: Thu, 28 Oct 2010 11:49:06 -0400 From: Linus Walleij <linus.ml.walleij@...il.com> To: Cyril Chemparathy <cyril@...com> Cc: davinci-linux-open-source@...ux.davincidsp.com, spi-devel-general@...ts.sourceforge.net, broonie@...nsource.wolfsonmicro.com, lrg@...mlogic.co.uk, dbrownell@...rs.sourceforge.net, grant.likely@...retlab.ca, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, rpurdie@...ys.net, Samuel Ortiz <sameo@...ux.intel.com> Subject: Re: [PATCH v4 01/12] misc: add driver for sequencer serial port 2010/10/26 Cyril Chemparathy <cyril@...com>: > TI's sequencer serial port (TI-SSP) is a jack-of-all-trades type of serial port > device. It has a built-in programmable execution engine that can be programmed > to operate as almost any serial bus (I2C, SPI, EasyScale, and others). > > This patch adds a driver for this controller device. The driver does not > expose a user-land interface. Protocol drivers built on top of this layer are > expected to remain in-kernel. Why is this thing in drivers/misc? drivers/mfd is IMHO the apropriate place for a driver like this, and the subdrivers should be migrated to use mfd cells and platform drivers for the subdevices. All functions and abstractions you create here look suspiciously lot like other MFD devices. But please, beat me up if I'm wrong! Yours, Linus Walleij -- 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