* Sebastian Andrzej Siewior | 2014-11-26 23:01:46 [+0100]:
Technically speaking this is not required. If both are enabled then the
Maikefile order says that 8250 one wins, the second is never probed.
If we choose to enable 8250_omap via defconfig then one might get supprised
that his console
On Wed, Nov 12, 2014 at 04:41:00PM +0200, Jyri Sarha wrote:
The platform device should only be registered from OMAPDSS HDMI
driver. The platform driver registers and unregisters all ASoC
components needed for OMAP HDMI audio.
So, this basically seems fine but I'm looking at this code and I'm
On Wed, Nov 12, 2014 at 04:40:51PM +0200, Jyri Sarha wrote:
The patches are based on:
git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git for-next
The base, the patches, and couple of additional not-to-be-merged
omap2plus_defconfig patches can be found here:
Hi,
On Fri, Nov 28, 2014 at 11:35:53AM +0100, Yegor Yefremov wrote:
On Wed, Nov 19, 2014 at 6:53 PM, Tony Lindgren t...@atomide.com wrote:
* Enric Balletbo Serra eballe...@gmail.com [141119 03:14]:
2014-11-18 16:42 GMT+01:00 Tony Lindgren t...@atomide.com:
Checked again, and no luck.
* Sebastian Andrzej Siewior bige...@linutronix.de [141129 01:50]:
* Sebastian Andrzej Siewior | 2014-11-26 23:01:46 [+0100]:
Technically speaking this is not required. If both are enabled then the
Maikefile order says that 8250 one wins, the second is never probed.
If we choose to enable
The first patch fix i2c-omap driver for omap2420, found by code review and
later reported by Tony Lindgren t...@atomide.com here[1].
Candidate for stable?
The second patch unhide the reson of system lockup.
The patch is rebased on branch 'i2c/for-next' of
Commit 079d8af24b948261e1dae5d7df6b31b7bf205cb4 (i2c: omap: bus:
add a receiver flag) changed ISR loop to silently ignore unwanted
XDR/XRDY or RDR/RRDY events without processing. That unwanted events
will fire interrupt again and most likely they will be ignored again.
As a result, system enters
commit dd74548ddece4b9d68e5528287a272fa552c81d0 (i2c: omap:
resize fifos before each message) dropped check for dev-buf_len.
As result, data processing loop cause dev-buf overruns for
devices with 16-bit data register (omap2420).
In the dd74548ddece4b9d68 code, for each loop iteration if the
flag
* Alexander Kochetkov al.koc...@gmail.com [141128 15:27]:
Hello, Tony!
I just want to know, is multimaster i2c feature is interesting for TI SOC,
so I could send another patches?
Sure and thanks for looking into fixing things.
Or it's better to leave the thing without changes, as current
