On 11/05/2014 02:15 AM, Lennart Sorensen wrote:
Well 4 hours running with multiple reboots (our testsuite reboots every
30 minutes to test the watchdog). So far it has only lost 70 bytes out
of 40MB of data sent between uart7 and uart8 (and we are pretty sure
the serial test has a small bug
In commit 7d5929c1f343 (mtd: nand: omap: Revert to using software ECC by
default),
we switched back to using 1-bit SW ECC scheme by default. However
commit b491da7233d5 (mtd: nand: omap: clean-up ecc layout for BCH ecc schemes)
didn't take into account the 1-bit SW scheme (i.e.
On 11/04/2014 05:55 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [141104 02:50]:
Hi Tony,
These patches add CAN support for am33xx, am43xx and dra7 platforms.
They must go in together with CAN driver RAMINIT Syscon support [1].
Can you make this series not depend on [1] for most
On 11/04/2014 12:20 PM, Roger Quadros wrote:
Some TI SoCs like DRA7 have a RAMINIT register specification
different from the other AMxx SoCs and as expected by the
existing driver.
To add more insanity, this register is shared with other
IPs like DSS, PCIe and PWM.
Provides a more
On Tuesday 04 November 2014 06:07 PM, Sebastian Andrzej Siewior wrote:
On 11/04/2014 12:44 PM, Vignesh R wrote:
I ran following commands
$ evtest /dev/input/touchscreen0
(with heavy item on touchscreen)
and
$ cat /sys/bus/iio/devices/iio\:device0/scan_elements/in_voltage4_en
(in a
On 11/04/2014 07:49 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [141030 08:25]:
On 10/30/2014 05:10 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [141021 05:43]:
Hi Tony,
These patches address GPMC configuration issues and are for v3.19.
Patches based on v3.18-rc1.
-
On 11/04/2014 11:20 AM, Roger Quadros wrote:
DRA7 CAN IP suffers from a problem which causes it to be prevented
from fully turning OFF (i.e. stuck in transition) if the module was
disabled while there was traffic on the CAN_RX line.
To work around this issue we select the SLEEP pin state by
On 11/04/2014 11:21 AM, Roger Quadros wrote:
DRA7 SoC has 2 CAN IPs. Provide compatible IDs and RAMINIT
register data for both.
My understanding of the discussion with Wolfram was:
- We should put the number of the Interface into to DT as a regmap
parameter.
- We put the method how to find
On 11/05/2014 03:24 PM, Marc Kleine-Budde wrote:
On 11/04/2014 11:20 AM, Roger Quadros wrote:
DRA7 CAN IP suffers from a problem which causes it to be prevented
from fully turning OFF (i.e. stuck in transition) if the module was
disabled while there was traffic on the CAN_RX line.
To work
On 11/05/2014 03:30 PM, Marc Kleine-Budde wrote:
On 11/04/2014 11:21 AM, Roger Quadros wrote:
DRA7 SoC has 2 CAN IPs. Provide compatible IDs and RAMINIT
register data for both.
My understanding of the discussion with Wolfram was:
- We should put the number of the Interface into to DT as a
On 11/05/2014 02:36 PM, Roger Quadros wrote:
On 11/05/2014 03:30 PM, Marc Kleine-Budde wrote:
On 11/04/2014 11:21 AM, Roger Quadros wrote:
DRA7 SoC has 2 CAN IPs. Provide compatible IDs and RAMINIT
register data for both.
My understanding of the discussion with Wolfram was:
- We should put
On 11/04/2014 08:11 PM, Felipe Balbi wrote:
On Tue, Nov 04, 2014 at 11:42:04AM +0530, George Cherian wrote:
Hi Felipe et al.
Another series was posted by removing the platform support.
https://lkml.org/lkml/2014/10/14/244
I guess I forgot to copy linux-omap.
you do too many things in patch
Add support for using cable names. Enables other drivers to register interest
and get notified using extcon provided notifier call backs.
Signed-off-by: George Cherian george.cher...@ti.com
---
Documentation/devicetree/bindings/extcon/extcon-gpio.txt | 2 ++
drivers/extcon/extcon-gpio.c
Add device tree support to extcon-gpio driver.
Add devicetree binding documentation
While at that
- Cleanup the pdata as there are no users for the same.
- Convert the driver to use gpiod_* API's.
- Some gpio's can sleep while reading, so always use
This series
- Adds dt support to extcon-gpio driver.
- Add cable name support in case of dt.
George Cherian (2):
extcon: gpio: Add dt support for the driver
extcon: gpio: Add support for using cable names
drivers/extcon/extcon-gpio.c | 87
On Wed, Nov 05, 2014 at 09:11:35AM +0100, Sebastian Andrzej Siewior wrote:
Okay. No DMA but the basic part seems to work for you. Thanks for
testing.
Two systems ran 16 hours each so far with no issues. Pushed 170MB of
data through the pair of serial ports on one system at 230400.
--
Len
On 08/26/2014 03:52 AM, Daniel Mack wrote:
This patch makes the edma driver resume correctly after suspend. Tested
on an AM33xx platform with cyclic audio streams and omap_hsmmc.
All information can be reconstructed by already known runtime
information.
As we now use some functions that
On Wednesday 05 November 2014 09:27 PM, Dave Gerlach wrote:
On 08/26/2014 03:52 AM, Daniel Mack wrote:
This patch makes the edma driver resume correctly after suspend. Tested
on an AM33xx platform with cyclic audio streams and omap_hsmmc.
All information can be reconstructed by already known
* Roger Quadros rog...@ti.com [141105 04:47]:
On 11/04/2014 07:49 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [141030 08:25]:
On 10/30/2014 05:10 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [141021 05:43]:
Hi Tony,
These patches address GPMC configuration issues
On Wed, Nov 05, 2014 at 10:33:15AM -0500, Lennart Sorensen wrote:
Two systems ran 16 hours each so far with no issues. Pushed 170MB of
data through the pair of serial ports on one system at 230400.
The console on uart3 doesn't appear to be using the dma assuming the
values in /sys for the dma
On 11/05/2014 05:20 PM, Lennart Sorensen wrote:
On Wed, Nov 05, 2014 at 10:33:15AM -0500, Lennart Sorensen wrote:
Two systems ran 16 hours each so far with no issues. Pushed 170MB of
data through the pair of serial ports on one system at 230400.
The console on uart3 doesn't appear to be
On 11/03/2014 04:09 AM, Roger Quadros wrote:
For PIN_OUTPUT_PULLUP and PIN_OUTPUT_PULLDOWN we must not set the
PULL_DIS bit which disables the PULLs.
PULL_ENA is a 0 and using it in an OR operation is a NOP, so don't
use it in the PIN_OUTPUT_PULLUP/DOWN macros.
Fixes: 23d9cec07c58
Sekhar,
On 11/05/2014 10:04 AM, Sekhar Nori wrote:
On Wednesday 05 November 2014 09:27 PM, Dave Gerlach wrote:
On 08/26/2014 03:52 AM, Daniel Mack wrote:
This patch makes the edma driver resume correctly after suspend. Tested
on an AM33xx platform with cyclic audio streams and omap_hsmmc.
On Wed, Nov 05, 2014 at 08:55:17PM +0530, George Cherian wrote:
On 11/04/2014 08:11 PM, Felipe Balbi wrote:
On Tue, Nov 04, 2014 at 11:42:04AM +0530, George Cherian wrote:
Hi Felipe et al.
Another series was posted by removing the platform support.
https://lkml.org/lkml/2014/10/14/244
On Wed, Nov 05, 2014 at 08:59:47PM +0530, George Cherian wrote:
Add device tree support to extcon-gpio driver.
Add devicetree binding documentation
While at that
- Cleanup the pdata as there are no users for the same.
should be a patch of its own.
- Convert the driver to use
Here are few fixes to reduce bootup errors and warnings when
booting omaps in device tree mode. All these are non-critical,
so these are intended for the v3.19 merge window unless somebody
comes up with a real need for these earlier.
Regards,
Tony
Tony Lindgren (5):
ARM: OMAP3: Fix errors
Looks like we're still missing the keypad map for LDP.
Let's add it since we have the binding now available
for the twl4030_keypad as otherwise we get the following
errors during the boot:
twl4030_keypad keypad.31: OF: linux,keymap property not defined
in /ocp/i2c@4807/twl@48/keypad
Omap4 and later have been booting in device tree only
mode for quite some time now. This initcall is no longer
needed. Note that omap3 uses a different driver omap_l3_smx,
and the initcall for that one is still needed until omap3
boots in device tree only mode.
Signed-off-by: Tony Lindgren
Fix the following warning during the boot:
mtd: partition Filesystem extends beyond the end of device
omap2-nand.0 -- size truncated to 0x600
Looks like I got the last partition size wrong while setting
up the .dts file. Note that this does not affect the partition
as the size has been
When booting omap3 in device tree mode, we're currently getting
the following errors:
omap_l3_smx omap_l3_smx.0: couldn't request debug irq
omap_l3_smx: probe of omap_l3_smx.0 failed with error -22
This is because we don't have handling in the driver for the
compatible property and instead
Looks like we're still missing the keypad map for LDP.
Let's add it since we have the binding now available
for the twl4030_keypad as otherwise we get the following
errors during the boot:
twl4030_keypad keypad.31: OF: linux,keymap property not defined
in /ocp/i2c@4807/twl@48/keypad
* Tony Lindgren t...@atomide.com [141105 10:39]:
Looks like we're still missing the keypad map for LDP.
Let's add it since we have the binding now available
for the twl4030_keypad as otherwise we get the following
errors during the boot:
twl4030_keypad keypad.31: OF: linux,keymap property
* Roger Quadros rog...@ti.com [141105 03:08]:
On 11/04/2014 05:55 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [141104 02:50]:
Hi Tony,
These patches add CAN support for am33xx, am43xx and dra7 platforms.
They must go in together with CAN driver RAMINIT Syscon support [1].
On Wed, Nov 05, 2014 at 05:30:51PM +0100, Sebastian Andrzej Siewior wrote:
On 11/05/2014 05:20 PM, Lennart Sorensen wrote:
On Wed, Nov 05, 2014 at 10:33:15AM -0500, Lennart Sorensen wrote:
Two systems ran 16 hours each so far with no issues. Pushed 170MB of
data through the pair of serial
On 11/05/2014 10:35 AM, Tony Lindgren wrote:
When booting omap3 in device tree mode, we're currently getting
the following errors:
omap_l3_smx omap_l3_smx.0: couldn't request debug irq
omap_l3_smx: probe of omap_l3_smx.0 failed with error -22
This is because we don't have handling in the
On 11/05/2014 10:35 AM, Tony Lindgren wrote:
When booting omap3 in device tree mode, we're currently getting
the following errors:
omap_l3_smx omap_l3_smx.0: couldn't request debug irq
omap_l3_smx: probe of omap_l3_smx.0 failed with error -22
This is because we don't have handling in the
On Wed 2014-11-05 02:11:22, Sebastian Reichel wrote:
Hi Pavel,
On Tue, Nov 04, 2014 at 09:51:17PM +0100, Pavel Machek wrote:
I'd like to test a modem (and eventually to get it to work :-) ) on
n900. So far I found:
http://lwn.net/Articles/592485/
It says:
# supported.
Hello, have you enabled CONFIG_PHONET?
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
Hi!
Hello, have you enabled CONFIG_PHONET?
Yes:
CONFIG_PHONET=y
And this:
# SPI Protocol Masters
#
#
Maybe you need to enable modem?
This is n900 init sequence from script: nokia-n900-configs.sh
# set up the GPIO's for N900 modem:
echo 70 /sys/class/gpio/export
echo low /sys/class/gpio/gpio70/direction
echo 0 /sys/class/gpio/gpio70/value
echo 73 /sys/class/gpio/export
Hi!
Maybe you need to enable modem?
This is n900 init sequence from script: nokia-n900-configs.sh
From the dts, it looks like this should somehow work without this.
I can try but.. is it safe? I'm using DT-based config, and interrupt
numbers definitely changed. If GPIO numbers changed, it
Here are some basic OMAP test results for Linux v3.18-rc3.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.18-rc3/20141105113246/
Test summary
Build: uImage:
Pass ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only,
Hi,
On Wed, Nov 05, 2014 at 11:03:59PM +0100, Pavel Machek wrote:
Maybe you need to enable modem?
This is n900 init sequence from script: nokia-n900-configs.sh
From the dts, it looks like this should somehow work without this.
Right :) The n900-modem driver will take care of this if
Hi George,
On 11/06/2014 12:29 AM, George Cherian wrote:
This series
- Adds dt support to extcon-gpio driver.
- Add cable name support in case of dt.
George Cherian (2):
extcon: gpio: Add dt support for the driver
extcon: gpio: Add support for using cable names
On Mon, Sep 29, 2014 at 08:06:36PM +0200, Sebastian Andrzej Siewior wrote:
The queue is getting smaller. The highlights of v9…v10
- the DMA stall Frans Klaver reported which popped up in yocto is gone. It
also seems that the ack the err-irq even if nothing happened in EDMA
can be dropped.
On Monday 03 November 2014 11:39 PM, Richard Cochran wrote:
On Mon, Oct 27, 2014 at 04:38:27PM +0530, Vignesh R wrote:
This series of patches fix TSC defects related to lag in touchscreen
performance and cursor jump at touch release. The lag was result of
udelay in TSC interrupt handler.
46 matches
Mail list logo
