On 1/21/2015 12:43 PM, Tony Lindgren wrote:
* santosh shilimkar [150121 12:16]:
On 1/21/2015 10:36 AM, Tony Lindgren wrote:
* Marc Zyngier [150121 09:25]:
On 21/01/15 16:30, Tony Lindgren wrote:
I gave this a quick boot test on am437x-gp-evm and the
interrupts look OK with the fix also
On 1/21/2015 10:36 AM, Tony Lindgren wrote:
* Marc Zyngier [150121 09:25]:
On 21/01/15 16:30, Tony Lindgren wrote:
I gave this a quick boot test on am437x-gp-evm and the
interrupts look OK with the fix also applied:
# cat /proc/interrupts
CPU0
16:657 WUGEN 68 gp_
up the GIC code for better.
Feel free to add my ack if you need one.
Acked-by: Santosh Shilimkar
Regards,
Snatosh
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Saturday 14 December 2013 06:47 AM, Sebastian Hesselbarth wrote:
[..]
> From 4ef4720c0d7ca9be57b06dc7ab1483c77a5ada1d Mon Sep 17 00:00:00 2001
> From: Sebastian Hesselbarth
> Date: Sat, 14 Dec 2013 12:21:01 +0100
> Subject: [PATCH] ARM: keystone: remove call to of_clk_init
>
> Commit
>
> 41
Arnd, Olof,
On Saturday 14 December 2013 12:50 AM, Olof Johansson wrote:
> On Fri, Dec 13, 2013 at 7:00 PM, Arnd Bergmann wrote:
>> On Friday 13 December 2013, Tomasz Figa wrote:
>>> Commit
>>>
>>> 4178bac ARM: call of_clk_init from default time_init handler
>>>
>>> added implicit call to of_clk_
On Thursday 12 December 2013 07:43 PM, Felipe Balbi wrote:
> On Thu, Dec 12, 2013 at 07:29:24PM -0500, Santosh Shilimkar wrote:
>> On Thursday 12 December 2013 04:45 PM, Felipe Balbi wrote:
>>> A bare-minimum PM implementation which will
>>> server as building block f
On Thursday 12 December 2013 04:45 PM, Felipe Balbi wrote:
> A bare-minimum PM implementation which will
> server as building block for more complex
s/server/serve ;-)
> PM implementation in the future.
>
> At the least will not leave clocks on unnecessarily
> when e.g. a user write mem to /sys/p
de effect of enabling sched_clock on omap5 and exynos5. There
> should not be any reason not to use the arch timers for sched_clock.
>
Absolutely.
> Signed-off-by: Rob Herring
[..]
> arch/arm/mach-omap2/timer.c |5 +
Acked-by: Santosh Shilimkar
--
To unsubscr
Benoit,
On Thursday 24 January 2013 06:46 PM, Marc Zyngier wrote:
Hi Benoit,
On 24/01/13 12:42, Benoit Cousson wrote:
Hi Santosh,
On 01/23/2013 11:55 AM, Santosh Shilimkar wrote:
Looping Marc, Benoit
On Wednesday 23 January 2013 04:06 PM, Mark Rutland wrote:
On Tue, Jan 22, 2013 at 10:05
On Thursday 24 January 2013 06:12 PM, Benoit Cousson wrote:
Hi Santosh,
On 01/23/2013 11:55 AM, Santosh Shilimkar wrote:
Looping Marc, Benoit
On Wednesday 23 January 2013 04:06 PM, Mark Rutland wrote:
On Tue, Jan 22, 2013 at 10:05:18PM +, Kukjin Kim wrote:
Mark Rutland wrote
Looping Marc, Benoit
On Wednesday 23 January 2013 04:06 PM, Mark Rutland wrote:
On Tue, Jan 22, 2013 at 10:05:18PM +, Kukjin Kim wrote:
Mark Rutland wrote:
+ devicetree-discuss, Grant Likely, Rob Herring and Tony Lindgren
On Tue, Jan 22, 2013 at 01:41:27AM +, Kukjin Kim wrote:
Fro
On 6/22/2011 9:40 PM, Russell King - ARM Linux wrote:
A couple of things to point out here:
On Wed, Jun 22, 2011 at 04:16:58PM +0100, Russell King - ARM Linux wrote:
- mrc p15, 0, r4, c13, c0, 1 @ Context ID
- mrc p15, 0, r5, c13, c0, 2 @ User r/w thread and process ID
-
On 6/23/2011 2:31 AM, Russell King - ARM Linux wrote:
On Wed, Jun 22, 2011 at 04:08:16PM +0100, Russell King - ARM Linux wrote:
Tested on Assabet (SA1100) and 3430LDP only.
Correction - because suspend only goes into retention mode, these
changes have not been tested on the 3430. Someone who
On 5/31/2011 3:24 AM, Russell King - ARM Linux wrote:
On Mon, May 30, 2011 at 03:08:17PM +0530, Santosh Shilimkar wrote:
When do you plan to fix the SGI usage as discussed
in above thread. I thought SGI1 usage was ok for OMAP,
realview/versatile and MSM.
I'd like the use of the arbitary
On 5/30/2011 2:43 PM, Inderpal Singh wrote:
[...]
2. Fix to remove the "Unknown IPI message 0x1" message when
secondary CPU boots.
For this one you are avoiding a wakeup IPI and rather
relying on schedule IPI. That just avoiding the issue.
This doesn't seems to be right. Refer below threa
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Russell King - ARM Linux
> Sent: Saturday, December 04, 2010 2:18 PM
> To: Tony Lindgren; Kukjin Kim; Srinidhi Kasagar; Jamie Iles; Anton
> Vorontsov; linux-ker...@vger.ke
16 matches
Mail list logo
