All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Simon Glass <sjg@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Rob Landley <rob@landley.net>, Felipe Balbi <balbi@ti.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Wolfram Sang <w.sang@pengutronix.de>,
	Luigi Semenzato <semenzato@chromium.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Che-Liang Chiou <clchiou@chromium.org>,
	Jonathan Kliegman <kliegs@chromium.org>,
	linux-input@vger.kernel.org, Sourav Poddar <sourav.poddar@ti.com>,
	devicetree-discuss@lists.ozlabs.org,
	Alban Bedel <alban.bedel@avionic-design.de>,
	Roland Stigge <stigge@antcom.de>,
	Vincent Palatin <vpalatin@chromium.org>,
	Javier Martinez Canillas <javier@dowhile0.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-doc@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	Bill Pemberton <wfp5p@virginia.edu>,
	Doug Anderson <dianders@chromium.org>,
	Olof Johansson <olofj@chromium.or>
Subject: Re: [PATCH v6 0/6] Add ChromeOS Embedded Controller support
Date: Wed, 27 Feb 2013 09:40:34 +0100	[thread overview]
Message-ID: <20130227084034.GE16414@sortiz-mobl> (raw)
In-Reply-To: <CAPnjgZ3enERPu1uK5GW9+_ZinhiDmDuoNn2FGhgVNOZbFVQ0tQ@mail.gmail.com>

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@chromium.org> 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.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

WARNING: multiple messages have this Message-ID (diff)
From: Samuel Ortiz <sameo@linux.intel.com>
To: Simon Glass <sjg@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Rob Landley <rob@landley.net>, Felipe Balbi <balbi@ti.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Wolfram Sang <w.sang@pengutronix.de>,
	Luigi Semenzato <semenzato@chromium.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Che-Liang Chiou <clchiou@chromium.org>,
	Jonathan Kliegman <kliegs@chromium.org>,
	linux-input@vger.kernel.org, Sourav Poddar <sourav.poddar@ti.com>,
	devicetree-discuss@lists.ozlabs.org,
	Alban Bedel <alban.bedel@avionic-design.de>,
	Roland Stigge <stigge@antcom.de>,
	Vincent Palatin <vpalatin@chromium.org>,
	Javier Martinez Canillas <javier@dowhile0.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-doc@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	Bill Pemberton <wfp5p@virginia.edu>,
	Doug Anderson <dianders@chromium.org>,
	Olof Johansson <olofj@chromium.org>
Subject: Re: [PATCH v6 0/6] Add ChromeOS Embedded Controller support
Date: Wed, 27 Feb 2013 09:40:34 +0100	[thread overview]
Message-ID: <20130227084034.GE16414@sortiz-mobl> (raw)
In-Reply-To: <CAPnjgZ3enERPu1uK5GW9+_ZinhiDmDuoNn2FGhgVNOZbFVQ0tQ@mail.gmail.com>

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@chromium.org> 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.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2013-02-27  8:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 22:08 [PATCH v6 0/6] Add ChromeOS Embedded Controller support Simon Glass
2013-02-25 22:08 ` [PATCH v6 1/6] mfd: Add ChromeOS EC messages header Simon Glass
2013-02-25 22:08 ` [PATCH v6 3/6] mfd: Add ChromeOS EC I2C driver Simon Glass
2013-02-25 22:08 ` [PATCH v6 4/6] mfd: Add ChromeOS EC SPI driver Simon Glass
2013-02-25 22:08 ` [PATCH v6 5/6] Input: matrix-keymap: Add function to read the new DT binding Simon Glass
     [not found] ` <1361830121-32284-1-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2013-02-25 22:08   ` [PATCH v6 2/6] mfd: Add ChromeOS EC implementation Simon Glass
2013-02-25 22:08     ` Simon Glass
2013-02-25 22:08   ` [PATCH v6 6/6] Input: Add ChromeOS EC keyboard driver Simon Glass
2013-02-25 22:08     ` Simon Glass
2013-02-25 22:12     ` Dmitry Torokhov
2013-02-27  5:13 ` [PATCH v6 0/6] Add ChromeOS Embedded Controller support Simon Glass
2013-02-27  8:40   ` Samuel Ortiz [this message]
2013-02-27  8:40     ` Samuel Ortiz
2013-02-28  0:25     ` Simon Glass
2013-02-28  0:25       ` Simon Glass
2013-03-18 18:41     ` Simon Glass
2013-03-18 18:41       ` Simon Glass
2013-03-20  0:56 ` Samuel Ortiz
2013-03-20  1:12   ` Samuel Ortiz
2013-03-20  1:12     ` Samuel Ortiz
2013-03-20  2:01     ` Simon Glass
2013-03-20  2:01       ` Simon Glass
2013-03-20  8:14       ` Samuel Ortiz
2013-03-20  8:14         ` Samuel Ortiz
2013-03-20  8:52         ` Samuel Ortiz
2013-03-20  8:52           ` Samuel Ortiz
2013-03-21  1:40           ` Simon Glass
2013-03-21  1:40             ` Simon Glass

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130227084034.GE16414@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=alban.bedel@avionic-design.de \
    --cc=balbi@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=clchiou@chromium.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=javier@dowhile0.org \
    --cc=kliegs@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olofj@chromium.or \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=semenzato@chromium.org \
    --cc=sjg@chromium.org \
    --cc=sourav.poddar@ti.com \
    --cc=stigge@antcom.de \
    --cc=tony@atomide.com \
    --cc=vpalatin@chromium.org \
    --cc=w.sang@pengutronix.de \
    --cc=wfp5p@virginia.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.