From 3744dea27455045dd2190a1ba5f6622d78f30ccc Mon Sep 17 00:00:00 2001 From: deepakala-k Date: Mon, 5 Feb 2024 05:36:10 -0600 Subject: [PATCH] Use a unique class name for ody perv target If the compatible property and the class name for both proc processor and odyssey processor is same, then we need to check everywhere if that is a chiplet under a proc or under a odyssey. Having a unique name solves the issue. Signed-off-by: Deepa Karthikeyan --- libpdbg/p10_fapi_targets.c | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/libpdbg/p10_fapi_targets.c b/libpdbg/p10_fapi_targets.c index 4c7322ef6..5ba65f454 100644 --- a/libpdbg/p10_fapi_targets.c +++ b/libpdbg/p10_fapi_targets.c @@ -488,6 +488,17 @@ static struct chiplet p10_chiplet = { }; DECLARE_HW_UNIT(p10_chiplet); +static struct chiplet ody_chiplet = { + .target = { + .name = "POWER10 Ody Chiplet", + .compatible = "ibm,ody-chiplet", + .class = "ody_chiplet", + .translate = translate_cast(p10_chiplet_translate), + }, + .getring = p10_chiplet_getring, +}; +DECLARE_HW_UNIT(ody_chiplet); + static uint64_t no_translate(struct pdbg_target *target, uint64_t addr) { /* No translation performed */ @@ -658,6 +669,7 @@ static void register_p10_fapi_targets(void) pdbg_hwunit_register(PDBG_DEFAULT_BACKEND, &p10_pauc_hw_unit); pdbg_hwunit_register(PDBG_DEFAULT_BACKEND, &p10_pau_hw_unit); pdbg_hwunit_register(PDBG_DEFAULT_BACKEND, &p10_chiplet_hw_unit); + pdbg_hwunit_register(PDBG_DEFAULT_BACKEND, &ody_chiplet_hw_unit); pdbg_hwunit_register(PDBG_DEFAULT_BACKEND, &p10_fc_hw_unit); pdbg_hwunit_register(PDBG_DEFAULT_BACKEND, &p10_smpgroup_hw_unit); pdbg_hwunit_register(PDBG_DEFAULT_BACKEND, &p10_mem_port_hw_unit);