<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>119a3cb6 - platform/chrome: wilco_ec: Add keyboard backlight LED support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/platform/chrome/wilco_ec/Makefile#119a3cb6</link>
        <description>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&apos;t need to implement a brightness_get() method.Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;Signed-off-by: Daniel Campello &lt;campello@chromium.org&gt;Reviewed-by: Daniel Campello &lt;campello@chromium.org&gt;Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;

            List of files:
            /linux-6.15/drivers/platform/chrome/wilco_ec/Makefile</description>
        <pubDate>Wed, 06 Nov 2019 16:33:19 +0000</pubDate>
        <dc:creator>Daniel Campello &lt;campello@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>1210d1e6 - platform/chrome: wilco_ec: Add telemetry char device interface</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/platform/chrome/wilco_ec/Makefile#1210d1e6</link>
        <description>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&apos;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 &lt;ncrews@chromium.org&gt;Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;

            List of files:
            /linux-6.15/drivers/platform/chrome/wilco_ec/Makefile</description>
        <pubDate>Tue, 21 May 2019 19:20:45 +0000</pubDate>
        <dc:creator>Nick Crews &lt;ncrews@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>f7b0bc5e - platform/chrome: wilco_ec: Add event handling</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/platform/chrome/wilco_ec/Makefile#f7b0bc5e</link>
        <description>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 &apos;1/1 &quot;%x\n&quot;&apos;and then create an event by plugging/unplugging the battery.Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;

            List of files:
            /linux-6.15/drivers/platform/chrome/wilco_ec/Makefile</description>
        <pubDate>Thu, 23 May 2019 23:06:24 +0000</pubDate>
        <dc:creator>Nick Crews &lt;ncrews@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>0c0b7ea2 - platform/chrome: wilco_ec: Add property helper library</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/platform/chrome/wilco_ec/Makefile#0c0b7ea2</link>
        <description>platform/chrome: wilco_ec: Add property helper libraryA Property is typically a data item that is stored to NVRAMby the EC. Each of these data items has an index associatedwith it, known as the Property ID (PID). Properties may havevariable lengths, up to a max of WILCO_EC_PROPERTY_MAX_SIZEbytes. Properties can be simple integers, or they may be morecomplex binary data.This patch adds support for getting and setting properties.This will be useful for setting the charge algorithm and chargeschedules, which all use properties.Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;

            List of files:
            /linux-6.15/drivers/platform/chrome/wilco_ec/Makefile</description>
        <pubDate>Wed, 24 Apr 2019 16:56:50 +0000</pubDate>
        <dc:creator>Nick Crews &lt;ncrews@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>4c1ca625 - platform/chrome: wilco_ec: Add Boot on AC support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/platform/chrome/wilco_ec/Makefile#4c1ca625</link>
        <description>platform/chrome: wilco_ec: Add Boot on AC supportBoot on AC is a policy which makes the device boot from S5 when ACpower is connected. This is useful for users who want to run theirdevice headless or with a dock.Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;

            List of files:
            /linux-6.15/drivers/platform/chrome/wilco_ec/Makefile</description>
        <pubDate>Wed, 17 Apr 2019 01:20:47 +0000</pubDate>
        <dc:creator>Nick Crews &lt;ncrews@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>b787bb12 - platform/chrome: wilco_ec: Add support for raw commands in debugfs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/platform/chrome/wilco_ec/Makefile#b787bb12</link>
        <description>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&gt; echo 00 f0 38 00 03 00 &gt; rawThen read the result. &quot;12/21/18&quot; is in the middle of the response&gt; 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&gt; echo 00 f0 38 00 03 00 &gt; rawThen read the result. &quot;12/21/18&quot; is in the middle of the response&gt; 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 &lt;dlaurie@google.com&gt;Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;[Fix off-by-one error in wilco_ec/debugfs.c]Reported-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;

            List of files:
            /linux-6.15/drivers/platform/chrome/wilco_ec/Makefile</description>
        <pubDate>Sat, 09 Feb 2019 00:37:18 +0000</pubDate>
        <dc:creator>Nick Crews &lt;ncrews@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>7b3d4f44 - platform/chrome: Add new driver for Wilco EC</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/platform/chrome/wilco_ec/Makefile#7b3d4f44</link>
        <description>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 &lt;dlaurie@google.com&gt;Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;[Fix the sparse warning: symbol &apos;wilco_ec_transfer&apos; was not declared]Signed-off-by: Wei Yongjun &lt;weiyongjun1@huawei.com&gt;[Fix Kconfig dependencies for wilco_ec]Reported-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;

            List of files:
            /linux-6.15/drivers/platform/chrome/wilco_ec/Makefile</description>
        <pubDate>Sat, 09 Feb 2019 00:37:17 +0000</pubDate>
        <dc:creator>Nick Crews &lt;ncrews@chromium.org&gt;</dc:creator>
    </item>
</channel>
</rss>
