Commit 517c2757 authored by Michael Neuling's avatar Michael Neuling Committed by Michael Ellerman

powerpc/powernv: Fix XSCOM address mangling for form 1 indirect

POWER9 adds form 1 scoms. The form of the indirection is specified in
the top nibble of the scom address.

Currently we do some (ugly) bit mangling so that we can fit a 64 bit
scom address into the debugfs interface. The current code only shifts
the top bit (indirect bit).

This patch changes it to shift the whole top nibble so that the form
of the indirection is also shifted.

This patch is backwards compatible with older scoms.

(This change isn't required in the arch/powerpc/platforms/powernv/opal-prd.c
scom interface as it passes the whole 64bit scom address without any bit
mangling)
Signed-off-by: default avatarMichael Neuling <mikey@neuling.org>
Signed-off-by: default avatarMichael Ellerman <mpe@ellerman.id.au>
parent c3a08e93
...@@ -73,25 +73,32 @@ static int opal_xscom_err_xlate(int64_t rc) ...@@ -73,25 +73,32 @@ static int opal_xscom_err_xlate(int64_t rc)
static u64 opal_scom_unmangle(u64 addr) static u64 opal_scom_unmangle(u64 addr)
{ {
u64 tmp;
/* /*
* XSCOM indirect addresses have the top bit set. Additionally * XSCOM addresses use the top nibble to set indirect mode and
* the rest of the top 3 nibbles is always 0. * its form. Bits 4-11 are always 0.
* *
* Because the debugfs interface uses signed offsets and shifts * Because the debugfs interface uses signed offsets and shifts
* the address left by 3, we basically cannot use the top 4 bits * the address left by 3, we basically cannot use the top 4 bits
* of the 64-bit address, and thus cannot use the indirect bit. * of the 64-bit address, and thus cannot use the indirect bit.
* *
* To deal with that, we support the indirect bit being in bit * To deal with that, we support the indirect bits being in
* 4 (IBM notation) instead of bit 0 in this API, we do the * bits 4-7 (IBM notation) instead of bit 0-3 in this API, we
* conversion here. To leave room for further xscom address * do the conversion here.
* expansion, we only clear out the top byte
* *
* For in-kernel use, we also support the real indirect bit, so * For in-kernel use, we don't need to do this mangling. In
* we test for any of the top 5 bits * kernel won't have bits 4-7 set.
* *
* So:
* debugfs will always set 0-3 = 0 and clear 4-7
* kernel will always clear 0-3 = 0 and set 4-7
*/ */
if (addr & (0x1full << 59)) tmp = addr;
addr = (addr & ~(0xffull << 56)) | (1ull << 63); tmp &= 0x0f00000000000000;
addr &= 0xf0ffffffffffffff;
addr |= tmp << 4;
return addr; return addr;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment