Hi,
On Wed, May 09, 2012 at 08:00:41AM +0300, Sakari Ailus wrote:
The OMAP 3630 has configuration how the ISP CSI-2 PHY pins are connected to
the actual CSI-2 receivers outside the ISP itself. Allow changing this
configuration from the ISP driver.
Signed-off-by: Sakari Ailus
On 05/08/12 19:24, Greg Kroah-Hartman wrote:
On Tue, May 08, 2012 at 10:53:44AM +0300, Igor Grinberg wrote:
On 05/07/12 17:48, Alan Stern wrote:
On Mon, 7 May 2012, Igor Grinberg wrote:
On 05/07/12 17:04, Alan Stern wrote:
On Sun, 6 May 2012, Igor Grinberg wrote:
Hi Alan,
...
Sorry,
The DMADISABLE bit is a semi-automatic bit present in sysconfig register
of some modules. When the DMA must perform read/write accesses, the
DMADISABLE bit is cleared by the hardware. But when the DMA must stop for power
management, software must set the DMADISABLE bit back to 1.
In cases where
Hi,
On Mon, May 7, 2012 at 3:36 PM, Tony Lindgren t...@atomide.com wrote:
The following changes since commit 69964ea4c7b68c9399f7977aa5b9aa6539a6a98a:
[..]
Enrico Butera (1):
ARM: OMAP: igep0020: fix smsc911x dummy regulator id
Hmm. Picking 40 without any kind of comment in the code
Hi Dmitry ,
On Wed, May 9, 2012 at 10:48 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Ho Sourav,
On Thu, Apr 26, 2012 at 11:24:37AM +0530, Sourav Poddar wrote:
-config KEYBOARD_OMAP4
- tristate TI OMAP4 keypad support
+config KEYBOARD_OMAP4+
I think this works purely by
On Wed, May 9, 2012 at 12:24 PM, Poddar, Sourav sourav.pod...@ti.com wrote:
Hi Dmitry ,
On Wed, May 9, 2012 at 10:48 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Ho Sourav,
On Thu, Apr 26, 2012 at 11:24:37AM +0530, Sourav Poddar wrote:
-config KEYBOARD_OMAP4
- tristate TI
On Mon, 2012-05-07 at 15:21 -0400, Ashwin Bihari wrote:
Use the generic DSS panel driver that provides support for
the 4.3 Sharp LQ043T1DG01 that comes standard on the
OMAP3530 SOM-LV and Torpedo DevKits.
Signed-off-by: Ashwin Bihari ashwin.bih...@logicpd.com
---
When PHY reset pin is connected to a GPIO on external GPIO chip
(e.g. I2C), we should not call the gpio_set_value() function, but
gpio_set_value_cansleep().
Signed-off-by: Igor Grinberg grinb...@compulab.co.il
Acked-by: Felipe Balbi ba...@ti.com
Tested-by: Govindraj.R govindraj.r...@ti.com
Hello,
Changes since v1:
- rebased on 3.4-rc6
Original intro message:
This series adds common configuration for the V1V8, V2V1 regulators from
twl6030. These regulators are commonly used to feed the twl6040 audio IC on
OMAP4 based boards (SDP4430, PandaBoards).
The regulator support for the
V1V8 supply from twl6030 commonly used as VIO for the machine.
V2V1 is adviced to supply the twl6040, and also to feed the twl6030's
VCXIO_IN, and VDAC_IN inputs.
Create the common regulator configurations for these regulators:
Make the V2V1 as supply_regulator for VCXIO, VDAC.
Add twl6040
These supplies going to be needed for the twl6040 driver.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-4430sdp.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/board-4430sdp.c
These supplies going to be needed for the twl6040 driver.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-omap4panda.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap4panda.c
Hi Dmitry ,
On Wed, May 9, 2012 at 10:48 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Ho Sourav,
On Thu, Apr 26, 2012 at 11:24:37AM +0530, Sourav Poddar wrote:
-config KEYBOARD_OMAP4
- tristate TI OMAP4 keypad support
+config KEYBOARD_OMAP4+
I think this works
On Tue, 2012-05-08 at 17:17 -0700, Tony Lindgren wrote:
* Artem Bityutskiy dedeki...@gmail.com [120508 07:02]:
From: Artem Bityutskiy artem.bityuts...@linux.intel.com
SX1 board requirese i2c, so select it in Kconfig, otherwise I have the
following build error:
Thanks applying into
On Wed, May 09, 2012 at 01:29:28AM +0100, Tony Lindgren wrote:
* Ivan Djelic ivan.dje...@parrot.com [120426 05:23]:
Hello,
Here is version 3 of this patch after review from Tony Lindgren.
This version adds a separate initialization function mostly to check CPU
compatibility. This check
On Mon, 2012-05-07 at 10:46 -0700, Tony Lindgren wrote:
Hi,
* Tomi Valkeinen tomi.valkei...@ti.com [120503 07:01]:
Hi,
I started cleaning up and restructuring omapdss for device tree, and here's
the
first set of patches from that ordeal. There's nothing DT specific in these
On Wed, May 09, 2012 at 01:29:28AM +0100, Tony Lindgren wrote:
* Ivan Djelic ivan.dje...@parrot.com [120426 05:23]:
Hello,
Here is version 3 of this patch after review from Tony Lindgren.
This version adds a separate initialization function mostly to check CPU
compatibility. This check
Op 9 mei 2012, om 02:39 heeft Woodruff, Richard het volgende geschreven:
From: Hilman, Kevin
Sent: Tuesday, May 08, 2012 5:17 PM
A basic OMAP AVS driver has been in mainline for a long time, yet we
have not seen support submitted for all of these features.
1.5/3.5 is a feature.
ABB
On Tue, 2012-05-08 at 18:55 -0500, Ricardo Neri wrote:
Hi Tomi,
Thanks for taking the time to comment.
On 05/07/2012 06:43 AM, Tomi Valkeinen wrote:
Hi,
On Thu, 2012-05-03 at 20:44 -0500, Ricardo Neri wrote:
Implement the DSS device driver audio support interface in the HDMI
panel
On Wed, May 9, 2012 at 8:48 AM, Olof Johansson o...@lixom.net wrote:
Hi,
On Mon, May 7, 2012 at 3:36 PM, Tony Lindgren t...@atomide.com wrote:
The following changes since commit 69964ea4c7b68c9399f7977aa5b9aa6539a6a98a:
[..]
Enrico Butera (1):
ARM: OMAP: igep0020: fix smsc911x dummy
On Wed, May 9, 2012 at 3:25 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Tue, May 08, 2012 at 07:31:57PM +0530, Shilimkar, Santosh wrote:
Ok. Assuming you mean it's _not_ cleaner to have two domains where
manager overrides XN attributes Note that DRAM can be in the middle of
On Wed, May 09, 2012 at 04:08:09, Hilman, Kevin wrote:
Vaibhav Hiremath hvaib...@ti.com writes:
The function __omap2_set_globals() can be common across all
platforms/architectures, even in case of omap4, internally it
calls same set of functions as in __omap2_set_globals() function
Tony,
[snip]
-#if defined(CONFIG_ARCH_OMAP4) !(defined(CONFIG_ARCH_OMAP2) || \
- defined(CONFIG_ARCH_OMAP3))
+#if (defined(CONFIG_ARCH_OMAP5) || defined(CONFIG_ARCH_OMAP4)) \
+ !(defined(CONFIG_ARCH_OMAP2) || defined(CONFIG_ARCH_OMAP3))
On Wed, May 09, 2012 at 04:20:06, Hilman, Kevin wrote:
Vaibhav Hiremath hvaib...@ti.com writes:
This patch cleans up dpll_data structure, making structure
fields definition based on feature availability for given SoC,
managed using Kconfig rules.
SOC_HAS_OMAP3_DPLL_IDLE: idle state
On Wed, May 09, 2012 at 01:38:34, Tony Lindgren wrote:
* Vaibhav Hiremath hvaib...@ti.com [120508 08:32]:
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -123,8 +123,11 @@ config SOC_OMAPTI81XX
config SOC_OMAPAM33XX
bool AM33XX support
- depends on
Hi Dmitry,
I did some minor fixes to the patch which you suggested above and
the keypad is functional now.
Changes:
- Move pm_runtime_enable before using pm_runtime_get_sync.
Sending the patch inlined..(also attached).
From: G, Manjunath Kondaiah manj...@ti.com
Date: Mon, 10 Oct 2011 20:52:05
On Tuesday 08 May 2012 06:05 PM, Archit Taneja wrote:
On Tuesday 08 May 2012 05:25 PM, Tomi Valkeinen wrote:
On Tue, 2012-05-08 at 16:52 +0530, Archit Taneja wrote:
On Tuesday 08 May 2012 04:20 PM, Tomi Valkeinen wrote:
Checking the validity of all the settings is a bit tricky, but
Hi Dmitry,
On Wed, May 9, 2012 at 3:14 PM, Poddar, Sourav sourav.pod...@ti.com wrote:
Hi Dmitry,
I did some minor fixes to the patch which you suggested above and
the keypad is functional now.
Changes:
- Move pm_runtime_enable before using pm_runtime_get_sync.
Sending the patch
An overlay manager's timings (the manager size, and blanking parameters if an
LCD manager) are DISPC shadow registers, and they should hence follow the
correct programming model.
This set makes the timings an extra_info parameter in manager's private data .
The interface drivers now apply the
DISPC manager size and DISPC manager blanking parameters(for LCD managers)
follow the shadow register programming model. Currently, they are programmed
directly by the interface drivers.
To configure manager timings using APPLY, there is a need to introduce extra
info flags for managers, similar
Replace the function dispc_mgr_set_timings() with dss_mgr_set_timings() in the
interface drivers. The latter function ensures that the timing related DISPC
registers are configured according to the shadow register programming model.
Remove the call to dispc_mgr_go() in dpi_set_timings() as the
Create a function dss_mgr_check_timings() which wraps around the function
dispc_mgr_timings_ok(). This is mainly a clean up to hide dispc functions
from interface drivers.
dss_mgr_check_timings() is added in the function dss_mgr_check(), it currently
takes the timings maintained in the
If a manager is disabled, there is no guarantee at any point in time that all
it's parameters are configured. There is always a chance that some more
parameters are yet to be configured by a user of DSS, or by DSS itself.
However, when the manager is enabled, we can be certain that all the
In order to check the validity of overlay and manager info, there was a need to
use the omap_dss_device struct to get the panel resolution. The manager's
private data in APPLY now contains the manager timings. Hence, we don't need to
rely on the display resolution any more.
Pass the manager's
The DPI and HDMI interfaces use their 'set_timing' functions to take in a new
set of timings. If the panel is disabled, they do not disable and re-enable
the interface. Currently, the manager timings are applied in hdmi_power_on()
and dpi_set_mode() respectively, these are not called by
The omap_dss_device pointer declared in dss_ovl_setup_fifo() isn't used. Remove
the pointer variable declaration and it's assignment.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/apply.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git
The pixel clock rate for the TV manager is calculated by checking the device
type connected to the manager, and then requesting the VENC/HDMI interface for
the pixel clock rate.
Remove the use of omap_dss_device pointer from here by checking which interface
generates the pixel clock by reading
The functions calc_fclk_five_taps() and check_horiz_timing_omap3() use the
function dispc_mgr_get_device() to get the omap_dss_device pointer to which
the manager is connected, the width of the panel is derived from it.
The manager's timing is stored in it's private data in APPLY. This contains
On Fri, 2012-04-20 at 09:55 -0700, Tony Lindgren wrote:
* Tero Kristo t-kri...@ti.com [120420 01:24]:
Hi,
What happened with this pull request? It doesn't seem to be in 3.4 at
least.
There was a boot issue on omap3 evm and that branch got dropped.
Will merge it again after Paul has
On Wed, 2012-05-09 at 15:23 +0530, Archit Taneja wrote:
On Tuesday 08 May 2012 06:05 PM, Archit Taneja wrote:
On Tuesday 08 May 2012 05:25 PM, Tomi Valkeinen wrote:
On Tue, 2012-05-08 at 16:52 +0530, Archit Taneja wrote:
On Tuesday 08 May 2012 04:20 PM, Tomi Valkeinen wrote:
Checking
On Wed, May 09, 2012 at 00:09:34, Hilman, Kevin wrote:
Vaibhav Hiremath hvaib...@ti.com writes:
With addition to TI81XX, AM33XX family of devices, the number
of interrupts supported has increased to 128, compared to 96.
The current implementation for irq handling is hardcoded to use
96
On Wed, May 09, 2012 at 09:50:28AM +0100, Shilimkar, Santosh wrote:
On Wed, May 9, 2012 at 3:25 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Tue, May 08, 2012 at 07:31:57PM +0530, Shilimkar, Santosh wrote:
Ok. Assuming you mean it's _not_ cleaner to have two domains where
From: Jean Pihet j-pi...@ti.com
One of the main contributors of the low power code latency is
the PER power domain. To optimize the high-performance and
low-latency C1 state, prevent any PER state which is lower
than the CORE state in C1.
Reported and suggested by Kevin Hilman.
Reported-by:
From: Jean Pihet j-pi...@ti.com
It is not needed to iterate through all the clock domains of a
power domain in order to allow or deny it to idle.
This patch allows or denies only the first registered clock domain
of a power domain, and so optimizes the latency of the low power
code. The functions
Hi Kevin and Jon,
On 5/8/2012 11:22 PM, Kevin Hilman wrote:
Jon Hunterjon-hun...@ti.com writes:
Hi Benoit,
On 05/08/2012 06:01 AM, Cousson, Benoit wrote:
[...]
P.S. Please note there is also already a different fix in mainline for
the EMU clkdm data from Paul which adds the force
Hi Kevin,
On Mon, May 7, 2012 at 7:31 PM, Kevin Hilman khil...@ti.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
On Tue, May 1, 2012 at 7:27 PM, Kevin Hilman khil...@ti.com wrote:
Jean Pihet jean.pi...@newoldbits.com writes:
HI Kevin, Grazvydas,
On Tue, Apr 24, 2012 at 4:29 PM,
Hi Sakari,
Thanks for the patch.
On Wednesday 09 May 2012 08:00:41 Sakari Ailus wrote:
The OMAP 3630 has configuration how the ISP CSI-2 PHY pins are connected to
the actual CSI-2 receivers outside the ISP itself. Allow changing this
configuration from the ISP driver.
Signed-off-by: Sakari
Hi Olof,
On Tuesday 08 May 2012 23:48:06 Olof Johansson wrote:
Hi,
On Mon, May 7, 2012 at 3:36 PM, Tony Lindgren t...@atomide.com wrote:
The following changes since commit
69964ea4c7b68c9399f7977aa5b9aa6539a6a98a:
[..]
Enrico Butera (1):
ARM: OMAP: igep0020: fix smsc911x dummy
On Wed, 2012-05-09 at 15:40 +0530, Archit Taneja wrote:
An overlay manager's timings (the manager size, and blanking parameters if an
LCD manager) are DISPC shadow registers, and they should hence follow the
correct programming model.
This set makes the timings an extra_info parameter in
Initially, we decided to make am33xx family of device to fall
under omap3 class (cpu_is_omap34xx() = true), since it carries
Cortex-A8 core. But while adding complete baseport support
(like, clock, power and hwmod) support, it is observed that,
we are creating more and more problems by treating
On Wednesday 09 May 2012 04:43 PM, Tomi Valkeinen wrote:
On Wed, 2012-05-09 at 15:40 +0530, Archit Taneja wrote:
An overlay manager's timings (the manager size, and blanking parameters if an
LCD manager) are DISPC shadow registers, and they should hence follow the
correct programming model.
Am 03.05.2012 13:09, schrieb Javier Martinez Canillas:
On Wed, May 2, 2012 at 1:42 PM, Thomas Klute
thomas2.kl...@uni-dortmund.de wrote:
Am 01.04.2012 21:20, schrieb Javier Martinez Canillas:
On Fri, Mar 30, 2012 at 5:28 PM, Thomas Klute
thomas2.kl...@uni-dortmund.de wrote:
Hi,
I finally
On Wed, 2012-05-09 at 16:54 +0530, Archit Taneja wrote:
On Wednesday 09 May 2012 04:43 PM, Tomi Valkeinen wrote:
On Wed, 2012-05-09 at 15:40 +0530, Archit Taneja wrote:
An overlay manager's timings (the manager size, and blanking parameters if
an
LCD manager) are DISPC shadow registers,
On Wed, May 09, 2012 at 02:20:28PM +0530, Shilimkar, Santosh wrote:
The only change done common code is clearing 'XN' bit for DRAM
region in page table entries. The other change of setting the DACR
register is done in ARMv7 specific code.
Yes, XN is an ARMv6+ thing. Before ARMv5, it was
On Mon, Apr 23, 2012 at 9:34 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
For the full text, please see
http://lists.arm.linux.org.uk/lurker/message/20120418.100954.7fa7acf8.en.html
This version contains updates for some of the comments received from the
previous round, and
On Tuesday 08 May 2012, Jassi Brar wrote:
On 8 May 2012 22:05, Stephen Warren swar...@wwwdotorg.org wrote:
The data doesn't need to be part of the DMA controller node in order for
the DMA controller driver to be the entity interpreting it.
I rather say, if the dma controller driver is
Cleanup probe and remove routines, use devm_* functions for
managing resources.
Also, in under free_master label, change use of kfree() into
spi_master_put().
CC: grant.lik...@secretlab.ca
CC: t...@atomide.com
Signed-off-by: Hannu Heikkinen hann...@iki.fi
---
drivers/spi/spi-omap2-mcspi.c |
On Wed, May 9, 2012 at 1:16 AM, Tony Lindgren t...@atomide.com wrote:
* Javier Martinez Canillas jav...@dowhile0.org [120427 02:33]:
On Wed, Apr 25, 2012 at 9:59 AM, Enric Balletbò i Serra
eballe...@gmail.com wrote:
Tony, as this is a fix ,may be included ?
Acked-by: Enric Balletbo i
Hi Laurent,
Thanks for the review!
On Wed, May 09, 2012 at 01:01:34PM +0200, Laurent Pinchart wrote:
Hi Sakari,
Thanks for the patch.
On Wednesday 09 May 2012 08:00:41 Sakari Ailus wrote:
The OMAP 3630 has configuration how the ISP CSI-2 PHY pins are connected to
the actual CSI-2
On Wednesday 09 May 2012, Dave Chinner wrote:
In low end flash devices, some requests might take too long than normal
due to background device maintenance (i.e flash erase / reclaim procedure)
kicking in in the context of an ongoing write, stalling them by several
orders of magnitude.
On Wednesday 09 May 2012, kdorf...@codeaurora.org wrote:
+static bool mmc_can_do_foreground_hpi(struct mmc_queue *mq,
+ struct request *req, unsigned int thpi)
+{
+
+ /*
+ * If some time has elapsed since the issuing of previous write
+ * command, or
On Wed, May 9, 2012 at 2:05 PM, kdorf...@codeaurora.org wrote:
+static bool mmc_can_do_foreground_hpi(struct mmc_queue *mq,
+ struct request *req, unsigned int thpi)
+{
+
+ /*
+ * If some time has elapsed since the issuing of previous write
+ * command,
Hi Sakari,
On Wednesday 09 May 2012 16:43:08 Sakari Ailus wrote:
On Wed, May 09, 2012 at 01:01:34PM +0200, Laurent Pinchart wrote:
On Wednesday 09 May 2012 08:00:41 Sakari Ailus wrote:
The OMAP 3630 has configuration how the ISP CSI-2 PHY pins are connected
to the actual CSI-2 receivers
On Wed, May 09, 2012 at 01:59:40PM +, Arnd Bergmann wrote:
My feeling is that we should just treat every (REQ_SYNC | REQ_READ)
request the same and let them interrupt long-running writes,
independent of whether it's REQ_META or demand paging.
It's funny that the CFQ scheduler used to boost
* Laurent Pinchart laurent.pinch...@ideasonboard.com [120509 04:09]:
Hi Olof,
On Tuesday 08 May 2012 23:48:06 Olof Johansson wrote:
Hi,
On Mon, May 7, 2012 at 3:36 PM, Tony Lindgren t...@atomide.com wrote:
The following changes since commit
69964ea4c7b68c9399f7977aa5b9aa6539a6a98a:
* Enrico Butera ebut...@users.sourceforge.net [120509 02:32]:
From: Enrico Butera ebut...@users.berlios.de
id 0 is already used and causes errors at boot:
WARNING: at fs/sysfs/dir.c:508 sysfs_add_one+0x9c/0xac()
sysfs: cannot create duplicate filename
On Mon, May 07, 2012 at 10:16:30PM +0530, S, Venkatraman wrote:
[..]
This feature doesn't fiddle with the I/O scheduler's ability to balance
read vs write requests or handling requests from various process queues (CFQ).
Does this feature work with CFQ? As CFQ does not submit sync IO (for
Tomi,
In drivers/video/omap2/omapfb/omapfb-main.c:
static int omapfb_parse_vram_param(const char *param, int max_entries,
unsigned long *sizes, unsigned long *paddrs)
{
int fbnum;
unsigned long size;
unsigned long paddr = 0;
char *p, *start;
* Ivan Djelic ivan.dje...@parrot.com [120509 01:15]:
On Wed, May 09, 2012 at 01:29:28AM +0100, Tony Lindgren wrote:
* Ivan Djelic ivan.dje...@parrot.com [120426 05:23]:
Hello,
Here is version 3 of this patch after review from Tony Lindgren.
This version adds a separate
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, May 08, 2012 8:13 PM
To: Ashwin Bihari
Cc: linux-omap; Tomi Valkeinen
Subject: Re: [PATCH 2/2] Add LCD support for the LogicPD OMAP3530 DevKits
* Ashwin Bihari ashwin.bih...@logicpd.com [120507 12:41]:
Hi Olof,
Here's this one updated to drop the non-regression patch and to use updated
version of Enrico's patch. The other two patches are the same.
Regards,
Tony
The following changes since commit 69964ea4c7b68c9399f7977aa5b9aa6539a6a98a:
Linux 3.4-rc5 (2012-04-29 15:19:10 -0700)
are
-Original Message-
From: Tomi Valkeinen [mailto:tomi.valkei...@ti.com]
Sent: Wednesday, May 09, 2012 3:16 AM
To: Ashwin Bihari
Cc: linux-omap; Tony Lindgren
Subject: Re: [PATCH 2/2] Add LCD support for the LogicPD OMAP3530 DevKits
snip
+static int
* Tomi Valkeinen tomi.valkei...@ti.com [120509 01:12]:
Below is the pull request for board file related changes. Tested on
panda 4430sdp.
Thanks, I've merged that into clenaup-dss branch and will send it
along with other still pending cleanup branches.
How should I manage my tree related
On Wed, May 09, 2012 at 06:00:10PM +0530, Shilimkar, Santosh wrote:
On Wed, May 9, 2012 at 5:53 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Wed, May 09, 2012 at 02:20:28PM +0530, Shilimkar, Santosh wrote:
The only change done common code is clearing 'XN' bit for DRAM
On Wed, 2012-05-09 at 10:38 -0500, Ashwin Bihari wrote:
-Original Message-
From: Tomi Valkeinen [mailto:tomi.valkei...@ti.com]
Sent: Wednesday, May 09, 2012 3:16 AM
To: Ashwin Bihari
Cc: linux-omap; Tony Lindgren
Subject: Re: [PATCH 2/2] Add LCD support for the LogicPD OMAP3530
Hi Neil,
On Wed, Apr 25, 2012 at 01:05:24PM +1000, NeilBrown wrote:
Most of the interrupts that come through this line should trigger
wakeups:
power button
RTC alarm
power available
usb plug/unplug
so mark the interrupt as a wakeup interrupt.
This is particularly important for
Hi Tomi,
* Russ Dill russ.d...@ti.com [120508 19:52]:
This removes several boot warnings from board-omap3beagle.c:
- gpio_request: gpio--22 (DVI reset) status -22
- Unable to get DVI reset GPIO
There is a combination of leftover code and revision confusion.
Additionally, xM support is
Hi Neil,
On Wed, Apr 25, 2012 at 05:33:11PM +1000, NeilBrown wrote:
The charger needs usb3v1 to be running, so add a new consumer to
keep it running.
This allows the charger to draw current even when the USB driver has
powered down.
Signed-off-by: NeilBrown ne...@suse.de
---
* R, Sricharan r.sricha...@ti.com [120509 02:09]:
Tony,
[snip]
-#if defined(CONFIG_ARCH_OMAP4) !(defined(CONFIG_ARCH_OMAP2) || \
- defined(CONFIG_ARCH_OMAP3))
+#if (defined(CONFIG_ARCH_OMAP5) || defined(CONFIG_ARCH_OMAP4)) \
+
On Wed, May 9, 2012 at 8:35 AM, Tony Lindgren t...@atomide.com wrote:
Hi Olof,
Here's this one updated to drop the non-regression patch and to use updated
version of Enrico's patch. The other two patches are the same.
Pulled, thanks!
-Olof
--
To unsubscribe from this list: send the line
Vaibhav,
Thanks for your help on this. I was unaware that the Kernel changed
the pin-mux after U-boot did the initial setup. Applying this fix to
the linux kernel fixed the problem. Much appreciated,
Neil Johnson
On Mon, May 7, 2012 at 11:21 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Wed, May 9, 2012 at 8:55 AM, Tony Lindgren t...@atomide.com wrote:
Hi Tomi,
* Russ Dill russ.d...@ti.com [120508 19:52]:
This removes several boot warnings from board-omap3beagle.c:
- gpio_request: gpio--22 (DVI reset) status -22
- Unable to get DVI reset GPIO
There is a combination
* Russ Dill russ.d...@ti.com [120509 09:29]:
On Wed, May 9, 2012 at 8:55 AM, Tony Lindgren t...@atomide.com wrote:
Hi Tomi,
* Russ Dill russ.d...@ti.com [120508 19:52]:
This removes several boot warnings from board-omap3beagle.c:
- gpio_request: gpio--22 (DVI reset) status -22
-
On Thu, May 3, 2012 at 6:57 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
The driver for the TFP410 chip should handle the power-down signal of
the chip, instead of the current way of handling it in the board files.
This patch adds power_down_gpio into the device's platform data, and
adds
On Wednesday 09 May 2012, Christoph Hellwig wrote:
On Wed, May 09, 2012 at 01:59:40PM +, Arnd Bergmann wrote:
My feeling is that we should just treat every (REQ_SYNC | REQ_READ)
request the same and let them interrupt long-running writes,
independent of whether it's REQ_META or demand
On Wed, May 9, 2012 at 9:36 AM, Tony Lindgren t...@atomide.com wrote:
* Russ Dill russ.d...@ti.com [120509 09:29]:
On Wed, May 9, 2012 at 8:55 AM, Tony Lindgren t...@atomide.com wrote:
Hi Tomi,
* Russ Dill russ.d...@ti.com [120508 19:52]:
This removes several boot warnings from
* Paul Walmsley p...@pwsan.com [120508 17:37]:
Hi Tony,
this pull request is for some hwmod data additions for v3.5. It
is based on top of the commits in the omap-devel-b-for-3.5 tag.
Thanks pulling into devel-hwmod-data.
Tony
--
To unsubscribe from this list: send the line unsubscribe
* Peter Ujfalusi peter.ujfal...@ti.com [120509 00:37]:
Hello,
Changes since v1:
- rebased on 3.4-rc6
Original intro message:
This series adds common configuration for the V1V8, V2V1 regulators from
twl6030. These regulators are commonly used to feed the twl6040 audio IC on
OMAP4 based
Hi,
* Uri Yosef ur...@variscite.com [120312 03:23]:
From: Uri yosef ur...@variscite.com
Hi Tony,
This patch add device tree support for Variscite OMAP4 System-On-Modeule.
Do you have an updated version of this available now that MMC mostly works?
Regards,
Tony
--
To unsubscribe from
On Wed, 2012-05-09 at 09:50 -0700, Russ Dill wrote:
On Thu, May 3, 2012 at 6:57 AM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
The driver for the TFP410 chip should handle the power-down signal of
the chip, instead of the current way of handling it in the board files.
This patch adds
* Vaibhav Hiremath hvaib...@ti.com [120503 01:02]:
Current OMAP code supports couple of clocksource options based
on compilation flag (CONFIG_OMAP_32K_TIMER). The 32KHz sync-timer
and a gptimer which can run on 32KHz or system clock (e.g 38.4 MHz)
I'll apply these into cleanup-timer branch
* Grazvydas Ignotas nota...@gmail.com [120505 17:00]:
Each irq_chip for the main interrupt controller has offsets set for irq
masking registers, which added to respective base results in a pointer
to appropriate hardware register. However this is not correct for
INTC_CONTROL as there is only
Hi Benoit,
On 05/09/2012 05:58 AM, Cousson, Benoit wrote:
Hi Kevin and Jon,
On 5/8/2012 11:22 PM, Kevin Hilman wrote:
Jon Hunterjon-hun...@ti.com writes:
Hi Benoit,
On 05/08/2012 06:01 AM, Cousson, Benoit wrote:
[...]
P.S. Please note there is also already a different fix in
From: Tomi Valkeinen [mailto:tomi.valkei...@ti.com]
Sent: Wednesday, May 09, 2012 11:52 AM
To: Ashwin Bihari
Cc: linux-omap; Tony Lindgren
Subject: RE: [PATCH 2/2] Add LCD support for the LogicPD OMAP3530 DevKits
On Wed, 2012-05-09 at 10:38 -0500, Ashwin Bihari wrote:
-Original
Woodruff, Richard r-woodru...@ti.com writes:
From: Hilman, Kevin
Sent: Tuesday, May 08, 2012 5:17 PM
A basic OMAP AVS driver has been in mainline for a long time, yet we
have not seen support submitted for all of these features.
1.5/3.5 is a feature.
And I'm still waiting for it to be
* Vaibhav Hiremath hvaib...@ti.com [120509 04:28]:
Initially, we decided to make am33xx family of device to fall
under omap3 class (cpu_is_omap34xx() = true), since it carries
Cortex-A8 core. But while adding complete baseport support
(like, clock, power and hwmod) support, it is observed
On 05/08/2012 01:09 PM, Jassi Brar wrote:
On 8 May 2012 22:05, Stephen Warren swar...@wwwdotorg.org wrote:
The data doesn't need to be part of the DMA controller node in order for
the DMA controller driver to be the entity interpreting it.
I rather say, if the dma controller driver is the
On 05/09/2012 01:04 PM, Jon Hunter wrote:
Hi Benoit,
On 05/09/2012 05:58 AM, Cousson, Benoit wrote:
Hi Kevin and Jon,
On 5/8/2012 11:22 PM, Kevin Hilman wrote:
Jon Hunterjon-hun...@ti.com writes:
Hi Benoit,
On 05/08/2012 06:01 AM, Cousson, Benoit wrote:
[...]
P.S. Please note
Hi Peter,
On Wed, May 02, 2012 at 04:54:42PM +0300, Peter Ujfalusi wrote:
twl6040 has three power supply source:
VBAT needs to be connected to VBAT, VIO, and V2V1.
Add regulator support for the VIO, V2V1 supplies.
Initially handle the two supply together with bulk commands.
Signed-off-by:
On 05/04/2012 03:57 PM, Tony Lindgren wrote:
* Stephen Warren swar...@wwwdotorg.org [120504 12:27]:
On 05/02/2012 11:24 AM, Tony Lindgren wrote:
diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-simple.txt
b/Documentation/devicetree/bindings/pinctrl/pinctrl-simple.txt
...
On
1 - 100 of 144 matches
Mail list logo
