linux-stable.git/drivers/platform/chrome/Kconfig, branch linux-5.7.y

platform/chrome: Add Type C connector class driver

2020-03-22T10:11:26+00:00

Add a driver to implement the Type C connector class for Chrome OS
devices with ECs (Embedded Controllers).

The driver relies on firmware device specifications for various port
attributes. On ACPI platforms, this is specified using the logical
device with HID GOOG0014. On DT platforms, this is specified using the
DT node with compatible string "google,cros-ec-typec".

The driver reads the device FW node and uses the port attributes to
register the typec ports with the Type C connector class framework, but
doesn't do much else.

Subsequent patches will add more functionality to the driver, including
obtaining current port information (polarity, vconn role, current power
role etc.) after querying the EC.

Co-developed-by: Benson Leung 
Signed-off-by: Prashant Malani 
Reviewed-by: Heikki Krogerus 
Signed-off-by: Enric Balletbo i Serra

platform/chrome: Kconfig: Remove CONFIG_ prefix from MFD_CROS_EC section

2020-03-06T16:55:20+00:00

Remove the CONFIG_ prefix from the select statement for MFD_CROS_EC.

Fixes: 2fa2b980e3fe1 ("mfd / platform: cros_ec: Rename config to a better name")
Reported-by: Randy Dunlap 
Signed-off-by: Enric Balletbo i Serra 
Acked-by: Andy Shevchenko 
Acked-by: Randy Dunlap

platform: chrome: Add cros-usbpd-notify driver

2020-02-10T18:14:19+00:00

ChromiumOS uses ACPI device with HID "GOOG0003" for power delivery
related events. The existing cros-usbpd-charger driver relies on these
events without ever actually receiving them on ACPI platforms. This is
because in the ChromeOS kernel trees, the GOOG0003 device is owned by an
ACPI driver that offers firmware updates to USB-C chargers.

Introduce a new platform driver under cros-ec, the ChromeOS embedded
controller, that handles these PD events and dispatches them
appropriately over a notifier chain to all drivers that use them.

On platforms that don't have the ACPI device defined, the driver gets
instantiated for ECs which support the EC_FEATURE_USB_PD feature bit,
and the notification events will get delivered using the MKBP event
handling mechanism.

Co-Developed-by: Prashant Malani 
Reviewed-by: Gwendal Grignou 
Reviewed-by: Benson Leung 
Signed-off-by: Jon Flatley 
Signed-off-by: Prashant Malani 
Acked-By: Enric Balletbo i Serra 
Signed-off-by: Benson Leung

platform/chrome: cros_ec: Add Kconfig default for cros-ec-sensorhub

2019-11-27T09:28:09+00:00

Like the other CrOS EC sub-drivers set that depends on his parent and
set default to the parent's value.

Signed-off-by: Enric Balletbo i Serra

Merge tag 'tag-ib-chrome-mfd-iio-input-5.5' into chrome-platform-5.5

2019-11-21T10:52:51+00:00

IB between mfd, iio, input and chrome platform for cros-ec-sensorhub

Signed-off-by: Enric Balletbo i Serra

iio / platform: cros_ec: Add cros-ec-sensorhub driver

2019-11-21T10:23:14+00:00

Similar to HID sensor stack, the new driver sits between cros-ec-dev
and the IIO device drivers:

The EC based IIO device topology would be:

iio:device1 ->
   ...0/0000:00:1f.0/PNP0C09:00/GOOG0004:00/cros-ec-dev.6.auto/
                                            cros-ec-sensorhub.7.auto/
                                            cros-ec-accel.15.auto/
                                            iio:device1

It will be expanded to control EC sensor FIFO.

Signed-off-by: Gwendal Grignou 
Reviewed-by: Jonathan Cameron 
[Fix "unknown type name 'uint32_t'" type errors]
Reported-by: kbuild test robot 
Signed-off-by: Enric Balletbo i Serra

platform/chrome: cros_ec: Fix Kconfig indentation

2019-11-20T15:08:12+00:00

Adjust indentation from spaces to tab (+optional two spaces) as in
coding style with command like:
	$ sed -e 's/^        /\t/' -i */Kconfig

Signed-off-by: Krzysztof Kozlowski 
Signed-off-by: Enric Balletbo i Serra

mfd / platform: cros_ec: Rename config to a better name

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

The cros-ec-dev is a multifunction device that now doesn't implement any
chardev communication interface. MFD_CROS_EC_CHARDEV doesn't look
a good name to describe that device and can cause confusion. Hence
rename it to CROS_EC_DEV.

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: 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