On Wednesday 05 November 2014 11:40 PM, Dave Gerlach wrote:
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
On 11/06/2014 04:14 AM, Greg KH wrote:
I've now applied the patches here that I could, if I have missed any,
please let me know and resend.
Thank you Greg. I pulled your tty-testing and it seems to work on
am335x-evm/dra7-evm.
Tony, if you could please take the two .dts files then the series
Fix DCDC3 volatge to 1.5V which is the right value to be supplied by
DCDC3 for all the boards.
Keerthy (3):
ARM: dts: AM43x-EPOS-EVM: Fix DCDC3 voltage
ARM: dts: AM437x-GP-EVM: Fix DCDC3 voltage
ARM: dts: AM437x-SK-EVM: Fix DCDC3 voltage
arch/arm/boot/dts/am437x-gp-evm.dts |4 ++--
DCDC3 supplies voltage to DDR. Fix DCDC3 volatge to 1.5V which is the reset
value. Programming to a non-reset value while executing from DDR will result
in random hangs.
Signed-off-by: Keerthy j-keer...@ti.com
---
arch/arm/boot/dts/am437x-gp-evm.dts |4 ++--
1 file changed, 2 insertions(+),
DCDC3 supplies voltage to DDR. Fix DCDC3 volatge to 1.5V which is the reset
value. Programming to a non-reset value while executing from DDR will result
in random hangs.
Signed-off-by: Keerthy j-keer...@ti.com
---
arch/arm/boot/dts/am437x-sk-evm.dts |4 ++--
1 file changed, 2 insertions(+),
DCDC3 supplies voltage to DDR. Fix DCDC3 volatge to 1.5V which is the reset
value. Programming to a non-reset value while executing from DDR will result
in random hangs.
Signed-off-by: Keerthy j-keer...@ti.com
---
arch/arm/boot/dts/am43x-epos-evm.dts |4 ++--
1 file changed, 2 insertions(+),
At this moment all supported boards use same NAND chip, so has more sense
move the GPMC and NAND configuration to the omap3-igep.dtsi common place.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/omap3-igep.dtsi| 49 ++
Use the omap3-igep0020-common.dtsi file and remove repeated parts leaving
the nodes that are not common between IGEPv2 hardware revisions.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/omap3-igep0020-common.dtsi | 246 +++
We'll introduce new hardware revisions soon. This patch is only to
indicate which board revision supports this device tree file in order
to avoid confusions.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/omap3-igep0030.dts | 4 ++--
1 file changed, 2
We can't suppose that the i2c2 pins are configured as I2C bus, these pins are
connected to expansion connectors.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/omap3-igep.dtsi | 13 -
1 file changed, 13 deletions(-)
diff --git
Add support for the new hardware revision of the IGEPv2. Basically, the new
revision F replaces the old Wifi module for a Wilink8 based module.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/Makefile | 1 +
Use the omap3-igep0030-common.dtsi file and remove repeated parts leaving
the nodes that are not common between IGEP COM MODULE hardware revisions.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/omap3-igep0030-common.dtsi | 60
Add support for the new hardware revision of the IGEP COM MODULE. Basically,
the new revision G replaces the old Wifi module for a Wilink8 based module.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/Makefile | 1 +
New IGEP boards revisions will use another Wifi module, so this patch moves
the DT nodes outside the common omap3-igep.dtsi file to specific DT for every
board.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/omap3-igep.dtsi| 29 ---
Add btwilink device for IGEPv2 Rev. F and IGEP COM MODULE Rev. G.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/mach-omap2/pdata-quirks.c | 36 ++--
1 file changed, 34 insertions(+), 2 deletions(-)
diff --git
We'll introduce new hardware revisions soon. This patch is only to
indicate which board revision supports this device tree file in order
to avoid confusions.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
arch/arm/boot/dts/omap3-igep0020.dts | 4 ++--
1 file changed, 2
UART2 is used to connect the processor with the bluetooth chip, these pins
are not common between IGEPv2 boards and IGEP COM MODULE boards. This patch
muxes the correct pins for every board and removes UART2 configuration from
common omap3-igep.dtsi file.
Signed-off-by: Enric Balletbo i Serra
Hi,
This series is based on omap-for-v3.19/dt from tmlind repository and adds
device tree support for two new hardware revisions of IGEPv2 and IGEP COM
MODULE.
Please could these patches be queued for 3.19 considering that these are not
fixes, might be nice to get them merged for 3.19 series.
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
On 11/06/2014 04:50 AM, Keerthy wrote:
Fix DCDC3 volatge to 1.5V which is the right value to be supplied by
DCDC3 for all the boards.
Keerthy (3):
ARM: dts: AM43x-EPOS-EVM: Fix DCDC3 voltage
ARM: dts: AM437x-GP-EVM: Fix DCDC3 voltage
ARM: dts: AM437x-SK-EVM: Fix DCDC3 voltage
On Mon, Oct 27, 2014 at 04:38:28PM +0530, Vignesh R wrote:
...
@@ -209,6 +214,7 @@ static void titsc_read_coordinates(struct titsc *ts_dev,
unsigned int read, diff;
unsigned int i, channel;
unsigned int creads = ts_dev-coordinate_readouts;
+ unsigned int first_step =
Sekhar,
On 11/06/2014 02:33 AM, Sekhar Nori wrote:
On Wednesday 05 November 2014 11:40 PM, Dave Gerlach wrote:
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
These files are very important to the healt
of the OMAP architecture, specially when it
comes to PM support which currently we have
working for at least OMAP3 and we'd like
to know about any changes being made to our
PMICs and IRQ controllers.
Signed-off-by: Felipe Balbi ba...@ti.com
---
BeagleBoard-X15 is the next generation Open Source Hardware
BeagleBoard based on TI's AM5728 SoC featuring dual core 1.5GHZ A15
processor. The platform features 2GB DDR3L (w/dual 32bit busses),
eSATA, 3 USB3.0 ports, integrated HDMI (1920x108@60), separate LCD
port, video In port, 4GB eMMC, uSD,
On Mon, Nov 03, 2014 at 11:39:52PM -0600, Felipe Balbi wrote:
Hi,
On Mon, Jul 28, 2014 at 05:24:34AM +, Paul Walmsley wrote:
On Tue, 15 Jul 2014, Felipe Balbi wrote:
ml-node and sl-node are currently initialized
by means of INIT_LIST_HEAD(). That initialiation
is followed by
On Thu, Nov 06, 2014 at 10:18:22AM -0600, Nishanth Menon wrote:
BeagleBoard-X15 is the next generation Open Source Hardware
BeagleBoard based on TI's AM5728 SoC featuring dual core 1.5GHZ A15
processor. The platform features 2GB DDR3L (w/dual 32bit busses),
eSATA, 3 USB3.0 ports, integrated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/06/2014 11:32 AM, Felipe Balbi wrote:
On Thu, Nov 06, 2014 at 10:18:22AM -0600, Nishanth Menon wrote:
BeagleBoard-X15 is the next generation Open Source Hardware
BeagleBoard based on TI's AM5728 SoC featuring dual core 1.5GHZ
A15 processor.
On Thu, Nov 06, 2014 at 10:18:22AM -0600, Nishanth Menon wrote:
BeagleBoard-X15 is the next generation Open Source Hardware
BeagleBoard based on TI's AM5728 SoC featuring dual core 1.5GHZ A15
processor. The platform features 2GB DDR3L (w/dual 32bit busses),
eSATA, 3 USB3.0 ports, integrated
On 11/06/2014 10:37 AM, Tom Rini wrote:
device_type = memory; + reg = 0x8000 0x4000; /* 1GB
to start. Target 2GB */
1GiB ? Why would you put this here btw ? u-boot fills this one up.
Yes, it should either be the full and correct value or 0x0 (like a
number of PowerPC
Register with kernel power-off handler instead of setting pm_power_off
directly. Register with low priority to reflect that the original code
only sets pm_power_off if it was not already set.
Cc: Samuel Ortiz sa...@linux.intel.com
Cc: Lee Jones lee.jo...@linaro.org
Cc: linux-omap@vger.kernel.org
Register with kernel power-off handler instead of setting pm_power_off
directly. Always use register_power_off_handler_simple as there is no
indication that more than one power-off handler is registered.
If the power-off handler only resets the system or puts the CPU in sleep mode,
select the
Yes. We have three USB 3.0 ports.
Gerald
-Original Message-
From: Lennart Sorensen [mailto:lsore...@csclub.uwaterloo.ca]
Sent: Thursday, November 6, 2014 10:42 AM
To: Nishanth Menon
Cc: Tony Lindgren; linux-ker...@vger.kernel.org;
linux-arm-ker...@lists.infradead.org;
* Nishanth Menon n...@ti.com [141106 08:44]:
On 11/06/2014 10:37 AM, Tom Rini wrote:
device_type = memory; + reg = 0x8000 0x4000; /* 1GB
to start. Target 2GB */
1GiB ? Why would you put this here btw ? u-boot fills this one up.
Yes, it should either be the full and
Convert 12V to 5V and 3.3V. 5V supplies are too expensive at the required
wattage level.
Gerald
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Thursday, November 6, 2014 10:49 AM
To: Nishanth Menon
Cc: Tom Rini; ba...@ti.com; devicet...@vger.kernel.org;
On 11/06/2014 10:48 AM, Tony Lindgren wrote:
* Nishanth Menon n...@ti.com [141106 08:44]:
On 11/06/2014 10:37 AM, Tom Rini wrote:
device_type = memory; + reg = 0x8000 0x4000; /* 1GB
to start. Target 2GB */
1GiB ? Why would you put this here btw ? u-boot fills this one up.
Register with kernel power-off handler instead of setting pm_power_off
directly. Register with low priority to reflect that the original code
only sets pm_power_off if it was not already set.
Make twl4030_power_off static as it is only called from the twl4030-power
driver. Drop remove function as
Register with kernel power-off handler instead of setting pm_power_off
directly. Register with low priority to reflect that the original code
only sets pm_power_off if it was not already set.
Cc: Samuel Ortiz sa...@linux.intel.com
Cc: Lee Jones lee.jo...@linaro.org
Cc: linux-omap@vger.kernel.org
Register with kernel power-off handler instead of setting pm_power_off
directly. Register with low priority to reflect that the original code
only sets pm_power_off if it was not already set.
Cc: Samuel Ortiz sa...@linux.intel.com
Cc: Lee Jones lee.jo...@linaro.org
Cc: linux-omap@vger.kernel.org
Register with kernel power-off handler instead of setting pm_power_off
directly. Register with low priority to reflect that the original code
only sets pm_power_off if it was not already set.
Cc: Samuel Ortiz sa...@linux.intel.com
Cc: Lee Jones lee.jo...@linaro.org
Cc: linux-omap@vger.kernel.org
On 10:53-20141106, Nishanth Menon wrote:
On 11/06/2014 10:48 AM, Tony Lindgren wrote:
* Nishanth Menon n...@ti.com [141106 08:44]:
On 11/06/2014 10:37 AM, Tom Rini wrote:
device_type = memory; + reg = 0x8000 0x4000;
/* 1GB
to start. Target 2GB */
1GiB ? Why
Tony
On Monday 03 November 2014 09:57 PM, Felipe Balbi wrote:
On Tue, Oct 21, 2014 at 12:22:23PM -0500, Nishanth Menon wrote:
On 15:37-20141021, Mugunthan V N wrote:
Nishanth
On Tuesday 21 October 2014 03:30 PM, Mugunthan V N wrote:
Adding device tree entry for CPSW to make it work in Dual
as it turns out, at least AM437x silicon (non-FPGA)
needs to enable PHY suspend quirk. So let's allow
for PHY suspend quirk to be used with non-FPGA
builds too.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/dwc3/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Whenever Suspend PHY bit is set on AM437x devices,
USB will not work due to Set EP Configuration command
always failing.
This was only found after a recent commit 2164a47 (usb:
dwc3: set SUSPHY bit for all cores, which will be merged
for v3.19) added a missing *required* step to dwc3
Hi,
On Thu, Nov 06, 2014 at 01:47:11PM +0100, Pavel Machek wrote:
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
* Roger Quadros rog...@ti.com [141105 03:02]:
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
* Masanari Iida standby2...@gmail.com [141007 07:17]:
This patch remove unnecessary KERN_INFO and KERN_ERR from omap_phy_internal.c.
Add pr_fmt.
Applying into omap-for-v3.19/fixes-not-urgent thanks.
Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a
* Roger Quadros rog...@ti.com [141021 04:27]:
The 5th NAND partition should be named NAND.u-boot-spl-os
instead of NAND.u-boot-spl. This is to be consistent with other
TI boards as well as u-boot.
Applying into omap-for-v3.18/fixes thanks.
Tony
Fixes: 91994facdd2d (ARM: dts: am335x-evm:
Hi Ohad,
On 10/06/2014 04:44 AM, Ohad Ben-Cohen wrote:
On Fri, Sep 26, 2014 at 7:25 PM, Suman Anna s-a...@ti.com wrote:
I am yet to receive any comments on v6, but that series should address
both your need for a probe deferral and Ohad's request to not change any
return types. Please give it
* Keerthy j-keer...@ti.com [141106 02:55]:
Fix DCDC3 volatge to 1.5V which is the right value to be supplied by
DCDC3 for all the boards.
Hmm so what about the comments for similar beaglebone changes
in thread [PATCH] ARM: dts: am335x-boneblack: set dcdc1 regulator
for 1.35v ddr3?
Regards,
Dear user,
Your mailbox has Exceeded the quota limit set by the administrator, you will
not be able to send or receive mailuntil you revalidates your account.
Please click the link below or copy paste to your browser to validate your
mailbox.
http://www.urlme.co/quota-service
Failure to do
* Javier Martinez Canillas javier.marti...@collabora.co.uk [140318 23:12]:
The GPMC driver includes arch/arm/mach-omap2/common.h but
does not use anything on that header so it can be removed.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Signed-off-by: Tony Lindgren
This is mostly an equivalent for the 8250-omap driver based on a patch
of Dave Gerlach for the omap-serial driver (which is not yet merged).
From his changelog:
|By optionally putting the pins into sleep state in the suspend callback
|we can accomplish two things.
|- minimize current leakage from
On 11/06/2014 01:07 PM, Sebastian Andrzej Siewior wrote:
This is mostly an equivalent for the 8250-omap driver based on a patch
of Dave Gerlach for the omap-serial driver (which is not yet merged).
From his changelog:
|By optionally putting the pins into sleep state in the suspend callback
On Thu, Nov 6, 2014 at 12:25 PM, Tony Lindgren t...@atomide.com wrote:
* Keerthy j-keer...@ti.com [141106 02:55]:
Fix DCDC3 volatge to 1.5V which is the right value to be supplied by
DCDC3 for all the boards.
Hmm so what about the comments for similar beaglebone changes
in thread [PATCH]
On 11/06/2014 08:15 PM, Nishanth Menon wrote:
sounds good to me *IF* omap8250_enable_wakeup (wakeirq handling) is
the way we want to continue doing things for daisychain? - Tony, can
you comment?
http://marc.info/?l=linux-omapm=141222144402707w=2
I wonder if wakeirq explicit handling is
On Thu, Nov 6, 2014 at 1:42 PM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
On 11/06/2014 08:15 PM, Nishanth Menon wrote:
sounds good to me *IF* omap8250_enable_wakeup (wakeirq handling) is
the way we want to continue doing things for daisychain? - Tony, can
you comment?
Hello Tony,
On 11/06/2014 07:52 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [140318 23:12]:
The GPMC driver includes arch/arm/mach-omap2/common.h but
does not use anything on that header so it can be removed.
Signed-off-by: Javier Martinez Canillas
* Nishanth Menon n...@ti.com [141106 11:59]:
On Thu, Nov 6, 2014 at 1:42 PM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
On 11/06/2014 08:15 PM, Nishanth Menon wrote:
sounds good to me *IF* omap8250_enable_wakeup (wakeirq handling) is
the way we want to continue doing things for
Thomas,
Any comments on the patch below? Let me know if you want to keep the
devm stuff out of kernel/irq/manage.c.
* Tony Lindgren t...@atomide.com [141001 20:45]:
Hi Thomas,
* Thomas Gleixner t...@linutronix.de [140919 12:47]:
The wakeup handler is supposed to bring the thing out of
Hi!
I actually had pm=0 on the command line, but I removed it now, and no
change: [...]
Let me try with explicit =1. .. aha, that helps. Thanks!
mh seems I actually missed to make 1 the default value. I will
prepare a patch for that.
I assume, that the example ofono commands work
On Thursday 06 November 2014 23:50:05 Pavel Machek wrote:
What is needed to get voice calls to work?
There's still a kernel driver missing in mainline for
exchanging voice data between the modem and the cpu (called
cmt-speech).
BTW the CMT driver should be removed from your kernel
On Thursday 06 November 2014 11:55 PM, Tony Lindgren wrote:
* Keerthy j-keer...@ti.com [141106 02:55]:
Fix DCDC3 volatge to 1.5V which is the right value to be supplied by
DCDC3 for all the boards.
Hmm so what about the comments for similar beaglebone changes
in thread [PATCH] ARM: dts:
Hi Suman,
On Thu, Nov 6, 2014 at 8:24 PM, Suman Anna s-a...@ti.com wrote:
Ping on this. Can you review the latest series v6 [1] and pick it up for
3.19? The MSM spinlock driver is also blocked/dependent on that series.
Sure, it's on my mind, I hope I'll get to it next week.
Thanks,
Ohad.
--
On Friday 07 November 2014 10:56 AM, Keerthy wrote:
On Friday 07 November 2014 12:59 AM, Robert Nelson wrote:
On Thu, Nov 6, 2014 at 12:25 PM, Tony Lindgren t...@atomide.com wrote:
* Keerthy j-keer...@ti.com [141106 02:55]:
Fix DCDC3 volatge to 1.5V which is the right value to be supplied by
On Friday 07 November 2014 12:59 AM, Robert Nelson wrote:
On Thu, Nov 6, 2014 at 12:25 PM, Tony Lindgren t...@atomide.com wrote:
* Keerthy j-keer...@ti.com [141106 02:55]:
Fix DCDC3 volatge to 1.5V which is the right value to be supplied by
DCDC3 for all the boards.
Hmm so what about the
On Thursday 06 November 2014 07:49 PM, Richard Cochran wrote:
On Mon, Oct 27, 2014 at 04:38:28PM +0530, Vignesh R wrote:
...
@@ -209,6 +214,7 @@ static void titsc_read_coordinates(struct titsc *ts_dev,
unsigned int read, diff;
unsigned int i, channel;
unsigned int creads
On Monday 03 November 2014 08:35 PM, Lee Jones wrote:
On Mon, 27 Oct 2014, Vignesh R wrote:
From: Brad Griffis bgrif...@ti.com
TSC interrupt handler had udelay to avoid reporting of false pen-up
interrupt to user space. This patch implements workaround suggesting in
Advisory 1.0.31 of
From: Brad Griffis bgrif...@ti.com
This patch makes the initial changes required to workaround TSC-false
pen-up interrupts. It is required to implement these changes in order to
remove udelay in the TSC interrupt handler and false pen-up events.
The charge step is to be executed immediately after
On Saturday 01 November 2014 02:39 AM, Hartmut Knaack wrote:
Vignesh R schrieb am 27.10.2014 12:08:
The charge delay value is by default 0xB000. But it can be set to lower
values on some boards as long as false pen-ups are avoided. Lowering the
value increases the sampling rate (though
On Saturday 01 November 2014 02:33 AM, Hartmut Knaack wrote:
Vignesh R schrieb am 27.10.2014 12:08:
From: Brad Griffis bgrif...@ti.com
This patch makes the initial changes required to workaround TSC-false
pen-up interrupts. It is required to implement these changes in order to
remove
This patch reads charge delay from tsc DT node and writes to
REG_CHARGEDELAY register. If the charge delay is not specified in DT
then default value of 0xB000(CHARGEDLY_OPENDLY) is used.
Signed-off-by: Vignesh R vigne...@ti.com
---
drivers/input/touchscreen/ti_am335x_tsc.c | 8 +++-
1 file
In one shot mode, sequencer automatically disables all enabled steps at
the end of each cycle. (both ADC steps and TSC steps) Hence these steps
need not be saved in reg_se_cache for clearing these steps at a later
stage.
Also, when ADC wakes up Sequencer should not be busy executing any of the
The charge delay value is by default 0xB000. But it can be set to lower
values on some boards as long as false pen-ups are avoided. Lowering the
value increases the sampling rate (though current sampling rate is
sufficient for tsc operation). Hence charge delay has been made a DT
parameter.
From: Brad Griffis bgrif...@ti.com
TSC interrupt handler had udelay to avoid reporting of false pen-up
interrupt to user space. This patch implements workaround suggesting in
Advisory 1.0.31 of silicon errata for am335x, thus eliminating udelay
and touchscreen lag. This also improves performance
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. Cursor jump due to false pen-up event.
The patches implement Advisory 1.0.31 in silicon errata of am335x-evm
to avoid false
On 7.11.2014 01:01, Pali Rohár wrote:
For voice calls you need:
* kernel driver cmt-speech (or it has some new name)
* cmt-speech userspace library (communication with kernel)
* pulseaudio modules which are using that library
Freemangordon (Ivaylo Dimitrov, CCed) should know more about it,
76 matches
Mail list logo
