Re: [PATCH 1/2] remoteproc: use a flag to detect the presence of IOMMU

2014-08-05 Thread Ohad Ben-Cohen
On Mon, Aug 4, 2014 at 6:48 PM, Suman Anna s-a...@ti.com wrote: On 08/04/2014 06:50 AM, Ohad Ben-Cohen wrote: On Tue, Jul 29, 2014 at 7:10 PM, Suman Anna s-a...@ti.com wrote: We are trying to add a remoteproc driver for a small Cortex M3 called the WkupM3 used for suspend/resume management on

[PATCH 0/3] [PATCH 0/3] mtd: nand: omap: Use Software ECC by default

2014-08-05 Thread Roger Quadros
Hi, In Linux v3.12 and earlier some boards [1] used Software based ECC as the NAND ECC scheme. In 3.13 commit c66d039197e4 changed that to Hardware ECC using ROM code ECC layout. This will cause NAND filesystems created in 3.12 and earlier to be unreadable in v3.13 and later till they are erased

[PATCH 3/3] ARM: dts: omap3430-sdp: Revert to using software ECC for NAND

2014-08-05 Thread Roger Quadros
For v3.14 and prior, 1-bit Hamming code ECC via software was used for NAND on this board. Commit c06c52701695 in v3.15 changed the behaviour to use 1-bit Hamming code via Hardware using a different ECC layout i.e. (ROM code layout) than what is used by software ECC. This ECC layout change causes

[PATCH 1/3] mtd: nand: omap: Revert to using software ECC by default

2014-08-05 Thread Roger Quadros
For v3.12 and prior, 1-bit Hamming code ECC via software was the default choice. Commit c66d039197e4 in v3.13 changed the behaviour to use 1-bit Hamming code via Hardware using a different ECC layout i.e. (ROM code layout) than what is used by software ECC. This ECC layout change causes NAND

[PATCH 2/3] ARM: OMAP2+: GPMC: Support Software ECC scheme via DT

2014-08-05 Thread Roger Quadros
For v3.14 and prior, 1-bit Hamming code ECC via software was the default choice for some boards e.g. 3430sdp. Commit ac65caf514ec in v3.15 changed the behaviour to use 1-bit Hamming code via Hardware using a different ECC layout i.e. (ROM code layout) than what is used by software ECC. This ECC

Re: [PATCH 1/3] mtd: nand: omap: Revert to using software ECC by default

2014-08-05 Thread Grazvydas Ignotas
On Tue, Aug 5, 2014 at 1:11 PM, Roger Quadros rog...@ti.com wrote: For v3.12 and prior, 1-bit Hamming code ECC via software was the default choice. Commit c66d039197e4 in v3.13 changed the behaviour to use 1-bit Hamming code via Hardware using a different ECC layout i.e. (ROM code layout) than

TSC2004 driver

2014-08-05 Thread Michael Welling
The TSC2004 driver has yet to appear in the mainline kernel. We have been using the driver referenced here as provided by TI: https://www.mail-archive.com/linux-omap@vger.kernel.org/msg22018.html Are there any plans of supporting this device in the mainline kernel? Mysteriously a device tree

Re: [PATCH 1/3] mtd: nand: omap: Revert to using software ECC by default

2014-08-05 Thread pekon
Hi Roger, On Tuesday 05 August 2014 09:45 PM, Grazvydas Ignotas wrote: On Tue, Aug 5, 2014 at 1:11 PM, Roger Quadros rog...@ti.com wrote: For v3.12 and prior, 1-bit Hamming code ECC via software was the default choice. Commit c66d039197e4 in v3.13 changed the behavior to use 1-bit Hamming code