bus: omap_l3_noc: use of_match_data to pick up SoC information
authorSricharan R <r.sricharan@ti.com>
Tue, 26 Nov 2013 13:38:23 +0000 (07:38 -0600)
committerNishanth Menon <nm@ti.com>
Mon, 5 May 2014 19:33:33 +0000 (14:33 -0500)
commit0659452dd2b2602058b80cfdcc673e98f2a67184
tree388e6d8d848f72e2f61466169bec7057461d1e89
parent3340d739f8e1273abd408c59ad1843ea2ac35566
bus: omap_l3_noc: use of_match_data to pick up SoC information

DRA7xx SoC has the same l3-noc interconnect ip (as OMAP4 and OMAP5), but
AM437x SoC has just 2 modules instead of 3 which other SoCs have.

So, stop using direct access of array indices and use of->match data and
simplify implementation to benefit future usage.

While at it, rename a few very generic variables to make them omap
specific. This helps us differentiate from DRA7 and AM43xx data in the
future.

NOTE: None of the platforms that use omap_l3_noc are non-device tree
anymore. So, it is safe to assume OF match here.

Signed-off-by: Sricharan R <r.sricharan@ti.com>
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
[nm@ti.com: split, refactor and optimize logic]
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>
drivers/bus/omap_l3_noc.c
drivers/bus/omap_l3_noc.h