[Skiboot] [PATCH 2/4] npu3: Add ibm, ioda2-npu3-phb to compatible property

[Reza Arbab]

Though they are currently identical to the OS, it may become necessary
to distinguish npu3 phbs from npu2 ones at some point. Add a unique
string to the compatible property.

Signed-off-by: Reza Arbab <arbab at linux.ibm.com>
---
 hw/npu3-nvlink.c | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/hw/npu3-nvlink.c b/hw/npu3-nvlink.c
index 6969b89b2488..0a185a1780be 100644
--- a/hw/npu3-nvlink.c
+++ b/hw/npu3-nvlink.c
@@ -1464,10 +1464,15 @@ static void npu3_dt_add_props(struct npu3 *npu)
 	dt_add_property_cells(dn, "clock-frequency", 0x200, 0);
 
 	dt_add_property_strings(dn, "device_type", "pciex");
-	/* To the OS, npu2 and npu3 are both ibm,ioda2-npu2-phb */
+
+	/*
+	 * To the OS, npu2 and npu3 are both ibm,ioda2-npu2-phb. The added
+	 * ibm,ioda3-npu3-phb allows for possible quirks.
+	 */
 	dt_add_property_strings(dn, "compatible",
 				"ibm,power9-npu-pciex",
-				"ibm,ioda2-npu2-phb");
+				"ibm,ioda2-npu2-phb",
+				"ibm,ioda2-npu3-phb");
 
 	dt_add_property_cells(dn, "ibm,phb-index",
 			      dt_prop_get_u32(npu->dt_node, "ibm,phb-index"));
-- 
1.8.3.1