From: avinash philip avinashphi...@ti.com
ELM is used for locating bit-flip errors in when using BCH ECC scheme.
This patch adds suspend/resume support for leaf level ELM driver,
And also provides ELM register context save restore support, so that
configurations are preserved across
On Tue, 2013-06-18 at 00:16 +0530, Pekon Gupta wrote:
From: avinash philip avinashphi...@ti.com
ELM is used for locating bit-flip errors in when using BCH ECC scheme.
This patch adds suspend/resume support for leaf level ELM driver,
And also provides ELM register context save restore
On Sun, Jun 30, 2013 at 2:25 AM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
Yes, It doesn't apply cleanly to your next branch cleanly because
this patch-set depends on the following bugfix patch merged late on
the -rc cycle (3.10-rc7):
397eada9 (gpio/omap: don't use linear
Hi Kevin,
On 26 June 2013 03:12, Kevin Hilman khil...@linaro.org wrote:
Naresh Kamboju naresh.kamb...@linaro.org writes:
ping
This is a known issue[1] and already has some proposed fixes, they are just
not merged yet.
Kevin
[1]
Hi Pekon,
On Sun, 2013-06-23 at 23:28 +0530, Pekon Gupta wrote:
+---+---+---+
| ECC scheme |ECC calculation|Error detection|
+---+---+---+
On 06/28/2013 10:06 PM, Alan Stern wrote:
On Fri, 28 Jun 2013, Roger Quadros wrote:
That's not what I meant. Never mind the pinctrl; I was asking about
the EHCI controller itself. Under what circumstances does the
controller assert its wakeup signal? And how do you tell it to stop
On 06/28/2013 10:18 PM, Alan Stern wrote:
On Fri, 28 Jun 2013, Roger Quadros wrote:
Just found the problem. It seems that enabling the ehci_irq _after_ the root
hub is resumed
is the root cause of the problem. Doing so will miss events from the root
hub.
This sounds like a bug in the
Changes v3 - v4
- [Patch 1/3] removed MTD_NAND_OMAP_BCH8 MTD_NAND_OMAP_BCH4 from nand/Kconfig
ECC scheme selectable via nand DT (nand-ecc-opt).
= [*] rebased for l2-mtd.git
(with Author Name fixed)
Changes v2 - v3
- PATCH-1: re-arranged code to remove redundancy, added NAND_BUSWIDTH_AUTO
This patch adds following two flavours of BCH4 ECC scheme in omap2-nand driver
- OMAP_ECC_BCH4_CODE_HW_DETECTION_SW
- uses GPMC H/W engine for calculating ECC.
- uses software library (lib/bch.h nand_bch.h) for error correction.
- OMAP_ECC_BCH4_CODE_HW
- uses GPMC H/W
ECC scheme on NAND devices can be implemented in multiple ways.Some using
Software algorithm, while others using in-build Hardware engines.
omap2-nand driver currently supports following flavours of ECC schemes,
selectable via DTB.
ECC scheme on NAND devices can be implemented in multiple ways.Some using
Software algorithm, while others using in-build Hardware engines.
omap2-nand driver currently supports following flavours of ECC schemes.
+---+---+---+
| ECC
DT property values for OMAP based gpmc-nand have been updated
to match changes in commit:
6faf096 ARM: OMAP2+: cleaned-up DT support of various ECC schemes
Refer: Documentation/devicetree/bindings/mtd/gpmc-nand.txt
Signed-off-by: Pekon Gupta pe...@ti.com
---
Hi Pekon,
On Sun, 2013-06-23 at 23:28 +0530, Pekon Gupta wrote:
+---+---+---+
| ECC scheme|ECC calculation|Error
detection|
On Mon, 2013-07-01 at 15:21 +0530, Pekon Gupta wrote:
+---+---+---+
| ECC scheme |ECC calculation|Error detection|
+---+---+---+
On Wed, Jun 26, 2013 at 01:11:11PM +0530, Sourav Poddar wrote:
+static int dra7xxx_qspi_prepare_xfer(struct spi_master *master)
+{
+ return 0;
+}
+
+static int dra7xxx_qspi_unprepare_xfer(struct spi_master *master)
+{
+ return 0;
+}
Remove empty functions, though...
+ if
On 01/07/2013, at 10:04, Linus Walleij linus.wall...@linaro.org wrote:
On Sun, Jun 30, 2013 at 2:25 AM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
Yes, It doesn't apply cleanly to your next branch cleanly because
this patch-set depends on the following bugfix patch merged
Hi Mark,
Thanks for the review.
Comments in lined.
On Monday 01 July 2013 04:26 PM, Mark Brown wrote:
On Wed, Jun 26, 2013 at 01:11:11PM +0530, Sourav Poddar wrote:
+static int dra7xxx_qspi_prepare_xfer(struct spi_master *master)
+{
+ return 0;
+}
+
+static int
On Mon, Jul 1, 2013 at 1:01 PM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
On 01/07/2013, at 10:04, Linus Walleij linus.wall...@linaro.org wrote:
Let's see if we can cram it in as part of a late v3.11 merge or
if we'll have to defer to v3.12.
Ok no worries. Since these
On Fri, 2013-06-28 at 16:21 +0300, Luciano Coelho wrote:
On Fri, 2013-06-28 at 15:18 +0300, Felipe Balbi wrote:
On Fri, Jun 28, 2013 at 03:13:52PM +0300, Luciano Coelho wrote:
On Fri, 2013-06-28 at 14:41 +0300, Felipe Balbi wrote:
On Fri, Jun 28, 2013 at 02:22:11PM +0300, Luciano Coelho
On Mon, Jul 1, 2013 at 9:04 AM, Linus Walleij linus.wall...@linaro.org wrote:
On Sun, Jun 30, 2013 at 2:25 AM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
Yes, It doesn't apply cleanly to your next branch cleanly because
this patch-set depends on the following bugfix patch
As this config must support boards which cannot support separate device
trees, enable support for appended ones.
Cc: Tony Lindgren t...@atomide.com
Cc: Russell King li...@arm.linux.org.uk
Signed-off-by: Tom Rini tr...@ti.com
---
arch/arm/configs/omap2plus_defconfig |2 ++
1 file changed, 2
On Mon, Jul 1, 2013 at 2:49 PM, Grant Likely grant.lik...@linaro.org wrote:
Linus, you can actually merge in the final v3.10 tag into your
gpio-next branch and then apply on top of that. I would send it as two
separate pull requests though. One pull with all the stuff that was in
linux-next,
Errata workarounds for N900 hardware actually break operation on
emulator. Fix it.
This approach was suggested by Pali Rohár pali.ro...@gmail.com
(thanks!).
(Also explain what sleep_ind led actually does).
Signed-off-by: Pavel Machek pa...@ucw.cz
diff --git a/arch/arm/mach-omap2/board-rx51.c
Tony,
Any chance of picking these up?
I see that next-20130701 is broke as well in an OMAP5 only build. beyond
the fixes already merged in - the missing series seems to be the
$subject series to allow an OMAP5 only build.
On 06/26/2013 09:39 AM, Nishanth Menon wrote:
Hi,
Cortex-A15 based
On Mon, 1 Jul 2013, Roger Quadros wrote:
On 06/28/2013 10:06 PM, Alan Stern wrote:
On Fri, 28 Jun 2013, Roger Quadros wrote:
That's not what I meant. Never mind the pinctrl; I was asking about
the EHCI controller itself. Under what circumstances does the
controller assert its wakeup
On Mon, Jul 01, 2013 at 12:24:07PM -0400, Alan Stern wrote:
On Mon, 1 Jul 2013, Roger Quadros wrote:
On 06/28/2013 10:06 PM, Alan Stern wrote:
On Fri, 28 Jun 2013, Roger Quadros wrote:
That's not what I meant. Never mind the pinctrl; I was asking about
the EHCI controller
On 7/1/2013 3:32 PM, Gupta, Pekon wrote:
Hi Pekon,
On Sun, 2013-06-23 at 23:28 +0530, Pekon Gupta wrote:
+---+---+---+
| ECC scheme|ECC calculation|Error
detection|
Hello.
On 07/01/2013 06:03 PM, Pavel Machek wrote:
Errata workarounds for N900 hardware actually break operation on
emulator. Fix it.
This approach was suggested by Pali Rohár pali.ro...@gmail.com
(thanks!).
(Also explain what sleep_ind led actually does).
Looks like unrelated
Add refclock and tcxoclock as clock providers in WiLink. These clocks
are not accesible outside the WiLink module, but they are registered
in the clock framework anyway. Only the WiLink chip consumes these
clocks.
In theory, the WiLink chip could be connected to external clocks
instead of using
Here are some basic OMAP test results for Linux v3.10-rc7.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.10-rc7/20130630191558/
Special thanks to Lokesh Vutla, Vaibhav Hiremath, Kevin Hilman, and
Rajendra Nayak for helping unravel the Beaglebone-White test problems.
On Mon 2013-07-01 22:22:21, Sergei Shtylyov wrote:
Hello.
On 07/01/2013 06:03 PM, Pavel Machek wrote:
Errata workarounds for N900 hardware actually break operation on
emulator. Fix it.
This approach was suggested by Pali Rohár pali.ro...@gmail.com
(thanks!).
(Also explain what
Hello.
On 07/01/2013 11:51 PM, Pavel Machek wrote:
Errata workarounds for N900 hardware actually break operation on
emulator. Fix it.
This approach was suggested by Pali Rohár pali.ro...@gmail.com
(thanks!).
(Also explain what sleep_ind led actually does).
Looks like unrelated
Hi,
On Mon, Jul 01, 2013 at 07:48:50PM +, Paul Walmsley wrote:
Boot to userspace:
FAIL ( 2/12): 37xxevm, am335xbonelt
quoting part of [1]
| U-Boot# tftp 0x8200 am335x-boneblack.dtb
| link up on port 0, speed 100, full duplex
| Using cpsw device
| TFTP from server 192.168.57.1; our
Hi,
On Mon, Jul 01, 2013 at 10:34:10PM +0300, Luciano Coelho wrote:
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi
b/arch/arm/boot/dts/omap4-panda-common.dtsi
index 670c3ce..7f061b8 100644
--- a/arch/arm/boot/dts/omap4-panda-common.dtsi
+++
Hi!
Errata workarounds for N900 hardware actually break operation on
emulator. Fix it.
This approach was suggested by Pali Rohár pali.ro...@gmail.com
(thanks!).
(Also explain what sleep_ind led actually does).
Looks like unrelated change and probably worth another patch?
Ok, more
On Mon, 2013-07-01 at 23:46 +0300, Felipe Balbi wrote:
Hi,
On Mon, Jul 01, 2013 at 10:34:10PM +0300, Luciano Coelho wrote:
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi
b/arch/arm/boot/dts/omap4-panda-common.dtsi
index 670c3ce..7f061b8 100644
---
On Mon, 1 Jul 2013, Felipe Balbi wrote:
I don't know what Pad wakeup is. The wakeup signal has to originate
from the EHCI controller, doesn't it? If not, how does the Pad know
when a wakeup is needed?
That's really an OMAP thing, I guess. Pad wakeup sits in the PRCM (IIRC)
inside
We still need video sound drivers with device tree enabled.
Signed-off-by: Pavel Machek pa...@ucw.cz
---
Patch against 3.10.
--- linux-delme-clean//arch/arm/mach-omap2/board-rx51-video.c 2013-07-01
21:51:07.0 +0200
+++ linux-delme/arch/arm/mach-omap2/board-rx51-video.c 2013-07-01
This adds device tree with neccessary support to boot with functional
video (on both emulator and real N900 device).
Signed-off-by: Pavel Machek pa...@ucw.cz
--- linux-delme-clean//arch/arm/boot/dts/Makefile 2013-07-01
21:51:00.0 +0200
+++ linux-delme/arch/arm/boot/dts/Makefile
Javier Martinez Canillas javier.marti...@collabora.co.uk writes:
When an OMAP GPIO is used as an IRQ line, a call to gpio_request()
has to be made to initialize the OMAP GPIO bank before a driver
request the IRQ. Otherwise the call to request_irq() fails.
Drivers should not be aware of this
Hebbar Gururaja gururaja.heb...@ti.com writes:
rtc-omap driver modules is used both by OMAP1/2, Davinci SoC platforms.
However, rtc wake support on OMAP1 is broken. Hence the
device_init_wakeup() was removed from rtc-omap driver and moved to
platform board files that supported it
Hebbar Gururaja gururaja.heb...@ti.com writes:
Since now rtc-omap driver itself calls deice_init_wakeup(dev, true),
duplicate call from the rtc device registration can be removed.
This is basically a partial revert of the prev commit
commit 75c99bb0006ee065b4e2995078d779418b0fab54
Author:
Hebbar Gururaja gururaja.heb...@ti.com writes:
On some platforms (like AM33xx), a special register (RTC_IRQWAKEEN)
is available to enable Alarm Wakeup feature. This register needs to be
properly handled for the rtcwake to work properly.
Platforms using such IP should set ti,am3352-rtc in rtc
Hi Hebbar,
Hebbar Gururaja gururaja.heb...@ti.com writes:
rtc-omap driver modules is used both by OMAP1/2, Davinci SoC platforms.
However, rtc wake support on OMAP1 is broken. Hence the
device_init_wakeup() was removed from rtc-omap driver and moved to
platform board files that supported it
This does not apply to l2-mtd.git, could you please re-base?
[Pekon]: rebased to l2-mtd.git
- updated [Patch 3/4] which conflicted with commit '26331c04' which
touched omap2.c.
- Please ignore [Patch 4/4] as it’s a DT update, which adds on top of
Benoit's
tree (which has NAND node
-Original Message-
From: Paul Walmsley [mailto:p...@pwsan.com]
Sent: Monday, July 01, 2013 7:46 AM
To: Vutla, Lokesh
Cc: Nayak, Rajendra; Hiremath, Vaibhav; Kevin Hilman; Rini, Tom; linux-
o...@vger.kernel.org; Balbi, Felipe; linux-arm-
ker...@lists.infradead.org
Subject: Re: OMAP
-Original Message-
From: Balbi, Felipe
Sent: Friday, June 28, 2013 4:24 PM
To: Hiremath, Vaibhav
Cc: Menon, Nishanth; Peter Korsgaard; Kevin Hilman; Balbi, Felipe; Paul
Walmsley; linux-omap@vger.kernel.org; Tony Lindgren; Sebastian Andrzej
Siewior
Subject: Re: reset handling in
On Tue, Jul 02, 2013 at 05:37:43, Kevin Hilman wrote:
Hebbar Gururaja gururaja.heb...@ti.com writes:
Since now rtc-omap driver itself calls deice_init_wakeup(dev, true),
duplicate call from the rtc device registration can be removed.
This is basically a partial revert of the prev commit
On Tue, Jul 02, 2013 at 05:45:01, Kevin Hilman wrote:
Hebbar Gururaja gururaja.heb...@ti.com writes:
On some platforms (like AM33xx), a special register (RTC_IRQWAKEEN)
is available to enable Alarm Wakeup feature. This register needs to be
properly handled for the rtcwake to work
On 6/28/2013 3:05 PM, Hebbar Gururaja wrote:
Since now rtc-omap driver itself calls deice_init_wakeup(dev, true),
duplicate call from the rtc device registration can be removed.
This is basically a partial revert of the prev commit
commit 75c99bb0006ee065b4e2995078d779418b0fab54
Author:
On Tue, Jul 02, 2013 at 11:10:14, Nori, Sekhar wrote:
On 6/28/2013 3:05 PM, Hebbar Gururaja wrote:
Since now rtc-omap driver itself calls deice_init_wakeup(dev, true),
duplicate call from the rtc device registration can be removed.
This is basically a partial revert of the prev commit
51 matches
Mail list logo
