summaryrefslogtreecommitdiff
path: root/src/device/mdio.c
diff options
context:
space:
mode:
authorShelley Chen <shchen@google.com>2024-02-13 12:55:56 -0800
committerShelley Chen <shchen@google.com>2024-02-16 16:58:55 +0000
commitb54045fcba32da0972a5dff93699feaa650aaa03 (patch)
tree973443ec23e2617a93e0250c8bd17967d8c7e266 /src/device/mdio.c
parentb76ff876eabf624e01368d0f4931adae96e51b0f (diff)
mb/google/brox: Set PCH_EC_PCH_INT_ODL pin as IOAPIC
Setting the EC interrupt GPIO as an APIC is able to solve many problems that we are currently seeing: 1. Routing through the APIC make the IRQ# associated with this pin unavailable to claim for other devices in the kernel. This is causing EC interrupts to not work. 2. Since EC interrupt are not working, we are not able to flash the EC from the DUT. 3. Also, the GPI_INT configuration does not allow us to set the polarity of the GPIO, which means that it is by default set as active high. As a result, we are seeing an excessive number of host command interrupts to the EC. This disappears when we change the configuration to APIC and set the polarity as INVERT. BUG=b:319129926,b:324707182 BRANCH=None TEST=1. After boot up, check if ec_cros_lpcs driver was successfully registered. Look for the following string: "cros_ec_lpcs GOOG0004:00: Chrome EC device registered" 2. Make sure can flash the EC image from the DUT 3. Make sure EC console is not getting continuous stream of host commands. Change-Id: I74bff88d2ddbaf1f4b085c31d582bd66e18c438a Signed-off-by: Shelley Chen <shchen@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/80467 Reviewed-by: Karthik Ramasubramanian <kramasub@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Ashish Kumar Mishra <ashish.k.mishra@intel.corp-partner.google.com>
Diffstat (limited to 'src/device/mdio.c')
0 files changed, 0 insertions, 0 deletions