Changes in Kconfig

d33d2255 - platform/chrome: add HAS_IOPORT dependencies

Fri, 05 Apr 2024 13:41:51 +0000

platform/chrome: add HAS_IOPORT dependenciesIn a future patch HAS_IOPORT=n will disable inb()/outb() and friends atcompile time. We thus need to add HAS_IOPORT as dependency for thosedrivers using them.Co-developed-by: Arnd Bergmann Signed-off-by: Arnd Bergmann Signed-off-by: Niklas Schnelle Link: https://lore.kernel.org/r/20240405134151.5560-2-schnelle@linux.ibm.comSigned-off-by: Tzung-Bi Shih List of files: /linux-6.15/drivers/platform/chrome/wilco_ec/Kconfig

60fb8a8e - platform/chrome: wilco_ec: Allow wilco to be compiled in COMPILE_TEST

Wed, 22 Jan 2020 01:24:34 +0000

platform/chrome: wilco_ec: Allow wilco to be compiled in COMPILE_TESTEnable this Kconfig on COMPILE_TEST enabled configs so we can get morebuild coverage.Signed-off-by: Stephen Boyd Signed-off-by: Enric Balletbo i Serra List of files: /linux-6.15/drivers/platform/chrome/wilco_ec/Kconfig

119a3cb6 - platform/chrome: wilco_ec: Add keyboard backlight LED support

Wed, 06 Nov 2019 16:33:19 +0000

platform/chrome: wilco_ec: Add keyboard backlight LED supportThe EC is in charge of controlling the keyboard backlight onthe Wilco platform. We expose a standard LED class devicenamed platform::kbd_backlight.Since the EC will never change the backlight level of its own accord,we don't need to implement a brightness_get() method.Signed-off-by: Nick Crews Signed-off-by: Daniel Campello Reviewed-by: Daniel Campello Signed-off-by: Enric Balletbo i Serra List of files: /linux-6.15/drivers/platform/chrome/wilco_ec/Kconfig

22c040fa - platform/chrome: cros_ec_lpc: Choose Microchip EC at runtime

Fri, 14 Jun 2019 21:43:01 +0000

platform/chrome: cros_ec_lpc: Choose Microchip EC at runtimeOn many boards, communication between the kernel and the EmbeddedController happens over an LPC bus. In these cases, the kernel configCONFIG_CROS_EC_LPC is enabled. Some of these LPC boards contain aMicrochip Embedded Controller (MEC) that is different from the regularEC. On these devices, the same LPC bus is used, but the protocol isa little different. In these cases, the CONFIG_CROS_EC_LPC_MEC kernelconfig is enabled. Currently, the kernel decides at compile-time whetheror not to use the MEC variant, and, when that kernel option is selectedit breaks the other boards. We would like a kind of runtime detection toavoid this.This patch adds that detection mechanism by probing the protocol atruntime, first we assume that a MEC variant is connected, and if theprotocol fails it fallbacks to the regular EC. This adds a bit ofoverload because we try to read twice on those LPC boards that doesn'tcontain a MEC variant, but is a better solution than having to select theEC variant at compile-time.While here also fix the alignment in Kconfig file for this config optionreplacing the spaces by tabs.Signed-off-by: Enric Balletbo i Serra Reviewed-by: Ezequiel Garcia Tested-by: Nick Crews Reviewed-by: Nick Crews List of files: /linux-6.15/drivers/platform/chrome/wilco_ec/Kconfig

1210d1e6 - platform/chrome: wilco_ec: Add telemetry char device interface

Tue, 21 May 2019 19:20:45 +0000

platform/chrome: wilco_ec: Add telemetry char device interfaceThe Wilco Embedded Controller is able to send telemetry datawhich is useful for enterprise applications. A daemon running onthe OS sends a command to the EC via a write() to a char device,and can read the response with a read(). The write() request isverified by the driver to ensure that it is performing only oneof the whitelisted commands, and that no extraneous data isbeing transmitted to the EC. The response is passed directlyback to the reader with no modification.The character device will appear as /dev/wilco_telemN, where Nis some small non-negative integer, starting with 0. Only oneprocess may have the file descriptor open at a time. The callinguserspace program needs to keep the device file descriptor openbetween the calls to write() and read() in order to preserve theresponse. Up to 32 bytes will be available for reading.For testing purposes, try requesting the EC's firmware builddate, by sending the WILCO_EC_TELEM_GET_VERSION command withargument index=3. i.e. write [0x38, 0x00, 0x03]to the device node. An ASCII string of the build date isreturned.Signed-off-by: Nick Crews Signed-off-by: Enric Balletbo i Serra List of files: /linux-6.15/drivers/platform/chrome/wilco_ec/Kconfig

f7b0bc5e - platform/chrome: wilco_ec: Add event handling

Thu, 23 May 2019 23:06:24 +0000

platform/chrome: wilco_ec: Add event handlingThe Wilco Embedded Controller can create custom events thatare not handled as standard ACPI objects. These events cancontain information about changes in EC controlled features,such as errors and events in the dock or display. For example,an event is triggered if the dock is plugged into a displayincorrectly. These events are needed for telemetry anddiagnostics reasons, and for possibly alerting the user.These events are triggered by the EC with an ACPI Notify(0x90),and then the BIOS reads the event buffer from EC RAM via anACPI method. When the OS receives these events via ACPI,it passes them along to this driver. The events are put intoa queue which can be read by a userspace daemon via a char devicethat implements read() and poll(). The event queue acts as acircular buffer of size 64, so if there are no userspace consumersthe kernel will not run out of memory. The char device will appear at/dev/wilco_event{n}, where n is some small non-negative integer,starting from 0. Standard ACPI events such as the battery gettingplugged/unplugged can also come through this path, but they aredealt with via other paths, and are ignored here.To test, you can tail the binary data with$ cat /dev/wilco_event0 | hexdump -ve '1/1 "%x\n"'and then create an event by plugging/unplugging the battery.Signed-off-by: Nick Crews Signed-off-by: Enric Balletbo i Serra List of files: /linux-6.15/drivers/platform/chrome/wilco_ec/Kconfig

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/platform/chrome/wilco_ec/Kconfig

27944495 - platform/chrome: fix wilco-ec dependencies

Mon, 04 Mar 2019 20:06:51 +0000

platform/chrome: fix wilco-ec dependenciesWhen CROS_EC_LPC is set to =m, we get a link failure for abuiltin wilco-ec module:drivers/platform/chrome/wilco_ec/core.o: In function `wilco_ec_remove':core.c:(.text+0x26): undefined reference to `cros_ec_lpc_mec_destroy'drivers/platform/chrome/wilco_ec/core.o: In function `wilco_ec_probe':core.c:(.text+0x18c): undefined reference to `cros_ec_lpc_mec_init'core.c:(.text+0x224): undefined reference to `cros_ec_lpc_mec_destroy'drivers/platform/chrome/wilco_ec/mailbox.o: In function `wilco_ec_mailbox':mailbox.c:(.text+0x104): undefined reference to `cros_ec_lpc_io_bytes_mec'The problem with the existing CROS_EC_LPC_MEC dependency is that thisis only for a 'bool' symbol, so the information about the exportedfunctions being in a module is lost on the way, and we actually haveto depend on both CROS_EC_LPC and CROS_EC_LPC_MEC.Fixes: 7b3d4f44abf0 ("platform/chrome: Add new driver for Wilco EC")Signed-off-by: Arnd Bergmann Signed-off-by: Enric Balletbo i Serra List of files: /linux-6.15/drivers/platform/chrome/wilco_ec/Kconfig

b787bb12 - platform/chrome: wilco_ec: Add support for raw commands in debugfs

Sat, 09 Feb 2019 00:37:18 +0000

platform/chrome: wilco_ec: Add support for raw commands in debugfsAdd a debugfs attribute that allows sending raw commands to the EC.This is useful for development and debug but should not be enabledin a production environment.To test:Get the EC firmware build dateFirst send the request command> echo 00 f0 38 00 03 00 > rawThen read the result. "12/21/18" is in the middle of the response> cat raw00 31 32 2f 32 31 2f 31 38 00 00 0f 01 00 01 00 .12/21/18.......Get the EC firmware build dateFirst send the request command> echo 00 f0 38 00 03 00 > rawThen read the result. "12/21/18" is in the middle of the response> cat raw00 31 32 2f 32 31 2f 31 38 00 00 0f 01 00 01 00 .12/21/18.......Signed-off-by: Duncan Laurie Signed-off-by: Nick Crews [Fix off-by-one error in wilco_ec/debugfs.c]Reported-by: Dan Carpenter Signed-off-by: Enric Balletbo i Serra List of files: /linux-6.15/drivers/platform/chrome/wilco_ec/Kconfig

7b3d4f44 - platform/chrome: Add new driver for Wilco EC

Sat, 09 Feb 2019 00:37:17 +0000

platform/chrome: Add new driver for Wilco ECThis EC is an incompatible variant of the typical Chrome OS embeddedcontroller. It uses the same low-level communication and a similarprotocol with some significant differences. The EC firmware doesnot support the same mailbox commands so it is not registered as acros_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 List of files: /linux-6.15/drivers/platform/chrome/wilco_ec/Kconfig