"ranges" is a standard property with common parsing functions. Users
shouldn't be implementing their own parsing of it. Refactor the FSL RapidIO
"ranges" parsing to use of_range_to_resource() instead.

Signed-off-by: Rob Herring <r...@kernel.org>
---
 arch/powerpc/sysdev/fsl_soc.c | 16 ++++------------
 1 file changed, 4 insertions(+), 12 deletions(-)

diff --git a/arch/powerpc/sysdev/fsl_soc.c b/arch/powerpc/sysdev/fsl_soc.c
index 6ebbbca41065..68709743450e 100644
--- a/arch/powerpc/sysdev/fsl_soc.c
+++ b/arch/powerpc/sysdev/fsl_soc.c
@@ -51,18 +51,10 @@ phys_addr_t get_immrbase(void)
 
        soc = of_find_node_by_type(NULL, "soc");
        if (soc) {
-               int size;
-               u32 naddr;
-               const __be32 *prop = of_get_property(soc, "#address-cells", 
&size);
-
-               if (prop && size == 4)
-                       naddr = be32_to_cpup(prop);
-               else
-                       naddr = 2;
-
-               prop = of_get_property(soc, "ranges", &size);
-               if (prop)
-                       immrbase = of_translate_address(soc, prop + naddr);
+               struct resource res;
+
+               if (!of_range_to_resource(soc, 0, &res))
+                       immrbase = res.start;
 
                of_node_put(soc);
        }
-- 
2.39.2

Reply via email to