summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorDoug Anderson <dianders@chromium.org>2013-04-16 06:29:00 +0000
committerWolfram Sang <wsa@the-dreams.de>2013-04-17 11:31:03 +0200
commitb81dfaa01f7057dde4a6356740c023db4e2ce83b (patch)
tree52f3884bbfb112210c08003df5f4a048ece8e9be /MAINTAINERS
parentd877a721e2a6afea3dfdd494b7d463137b6e6c6b (diff)
downloadlinux-b81dfaa01f7057dde4a6356740c023db4e2ce83b.tar.gz
linux-b81dfaa01f7057dde4a6356740c023db4e2ce83b.tar.bz2
linux-b81dfaa01f7057dde4a6356740c023db4e2ce83b.zip
i2c: mux: Add i2c-arb-gpio-challenge 'mux' driver
The i2c-arb-gpio-challenge driver implements an I2C arbitration scheme where masters need to claim the bus with a GPIO before they can start a transaction. This should generally only be used when standard I2C multimaster isn't appropriate for some reason (errata/bugs). This driver is based on code that Simon Glass added to the i2c-s3c2410 driver in the Chrome OS kernel 3.4 tree. The current incarnation as a mux driver is as suggested by Grant Likely. See <https://patchwork.kernel.org/patch/1877311/> for some history. Signed-off-by: Doug Anderson <dianders@chromium.org> Signed-off-by: Simon Glass <sjg@chromium.org> Signed-off-by: Naveen Krishna Chatradhi <ch.naveen@samsung.com> Reviewed-by: Stephen Warren <swarren@nvidia.com> Acked-by: Olof Johansson <olof@lixom.net> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions