aboutsummaryrefslogtreecommitdiff
path: root/doc/opal-api
diff options
context:
space:
mode:
authorStewart Smith <stewart@linux.ibm.com>2019-06-03 14:50:50 +1000
committerStewart Smith <stewart@linux.ibm.com>2019-06-04 10:29:05 +1000
commit16b7ae64103797b0ecab1dbb7c45df23b14810b9 (patch)
treea3330ee950c4f93c9c7afe278cf1425f66366b95 /doc/opal-api
parent9cae036fafea468219892406a846639f2715854d (diff)
downloadskiboot-16b7ae64103797b0ecab1dbb7c45df23b14810b9.zip
skiboot-16b7ae64103797b0ecab1dbb7c45df23b14810b9.tar.gz
skiboot-16b7ae64103797b0ecab1dbb7c45df23b14810b9.tar.bz2
Remove POWER7 and POWER7+ support
It's been a good long while since either OPAL POWER7 user touched a machine, and even longer since they'd have been okay using an old version rather than tracking master. There's also been no testing of OPAL on POWER7 systems for an awfully long time, so it's pretty safe to assume that it's very much bitrotted. It also saves a whole 14kb of xz compressed payload space. Signed-off-by: Stewart Smith <stewart@linux.ibm.com> Enthusiasticly-Acked-by: Oliver O'Halloran <oohall@gmail.com> Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
Diffstat (limited to 'doc/opal-api')
-rw-r--r--doc/opal-api/opal-pci-get-hub-diag-data-50.rst55
1 files changed, 4 insertions, 51 deletions
diff --git a/doc/opal-api/opal-pci-get-hub-diag-data-50.rst b/doc/opal-api/opal-pci-get-hub-diag-data-50.rst
index e7b2584..7ee9806 100644
--- a/doc/opal-api/opal-pci-get-hub-diag-data-50.rst
+++ b/doc/opal-api/opal-pci-get-hub-diag-data-50.rst
@@ -7,61 +7,14 @@ OPAL_PCI_GET_HUB_DIAG_DATA
#define OPAL_PCI_GET_HUB_DIAG_DATA 50
- enum {
- OPAL_P7IOC_DIAG_TYPE_NONE = 0,
- OPAL_P7IOC_DIAG_TYPE_RGC = 1,
- OPAL_P7IOC_DIAG_TYPE_BI = 2,
- OPAL_P7IOC_DIAG_TYPE_CI = 3,
- OPAL_P7IOC_DIAG_TYPE_MISC = 4,
- OPAL_P7IOC_DIAG_TYPE_I2C = 5,
- OPAL_P7IOC_DIAG_TYPE_LAST = 6
- };
-
- struct OpalIoP7IOCErrorData {
- __be16 type;
-
- /* GEM */
- __be64 gemXfir;
- __be64 gemRfir;
- __be64 gemRirqfir;
- __be64 gemMask;
- __be64 gemRwof;
-
- /* LEM */
- __be64 lemFir;
- __be64 lemErrMask;
- __be64 lemAction0;
- __be64 lemAction1;
- __be64 lemWof;
-
- union {
- struct OpalIoP7IOCRgcErrorData {
- __be64 rgcStatus; /* 3E1C10 */
- __be64 rgcLdcp; /* 3E1C18 */
- }rgc;
- struct OpalIoP7IOCBiErrorData {
- __be64 biLdcp0; /* 3C0100, 3C0118 */
- __be64 biLdcp1; /* 3C0108, 3C0120 */
- __be64 biLdcp2; /* 3C0110, 3C0128 */
- __be64 biFenceStatus; /* 3C0130, 3C0130 */
-
- uint8_t biDownbound; /* BI Downbound or Upbound */
- }bi;
- struct OpalIoP7IOCCiErrorData {
- __be64 ciPortStatus; /* 3Dn008 */
- __be64 ciPortLdcp; /* 3Dn010 */
-
- uint8_t ciPort; /* Index of CI port: 0/1 */
- }ci;
- };
- };
-
int64_t opal_pci_get_hub_diag_data(uint64_t hub_id, void *diag_buffer, uint64_t diag_buffer_len);
-Fetch diagnostic data for an IO hub. Currently, this is only implemented for
-p7ioc, which is specific to POWER7, something that was only ever available
+Fetch diagnostic data for an IO hub. This was only implemented for hardware
+specific to POWER7 systems, something that was only ever available
internally to IBM for development purposes.
+It is currently not used.
+
If :ref:`OPAL_PCI_NEXT_ERROR` error type is `OPAL_EEH_IOC_ERROR` and severity
is `OPAL_EEH_SEV_INF`, then the OS should call :ref:`OPAL_PCI_GET_HUB_DIAG_DATA`
to retreive diagnostic data to log appropriately.