From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] Add cros_ec changes for newer boards
Date: Wed, 23 Apr 2014 13:32:40 +0100 [thread overview]
Message-ID: <20140423123240.GA640@lee--X1> (raw)
In-Reply-To: <1398185154-19404-1-git-send-email-dianders@chromium.org>
On Tue, 22 Apr 2014, Doug Anderson wrote:
> This series adds the most critical cros_ec changes for newer boards
> using cros_ec. Specifically:
> * Fixes timing/locking issues with the previously upstreamed (but
> never used upstream) cros_ec_spi driver.
> * Updates the cros_ec header file to the latest version which allows
> us to use newer EC features like i2c tunneling.
> * Adds an i2c tunnel driver to allow communication to the EC's i2c
> devices.
>
> This _doesn't_ get the EC driver fully up to speed with what's in the
> current Chromium OS trees. There are a whole slew of cleanup patches
> there, an addition of an LPC transport mode, and exports of functions
> to userspace. Once these patches land and we have functionality we
> can continue to pick more cleanup patches.
>
> Changes in v2:
> - Update tunnel binding as per swarren
> - Removed i2c20 alias for i2c tunnel
>
> Bill Richardson (1):
> mfd: cros_ec: Sync to the latest cros_ec_commands.h from EC sources
>
> David Hendricks (1):
> mfd: cros_ec: spi: calculate delay between transfers correctly
>
> Doug Anderson (5):
> mfd: cros_ec: spi: Add mutex to cros_ec_spi
> mfd: cros_ec: spi: Make the cros_ec_spi timeout more reliable
> mfd: cros_ec: spi: Increase cros_ec_spi deadline from 5ms to 100ms
> i2c: ChromeOS EC tunnel driver
> ARM: tegra: Add the EC i2c tunnel to tegra124-venice2
>
> .../devicetree/bindings/i2c/i2c-cros-ec-tunnel.txt | 39 +
> arch/arm/boot/dts/tegra124-venice2.dts | 26 +
> drivers/i2c/busses/Kconfig | 9 +
> drivers/i2c/busses/Makefile | 1 +
> drivers/i2c/busses/i2c-cros-ec-tunnel.c | 304 ++++++
> drivers/mfd/cros_ec.c | 7 +-
> drivers/mfd/cros_ec_spi.c | 67 +-
> include/linux/mfd/cros_ec.h | 4 +-
> include/linux/mfd/cros_ec_commands.h | 1128 ++++++++++++++++++--
> 9 files changed, 1493 insertions(+), 92 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/i2c/i2c-cros-ec-tunnel.txt
> create mode 100644 drivers/i2c/busses/i2c-cros-ec-tunnel.c
Need to wait for the ARM, DT and I2C guys to review, at which point
I'll be happy to take in and supply a branch for them to pull from if
required. If there are no _true_ dependencies and the MFD changes can
be added independently without fear of build breakages, let me know
and I'll apply them separately.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-04-23 12:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 16:45 [PATCH v2 0/7] Add cros_ec changes for newer boards Doug Anderson
2014-04-22 16:45 ` [PATCH v2 7/7] ARM: tegra: Add the EC i2c tunnel to tegra124-venice2 Doug Anderson
2014-04-23 12:32 ` Lee Jones [this message]
2014-04-23 16:20 ` [PATCH v2 0/7] Add cros_ec changes for newer boards Stephen Warren
2014-04-23 16:32 ` Doug Anderson
2014-04-23 16:35 ` Doug Anderson
2014-04-28 9:19 ` Lee Jones
2014-04-28 21:18 ` Doug Anderson
2014-04-29 8:21 ` Lee Jones
2014-04-29 16:51 ` Doug Anderson
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=20140423123240.GA640@lee--X1 \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox