On Friday 19 April 2013 06:19 AM, Jon Hunter wrote:
On 04/18/2013 07:34 PM, Jon Hunter wrote:
On 04/18/2013 06:10 PM, Jon Hunter wrote:
On 04/18/2013 04:34 PM, Kevin Hilman wrote:
...
Why not just init context right here if bank-loses_context
!bank-context_valid?
I really like this
On Thu, 2013-04-18 at 18:26 -0500, Jon Hunter wrote:
On 04/18/2013 06:24 PM, Jon Hunter wrote:
To get the values right for dt-GPMC-NAND-Config, here are the GPMC
config registers for chip-select 0, they are taken from u-boot
by doing md 0x6E60 7 on the u-boot shell:
On Tue, 16 Apr 2013 15:48:07 +0530, Kishon Vijay Abraham I kis...@ti.com
wrote:
On Tuesday 16 April 2013 01:20 AM, Grant Likely wrote:
On Mon, 15 Apr 2013 17:56:10 +0530, Kishon Vijay Abraham I kis...@ti.com
wrote:
On Monday 15 April 2013 05:04 PM, Grant Likely wrote:
On Wed, 20 Mar
Hi Benoit/Tony
I've consolidated all the USB host device tree patches for Panda and Beagles
to one place and addressed Tony's comments.
NOTE: patch 1 depends on OMAP clock binding introduced in
https://lkml.org/lkml/2013/4/12/407
v3:
- updated mux mode to use pulldowns on panda as non-DT boot
Rev. Ax/Bx boards have reversed polarity for USBHOST_PWR_ENable
signal when compared to Rev. C boards.
We create a new dts file for Ax/Bx boards.
Also update model and compatible flags for Rev. C board.
CC: Benoît Cousson b-cous...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
---
Use a common naming scheme mode0name.modename flags for the
USB host pins to be consistent.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts | 25 +
1 files changed, 13 insertions(+), 12 deletions(-)
diff --git
Provide RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Also provide pin multiplexer information for USB host
pins.
CC: Benoît Cousson b-cous...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3-beagle-xm.dts | 61
Provide the RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
The USB PHY needs AUXCLK3 to operate. Provide this information
as well.
Also provide pin multiplexer information for the USB host
pins.
CC: Benoît Cousson b-cous...@ti.com
Signed-off-by: Roger
Hi Kishon,
On 3/20/2013 2:41 PM, Kishon Vijay Abraham I wrote:
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle. To obtain a reference to the PHY
On Fri, 2013-04-19 at 11:01 +0200, Christoph Fritz wrote:
This is how u-boot GPMC config differs from final kernel configuration:
u-boot: GPMC_CONFIG1: 0x6e60: 0x1800
kernel: 0x1800
u-boot: GPMC_CONFIG2: 0x6e64: 0x00141400
On 04/18/2013 10:17 PM, Sourav Poddar wrote:
Hi Kevin,
On Thursday 18 April 2013 11:53 PM, Kevin Hilman wrote:
Hi Sourav,
Sourav Poddarsourav.pod...@ti.com writes:
Hi,
This patch series contains fixes and cleanups around the issue that
the console UART should not idled on suspend while
On 04/19/2013 04:01 AM, Christoph Fritz wrote:
On Thu, 2013-04-18 at 18:26 -0500, Jon Hunter wrote:
On 04/18/2013 06:24 PM, Jon Hunter wrote:
To get the values right for dt-GPMC-NAND-Config, here are the GPMC
config registers for chip-select 0, they are taken from u-boot
by doing md
On Fri, 2013-04-19 at 07:57 -0500, Jon Hunter wrote:
On 04/19/2013 04:01 AM, Christoph Fritz wrote:
I think you need to convert the register settings to ns and put those
values in the dts file.
yes, I already did so. Please see my last mail.
--
To unsubscribe from this list: send the line
Hi Kevin,
On Friday 19 April 2013 03:33 AM, Kevin Hilman wrote:
Sourav Poddarsourav.pod...@ti.com writes:
On Thursday 18 April 2013 11:35 PM, Kevin Hilman wrote:
Sourav Poddarsourav.pod...@ti.com writes:
Remove the OMAP_DEVICE_NO_IDLE_ON_SUSPEND check, since UART was the only one
making
On 04/19/2013 07:02 AM, Christoph Fritz wrote:
On Fri, 2013-04-19 at 11:01 +0200, Christoph Fritz wrote:
This is how u-boot GPMC config differs from final kernel configuration:
u-boot: GPMC_CONFIG1: 0x6e60: 0x1800
kernel: 0x1800
Hi Grygorii,
On Friday 19 April 2013 05:32 PM, Grygorii Strashko wrote:
On 04/18/2013 10:17 PM, Sourav Poddar wrote:
Hi Kevin,
On Thursday 18 April 2013 11:53 PM, Kevin Hilman wrote:
Hi Sourav,
Sourav Poddarsourav.pod...@ti.com writes:
Hi,
This patch series contains fixes and cleanups
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Friday 19 April 2013 06:19 AM, Jon Hunter wrote:
On 04/18/2013 07:34 PM, Jon Hunter wrote:
On 04/18/2013 06:10 PM, Jon Hunter wrote:
On 04/18/2013 04:34 PM, Kevin Hilman wrote:
...
Why not just init context right here if
On Friday 19 April 2013 07:35 PM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Friday 19 April 2013 06:19 AM, Jon Hunter wrote:
On 04/18/2013 07:34 PM, Jon Hunter wrote:
On 04/18/2013 06:10 PM, Jon Hunter wrote:
On 04/18/2013 04:34 PM, Kevin Hilman wrote:
Sourav Poddar sourav.pod...@ti.com writes:
[...]
Yes, got your point. omap_device_idle should not be called only
for console uart.
Just did a quick testing by including the following hunk on top of my
patch series..
diff --git a/arch/arm/mach-omap2/omap_device.c
On Fri, 2013-04-19 at 09:00 -0500, Jon Hunter wrote:
On 04/19/2013 07:02 AM, Christoph Fritz wrote:
so I hacked the missing values to omap2_nand_gpmc_retime():
From 8868823925441a824fe0d3143614482f25fb379b Mon Sep 17 00:00:00 2001
From: Christoph Fritz chf.fr...@googlemail.com
Date:
* Roger Quadros rog...@ti.com [130419 01:23]:
On 04/18/2013 11:09 PM, Tony Lindgren wrote:
the naming should be mode0name.modename to be consistent. Here's
what I dumped out, please check and replace spaces with tabs:
0x82 0x10c /*
* Santosh Shilimkar santosh.shilim...@ti.com [130419 07:43]:
On Friday 19 April 2013 07:35 PM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Friday 19 April 2013 06:19 AM, Jon Hunter wrote:
On 04/18/2013 07:34 PM, Jon Hunter wrote:
On 04/18/2013 06:10
On 04/19/2013 09:53 AM, Christoph Fritz wrote:
On Fri, 2013-04-19 at 09:00 -0500, Jon Hunter wrote:
On 04/19/2013 07:02 AM, Christoph Fritz wrote:
so I hacked the missing values to omap2_nand_gpmc_retime():
From 8868823925441a824fe0d3143614482f25fb379b Mon Sep 17 00:00:00 2001
From:
* Roger Quadros rog...@ti.com [130419 03:02]:
Hi Benoit/Tony
I've consolidated all the USB host device tree patches for Panda and Beagles
to one place and addressed Tony's comments.
NOTE: patch 1 depends on OMAP clock binding introduced in
https://lkml.org/lkml/2013/4/12/407
v3:
-
* Jon Hunter jon-hun...@ti.com [130419 08:41]:
On 04/19/2013 09:53 AM, Christoph Fritz wrote:
-static int omap2_nand_gpmc_retime(
- struct omap_nand_platform_data *gpmc_nand_data,
- struct gpmc_timings *gpmc_t)
-{
- struct
On 04/19/2013 10:48 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [130419 08:41]:
On 04/19/2013 09:53 AM, Christoph Fritz wrote:
-static int omap2_nand_gpmc_retime(
- struct omap_nand_platform_data *gpmc_nand_data,
- struct
* Jon Hunter jon-hun...@ti.com [130419 09:01]:
On 04/19/2013 10:48 AM, Tony Lindgren wrote:
What about DVFS though? The L3 clock can get rescaled with DVFS,
and after that the retime function needs to get called. We are
not doing it in the mainline tree, but at least n8x0 - n900 vendor
This patch removes omap2_nand_gpmc_retime() which was used to quirk
some timing values before gpmc_cs_set_timings(). Due to recent changes,
gpmc_cs_set_timings() has evolved so that there is no more need for a
retime function.
To keep the gpmc configuration consistent for legacy board files, this
Hi all,
Here's a list of breakage I've noticed so far while trying to
use linux next on my pandaboard es. Probably similar issues exist
on other boards as well.
Ideally we would not have any breakage by the merge window, so
let's try to get these fixed ASAP:
1. Serial console broken on panda es
On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote:
Hi all,
Here's a list of breakage I've noticed so far while trying to
use linux next on my pandaboard es. Probably similar issues exist
on other boards as well.
Ideally we would not have any breakage by the merge window, so
let's try
* Santosh Shilimkar santosh.shilim...@ti.com [130419 10:43]:
On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote:
Hi all,
Here's a list of breakage I've noticed so far while trying to
use linux next on my pandaboard es. Probably similar issues exist
on other boards as well.
On Friday 19 April 2013 11:14 PM, Tony Lindgren wrote:
* Santosh Shilimkar santosh.shilim...@ti.com [130419 10:43]:
On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote:
Hi all,
Here's a list of breakage I've noticed so far while trying to
use linux next on my pandaboard es. Probably
* Santosh Shilimkar santosh.shilim...@ti.com [130419 10:56]:
On Friday 19 April 2013 11:14 PM, Tony Lindgren wrote:
* Santosh Shilimkar santosh.shilim...@ti.com [130419 10:43]:
On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote:
Hi all,
Here's a list of breakage I've noticed so far
Hi,
On Wed, Apr 17, 2013 at 08:39:37PM -0700, Tony Lindgren wrote:
The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
are available in the git repository at:
When a gpio interrupt is masked, the gpio event will still be latched in
the interrupt status register so when you unmask it later you may get an
interrupt straight away. However, if the interrupt is disabled then gpio
events occurring will not be latched/stored.
Signed-off-by: Andreas Fenkart
Hi Felipe,
On Fri, Apr 12, 2013 at 02:07:01PM +0300, Felipe Balbi wrote:
[snip]
Signed-off-by: Andreas Fenkart andreas.fenk...@streamunlimited.com
---
Patch is incomplete and still confusing ;-) if some one reads the
patch without the thread. I think you have already ask the question/
* Olof Johansson o...@lixom.net [130419 11:50]:
Hi,
On Wed, Apr 17, 2013 at 08:39:37PM -0700, Tony Lindgren wrote:
The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
are available in the git repository at:
OMAP devices support various NAND transfer modes.
Currently all device-tree definitions will use the default prefetch
polled mode, so this patch enables the transfer mode to be specified
in the device-tree.
---
.../devicetree/bindings/mtd/gpmc-nand.txt |8
On 04/19/2013 07:21 PM, Nishanth Menon wrote:
On 14:55-20130419, Taras Kondratiuk wrote:
Using a voltage tolerance for doing DVFS is not a proper way.
It leads to a few issues:
- voltage is limited to a narrow range near OPP voltage,
so other consumers of the same regulator can't set
39 matches
Mail list logo
