• Suman Anna's avatar
    bus: omap_l3_noc: Fix master id address decoding for OMAP5 · e7309c26
    Suman Anna authored
    The L3 Error handling on OMAP5 for the most part is very similar
    to that of OMAP4, and had leveraged common data structures and
    register layout definitions so far. Upon closer inspection, there
    are a few minor differences causing an incorrect decoding and
    reporting of the master NIU upon an error:
    
      1. The L3_TARG_STDERRLOG_MSTADDR.STDERRLOG_MSTADDR occupies
         11 bits on OMAP5 as against 8 bits on OMAP4, with the master
         NIU connID encoded in the 6 MSBs of the STDERRLOG_MSTADDR
         field.
      2. The CLK3 FlagMux component has 1 input source on OMAP4 and 3
         input sources on OMAP5. The common DEBUGSS source is at a
         different input on each SoC.
    
    Fix the above issues by using a OMAP5-specific compatible property
    and using SoC-specific data where there are differences.
    Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
    Acked-by: default avatarNishanth Menon <nm@ti.com>
    Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
    e7309c26