platform/chrome: Move cros-ec transport drivers to drivers/platform.

There are some cros-ec transport drivers (I2C, SPI) living in MFD, while
others (LPC) living in drivers/platform. The transport drivers are more
platform specific. So, move the I2C and SPI transport drivers to the
platform/chrome directory. The patch also removes the MFD_ prefix of
their Kconfig symbols.

Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Reviewed-by: Guenter Roeck <groeck@chromium.org>
Acked-by: Lee Jones <lee.jones@linaro.org>
Signed-off-by: Benson Leung <bleung@chromium.org>

1 files changed, 0 insertions, 20 deletions

diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index b860eb5aa194..013458e728dc 100644
--- a/drivers/mfd/Kconfig
+++ b/drivers/mfd/Kconfig
@@ -202,26 +202,6 @@ config MFD_CROS_EC
           You also need to enable the driver for the bus you are using. The
           protocol for talking to the EC is defined by the bus driver.
 
-config MFD_CROS_EC_I2C
-        tristate "ChromeOS Embedded Controller (I2C)"
-        depends on MFD_CROS_EC && I2C
-
-        help
-          If you say Y here, you get support for talking to the ChromeOS
-          EC through an I2C bus. This uses a simple byte-level protocol with
-          a checksum. Failing accesses will be retried three times to
-          improve reliability.
-
-config MFD_CROS_EC_SPI
-        tristate "ChromeOS Embedded Controller (SPI)"
-        depends on MFD_CROS_EC && SPI
-
-        ---help---
-          If you say Y here, you get support for talking to the ChromeOS EC
-          through a SPI bus, using a byte-level protocol. Since the EC's
-          response time cannot be guaranteed, we support ignoring
-          'pre-amble' bytes before the response actually starts.
-
 config MFD_CROS_EC_CHARDEV
         tristate "Chrome OS Embedded Controller userspace device interface"
         depends on MFD_CROS_EC