litmus-rt.git/drivers/platform/chrome, branch master

platform/chrome: chromeos_laptop - instantiate Atmel at primary address

2015-04-25T05:07:14+00:00

The new Atmel MXT driver expects i2c client's address contain the
primary (main address) of the chip, and calculates the expected
bootloader address form the primary address. Unfortunately chrome_laptop
does probe the devices and if touchpad (or touchscreen, or both) comes
up in bootloader mode the i2c device gets instantiated with the
bootloader address which confuses the driver.

To work around this issue let's probe the primary address first. If the
device is not detected at the primary address we'll probe alternative
addresses as "dummy" devices. If any of them are found, destroy the
dummy client and instantiate client with proper name at primary address
still.

Signed-off-by: Dmitry Torokhov 
Signed-off-by: Olof Johansson

platform/chrome: cros_ec_lpc - Depend on X86 || COMPILE_TEST

2015-03-04T19:29:45+00:00

The ChromeOS EC is connected by LPC only on x86 platforms and no others,
so add a dependency describing that.

But also build the driver if the COMPILE_TEST option is enabled
to have build coverage in other architectures.

Signed-off-by: Javier Martinez Canillas 
[olof: reworded commit message]
Signed-off-by: Olof Johansson

platform/chrome: cros_ec_lpc - Include linux/io.h header file

2015-03-04T19:28:28+00:00

The driver uses the inb() and outb() I/O functions so should
include the header file that has these functions definitions.

This patch fixes the following error when the header is not
explicitly included:

drivers/platform/chrome//cros_ec_lpc.c: In function ‘ec_response_timed_out’:
drivers/platform/chrome//cros_ec_lpc.c:40:3: error: implicit declaration of function ‘inb’ [-Werror=implicit-function-declaration]
drivers/platform/chrome//cros_ec_lpc.c: In function ‘cros_ec_cmd_xfer_lpc’:
drivers/platform/chrome//cros_ec_lpc.c:75:3: error: implicit declaration of function ‘outb’ [-Werror=implicit-function-declaration]

Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Olof Johansson

platform/chrome: fix platform_no_drv_owner.cocci warnings

2015-03-04T19:25:18+00:00

drivers/platform/chrome/cros_ec_lpc.c:272:3-8: No need to set .owner here. The core will do it.

 Remove .owner field if calls are used which set it automatically

Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci

CC: Bill Richardson 
Signed-off-by: Fengguang Wu 
Signed-off-by: Olof Johansson

platform/chrome: cros_ec_lightbar - fix duplicate const warning

2015-03-04T19:23:13+00:00

Fix the following sparse warning:

    drivers/platform/chrome/cros_ec_lightbar.c:254:25: sparse: duplicate const

Reported-by: Dan Carpenter 
Signed-off-by: Olof Johansson 
Reviewed-by: Gwendal Grignou 
Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Olof Johansson

platform/chrome: cros_ec_dev - fix Unknown escape '%' warning

2015-03-04T19:23:10+00:00

Fix the following sparse warning:

    drivers/platform/chrome/cros_ec_dev.c:64:45: sparse: Unknown escape '%'

Reported-by: Dan Carpenter 
Signed-off-by: Olof Johansson 
Reviewed-by: Gwendal Grignou 
Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Olof Johansson

platform/chrome: Expose Chrome OS Lightbar to users

2015-02-26T23:45:16+00:00

This adds some sysfs entries to provide userspace control of the
four-element LED "lightbar" on the Chromebook Pixel. This only instantiates
the lightbar controls if the device actually exists.

To prevent DoS attacks, this interface is limited to 20 accesses/second,
although that rate can be adjusted by a privileged user.

On Chromebooks without a lightbar, this should have no effect. On the
Chromebook Pixel, you should be able to do things like this:

    $ cd /sys/devices/virtual/chromeos/cros_ec/lightbar
    $ echo 0x80 > brightness
    $ echo 255 > brightness
    $
    $ cat sequence
    S0
    $ echo konami > sequence
    $ cat sequence
    KONAMI
    $
    $ cat sequence
    S0

And

    $ cd /sys/devices/virtual/chromeos/cros_ec/lightbar
    $ echo stop > sequence
    $ echo "4 255 255 255" > led_rgb
    $ echo "0 255 0 0  1 0 255 0  2 0 0 255  3 255 255 0" > led_rgb
    $ echo run  > sequence

Test the DoS prevention with this:

    $ cd /sys/devices/virtual/chromeos/cros_ec/lightbar
    $ echo 500 > interval_msec
    $ time (cat version version version version version version version)

Signed-off-by: Bill Richardson 
Reviewed-by: Olof Johansson 
Tested-by: Doug Anderson 
Reviewed-by: Benson Leung 
Signed-off-by: Javier Martinez Canillas 
Tested-by: Gwendal Grignou 
Reviewed-by: Gwendal Grignou 
Signed-off-by: Olof Johansson

platform/chrome: Create sysfs attributes for the ChromeOS EC

2015-02-26T23:45:12+00:00

This adds the first few sysfs attributes for the Chrome OS EC. These
controls are made available under /sys/devices/virtual/chromeos/cros_ec

    flashinfo   - display current flash info
    reboot      - tell the EC to reboot in various ways
    version     - information about the EC software and hardware

Future changes will build on this to add additional controls.

From a root shell, you should be able to do things like this:

    cd /sys/devices/virtual/chromeos/cros_ec
    cat flashinfo
    cat version
    echo rw > reboot
    cat version
    echo ro > reboot
    cat version
    echo rw > reboot
    cat version
    echo cold > reboot

That last command will reboot the AP too.

Signed-off-by: Bill Richardson 
Reviewed-by: Olof Johansson 
Signed-off-by: Javier Martinez Canillas 
Tested-by: Gwendal Grignou 
Reviewed-by: Gwendal Grignou 
Signed-off-by: Olof Johansson

platform/chrome: Add Chrome OS EC userspace device interface

2015-02-26T23:45:06+00:00

This patch adds a device interface to access the
Chrome OS Embedded Controller from user-space.

Signed-off-by: Bill Richardson 
Reviewed-by: Simon Glass 
Signed-off-by: Javier Martinez Canillas 
Reviewed-by: Gwendal Grignou 
Tested-by: Gwendal Grignou 
Reviewed-by: Gwendal Grignou 
Signed-off-by: Olof Johansson

platform/chrome: Add cros_ec_lpc driver for x86 devices

2015-02-26T23:45:02+00:00

Chromebooks have an Embedded Controller (EC) that is used to
implement various functions such as keyboard, power and battery.

The AP can communicate with the EC through different bus types
such as I2C, SPI or LPC.

The cros_ec mfd driver is then composed of a core driver that
register the sub-devices as mfd cells and provide a high level
communication interface that is used by the rest of the kernel
and bus specific interfaces modules.

Each connection method then has its own driver, which register
with the EC driver interface-agnostic interface.

Currently, there are drivers to communicate with the EC over
I2C and SPI and this driver adds support for LPC.

Signed-off-by: Bill Richardson 
Signed-off-by: Javier Martinez Canillas 
Tested-by: Gwendal Grignou 
Reviewed-by: Gwendal Grignou 
Signed-off-by: Olof Johansson