• Koby Elbaz's avatar
    habanalabs/gaudi: fix incorrect MME offset calculation · 70d25e96
    Koby Elbaz authored
    Once FW raised an event following a MME2 QMAN error, the driver should
    have gone to the corresponding status registers, trying to gather more
    info on the error, yet it was accidentally accessing MME1 QMAN address
    space.
    
    Generally, we have x4 MMEs, while 0 & 2 are marked MASTER, and
    1 & 3 are marked SLAVE. The former can be addressed, yet addressing
    the latter is considered an access violation, and will result in a
    hung system, which is what unintentionally happened above.
    Note that this cannot happen in a secured system, since these registers
    are protected with range registers.
    Signed-off-by: default avatarKoby Elbaz <kelbaz@habana.ai>
    Reviewed-by: default avatarOded Gabbay <ogabbay@kernel.org>
    Signed-off-by: default avatarOded Gabbay <ogabbay@kernel.org>
    70d25e96
gaudi.c 277 KB