diff options
| author | Oliver O'Halloran <oohall@gmail.com> | 2019-10-18 15:30:00 +1100 |
|---|---|---|
| committer | Oliver O'Halloran <oohall@gmail.com> | 2019-11-04 14:58:40 +1100 |
| commit | 6cf9ace9d69dcb5c37b328625132bc5c9624b778 (patch) | |
| tree | 4d271361769941bdc60c8bac50d95d0f53f11c8f /core/mem_region.c | |
| parent | b8bac56ad6b3f78623351ba9bbc211684ef8031a (diff) | |
| download | skiboot-6cf9ace9d69dcb5c37b328625132bc5c9624b778.zip skiboot-6cf9ace9d69dcb5c37b328625132bc5c9624b778.tar.gz skiboot-6cf9ace9d69dcb5c37b328625132bc5c9624b778.tar.bz2 | |
hw/port80: Squash No SYNC error
On Aspeed BMCs can be configured to route LPC IO address 0x80 to a GPIO
port. Some systems use this to implement a boot progress indicator, but
not all of them.
There's no easy way to tell if this has been setup or not and if it
hasn't we get an LPC SYNC no-response error from out LPC master. When we
reach Linux and enable interrupts this results in this spurious error
being printed:
LPC[000]: Got SYNC no-response error. Error address reg: 0xd0010082
lpc_probe_write() is intended to catch situations where the peripherial
being written to might not be configured, so use that instead of
lpc_outb() to squash the error.
Cc: Ranga <stewart@flamingspork.com>
Cc: Andrew Jeffery <andrew@aj.id.au>
Acked-by: Andrew Jeffery <andrew@aj.id.au>
[oliver: fixed the test]
Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
Diffstat (limited to 'core/mem_region.c')
0 files changed, 0 insertions, 0 deletions