upport, and some of them didn't! Those kernels that
have DIU enabled but not your patch will move the devices to I2C2. I was
running one of those kernels when I posted my patch.
So in summary, this patch "CS4270 node is misplaced in the MPC8610 device tree"
should no
Anton Vorontsov wrote:
> Hm... this should be controlled by the PIXIS' BRDCFG0's I2CSPAN and
> SERSEL bits:
Since these pins should not have changed from one kernel version to another, it
doesn't explain how my device "jumped" from I2C2 to I2C1. I'm debugging this
now.
> 1: I2C1 and I2C2 are b
On Mon, May 19, 2008 at 01:20:32PM -0500, Timur Tabi wrote:
> Timur Tabi wrote:
> > The CS4270 is using the second I2C bus, not the first, on the Freescale
> > MPC8610 HPCD, so its node in the device tree belongs under '[EMAIL
> > PROTECTED]'
> > and not '[EMAIL PROTECTED]'.
> >
> > Signed-off-by
Timur Tabi wrote:
> The CS4270 is using the second I2C bus, not the first, on the Freescale
> MPC8610 HPCD, so its node in the device tree belongs under '[EMAIL PROTECTED]'
> and not '[EMAIL PROTECTED]'.
>
> Signed-off-by: Timur Tabi <[EMAIL PROTECTED]>
Please disregard this patch. It turns out
The CS4270 is using the second I2C bus, not the first, on the Freescale
MPC8610 HPCD, so its node in the device tree belongs under '[EMAIL PROTECTED]'
and not '[EMAIL PROTECTED]'.
Signed-off-by: Timur Tabi <[EMAIL PROTECTED]>
---
Kumar, this is a must-fix for 2.6.26.
The reason this didn't sho
