Blackbird™ Linux sources for OpenPOWER https://git.raptorcs.com/git/blackbird-op-linux/atom?h=master 2020-01-22T09:10:44+00:00 2020-01-22T09:10:44+00:00 Stephen Boyd swboyd@chromium.org 2020-01-22T01:24:34+00:00 urn:sha1:60fb8a8e93ca94e752a509bb3f6f74068ccca739 Enable this Kconfig on COMPILE_TEST enabled configs so we can get more build coverage. Signed-off-by: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> 2020-01-22T09:10:44+00:00 Stephen Boyd swboyd@chromium.org 2020-01-22T00:40:32+00:00 urn:sha1:a532149c992eed9f8523d4ed5960b0068f213cd7 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 <ncrews@chromium.org> Cc: Daniel Campello <campello@chromium.org> Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com> Signed-off-by: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> 2020-01-10T23:08:35+00:00 Benson Leung bleung@chromium.org 2020-01-10T23:06:16+00:00 urn:sha1:3b0bfd33ffb21dff369afaa8b1e4a6f25407ff38 Merge dfb9a8857f4d platform/chrome: wilco_ec: Fix keyboard backlight probing from chrome-platform-5.5-fixes into chrome-platform-5.6 destined branch. Signed-off-by: Benson Leung <bleung@chromium.org> 2020-01-10T22:57:58+00:00 Daniel Campello campello@chromium.org 2020-01-07T18:24:21+00:00 urn:sha1:dfb9a8857f4decbba8c2206e8877e1d741ee1b47 The EC on the Wilco platform responds with 0xFF to commands related to the keyboard backlight on the absence of a keyboard backlight module. This change allows the EC driver to continue loading even if the backlight module is not present. Fixes: 119a3cb6d687 ("platform/chrome: wilco_ec: Add keyboard backlight LED support") Signed-off-by: Daniel Campello <campello@chromium.org> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> Signed-off-by: Benson Leung <bleung@chromium.org> 2020-01-10T10:42:51+00:00 Daniel Campello campello@chromium.org 2020-01-08T16:35:20+00:00 urn:sha1:ffd7263e63fe80a39c1222a6d68e05095ed04d03 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 <campello@chromium.org> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> 2019-12-02T11:14:42+00:00 Wen Yang wenyang@linux.alibaba.com 2019-11-30T13:08:42+00:00 urn:sha1:856a0a6e2d09d31fd8f00cc1fc6645196a509d56 This is caused by dereferencing 'dev_data' after put_device() in the telem_device_remove() function. This patch just moves the put_device() down a bit to avoid this issue. Fixes: 1210d1e6bad1 ("platform/chrome: wilco_ec: Add telemetry char device interface") Signed-off-by: Wen Yang <wenyang@linux.alibaba.com> Cc: Benson Leung <bleung@chromium.org> Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com> Cc: Nick Crews <ncrews@chromium.org> Cc: linux-kernel@vger.kernel.org Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> 2019-11-19T17:12:19+00:00 Daniel Campello campello@chromium.org 2019-11-06T16:33:19+00:00 urn:sha1:119a3cb6d687259f2be333351c1c5d634204e68b 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 <ncrews@chromium.org> Signed-off-by: Daniel Campello <campello@chromium.org> Reviewed-by: Daniel Campello <campello@chromium.org> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> 2019-11-19T17:12:19+00:00 Nick Crews ncrews@chromium.org 2019-10-24T22:28:05+00:00 urn:sha1:3c4d77b68928df6c2bf07f4c3ba8e5d5e490bf4e 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 <ncrews@chromium.org> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> 2019-10-11T10:12:04+00:00 Daniel Campello campello@chromium.org 2019-10-08T22:18:30+00:00 urn:sha1:fdf0fe2df3e32103dc87d4cd4d3be3653c0fd30d USB PowerShare is a policy which affects charging via the special USB PowerShare port (marked with a small lightning bolt or battery icon) when in low power states: - In S0, the port will always provide power. - In S0ix, if usb_charge is enabled, then power will be supplied to the port when on AC or if battery is > 50%. Else no power is supplied. - In S5, if usb_charge is enabled, then power will be supplied to the port when on AC. Else no power is supplied. Signed-off-by: Daniel Campello <campello@chromium.org> Signed-off-by: Nick Crews <ncrews@chromium.org> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> 2019-10-01T16:07:28+00:00 Daniel Campello campello@chromium.org 2019-09-24T20:37:16+00:00 urn:sha1:e6679fd1e2fc253f62bbea13b76d9b6a8f90c68e This change introduces a new debugfs file 'test_event' that when written to causes the EC to generate a test event. This adds a second sub cmd for the test event, and pulls out send_ec_cmd to be a common helper between h1_gpio_get and test_event_set. Signed-off-by: Daniel Campello <campello@chromium.org> Reviewed-by: Benson Leung <bleung@chromium.org> Reviewed-by: Nick Crews <ncrews@chromium.org> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>