linux-stable.git/drivers/platform/chrome/Makefile, branch linux-5.4.y

mfd / platform: cros_ec: Miscellaneous character device to talk with the EC

2019-09-02T10:33:21+00:00

That's a driver to talk with the ChromeOS Embedded Controller via a
miscellaneous character device, it creates an entry in /dev for every
instance and implements basic file operations for communicating with the
Embedded Controller with an userspace application. The API is moved to
the uapi folder, which is supposed to contain the user space API of the
kernel.

Note that this will replace current character device interface
implemented in the cros-ec-dev driver in the MFD subsystem. The idea is
to move all the functionality that extends the bounds of what MFD was
designed to platform/chrome subsystem.

Signed-off-by: Enric Balletbo i Serra 
Acked-by: Andy Shevchenko 
Reviewed-by: Gwendal Grignou 
Tested-by: Gwendal Grignou 
Signed-off-by: Lee Jones

mfd / platform: cros_ec: Move cros-ec core driver out from MFD

2019-09-02T10:33:12+00:00

Now, the ChromeOS EC core driver has nothing related to an MFD device, so
move that driver from the MFD subsystem to the platform/chrome subsystem.

Signed-off-by: Enric Balletbo i Serra 
Acked-by: Andy Shevchenko 
Acked-by: Thierry Reding 
Acked-by: Mark Brown 
Acked-by: Wolfram Sang 
Acked-by: Neil Armstrong 
Acked-by: Alexandre Belloni 
Acked-by: Jonathan Cameron 
Acked-by: Benjamin Tissoires 
Acked-by: Dmitry Torokhov 
Acked-by: Sebastian Reichel 
Acked-by: Chanwoo Choi 
Reviewed-by: Gwendal Grignou 
Tested-by: Gwendal Grignou 
Signed-off-by: Lee Jones

platform/chrome: cros_ec_lpc: Choose Microchip EC at runtime

2019-06-20T10:00:32+00:00

On many boards, communication between the kernel and the Embedded
Controller happens over an LPC bus. In these cases, the kernel config
CONFIG_CROS_EC_LPC is enabled. Some of these LPC boards contain a
Microchip Embedded Controller (MEC) that is different from the regular
EC. On these devices, the same LPC bus is used, but the protocol is
a little different. In these cases, the CONFIG_CROS_EC_LPC_MEC kernel
config is enabled. Currently, the kernel decides at compile-time whether
or not to use the MEC variant, and, when that kernel option is selected
it breaks the other boards. We would like a kind of runtime detection to
avoid this.

This patch adds that detection mechanism by probing the protocol at
runtime, first we assume that a MEC variant is connected, and if the
protocol fails it fallbacks to the regular EC. This adds a bit of
overload because we try to read twice on those LPC boards that doesn't
contain a MEC variant, but is a better solution than having to select the
EC variant at compile-time.

While here also fix the alignment in Kconfig file for this config option
replacing the spaces by tabs.

Signed-off-by: Enric Balletbo i Serra 
Reviewed-by: Ezequiel Garcia 
Tested-by: Nick Crews 
Reviewed-by: Nick Crews

platform/chrome: cros_ec_lpc: Merge cros_ec_lpc and cros_ec_lpc_reg

2019-06-20T09:53:52+00:00

The cros_ec_lpc_reg files are only used by the cros_ec_lpc core and
there isn't logical separation between them. So, merge those files into
the cros_ec_lpc also allowing us to drop the header file used for the
interface between the two.

Signed-off-by: Enric Balletbo i Serra 
Reviewed-by: Nick Crews

platform/chrome: Add ChromeOS EC ISHTP driver

2019-05-20T08:18:10+00:00

This driver implements a slim layer to enable the ChromeOS
EC kernel stack (cros_ec) to communicate with ChromeOS EC
firmware running on the Intel Integrated Sensor Hub (ISH).

The driver registers a ChromeOS EC MFD device to connect
with cros_ec kernel stack (upper layer), and it registers a
client with the ISH Transport Protocol bus (lower layer) to
talk with the ISH firwmare. See description of the ISHTP
protocol at Documentation/hid/intel-ish-hid.txt

Signed-off-by: Rushikesh S Kadam 
Acked-by: Srinivas Pandruvada 
Reviewed-by: Jett Rink 
Tested-by: Jett Rink 
Signed-off-by: Enric Balletbo i Serra

platform/chrome: cros_ec_proto: Add trace event to trace EC commands

2019-04-17T08:29:34+00:00

This is useful to see which EC commands are being executed and when.

To enable:

    echo 1 > /sys/kernel/debug/tracing/events/cros_ec/enable

Example:

    cros_ec_cmd: version: 0, command: EC_CMD_GET_VERSION
    cros_ec_cmd: version: 0, command: EC_CMD_GET_PROTOCOL_INFO
    cros_ec_cmd: version: 1, command: EC_CMD_GET_CMD_VERSIONS
    cros_ec_cmd: version: 1, command: EC_CMD_USB_PD_CONTROL

The list of current commands is generated using the following script:

    sed -n 's/^#define \(EC_CMD_[[:alnum:]_]*\)\s.*/\tTRACE_SYMBOL(\1),\\/p' include/linux/mfd/cros_ec_commands.h

Signed-off-by: Raul E Rangel 
Reviewed-by: Ross Zwisler 
Reviewed-by: Steven Rostedt (VMware) 
Signed-off-by: Enric Balletbo i Serra

platform/chrome: cros_ec: Add EC host command support using rpmsg

2019-04-16T09:00:36+00:00

Add EC host command support through rpmsg.

Signed-off-by: Pi-Hsun Shih 
Signed-off-by: Enric Balletbo i Serra

platform/chrome: Add CrOS USB PD logging driver

2019-04-15T10:13:24+00:00

The CrOS USB PD logging feature is logically separate functionality of
the charge manager, hence has its own driver. The driver logs the event
data for the USB PD charger available in some ChromeOS Embedded
Controllers.

Signed-off-by: Guenter Roeck 
[remove macro to APPEND_STRING and minor cleanups]
Signed-off-by: Enric Balletbo i Serra

platform/chrome: Add new driver for Wilco EC

2019-02-21T20:35:59+00:00

This EC is an incompatible variant of the typical Chrome OS embedded
controller.  It uses the same low-level communication and a similar
protocol with some significant differences.  The EC firmware does
not support the same mailbox commands so it is not registered as a
cros_ec device type.  This commit exports the wilco_ec_mailbox()
function so that other modules can use it to communicate with the EC.

Signed-off-by: Duncan Laurie 
Signed-off-by: Nick Crews 
[Fix the sparse warning: symbol 'wilco_ec_transfer' was not declared]
Signed-off-by: Wei Yongjun 
[Fix Kconfig dependencies for wilco_ec]
Reported-by: Randy Dunlap 
Signed-off-by: Enric Balletbo i Serra

mfd / platform: cros_ec: Move device sysfs attributes to its own driver

2019-02-01T08:09:27+00:00

The entire way how cros debugfs attibutes are created is broken.
cros_ec_sysfs should be its own driver and its attributes should be
associated with the sysfs driver not the mfd driver.

The patch also adds the sysfs documentation.

Signed-off-by: Enric Balletbo i Serra 
Reviewed-by: Guenter Roeck 
Signed-off-by: Lee Jones