On 01/02/2013 11:11 PM, Prashant Gaikwad wrote:On Thursday 03 January 2013 03:30 AM, Stephen Warren wrote:OK. It sounds like we need a true APB MISC driver then, to abstract theOn 12/27/2012 07:47 AM, Prashant Gaikwad wrote:apbmisc reg for Tegra30 can be divided into following entries:APB misc contains multiple registers required by different modulesI don't see a DT binding document that describes what
such as CAR.
nvidia,tegra30-apbmisc means. Also, the register range for this new node
overlaps that for the pinmux node, so they can't both "request" their
register region. You may need multiple entries in the apbmisc reg
property to avoid this.
jtag configuration registers
pull_up/pull_down control registers
vclk control registers
chip id revision registers
pad control registers
This list is not same for Tegra20 and Tegra30.
differences; the clock driver really shouldn't be touching the APB MISC
registers in all likelihood, unless a subset of the sections you mention
above are truly dedicated to clock functionality.
ORThe pinmux controller doesn't have a reg entry for the chip ID register.
another way is to add chip id revision register region to CAR node as
done for pinmux node and remove apb misc node.
I don't understand what you mean here.
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html