[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPnjgZ3OKUSxZLgu976RD3tRaMDzscL31TMx_tyzm22GmqnznQ@mail.gmail.com>
Date: Tue, 12 Feb 2013 16:37:27 -0800
From: Simon Glass <sjg@...omium.org>
To: LKML <linux-kernel@...r.kernel.org>
Cc: Samuel Ortiz <sameo@...ux.intel.com>,
Simon Glass <sjg@...omium.org>, linux-input@...r.kernel.org,
Vincent Palatin <vpalatin@...omium.org>,
Roland Stigge <stigge@...com.de>,
Grant Likely <grant.likely@...retlab.ca>,
Che-Liang Chiou <clchiou@...omium.org>,
devicetree-discuss@...ts.ozlabs.org,
Jonathan Kliegman <kliegs@...omium.org>,
linux-doc@...r.kernel.org, Rob Landley <rob@...dley.net>,
Wolfram Sang <w.sang@...gutronix.de>,
Felipe Balbi <balbi@...com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Sourav Poddar <sourav.poddar@...com>,
Luigi Semenzato <semenzato@...omium.org>,
Olof Johansson <olof@...om.net>,
Rob Herring <rob.herring@...xeda.com>
Subject: Re: [PATCH 0/5] Add ChromeOS Embedded Controller support
Hi Samuel,
On Wed, Dec 12, 2012 at 1:33 PM, Simon Glass <sjg@...omium.org> wrote:
> (get_maintainer.pl has produced an enormous list - I hope you are all
> interested.)
>
> The ChromeOS Embedded Controller (EC) is an Open Source EC implementation
> used on ARM and Intel Chromebooks. Current implementations use a Cortex-M3
> connected on a bus (such as I2C, SPI, LPC) to the AP. A separate interrupt
> line is used to indicate when the EC needs service.
>
> Functions performed by the EC vary by platform, but typically include
> battery charging, keyboard scanning and power sequencing.
>
> This series includes support for the EC message protocol, and implements
> a matrix keyboard handler for Linux using the protocol. The EC performs
> key scanning and passes scan data in response to AP requests. This is
> used on the Samsung ARM Chromebook. No driver is available for LPC at
> present.
>
> This series can in principle operate on any hardware, but for it to actually
> work on the Samsung ARM Chromebook, it needs patches which are currently in
> progress to mainline: Exynos FDT interrupt support and I2C bus arbitration.
>
> The driver is device-tree-enabled and a suitable binding is included in
> this series. Example device tree nodes are included in the examples,
> but no device tree patch for exynos5250-snow is provided at this stage, since
> we must wait for the above-mentioned patches to land to avoid errors from
> dtc. This can be added with a follow-on patch when that work is complete.
>
>
> Simon Glass (5):
> mfd: Add ChromeOS EC messages header
> mfd: Add ChromeOS EC implementation
> mfd: Add ChromeOS EC I2C driver
> mfd: Add ChromeOS EC SPI driver
> Input: Add ChromeOS EC keyboard driver
Are you planning to pick the mfd part of this series please? I am
going to send a new version of the input patch on its own now that the
DT binding is agreed.
Regards,
Simon
>
> .../devicetree/bindings/input/cros-ec-keyb.txt | 77 ++
> Documentation/devicetree/bindings/mfd/cros-ec.txt | 56 +
> drivers/input/keyboard/Kconfig | 10 +
> drivers/input/keyboard/Makefile | 1 +
> drivers/input/keyboard/cros_ec_keyb.c | 413 ++++++
> drivers/mfd/Kconfig | 28 +
> drivers/mfd/Makefile | 3 +
> drivers/mfd/cros_ec.c | 219 ++++
> drivers/mfd/cros_ec_i2c.c | 262 ++++
> drivers/mfd/cros_ec_spi.c | 412 ++++++
> include/linux/mfd/cros_ec.h | 190 +++
> include/linux/mfd/cros_ec_commands.h | 1369 ++++++++++++++++++++
> 12 files changed, 3040 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/input/cros-ec-keyb.txt
> create mode 100644 Documentation/devicetree/bindings/mfd/cros-ec.txt
> create mode 100644 drivers/input/keyboard/cros_ec_keyb.c
> create mode 100644 drivers/mfd/cros_ec.c
> create mode 100644 drivers/mfd/cros_ec_i2c.c
> create mode 100644 drivers/mfd/cros_ec_spi.c
> create mode 100644 include/linux/mfd/cros_ec.h
> create mode 100644 include/linux/mfd/cros_ec_commands.h
>
> --
> 1.7.7.3
>
--
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