summaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorNishanth Menon <nm@ti.com>2014-04-16 11:01:02 -0500
committerNishanth Menon <nm@ti.com>2014-05-05 14:33:46 -0500
commitd4d8819e205854cc102e366f30b8eadd60a58e97 (patch)
tree410e8709f090a439c50012b6fec0bfefcf780553 /firmware
parent97708c08c9955306742872ff7f2e47faec864ee7 (diff)
downloadop-kernel-dev-d4d8819e205854cc102e366f30b8eadd60a58e97.zip
op-kernel-dev-d4d8819e205854cc102e366f30b8eadd60a58e97.tar.gz
bus: omap_l3_noc: fix masterid detection
As per Documentation (OMAP4+), then masterid is infact encoded as follows: "L3_TARG_STDERRLOG_MSTADDR[7:0] STDERRLOG_MSTADDR stores the NTTP master address. The master address is the concatenation of Prefix & Initiator ConnID. It is defined on 8 bits. The 6 MSBs are used to distinguish the different initiators." So, when we matchup currently with the master ID list, we never get a proper match other than when MPU is the master (thanks to 0). Now, on other platforms such as AM437x, this tends to be bits[5:0]. Fix this by using the relevant 6MSBits to identify the master ID for standard and custom errors. Reported-by: Darren Etheridge <detheridge@ti.com> Signed-off-by: Nishanth Menon <nm@ti.com> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Acked-by: Peter Ujfalusi <peter.ujfalusi@ti.com> Tested-by: Darren Etheridge <detheridge@ti.com> Tested-by: Sekhar Nori <nsekhar@ti.com>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud