[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <46D905A0-2E71-4490-84BD-4D2467E13899@gmail.com>
Date: Fri, 5 Dec 2014 20:18:53 +0300
From: Alexander Kochetkov <al.kochet@...il.com>
To: Tony Lindgren <tony@...mide.com>
Cc: Kevin Hilman <khilman@...nel.org>, Felipe Balbi <balbi@...com>,
Wolfram Sang <wsa@...-dreams.de>,
linux-omap <linux-omap@...r.kernel.org>,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC 1/2] i2c: omap: fix buffer overruns during RX/TX data processing
Hello, Tony!
> The issue I'm seeing on 2430sdp is some earlier regression that
> has started happening over the past year or so.
I don't have 2430sdp. And I couldn't find 2430sdp schematics.
Looks, like this is NDA stuff.
> Of course the issue I'm seeing could be caused by hung twl4030
> PMIC too.
This could be switching twl4030 into inappropriate for 2430sdp mode.
For example, SMARTREFLEX_ENABLE bit is dangerous, because
it switch twl-pads from VMODE to i2c.
And when you set SMARTREFLEX_ENABLE, twl automatically drop
VDD1 and VDD2 to 1.2V (if VDD1_SR_CONTROL was not initialized through
BYPASS register early in the boot loader).
What mode is used in the 2430sdp? VMODE or Smartreflex?
And, that is my assumption, may be it wrong again.
I'd added trace in the twl_i2c_read_u8/twl_i2c_write_u8 functions to
easy find concrete line of code, what cause problem (by register address).
Hang happens on access to 0x004b address group.
That could be: BACKUP_REG, INT, PM_MASTER, PM_RECEIVER, RTC or
SECURED_REG. It hard to tell which one cause hang without trace.
Hope this helps.
Regards,
Alexander.
--
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