[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130904175909.GB31541@atomide.com>
Date: Wed, 4 Sep 2013 10:59:09 -0700
From: Tony Lindgren <tony@...mide.com>
To: Haojian Zhuang <haojian.zhuang@...aro.org>
Cc: Stephen Warren <swarren@...dotorg.org>,
Mike Turquette <mturquette@...aro.org>,
Kevin Hilman <khilman@...aro.org>,
Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Matt Sealey <neko@...uhatsu.net>,
Stephen Boyd <sboyd@...eaurora.org>,
Tero Kristo <t-kristo@...com>,
Heiko Stübner <heiko@...ech.de>,
devicetree@...r.kernel.org
Subject: Re: [PATCH v4 5/5] clk: dt: binding for basic gate clock
* Haojian Zhuang <haojian.zhuang@...aro.org> [130903 20:11]:
>
> We can see that it'll try to find static mapping. What's the static mapping?
> If we define iotable in machine driver, we have the static mapping, just like
> debug_ll. If we parse everything from DTS file, it'll always get a new virtual
> address from vm area. So it always create a new page mapping even for one
> register.
I may not follow you here.. But it seems that you've missing something with
the static mapping: It's found based on the physical address. So if you
create static mappings for your SoC with iotable_init(), those mappings
will be available everywhere including drivers when you do ioremap().
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists