Thread (3 messages) flat view 3 messages, 2 authors, 2012-01-20

Re: [PATCH v4 06/20] tegra: fdt: Add Tegra2x device tree file from kernel

From: Simon Glass <sjg@chromium.org>
Date: 2012-01-19 23:51:07
Also in: u-boot

Hi Stephen,

On Wed, Jan 18, 2012 at 2:24 PM, Stephen Warren [off-list ref] wrote:
On 01/11/2012 09:32 PM, Simon Glass wrote:
quoted
This was taken from commit b48c54e2 at:
git://git.kernel.org/pub/scm/linux/kernel/git/olof/tegra.git

config.mk is updated to provide this file to boards through the
built-in mechanism:

/include/ ARCH_CPU_DTS

Signed-off-by: Simon Glass <sjg@chromium.org>
quoted
diff --git a/arch/arm/dts/tegra20.dtsi b/arch/arm/dts/tegra20.dtsi
...
quoted
+     i2c@7000d000 {
+             #address-cells = <1>;
+             #size-cells = <0>;
+             compatible = "nvidia,tegra20-i2c";
+             reg = <0x7000D000 0x200>;
+             interrupts = < 85 >;
+     };
This is slightly out-of-date now; in next-20120118, that node's
compatible flag is nvidia,tegra20-i2c-dvc. The HW register layout is
somewhat different for this I2C controller, and the different compatible
flag is how the driver this.

Still, you can always apply that fix in a later patch before you add I2C
support.
This series was original submitted 24 November, so of course things
change. The changes you mention relate to I2C and I think I picked
these up in the later I2C patches.

But since we are chasing a moving target, I really don't want to get
too worried about redoing all the patches every time the kernel burps
:-) The changes you mention are not even in mainline yet and don't
relate to USB (this series).

Is it ok to adopt this sort of thinking throughout these series? As
you know it is easy to pick up a new fdt file later and make any
changes that are needed. I am well aware that things are still in
flux.

Regards,
Simon
--
nvpublic
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help