summaryrefslogtreecommitdiff
path: root/src/drivers/spi/sst.c
diff options
context:
space:
mode:
authorSubrata Banik <subratabanik@google.com>2024-09-09 12:54:47 +0530
committerSubrata Banik <subratabanik@google.com>2024-09-10 04:56:24 +0000
commit39d5ec73f0e1566742b5a09285b1dfd67fe91423 (patch)
tree2525a11327392ace2680a3e39b0b773a43c77fd1 /src/drivers/spi/sst.c
parent6e704e3ffcd61681eedb17366b6e686e596b4daf (diff)
mb/google/nissa/var/joxer: Use `DB_USB` to probe conn1 device
Joxer experienced error messages during developer mode entry due to failed USB-C1 probing. This patch adds the `DB_USB DB_1C` probe directive to the `conn1` device in the overridetree, ensuring USB-C1 is only probed when `FW_CONFIG` supports the applicable hardware SKU. This should resolve the error flood seen during dev mode entry on Joxer. BUG=b:364240631 TEST=Able to build and boot google/joxer to OS without any error. w/o this patch: send_packet: CrosEC result code 9 send_packet: CrosEC result code 3 Failed to get PD_MUX_INFO port1 ret:-3 update_all_tcss_ports_states: port C1: get_usb_pd_mux_info failed send_packet: CrosEC result code 9 send_packet: CrosEC result code 3 Failed to get PD_MUX_INFO port1 ret:-3 w/ this patch: No error reported during dev mode entry Change-Id: I8cdefa01409d5a8a75032f30dacde40057e064dd Signed-off-by: Subrata Banik <subratabanik@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/84255 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Dinesh Gehlot <digehlot@google.com> Reviewed-by: Eric Lai <ericllai@google.com>
Diffstat (limited to 'src/drivers/spi/sst.c')
0 files changed, 0 insertions, 0 deletions