On 3 August 2015 at 08:19, Simon Glass <s...@chromium.org> wrote:
> The Chrome OS EC supports tunnelling through to an I2C bus on the EC. This
> currently uses a copy of the I2C command code and a special 'crosec'
> sub-command.
>
> With driver model we can define an I2C bus which tunnels through to the EC,
> and use the normal 'i2c' command to access it. This simplifies the code and
> removes some duplication.
>
> Add an I2C driver which tunnels through to the EC. Adjust the EC code to
> support binding child devices so that it can be set up. Adjust the existing
> I2C xfer function to fit driver model better.
>
> For now the old code remains to allow things to still work. It will be
> removed in a later patch once the new flow is fully enabled.
>
> Signed-off-by: Simon Glass <s...@chromium.org>
> ---
>
> Changes in v2: None
>
>  configs/peach-pi_defconfig            |  2 +
>  configs/peach-pit_defconfig           |  2 +
>  drivers/i2c/Kconfig                   | 11 +++++
>  drivers/i2c/Makefile                  |  1 +
>  drivers/i2c/cros_ec_tunnel.c          | 41 +++++++++++++++
>  drivers/misc/cros_ec.c                | 93 
> +++++++++++++++++++++++++++++++++--
>  drivers/power/pmic/pmic_tps65090_ec.c |  8 +--
>  include/cros_ec.h                     | 14 +++++-
>  8 files changed, 161 insertions(+), 11 deletions(-)
>  create mode 100644 drivers/i2c/cros_ec_tunnel.c

Applied to u-boot-dm.
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to