* Jonathan Cameron ji...@cam.ac.uk [100607 19:55]:
Signed-off-by: Jonathan Cameron ji...@cam.ac.uk
---
I'm not a user of this code but was browsing the kautobuild logs
and saw the igep0020 build error that has been there since
24th of May using the defconfig. Looks like a trivial
* Peter Ujfalusi peter.ujfal...@nokia.com [100602 15:09]:
On Wednesday 02 June 2010 12:15:22 ext Liam Girdwood wrote:
On Wed, 2010-06-02 at 12:05 +0300, Peter Ujfalusi wrote:
Hi,
On Tuesday 01 June 2010 14:18:19 Ujfalusi Peter (Nokia-D/Tampere) wrote:
..
Liam if you are
On Wed, Jun 9, 2010 at 1:22 PM, Thomas Gleixner t...@linutronix.de wrote:
Though we could change that conditionally - the default would still be
the freeze of jiffies and CLOCK_MONOTONIC for historical compability.
If I were to change it only for our implementation, and make all the
user space
* Madhusudhan madhu...@ti.com [100602 20:13]:
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Gadiyar, Anand
Sent: Friday, May 28, 2010 2:55 PM
To: Stephen Schwarm, CSDP; linux-omap@vger.kernel.org
Subject:
* Sergio Aguirre saagui...@ti.com [100608 23:35]:
This fixes the following warning:
drivers/mmc/host/omap_hsmmc.c: In function 'omap_hsmmc_suspend':
drivers/mmc/host/omap_hsmmc.c:2275: warning: unused variable 'state'
Introduced by commit ID:
commit
On Wed, Jun 9, 2010 at 7:58 PM, Tony Lindgren t...@atomide.com wrote:
* Govindraj govindraj...@gmail.com [100607 17:50]:
On Mon, Jun 7, 2010 at 5:02 PM, Govindraj govindraj...@gmail.com wrote:
On Mon, Jun 7, 2010 at 3:36 PM, Tony Lindgren t...@atomide.com wrote:
* Kevin Hilman
On Thursday, June 10, 2010, Neil Brown wrote:
On Wed, 9 Jun 2010 11:40:27 +0200
Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday 09 June 2010, Felipe Contreras wrote:
On Wed, Jun 9, 2010 at 6:46 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Tue, 8 Jun 2010,
* Govindraj govindraj...@gmail.com [100610 11:49]:
- Shouldn't we just retrieve the offset and then use
omap_ctrl_writew\ omap_ctrl_readw calls?
Sure that works too. And that actually has the advantage
that it's more likely to keep the mux read/write access
in the platform init code.
-
From: Senthilvadivu Guruswamy svad...@ti.com
config VRFB should depend on ARCH_OMAP2 or ARCH_OMAP3.
Changes from v1:
- Addressed multi-omap build issue
Signed-off-by: Senthilvadivu Guruswamy svad...@ti.com
---
drivers/video/omap2/Kconfig|4
From: Senthilvadivu Guruswamy svad...@ti.com
Changes since v2:
Added a check to warn the wrong usage of vrfb in non-vrfb omap devices.
Force def_vrfb to 0 for non omap2, omap3 devices
Signed-off-by: Senthilvadivu Guruswamy svad...@ti.com
---
drivers/video/omap2/omapfb/omapfb-main.c |
From: Senthilvadivu Guruswamy svad...@ti.com
FB_OMAP2 can work without VRFB, but currently does not build. Fix this.
Signed-off-by: Senthilvadivu Guruswamy svad...@ti.com
---
arch/arm/plat-omap/include/plat/vrfb.h | 16
1 file changed, 16 insertions(+), 0 deletions(-)
diff
On Thu, 10 Jun 2010 10:59:43 +0200
Rafael J. Wysocki r...@sisk.pl wrote:
On Thursday, June 10, 2010, Neil Brown wrote:
On Wed, 9 Jun 2010 11:40:27 +0200
Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday 09 June 2010, Felipe Contreras wrote:
On Wed, Jun 9, 2010 at 6:46 AM, Linus
Mismatch between index for gpt clocks will result in writting
out of bounds into dsp clock timer array when requesting gpt8,
for the other gpt the bogus code is being masked as it falls
within the array's range.
Discovered-by: Ernesto Ramos Falcon erne...@ti.com
Signed-off-by: Omar Ramirez Luna
New function to encapsulate previous code to configure gpt overflow,
this prevents accessing dmtimer framework outside dsp-clock interface
or exposing clock handles to other bridge modules.
Besides that: duplicated and unused defines were removed, conditional
test for cnt was replaced for a time
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Thursday, June 10, 2010 1:49 AM
To: Aguirre, Sergio
Cc: linux-omap@vger.kernel.org; Matt Fleming
Subject: Re: [PATCH] omap_hsmmc: Remove unused state variable
* Sergio Aguirre saagui...@ti.com [100608 23:35]:
On Thu, Jun 10, 2010 at 10:59:43AM +0200, Rafael J. Wysocki wrote:
So, for a phone-like system, where you'd generally want to simplify user
space,
having a power manager in the kernel seems to make sense to me.
I'm not clear where this requirement to simplify user space specifically
for
Hi!
We started here because it's possibly the only api level change we have --
almost everything else is driver or subarch type work or controversial but
entirely self-contained (like the binder, which I would be shocked to see
ever hit mainline). [...]
So why arent those bits
On Wed, 9 Jun 2010, Arve Hjønnevåg wrote:
I think this is where you misunderstood. There is no report wakeup
event as such. All that happens is that data becomes available to be
read from the input device file. However the power manager process
isn't polling the device file at this
On Wed, 9 Jun 2010 da...@lang.hm wrote:
why could the suspend blocker process see all events, but the power
manager process not see the events?
have the userspace talk to the power manager the way it does to the
suspend blocker now and what's the difference?
effectivly think s/suspend
On Thu, 10 Jun 2010, Rafael J. Wysocki wrote:
Moreover, having thought a bit more about the power manager in user space
concept I'm not sure if it really is that better than the original wakelocks
idea. Namely, it only repaces a kernel-based mechanism with a user space
task doing basically
Hi,
Could someone tell me which repository is used for developing MTD
support for OMAP3 devices?
Best regards,
Elvis
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Thursday, June 10, 2010 1:36 AM
To: Madhusudhan
Cc: 'Gadiyar, Anand'; 'Stephen Schwarm, CSDP'; linux-omap@vger.kernel.org
Subject: Re: simple sd card performance bug fix on OMAP
* Madhusudhan madhu...@ti.com
Tony,
-Original Message-
From: Shilimkar, Santosh
Sent: Friday, May 28, 2010 9:38 PM
To: linux-omap@vger.kernel.org
Cc: Shilimkar, Santosh; Nayak, Rajendra; Ghorai, Sukumar; Kadiyala, Kishore
Subject: [PATCH] omap4: mmc: Fix the regulator resource for MMC2
The MMC1 and MMC2 cards
-Original Message-
From: Hiremath, Vaibhav
Sent: Friday, March 19, 2010 4:51 PM
To: linux-omap@vger.kernel.org
Cc: tomi.valkei...@nokia.com; t...@atomide.com; Hiremath, Vaibhav
Subject: [PATCH-V2] OMAP3EVM: Replace vdvi regulator supply with vdds_dsi
From: Vaibhav Hiremath
On Thu, Jun 10, 2010 at 04:56:04PM +0200, ext Elvis Dowson wrote:
Could someone tell me which repository is used for developing
MTD support for OMAP3 devices?
linux-2.6.git
Try to always use mainline kernel for every patch and send them to
correct mailing list with
On Thursday, June 10, 2010, Alan Stern wrote:
On Thu, 10 Jun 2010, Rafael J. Wysocki wrote:
Moreover, having thought a bit more about the power manager in user space
concept I'm not sure if it really is that better than the original wakelocks
idea. Namely, it only repaces a kernel-based
On Thursday, June 10, 2010, Mark Brown wrote:
On Thu, Jun 10, 2010 at 10:59:43AM +0200, Rafael J. Wysocki wrote:
So, for a phone-like system, where you'd generally want to simplify user
space,
having a power manager in the kernel seems to make sense to me.
I'm not clear where this
On Thursday, June 10, 2010, Neil Brown wrote:
On Thu, 10 Jun 2010 10:59:43 +0200
Rafael J. Wysocki r...@sisk.pl wrote:
On Thursday, June 10, 2010, Neil Brown wrote:
On Wed, 9 Jun 2010 11:40:27 +0200
Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday 09 June 2010, Felipe
The patch DSPBRIDGE: Check pointer instead of using MEM_IS_VALID_HANDLE
macro uncovered an issue when calling the assertion macros after the
pointer was freed, but not set to NULL.
This issue was not showing before the above patch because the macro
MEM_IS_VALID_HANDLE checked for the pointer and
On Thu, Jun 10, 2010 at 05:46:46PM +0200, Rafael J. Wysocki wrote:
On Thursday, June 10, 2010, Mark Brown wrote:
On Thu, Jun 10, 2010 at 10:59:43AM +0200, Rafael J. Wysocki wrote:
So, for a phone-like system, where you'd generally want to simplify user
space,
having a power manager
2010/6/10 Alan Stern st...@rowland.harvard.edu:
On Wed, 9 Jun 2010, Arve Hjønnevåg wrote:
I think this is where you misunderstood. There is no report wakeup
event as such. All that happens is that data becomes available to be
read from the input device file. However the power manager
On Wed, 2010-06-09 at 23:34 -0700, Suresh Rajashekara wrote:
On Wed, Jun 9, 2010 at 1:22 PM, Thomas Gleixner t...@linutronix.de wrote:
Though we could change that conditionally - the default would still be
the freeze of jiffies and CLOCK_MONOTONIC for historical compability.
If I were to
Some execution info is missing at the beginning of the
trace buffer printout. This fix is to include this information
according to the buffer contents description and
also couple of cosmetic changes to make the traces more
readable.
This fix also uses DYNEXTBASE address to filter symbols that
On Thu, 10 Jun 2010, Arve Hjønnevåg wrote:
For that to work the wakeup events would have to be reported to the
power manager in a reliable way in the first place. Passing the file
descriptor that the app uses to the power manager does not work for
this, since the app could read the event
2010/6/10 Alan Stern st...@rowland.harvard.edu:
On Thu, 10 Jun 2010, Arve Hjønnevåg wrote:
For that to work the wakeup events would have to be reported to the
power manager in a reliable way in the first place. Passing the file
descriptor that the app uses to the power manager does not
This is a bit off the topic of Android
flamage, but I thought it would be worth
highlighting an example where the current
frameworks may still have a deficiency...
one that likewise relates to needing to
block entry ot a system suspend state, but
in this case user-space isn't very involved
(just
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Guzman
Lugo, Fernando
Sent: Thursday, April 08, 2010 7:19 PM
To: linux-omap@vger.kernel.org
Cc: Hiroshi DOYU; Ameya Palande; felipe.contre...@nokia.com
Subject: [PATCH] DSPBRIDGE: Avoid possible buffer
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Guzman
Lugo, Fernando
Sent: Thursday, April 08, 2010 7:17 PM
To: linux-omap@vger.kernel.org
Cc: Hiroshi DOYU; Ameya Palande; felipe.contre...@nokia.com
Subject: [PATCH] DSPBRIDGE: Avoid possible NULL
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Ramos
Falcon, Ernesto
Sent: Friday, April 16, 2010 10:23 PM
To: linux-omap@vger.kernel.org
Cc: Ameya Palande; Doyu Hiroshi (Nokia-D/Helsinki); Contreras Felipe
(Nokia-D/Helsinki)
Subject: [PATCH]
From: Deepak Chitriki deepak.chitr...@ti.com
cpufreq_register_notifier() function calls
srcu_notifier_chain_register() which always returns 0 on success and
dspbridge throws the error message clk_notifier_register failed for
iva2_ck. Fix the faulty ! in if logic and the faulty error message
we
From: Chitriki Rudramuni, Deepak
Sent: Thursday, May 20, 2010 9:42 AM
To: Guzman Lugo, Fernando
Cc: linux-omap@vger.kernel.org; Hiroshi DOYU; Ameya Palande; Ramirez Luna,
Omar; Felipe Contreras
Subject: Re: [PATCH] DSPBRIDGE: fix incorrect reset in bridge_brd_start
function
Guzman Lugo,
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Gomez
Castellanos, Ivan
Sent: Wednesday, May 19, 2010 5:22 PM
To: linux-omap@vger.kernel.org
Cc: hiroshi.d...@nokia.com; ameya.pala...@nokia.com;
felipe.contre...@nokia.com; Gomez Castellanos,
Ivan
From: Felipe Contreras [mailto:felipe.contre...@gmail.com]
Sent: Sunday, May 16, 2010 10:44 AM
To: linux-omap
Cc: Ramirez Luna, Omar; Guzman Lugo, Fernando; Chitriki Rudramuni, Deepak;
Felipe Contreras
Subject: [PATCH v2] dspbridge: deh: fix corruption on MMU fault
The DSP might misbehave and
43 matches
Mail list logo