diff options
| author | Madhavan Srinivasan <maddy@linux.vnet.ibm.com> | 2017-04-04 13:04:54 +0530 |
|---|---|---|
| committer | Madhavan Srinivasan <maddy@linux.vnet.ibm.com> | 2017-04-04 13:04:54 +0530 |
| commit | 20ad051cbe044e4b1517ca484d23f924370ffc3c (patch) | |
| tree | 1a3a4f3666cab03cd3f87c855d26228c370f2aa1 | |
| parent | 1f4b1be62e9c3831739145cccd5435c1bfe2350a (diff) | |
| download | ima-catalog-20ad051cbe044e4b1517ca484d23f924370ffc3c.tar.gz ima-catalog-20ad051cbe044e4b1517ca484d23f924370ffc3c.zip | |
Fix the nx device node in power9
Microcode presents the list of possible nest units in the
"Unit Availability Matrix" vector of the control block.
Hypervisor need to look at this vector to know enabled units
in the system. And the UAV vector only list "nx" and not "nx0",
hence make the changes here.
| -rw-r--r-- | 81E00612.4E0100.dts | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/81E00612.4E0100.dts b/81E00612.4E0100.dts index b5d4f07..0e8ea9a 100644 --- a/81E00612.4E0100.dts +++ b/81E00612.4E0100.dts @@ -657,7 +657,7 @@ NEST_NX: nest-nx-events { desc = "One of the master engines (read" ; }; }; - nx0 { + nx { compatible = "ibm,imc-counters-nest"; events-prefix = "PM_NX_"; reg = <0xd18 0x8>; |
