Hi Samuel, On Wed, Feb 27, 2013 at 12:40 AM, Samuel Ortiz <sameo@xxxxxxxxxxxxxxx> wrote: > Hi Simon, > > On Tue, Feb 26, 2013 at 09:13:06PM -0800, Simon Glass wrote: >> Hi Samuel, >> >> On Mon, Feb 25, 2013 at 2:08 PM, Simon Glass <sjg@xxxxxxxxxxxx> wrote: >> > 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. >> > >> >> Are you happy with this series? Do you think it is ready to be picked >> up for mfd? > It probably is, and it will be part of the next merge window. I'll apply the > after the merge window closes. I'm just checking that we are still good to do this? Regards, Simon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
