<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-dev/drivers/platform/chrome/wilco_ec/core.c, branch linus/master</title>
<subtitle>Linux kernel development work - see feature branches</subtitle>
<id>https://git.zx2c4.com/linux-dev/atom/drivers/platform/chrome/wilco_ec/core.c?h=linus%2Fmaster</id>
<link rel='self' href='https://git.zx2c4.com/linux-dev/atom/drivers/platform/chrome/wilco_ec/core.c?h=linus%2Fmaster'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/'/>
<updated>2020-01-22T09:10:44Z</updated>
<entry>
<title>platform/chrome: wilco_ec: Add newlines to printks</title>
<updated>2020-01-22T09:10:44Z</updated>
<author>
<name>Stephen Boyd</name>
<email>swboyd@chromium.org</email>
</author>
<published>2020-01-22T00:40:32Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=a532149c992eed9f8523d4ed5960b0068f213cd7'/>
<id>urn:sha1:a532149c992eed9f8523d4ed5960b0068f213cd7</id>
<content type='text'>
printk messages all require newlines, or it looks very odd in the log
when messages are not on different lines. Add them.

Cc: Nick Crews &lt;ncrews@chromium.org&gt;
Cc: Daniel Campello &lt;campello@chromium.org&gt;
Cc: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;
Signed-off-by: Stephen Boyd &lt;swboyd@chromium.org&gt;
Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;
</content>
</entry>
<entry>
<title>platform/chrome: wilco_ec: Fix unregistration order</title>
<updated>2020-01-10T10:42:51Z</updated>
<author>
<name>Daniel Campello</name>
<email>campello@chromium.org</email>
</author>
<published>2020-01-08T16:35:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=ffd7263e63fe80a39c1222a6d68e05095ed04d03'/>
<id>urn:sha1:ffd7263e63fe80a39c1222a6d68e05095ed04d03</id>
<content type='text'>
The unregistration should happen in the opposite order of
the registration, so change it accordingly.

No real issue has been noticed, but it is good practice to
keep the correct unregistration order.

Signed-off-by: Daniel Campello &lt;campello@chromium.org&gt;
Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;
</content>
</entry>
<entry>
<title>platform/chrome: wilco_ec: Add keyboard backlight LED support</title>
<updated>2019-11-19T17:12:19Z</updated>
<author>
<name>Daniel Campello</name>
<email>campello@chromium.org</email>
</author>
<published>2019-11-06T16:33:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=119a3cb6d687259f2be333351c1c5d634204e68b'/>
<id>urn:sha1:119a3cb6d687259f2be333351c1c5d634204e68b</id>
<content type='text'>
The EC is in charge of controlling the keyboard backlight on
the Wilco platform. We expose a standard LED class device
named 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 &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;
</content>
</entry>
<entry>
<title>platform/chrome: wilco_ec: Add charging config driver</title>
<updated>2019-11-19T17:12:19Z</updated>
<author>
<name>Nick Crews</name>
<email>ncrews@chromium.org</email>
</author>
<published>2019-10-24T22:28:05Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=3c4d77b68928df6c2bf07f4c3ba8e5d5e490bf4e'/>
<id>urn:sha1:3c4d77b68928df6c2bf07f4c3ba8e5d5e490bf4e</id>
<content type='text'>
Add a device to control the charging algorithm used on Wilco devices,
which will be picked up by the drivers/power/supply/wilco-charger.c
driver. See Documentation/ABI/testing/sysfs-class-power-wilco for the
userspace interface and other info.

Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;
Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;
</content>
</entry>
<entry>
<title>platform/chrome: wilco_ec: Add telemetry char device interface</title>
<updated>2019-06-05T08:14:50Z</updated>
<author>
<name>Nick Crews</name>
<email>ncrews@chromium.org</email>
</author>
<published>2019-05-21T19:20:45Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=1210d1e6bad1e7ccccb19627b880a50d7c15dd51'/>
<id>urn:sha1:1210d1e6bad1e7ccccb19627b880a50d7c15dd51</id>
<content type='text'>
The Wilco Embedded Controller is able to send telemetry data
which is useful for enterprise applications. A daemon running on
the 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 is
verified by the driver to ensure that it is performing only one
of the whitelisted commands, and that no extraneous data is
being transmitted to the EC. The response is passed directly
back to the reader with no modification.

The character device will appear as /dev/wilco_telemN, where N
is some small non-negative integer, starting with 0. Only one
process may have the file descriptor open at a time. The calling
userspace program needs to keep the device file descriptor open
between the calls to write() and read() in order to preserve the
response. Up to 32 bytes will be available for reading.

For testing purposes, try requesting the EC's firmware build
date, by sending the WILCO_EC_TELEM_GET_VERSION command with
argument index=3. i.e. write [0x38, 0x00, 0x03]
to the device node. An ASCII string of the build date is
returned.

Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;
Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;
</content>
</entry>
<entry>
<title>platform/chrome: wilco_ec: Remove 256 byte transfers</title>
<updated>2019-05-20T08:18:10Z</updated>
<author>
<name>Nick Crews</name>
<email>ncrews@chromium.org</email>
</author>
<published>2019-05-08T21:38:09Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=2ad1f7a91449de48d4bd5d1ec361ba7bb9026505'/>
<id>urn:sha1:2ad1f7a91449de48d4bd5d1ec361ba7bb9026505</id>
<content type='text'>
The 0xF6 command, intended to send and receive 256 byte payloads to
and from the EC, is not needed. The 0xF5 command for 32 byte
payloads is sufficient. This patch removes support for the 0xF6
command and 256 byte payloads.

Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;
Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;
</content>
</entry>
<entry>
<title>platform/chrome: wilco_ec: Add Boot on AC support</title>
<updated>2019-05-20T08:18:09Z</updated>
<author>
<name>Nick Crews</name>
<email>ncrews@chromium.org</email>
</author>
<published>2019-04-17T01:20:47Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=4c1ca625c622b7a9f04c2949fd1ffdc6effa86de'/>
<id>urn:sha1:4c1ca625c622b7a9f04c2949fd1ffdc6effa86de</id>
<content type='text'>
Boot on AC is a policy which makes the device boot from S5 when AC
power is connected. This is useful for users who want to run their
device 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;
</content>
</entry>
<entry>
<title>platform/chrome: wilco_ec: Add RTC driver</title>
<updated>2019-02-21T20:36:53Z</updated>
<author>
<name>Nick Crews</name>
<email>ncrews@chromium.org</email>
</author>
<published>2019-02-09T00:37:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=0d2f2a3da1f2a9ebeb66bb03073dd149fccf1bdd'/>
<id>urn:sha1:0d2f2a3da1f2a9ebeb66bb03073dd149fccf1bdd</id>
<content type='text'>
This Embedded Controller has an internal RTC that is exposed
as a standard RTC class driver with read/write functionality.

The driver is added to the drivers/rtc/ so that the maintainer of that
directory will be able to comment on this change, as that maintainer is
the expert on this system. In addition, the driver code is called
indirectly after a corresponding device is registered from core.c,
as opposed to core.c registering the driver callbacks directly.

To test:
&gt; hwclock --show --rtc /dev/rtc1
2007-12-31 16:01:20.460959-08:00
&gt; hwclock --systohc --rtc /dev/rtc1
&gt; hwclock --show --rtc /dev/rtc1
2018-11-29 17:08:00.780793-08:00

&gt; hwclock --show --rtc /dev/rtc1
2007-12-31 16:01:20.460959-08:00
&gt; hwclock --systohc --rtc /dev/rtc1
&gt; hwclock --show --rtc /dev/rtc1
2018-11-29 17:08:00.780793-08:00

Signed-off-by: Duncan Laurie &lt;dlaurie@google.com&gt;
Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;
Acked-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
[Fix the sparse warning: symbol 'wilco_ec_rtc_read/write' was not declared]
Signed-off-by: Wei Yongjun &lt;weiyongjun1@huawei.com&gt;
Signed-off-by: Enric Balletbo i Serra &lt;enric.balletbo@collabora.com&gt;
</content>
</entry>
<entry>
<title>platform/chrome: wilco_ec: Add support for raw commands in debugfs</title>
<updated>2019-02-21T20:36:21Z</updated>
<author>
<name>Nick Crews</name>
<email>ncrews@chromium.org</email>
</author>
<published>2019-02-09T00:37:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=b787bb126cbcd73754bcbc055ae9f804ac576e4a'/>
<id>urn:sha1:b787bb126cbcd73754bcbc055ae9f804ac576e4a</id>
<content type='text'>
Add a debugfs attribute that allows sending raw commands to the EC.
This is useful for development and debug but should not be enabled
in a production environment.

To test:
Get the EC firmware build date
First send the request command
&gt; echo 00 f0 38 00 03 00 &gt; raw
Then read the result. "12/21/18" is in the middle of the response
&gt; cat raw
00 31 32 2f 32 31 2f 31 38 00 00 0f 01 00 01 00  .12/21/18.......

Get the EC firmware build date
First send the request command
&gt; echo 00 f0 38 00 03 00 &gt; raw
Then read the result. "12/21/18" is in the middle of the response
&gt; cat raw
00 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;
</content>
</entry>
<entry>
<title>platform/chrome: Add new driver for Wilco EC</title>
<updated>2019-02-21T20:35:59Z</updated>
<author>
<name>Nick Crews</name>
<email>ncrews@chromium.org</email>
</author>
<published>2019-02-09T00:37:17Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=7b3d4f44abf0e7a1ba762c8a9c99a8b39ee0c8b1'/>
<id>urn:sha1:7b3d4f44abf0e7a1ba762c8a9c99a8b39ee0c8b1</id>
<content type='text'>
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 &lt;dlaurie@google.com&gt;
Signed-off-by: Nick Crews &lt;ncrews@chromium.org&gt;
[Fix the sparse warning: symbol 'wilco_ec_transfer' 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;
</content>
</entry>
</feed>
