Re: [PATCH v4 2/2] platform/chrome: wilco_ec: Add h1_gpio status to debugfs

2019-04-15 Thread Enric Balletbo i Serra
On 12/4/19 20:14, Nick Crews wrote: > As part of Chrome OS's FAFT (Fully Automated Firmware Testing) > tests, we need to ensure that the H1 chip is properly setting > some GPIO lines. The h1_gpio attribute exposes the state > of the lines: > - ENTRY_TO_FACT_MODE in BIT(0) > - SPI_CHROME_SEL in B

[PATCH v4 2/2] platform/chrome: wilco_ec: Add h1_gpio status to debugfs

2019-04-12 Thread Nick Crews
As part of Chrome OS's FAFT (Fully Automated Firmware Testing) tests, we need to ensure that the H1 chip is properly setting some GPIO lines. The h1_gpio attribute exposes the state of the lines: - ENTRY_TO_FACT_MODE in BIT(0) - SPI_CHROME_SEL in BIT(1) There are two reasons that I am exposing thi