Duncan Laurie (dlaurie(a)chromium.org) just uploaded a new patch set to gerrit, which you can find at https://review.coreboot.org/18197
-gerrit
commit 63383a0e2c0986cb612043ab34200dbbbeb54a24
Author: Duncan Laurie <dlaurie(a)chromium.org>
Date: Sat Jan 21 15:42:26 2017 -0800
google/eve: Enable keyboard backlight in bootblock
Enable the keyboard backlight as early in boot as possible to
provide a indication that the BIOS is executing.
Since this is bootblock it can't use the convenience function
for checking for S3 resume so just read the PM1 value from the
SOC and check it directly.
Use a value of 75% for the current system as that is visible
without being full brightness.
BUG=chrome-os-partner:61464
TEST=boot on eve and check that keyboard backlight is enabled
as soon as the SOC starts booting
Change-Id: I9ac78e9c3913a2776943088f35142afe3ffef056
Signed-off-by: Duncan Laurie <dlaurie(a)chromium.org>
---
src/mainboard/google/eve/bootblock.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/src/mainboard/google/eve/bootblock.c b/src/mainboard/google/eve/bootblock.c
index 2c524f4..00d265c 100644
--- a/src/mainboard/google/eve/bootblock.c
+++ b/src/mainboard/google/eve/bootblock.c
@@ -14,9 +14,13 @@
* GNU General Public License for more details.
*/
+#include <arch/io.h>
#include <bootblock_common.h>
+#include <ec/google/chromeec/ec.h>
#include <gpio.h>
#include <soc/gpio.h>
+#include <soc/iomap.h>
+#include <soc/pm.h>
#include "gpio.h"
static void early_config_gpio(void)
@@ -26,5 +30,9 @@ static void early_config_gpio(void)
void bootblock_mainboard_init(void)
{
+ /* Turn on keyboard backlight to indicate we are booting */
+ if (acpi_sleep_from_pm1(inl(ACPI_BASE_ADDRESS + PM1_STS)) != ACPI_S3)
+ google_chromeec_kbbacklight(75);
+
early_config_gpio();
}
Duncan Laurie (dlaurie(a)chromium.org) just uploaded a new patch set to gerrit, which you can find at https://review.coreboot.org/18197
-gerrit
commit 0e07ce0ece7e6865fb5fa0e47e17fc84bcf3b83c
Author: Duncan Laurie <dlaurie(a)chromium.org>
Date: Sat Jan 21 15:42:26 2017 -0800
google/eve: Enable keyboard backlight in bootblock
Enable the keyboard backlight as early in boot as possible to
provide a indication that the BIOS is executing.
Since this is bootblock it can't use the convenience function
for checking for S3 resume so just read the PM1 value from the
SOC and check it directly.
Use a value of 75% for the current system as that is visible
without being full brightness.
BUG=chrome-os-partner:61464
TEST=boot on eve and check that keyboard backlight is enabled
as soon as the SOC starts booting
Change-Id: I9ac78e9c3913a2776943088f35142afe3ffef056
Signed-off-by: Duncan Laurie <dlaurie(a)chromium.org>
---
src/mainboard/google/eve/bootblock.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/src/mainboard/google/eve/bootblock.c b/src/mainboard/google/eve/bootblock.c
index 2c524f4..00d265c 100644
--- a/src/mainboard/google/eve/bootblock.c
+++ b/src/mainboard/google/eve/bootblock.c
@@ -14,9 +14,13 @@
* GNU General Public License for more details.
*/
+#include <arch/io.h>
#include <bootblock_common.h>
+#include <ec/google/chromeec/ec.h>
#include <gpio.h>
#include <soc/gpio.h>
+#include <soc/iomap.h>
+#include <soc/pm.h>
#include "gpio.h"
static void early_config_gpio(void)
@@ -26,5 +30,9 @@ static void early_config_gpio(void)
void bootblock_mainboard_init(void)
{
+ /* Turn on keyboard backlight to indicate we are booting */
+ if (acpi_sleep_from_pm1(inl(ACPI_BASE_ADDRESS + PM1_STS)) != ACPI_S3)
+ google_chromeec_kbbacklight(75);
+
early_config_gpio();
}
Paul Menzel (paulepanter(a)users.sourceforge.net) just uploaded a new patch set to gerrit, which you can find at https://review.coreboot.org/18196
-gerrit
commit 8d025e3fc7d8a836683259d336f01616508ebe08
Author: Paul Menzel <paulepanter(a)users.sourceforge.net>
Date: Fri Jan 20 23:29:21 2017 +0100
nvramcui: Declare variable outside for loop
Make the code C89 compatible, which doesn’t allow loop initial
declarations. Older compilers use C89 by default, so just declare the
variable outside.
Change-Id: I3c5a8109e66f7a25687f4e4b2c72718d74276e04
Signed-off-by: Paul Menzel <paulepanter(a)users.sourceforge.net>
---
payloads/nvramcui/nvramcui.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/payloads/nvramcui/nvramcui.c b/payloads/nvramcui/nvramcui.c
index 84e5536..97be9df 100644
--- a/payloads/nvramcui/nvramcui.c
+++ b/payloads/nvramcui/nvramcui.c
@@ -90,8 +90,9 @@ static void cmos_walk_options(struct cb_cmos_option_table *opttbl,
FIELD **fields, int numopts, int maxlength)
{
struct cb_cmos_entries *option = first_cmos_entry(opttbl);
+ int i;
- for (int i = 0; i < numopts; i++) {
+ for (i = 0; i < numopts; i++) {
while ((option->config == 'r') ||
(strcmp("check_sum", (char *)option->name) == 0)) {
option = next_cmos_entry(option);
@@ -173,6 +174,7 @@ static void cmos_walk_options(struct cb_cmos_option_table *opttbl,
int main(void)
{
int ch, done;
+ int i;
/* coreboot data structures */
lib_get_sysinfo();
@@ -268,7 +270,7 @@ int main(void)
endwin();
- for (int i = 0; i < numopts; i++) {
+ for (i = 0; i < numopts; i++) {
char *name = field_buffer(fields[2 * i], 0);
char *value = field_buffer(fields[2 * i + 1], 0);
char *ptr;
the following patch was just integrated into master:
commit ba32f0f91cfd79434b53d60a16d4c072fac384ec
Author: Aaron Durbin <adurbin(a)chromium.org>
Date: Fri Jan 20 14:10:26 2017 -0600
soc/intel/apollolake: correct GPIO 13 IRQ number
The define for GPIO_13_IRQ had the wrong IRQ number. It should
be 0x70 instead of 0x6f.
BUG=chrome-os-partner:62085
BRANCH=reef
TEST=touch controller doesn't indicate continuous interrupts
Change-Id: I3a0726db59fc1eb7736d348aecbf1082719f15b2
Signed-off-by: Aaron Durbin <adurbin(a)chromium.org>
Reviewed-on: https://review.coreboot.org/18190
Reviewed-by: Furquan Shaikh <furquan(a)google.com>
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter(a)users.sourceforge.net>
See https://review.coreboot.org/18190 for details.
-gerrit
the following patch was just integrated into master:
commit aa6482e88e2f553ee841284e5b44672eee85d3ec
Author: Aaron Durbin <adurbin(a)chromium.org>
Date: Fri Jan 20 14:03:50 2017 -0600
mainboard/google/reef: remove internal pullups on PP1800_S rail
The PP1800_S rail is turned off in S3. However, enabling internal
pullups on the pins which are connected to PP1800_S results in
leakage into the P1800_S rail. Fix this by disabling the internal
pullups on PP1800_S rail pins.
BUG=chrome-os-partner:61968
BRANCH=reef
TEST=measured leakage on PP1800_S rail. Gone with this patch.
Change-Id: I5ae92b31c1a633f59d425f4105b8db1c9c18c808
Signed-off-by: Aaron Duribn <adurbin(a)chromium.org>
Reviewed-on: https://review.coreboot.org/18189
Reviewed-by: Furquan Shaikh <furquan(a)google.com>
Tested-by: build bot (Jenkins)
Reviewed-by: Paul Menzel <paulepanter(a)users.sourceforge.net>
See https://review.coreboot.org/18189 for details.
-gerrit