On Friday 15 March 2013 10:30 AM, Will Deacon wrote:
> On Thu, Mar 14, 2013 at 01:08:00PM +0530, Santosh Shilimkar wrote:
>> Will,
>
> Hi guys,
>
> I'm out of the office at the moment and have really terrible connectivity,
> so I can't do too much until next w
On Monday 18 March 2013 08:37 PM, Will Deacon wrote:
> Hi Santosh,
>
> On Mon, Mar 18, 2013 at 06:51:30AM +, Santosh Shilimkar wrote:
>> On Friday 15 March 2013 10:30 AM, Will Deacon wrote:
>>> Furthermore, I was under the impression that hw_breakpoint did actually
On Monday 18 March 2013 10:36 PM, Will Deacon wrote:
> On Mon, Mar 18, 2013 at 03:46:28PM +0000, Santosh Shilimkar wrote:
>> On Monday 18 March 2013 08:37 PM, Will Deacon wrote:
>>> That really sucks :( Does this affect all OMAP-based boards?
>>>
>> All OMAP4
_suspend" in the
> bootargs.
>
> These patches are developed on 3.8 custom kernel containing omap5
> supend/resume support.
>
> Cc: Santosh Shilimkar
Thanks Sourav for sorting out the issue. With update of changelog
suggested by Kevin on patch 1, Feel free to add,
Acked-
On Wednesday 20 March 2013 05:45 PM, Laurent Navet wrote:
> Fix :
> gpio/gpio-omap.c:697: ERROR: space required before the open parenthesis '('
>
> Signed-off-by: Laurent Navet
> ---
Acked-by: Santosh Shilimkar
--
To unsubscribe from this list: send the line "un
On Wednesday 20 March 2013 05:54 PM, Santosh Shilimkar wrote:
> On Wednesday 20 March 2013 05:45 PM, Laurent Navet wrote:
>> Fix :
>> gpio/gpio-omap.c:697: ERROR: space required before the open parenthesis '('
>>
>> Signed-off-by: Laurent Navet
>>
arch/arm/boot/dts/omap5-evm.dts | 46 +++
arch/arm/boot/dts/omap5.dtsi| 40 +
2 files changed, 86 insertions(+), 0 deletions(-)
Acked-by: Santosh Shilimkar
--
To unsubscribe from this list: send the line "unsubs
On Tuesday 05 February 2013 06:01 AM, Joonsoo Kim wrote:
Now, there is no user for vmregion.
So remove it.
Acked-by: Nicolas Pitre
Signed-off-by: Joonsoo Kim
diff --git a/arch/arm/mm/Makefile b/arch/arm/mm/Makefile
index 8a9c4cb..4e333fa 100644
--- a/arch/arm/mm/Makefile
+++ b/arch/arm/mm/Mak
100644 arch/arm/mm/vmregion.c
delete mode 100644 arch/arm/mm/vmregion.h
Nice Clean-up. I tested this series on OMAP which uses few static
mappings. Feel free to add,
Tested-by: Santosh Shilimkar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Tuesday 05 February 2013 02:16 PM, kishon wrote:
Hi,
On Tuesday 05 February 2013 02:08 PM, Felipe Balbi wrote:
On Tue, Feb 05, 2013 at 01:59:26PM +0530, kishon wrote:
On Sunday 27 January 2013 01:17 AM, Sergei Shtylyov wrote:
Hello.
On 25-01-2013 15:11, Kishon Vijay Abraham I wrote:
Add
Mark,
On Thursday 07 February 2013 03:34 PM, Mark Rutland wrote:
Hi Stephen,
Sorry about this; I'm to blame for the bug.
On Wed, Feb 06, 2013 at 08:51:43PM +, Stephen Warren wrote:
On 01/14/2013 10:05 AM, Mark Rutland wrote:
Implement timer_broadcast for the arm architecture, allowing fo
On Thursday 07 February 2013 10:21 PM, Stephen Warren wrote:
On 02/07/2013 04:40 AM, Santosh Shilimkar wrote:
[...]
Stephan,
Do we have crash log seen on Tegra ? Which tegra CPUIDLE driver
is being used when crash is seen ?
The crash log is below. It's simply because td->evt->b
Mark,
On Thursday 07 February 2013 10:47 PM, Mark Rutland wrote:
[..]
I believe the patch below will fix this for Tegra and any other platforms where
broadcast is required in low power states.
From the Stephan's crash the issue is pretty clear and your patch make
sense. Some how I didn't man
On Wednesday 03 April 2013 04:47 PM, Peter Ujfalusi wrote:
> cyclic DMA is only used by audio which needs DMA to be started without a
> delay.
> If the DMA for audio is started using the tasklet we experience random
> channel switch (to be more precise: channel shift).
>
> Reported-by: Peter Meerw
On Wednesday 03 April 2013 05:22 PM, Peter Ujfalusi wrote:
> On 04/03/2013 01:24 PM, Santosh Shilimkar wrote:
>> On Wednesday 03 April 2013 04:47 PM, Peter Ujfalusi wrote:
>>> cyclic DMA is only used by audio which needs DMA to be started without a
>>> delay.
>>
>>>>>> used, od->flags
>>>>>>> should be ORed with "OMAP_DEVICE_NO_IDLE_ON_SUSPEND", thereby not
>>>>>>> allowing the console
>>>>>>> to idle in the suspend path. For non-dt case, this was taken care
>>>>
Jon,
On Tuesday 29 January 2013 05:31 AM, John Stultz wrote:
On 01/27/2013 10:08 PM, Santosh Shilimkar wrote:
On Tuesday 22 January 2013 08:35 PM, Santosh Shilimkar wrote:
On Tuesday 22 January 2013 08:21 PM, Russell King - ARM Linux wrote:
On Tue, Jan 22, 2013 at 03:44:03PM +0530, Santosh
On Wednesday 30 January 2013 04:42 AM, Ruslan Bilovol wrote:
Hi,
On Tue, Jan 29, 2013 at 6:08 PM, Russell King - ARM Linux
wrote:
On Tue, Jan 29, 2013 at 05:54:24PM +0200, Ruslan Bilovol wrote:
CPU implementer : 0x41
CPU name: OMAP4470 ES1.0 HS
Sigh. No. Look at what you're doing
On Wednesday 30 January 2013 06:08 AM, Ruslan Bilovol wrote:
The following patches update cpuinfo to print SoC
model name for ARM.
The first patch exactly makes needed changes for ARM
architecture and adds a common approach to show SoC name.
Second patch uses this approach for OMAP4 SoCs (as live
dts file is not adapted to use i2c through pinctrl
framework. Populating i2c pinctrl data to get rid of the error.
Tested on omap4430 sdp with 3.8-rc4 kernel.
Signed-off-by: Sourav Poddar
Reported-by: Santosh Shilimkar
---
Could you do the same thing for panda? I'm getting the same ki
ore
http://bugzilla.kernel.org/show_bug.cgi?id=5737
Many non-ACPI systems are filling this field by mistake, which makes its usage
confusing. Lets clean it.
Signed-off-by: Viresh Kumar
Cc: Linus Walleij
Cc: Stephen Warren
Cc: Shawn Guo
Cc: Santosh Shilimkar
---
I haven't looked at the
On Friday 01 February 2013 12:43 PM, Viresh Kumar wrote:
On 1 February 2013 12:17, Santosh Shilimkar wrote:
I haven't looked at the cpufreq code recently but remember
that it was needed to ensure that all the CPU which
share clock/voltage gets updated (affected cpus) on
freq change. The
On Friday 01 February 2013 01:32 PM, Viresh Kumar wrote:
On 1 February 2013 13:03, Santosh Shilimkar wrote:
I am not talking about just notifiers. This is for external users who
has subscribed for notifiers. The point is whether the core CPUFReq
gets updated without that flag for all affected
Viresh,
On Friday 01 February 2013 02:22 PM, Santosh Shilimkar wrote:
On Friday 01 February 2013 01:32 PM, Viresh Kumar wrote:
On 1 February 2013 13:03, Santosh Shilimkar
wrote:
I am not talking about just notifiers. This is for external users who
has subscribed for notifiers. The point is
On Saturday 02 February 2013 02:31 AM, Matt Porter wrote:
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports platforms booting
with or without DT populated.
Signed-off-by: Matt Porter
Acked-by: Tony Lindgren
---
Acked-by: Santosh Shilimkar
--
To
On Saturday 02 February 2013 02:31 AM, Matt Porter wrote:
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter
Acked-by: Tony Lindgren
---
Acked-by: Santosh Shilimkar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&qu
On Friday 25 January 2013 02:19 AM, Matt Porter wrote:
On Thu, Jan 24, 2013 at 05:12:05AM +, Shilimkar, Santosh wrote:
On Thursday 24 January 2013 02:19 AM, Matt Porter wrote:
On Wed, Jan 23, 2013 at 04:37:55PM +0530, Santosh Shilimkar wrote:
Matt,
On Wednesday 16 January 2013 02:02 AM
On Tuesday 22 January 2013 08:35 PM, Santosh Shilimkar wrote:
On Tuesday 22 January 2013 08:21 PM, Russell King - ARM Linux wrote:
On Tue, Jan 22, 2013 at 03:44:03PM +0530, Santosh Shilimkar wrote:
Sorry for not being clear enough. On OMAP, 32KHz is the only clock which
is always running(even
On Saturday 23 February 2013 12:22 AM, Thomas Gleixner wrote:
On Fri, 22 Feb 2013, Lorenzo Pieralisi wrote:
On Fri, Feb 22, 2013 at 03:03:02PM +, Thomas Gleixner wrote:
On Fri, 22 Feb 2013, Lorenzo Pieralisi wrote:
On Fri, Feb 22, 2013 at 12:07:30PM +, Thomas Gleixner wrote:
Now we co
On Wednesday 27 February 2013 03:47 AM, Daniel Lezcano wrote:
From: Viresh Kumar
When a cpu goes to a deep idle state where its local timer is shutdown, it
notifies the time frame work to use the broadcast timer instead.
Unfortunately, the broadcast device could wake up any CPU, including an i
On Wednesday 27 February 2013 10:29 AM, Viresh Kumar wrote:
On 27 February 2013 10:26, Santosh Shilimkar wrote:
On Wednesday 27 February 2013 03:47 AM, Daniel Lezcano wrote:
From: Viresh Kumar
When a cpu goes to a deep idle state where its local timer is shutdown, it
notifies the time
On Wednesday 27 February 2013 03:47 AM, Daniel Lezcano wrote:
The broadcast timer could be passed as parameter to the function
instead of using again tick_broadcast_device.evtdev which was
previously used in the caller function.
Signed-off-by: Daniel Lezcano
---
The change doesn't buy us as su
On Wednesday 27 February 2013 03:47 AM, Daniel Lezcano wrote:
When a cpu goes to a deep idle state where its local timer is shutdown,
it notifies the time frame work to use the broadcast timer instead.
Unfortunately, the broadcast device could wake up any CPU, including an
idle one which is not
On Wednesday 27 February 2013 03:47 AM, Daniel Lezcano wrote:
When a cpu goes to a deep idle state where its local timer is shutdown,
it notifies the time framework to use the broadcast timer instead.
Unfortunately, the broadcast device could wake up any CPU, including an
idle one which is not c
On Monday 18 February 2013 05:05 PM, Afzal Mohammed wrote:
(Resending, since it seems, LAKML doesn't accept patches with subject
prefix only as "RFC", but requires "PATCH" prefix also)
Hi,
This series adds minimal support to boot Linux on platforms having
AM43 based SoC's.
This is being sent a
On Monday 18 February 2013 05:07 PM, Afzal Mohammed wrote:
Register percpu local timer for scheduler tick in the case of one core
SMP configuration. In other cases - secondary cpu's as well as boot
cpu's having more than one core, this is being registered as per
existing boot flow, with a differe
On Monday 18 February 2013 05:07 PM, Afzal Mohammed wrote:
Add an optional property to find clock-frequency from DT. This helps
as a fallback mechanism in case there is no representation of clock
tree in DT.
Signed-off-by: Afzal Mohammed
---
This won't work always because twd clock is CPU depe
On Monday 18 February 2013 05:06 PM, Afzal Mohammed wrote:
Return percpu clock event on local timer register. It is the boot cpu
that calls this and it can use the returned percpu clock event to
register a clock event in the case of SMP configuration with one core.
SMP configuration with 1 core
On Monday 18 February 2013 05:07 PM, Afzal Mohammed wrote:
Selecting DEBUG_AM33XXUART1 routes low level debug messages to first
UART instance of AM335x based SoC's. This selection is valid for
upcoming AM43 based SoC's too. Make this information available upon
configuring.
Signed-off-by: Afzal M
On Monday 18 February 2013 05:08 PM, Afzal Mohammed wrote:
Add Kconfig option for AM43 family of SoC's, these are ARM Cortex A9
based (SMP configuration with 1 core).
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/Kconfig | 11 +++
1 file changed, 11 insertions(+)
diff --git
On Monday 18 February 2013 05:08 PM, Afzal Mohammed wrote:
Describe minimal DT boot machine details for AM43 based SoC's. AM43
family of SoC's are ARM Cortex-A9 based with one core in SMP
configuration. Low level debug could be achieved by selecting
DEBUG_AM33XXUART1. To boot AM43 SoC, this chang
On Monday 18 February 2013 05:08 PM, Afzal Mohammed wrote:
AM43 SoC is in pre-silicon stage, meanwhile it has been modelled in
a pre-silicon platform. To validate and boot Linux in pre-silicon
platform that emulates an AM43 SoC, add DT build support.
As bootloader is not used, bootargs is passed
On Tuesday 19 February 2013 04:22 PM, Mohammed, Afzal wrote:
Hi Santosh,
On Tue, Feb 19, 2013 at 16:05:22, Shilimkar, Santosh wrote:
On Monday 18 February 2013 05:08 PM, Afzal Mohammed wrote:
AM43 SoC is in pre-silicon stage, meanwhile it has been modelled in
a pre-silicon platform. To valid
On Tuesday 19 February 2013 04:26 PM, Felipe Balbi wrote:
On Tue, Feb 19, 2013 at 03:57:07PM +0530, Santosh Shilimkar wrote:
On Monday 18 February 2013 05:08 PM, Afzal Mohammed wrote:
Add Kconfig option for AM43 family of SoC's, these are ARM Cortex A9
based (SMP configuration with 1
On Tuesday 19 February 2013 04:00 PM, Mohammed, Afzal wrote:
Hi Santosh,
On Tue, Feb 19, 2013 at 15:55:59, Shilimkar, Santosh wrote:
With DT, IIRC DEBUGLL is broken. So did you hack debug-macro.S
to get the earlyprintk working ?
No, on linux-next, ll debug works properly.
Indeed. Tony fixe
On Tuesday 19 February 2013 04:33 PM, Mohammed, Afzal wrote:
Hi Santosh,
On Tue, Feb 19, 2013 at 16:30:13, Shilimkar, Santosh wrote:
On Tuesday 19 February 2013 04:22 PM, Mohammed, Afzal wrote:
SoC support is already added in patch 7/8. This is board (which doesn't
exist now) support, hence
On Tuesday 19 February 2013 05:44 PM, Felipe Balbi wrote:
On Tue, Feb 19, 2013 at 03:44:14PM +0530, Santosh Shilimkar wrote:
On Monday 18 February 2013 05:07 PM, Afzal Mohammed wrote:
Register percpu local timer for scheduler tick in the case of one core
SMP configuration. In other cases
ctiveness of such optimization solely depends
on how well the affinity (in low powers) supported by your IRQ chip.
Hope this is helpful for you.
Regards,
Santosh
From d70f2d48ec08a3f1d73187c49b16e4e60f81a50c Mon Sep 17 00:00:00 2001
From: Santosh Shilimkar
Date: Wed, 25 Jul 2012 03:42:33 +0530
S
On Thursday 21 February 2013 02:31 PM, Daniel Lezcano wrote:
On 02/21/2013 07:19 AM, Santosh Shilimkar wrote:
On Tuesday 19 February 2013 11:51 PM, Daniel Lezcano wrote:
On 02/19/2013 07:10 PM, Thomas Gleixner wrote:
On Tue, 19 Feb 2013, Daniel Lezcano wrote:
I am working on identifying the
one.
Tested-by: Santosh Shilimkar
Thanks for the patch.
And thanks to Jason for spotting the issue.
Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
Thomas,
On Friday 22 February 2013 03:49 AM, Thomas Gleixner wrote:
On Thu, 21 Feb 2013, Santosh Shilimkar wrote:
On Thursday 21 February 2013 07:18 PM, Thomas Gleixner wrote:
find below a completely untested patch, which should address that issue.
After looking at the thread, I tried to
On Friday 22 February 2013 03:54 PM, Thomas Gleixner wrote:
On Fri, 22 Feb 2013, Santosh Shilimkar wrote:
BTW, Lorenzo off-list mentioned to me about warning in boot-up
which I missed while testing your patch. It will take bit more
time for me to look into it and hence thought of reporting it
On Friday 22 February 2013 04:01 PM, Lorenzo Pieralisi wrote:
On Fri, Feb 22, 2013 at 10:24:00AM +, Thomas Gleixner wrote:
On Fri, 22 Feb 2013, Santosh Shilimkar wrote:
BTW, Lorenzo off-list mentioned to me about warning in boot-up
which I missed while testing your patch. It will take bit
On Tuesday 12 March 2013 07:58 PM, Benoit Cousson wrote:
> On 03/12/2013 06:07 AM, Santosh Shilimkar wrote:
>> On Tuesday 12 March 2013 04:35 AM, Nishanth Menon wrote:
>>> commit 5553f9e (cpufreq: instantiate cpufreq-cpu0 as a platform_driver)
>>> now forces platform
t;
I have tested this revised patches on OMAP4 and OMAP5 platforms
with CPUidle enabled against 3.9-rc2. As expected they seems to
work without any issue and also fixes the reported retry issue.
Tested-by: Santosh Shilimkar
--
To unsubscribe from this list: send the line "unsu
ere OSSR is mandatory.
>> Sorry about this and thanks for catching this.
> Thanks for confirming..:)
>
Can you please queue this one for 3.9-rc2+ ? Without this patch
CPUIDLE is unusable on OMAP4 devices because of those flood
of warning messages.
I was also wondering whether we should ju
OMAP interconnect drivers are used for the interconnect error handling.
Since they are bus driver, lets move it to newly created drivers/bus.
Cc: Arnd Bergmann
Cc: Tony Lindgren
Tested-by: Lokesh Vutla
Signed-off-by: Santosh Shilimkar
---
Patch just moves OMAP interconnect drivers as is to
IMERS
select ARM_CPU_SUSPEND if PM
select SOC_HAS_REALTIME_COUNTER
select ARM_ARCH_TIMER
Drop this change.
With that fixed, for OMAP changes
Acked-by: Santosh Shilimkar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a me
On Friday 05 October 2012 06:42 AM, Simon Horman wrote:
On Thu, Oct 04, 2012 at 02:41:46PM +0530, Santosh Shilimkar wrote:
On Thursday 04 October 2012 02:20 PM, Stephen Boyd wrote:
The TWD and SCU configs are selected by default as long as
SCORPIONMP is false and/or MCT is false. Implementing
Vincent,
Few comments/questions.
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
This new flag SD SHARE_POWERLINE reflects the sharing of the power rail
between the members of a domain. As this is the current assumption of the
scheduler, the flag is added to all sched_domain
Signed-
Vincent,
Few comments/questions.
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
During sched_domain creation, we define a pack buddy CPU if available.
On a system that share the powerline at all level, the buddy is set to -1
On a dual clusters / dual cores system which can powerga
$subject is bit confusing here.
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
The atomic update of runnable_avg_sum and runnable_avg_period are ensured
by their size and the toolchain. But we must ensure to not read an old value
for one field and a newly updated value for the other
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
Look for an idle CPU close the pack buddy CPU whenever possible.
s/close/close to
The goal is to prevent the wake up of a CPU which doesn't share the power
line of the pack CPU
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
The ARM platforms take advantage of packing small tasks on few cores.
This is true even when the cores of a cluster can't be powergated
independently.
Signed-off-by: Vincent Guittot
---
arch/arm/kernel/topology.c |5 +
1 file
On Friday 26 October 2012 04:17 AM, Shuah Khan wrote:
Add support for debug_dma_mapping_error() call to avoid warning from
debug_dma_unmap() interface when it checks for mapping error checked
status. Without this patch, device driver failed to check map error
warning is generated.
Signed-off-by:
On Thursday 01 November 2012 03:53 PM, Ivan Khoronzhuk wrote:
Replaces several flags bearing the same meaning. There is no need
to set flags due to different omap types here, it can be checked
in appropriate places as well.
Cc: Tony Lindgren
Cc: Russell King
Cc: linux-o...@vger.kernel.org
Cc:
On Thursday 01 November 2012 09:50 PM, ivan.khoronzhuk wrote:
On 11/01/2012 01:35 PM, Santosh Shilimkar wrote:
On Thursday 01 November 2012 03:53 PM, Ivan Khoronzhuk wrote:
Replaces several flags bearing the same meaning. There is no need
to set flags due to different omap types here, it can
On Thursday 01 November 2012 10:36 PM, Nishanth Menon wrote:
On 22:05-20121101, Santosh Shilimkar wrote:
On Thursday 01 November 2012 09:50 PM, ivan.khoronzhuk wrote:
On 11/01/2012 01:35 PM, Santosh Shilimkar wrote:
On Thursday 01 November 2012 03:53 PM, Ivan Khoronzhuk wrote:
Replaces
On Monday 29 October 2012 03:20 PM, Vincent Guittot wrote:
It looks like i need to describe more what
On 29 October 2012 10:40, Vincent Guittot wrote:
On 24 October 2012 17:17, Santosh Shilimkar wrote:
Vincent,
Few comments/questions.
On Sunday 07 October 2012 01:13 PM, Vincent Guittot
On Monday 29 October 2012 06:42 PM, Vincent Guittot wrote:
On 24 October 2012 17:20, Santosh Shilimkar wrote:
Vincent,
Few comments/questions.
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
During sched_domain creation, we define a pack buddy CPU if available.
On a system
On Monday 29 October 2012 06:57 PM, Vincent Guittot wrote:
On 24 October 2012 17:21, Santosh Shilimkar wrote:
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
Look for an idle CPU close the pack buddy CPU whenever possible.
s/close/close to
yes
The goal is to prevent the
On Monday 29 October 2012 06:58 PM, Vincent Guittot wrote:
On 24 October 2012 17:21, Santosh Shilimkar wrote:
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
The ARM platforms take advantage of packing small tasks on few cores.
This is true even when the cores of a cluster can&#
On Saturday 27 October 2012 05:33 PM, Constantine Shulyupin wrote:
From: Constantine Shulyupin
Tested SD (MMC) and Ethernet smsc95xx on linux-3.7-rc2
Signed-off-by: Constantine Shulyupin
--
kernel size is 2.3 MiB
---
arch/arm/configs/omap4_panda_defconfig | 115
On Tuesday 27 August 2013 04:17 PM, Stephen Warren wrote:
> On 08/26/2013 08:07 AM, Lars Poeschel wrote:
>> From: Linus Walleij
>>
>> Currently the kernel is ambigously treating GPIOs and interrupts
>> from a GPIO controller: GPIOs and interrupts are treated as
>> orthogonal. This unfortunately ma
On Tuesday 01 October 2013 09:48 AM, Rob Herring wrote:
> On 10/01/2013 06:13 AM, Sricharan R wrote:
>> Hi,
>>
>> On Monday 30 September 2013 08:39 PM, Rob Herring wrote:
>>> On 09/30/2013 08:59 AM, Sricharan R wrote:
Some socs have a large number of interrupts requests to service
the nee
On Tuesday 01 October 2013 10:53 AM, Rob Herring wrote:
> On 10/01/2013 08:57 AM, Santosh Shilimkar wrote:
>> On Tuesday 01 October 2013 09:48 AM, Rob Herring wrote:
>>> On 10/01/2013 06:13 AM, Sricharan R wrote:
>>>> Hi,
>>>>
>>>> On Monday 3
Cc: Russell King
Cc: Will Deacon
Cc: Rob Herring
Cc: Thomas Gleixner
Signed-off-by: Santosh Shilimkar
---
kernel/time/sched_clock.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/time/sched_clock.c b/kernel/time/sched_clock.c
index 0b479a6..15c4d78 100644
--- a
On Wednesday 02 October 2013 01:09 PM, Will Deacon wrote:
> On Wed, Oct 02, 2013 at 05:55:28PM +0100, Santosh Shilimkar wrote:
>> The sched_clock code uses 2 levels of function pointers, sched_clock_func()
>> and read_sched_clock() but the no sched_clock check in postinit()
On Wednesday 02 October 2013 01:22 PM, Stephen Boyd wrote:
> On 10/02/13 10:14, Santosh Shilimkar wrote:
>> On Wednesday 02 October 2013 01:09 PM, Will Deacon wrote:
>>> On Wed, Oct 02, 2013 at 05:55:28PM +0100, Santosh Shilimkar wrote:
>>>> The sched_clock code uses
On Wednesday 02 October 2013 01:48 PM, Will Deacon wrote:
> On Wed, Oct 02, 2013 at 06:42:40PM +0100, Stephen Boyd wrote:
>> On 10/02/13 10:27, Santosh Shilimkar wrote:
>>> Really... I have not created patch out of fun.
>>> Its broken on my keystone machine at lea
On Friday 04 October 2013 12:48 PM, Olof Johansson wrote:
> On Fri, Oct 4, 2013 at 6:22 AM, Greg Kroah-Hartman
> wrote:
>> On Fri, Oct 04, 2013 at 12:41:28PM +0100, Russell King - ARM Linux wrote:
>>>
>>> So, no, there will be no new drivers under arch/arm. They must be in the
>>> drivers subtree
.S
> b/arch/arm/mach-omap2/omap-smc.S
> >> index f6441c1..5c02b8d 100644
> >> --- a/arch/arm/mach-omap2/omap-smc.S
> >> +++ b/arch/arm/mach-omap2/omap-smc.S
> >> @@ -1,9 +1,11 @@
> >> /*
> >> - * OMAP44xx secure APIs file.
> >> + * O
s expected to return the DMAable maximum pfn
value across architectures.
Cc: Russell King
Cc: linux-s...@vger.kernel.org
Signed-off-by: Santosh Shilimkar
---
drivers/scsi/scsi_lib.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/
ill
won't work but this is one of the step to solve that problem for ARM.
Cc: Russell King
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Nicolas Pitre
Cc: Tejun Heo
Signed-off-by: Santosh Shilimkar
---
arch/arm/Kconfig|1 +
arch/arm/kernel/setup.c |2 +-
arch/arm/mm/init.c
block PFN number. In all the generic cases,
it is just "dev->dma_mask >> PAGE_SHIFT" and hence default behavior
is maintained as is.
Subsequent patches will make use of the helper. No functional change.
Cc: Russell King
Cc: Jens Axboe
Signed-off-by: Santosh Shilimkar
---
olas Pitre
Cc: Tejun Heo
Cc: Jens Axboe
Santosh Shilimkar (5):
block: Rename parameter dma_mask to max_addr for
blk_queue_bounce_limit()
mm: dma-mapping: Add dma_max_pfn(dev) helper function
scsi: Use dma_max_pfn(dev) helper for bounce_limit calculations
ARM: mm: change max*pfn to i
. It is done this way just to enable testing
since its understood that it can come in way of single zImage.
Cc: Russell King
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Nicolas Pitre
Signed-off-by: Santosh Shilimkar
---
arch/arm/include/asm/dma-mapping.h | 16
arch/arm/mm
t could
be miss-interpreted.
Cc: Russell King
Cc: Jens Axboe
Signed-off-by: Santosh Shilimkar
---
block/blk-settings.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/block/blk-settings.c b/block/blk-settings.c
index c50ecf0..026c151 100644
--- a/block/blk-settin
Thomas,
On Friday 13 September 2013 10:55 AM, Santosh Shilimkar wrote:
> On Friday 13 September 2013 10:24 AM, Thomas Gleixner wrote:
[...]
>> Before you dig into MSI, lets talk about irq domains first.
>>
>> GIC implements a legacy irq domain, i.e. a linear domain o
Thomas,
On Thursday 12 September 2013 04:18 PM, Thomas Gleixner wrote:
> On Thu, 12 Sep 2013, Sricharan R wrote:
>> Signed-off-by: Sricharan R
>> ---
>> There is lockdep warning during the boot. This is because we try to
>> do one request_irq with in another and that results in kmalloc being
>> c
On Thursday 12 September 2013 06:22 PM, Thomas Gleixner wrote:
> On Thu, 12 Sep 2013, Santosh Shilimkar wrote:
>> Specifically for the IRQ case addressed here, the cross-bar IP
>> sits between the interrupt controller and peripheral interrupts.
>>
>> CPU <-- GIC <
On Thursday 12 September 2013 08:26 PM, Thomas Gleixner wrote:
> On Thu, 12 Sep 2013, Santosh Shilimkar wrote:
>> On Thursday 12 September 2013 06:22 PM, Thomas Gleixner wrote:
>>> Now the real question is, how that expansion mechanism is supposed to
>>> work. There
On Friday 13 September 2013 10:24 AM, Thomas Gleixner wrote:
> On Thu, 12 Sep 2013, Santosh Shilimkar wrote:
>> On Thursday 12 September 2013 08:26 PM, Thomas Gleixner wrote:
>>> Let me summarize:
>>>
>>>- GIC supports up to 160 interrupts
>>>
&g
On Wednesday 09 October 2013 07:59 PM, John Stultz wrote:
> On 10/02/2013 11:07 AM, Santosh Shilimkar wrote:
>> On Wednesday 02 October 2013 01:48 PM, Will Deacon wrote:
>>> On Wed, Oct 02, 2013 at 06:42:40PM +0100, Stephen Boyd wrote:
>>>> On 10/02/13 10:27, Santosh
support and tested these patches on Keystone EVM. Will
post those patches soon on the lists.
For the series if you need more tested-by tags, feel free to
add,
Tested-by: Santosh Shilimkar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messa
is approach,
am fine with both of your patches. Again thanks a lot for
fixing the long nagging issue.
FWIW,
Acked-by: Santosh Shilimkar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at h
On Monday 30 September 2013 09:59 AM, Sricharan R wrote:
> Some socs have a large number of interrupts requests to service
> the needs of its many peripherals and subsystems. All of the interrupt
> requests lines from the subsystems are not needed at the same
> time, so they have to be muxed to the
On Monday 30 September 2013 10:16 AM, Marc Zyngier wrote:
> On 30/09/13 14:59, Sricharan R wrote:
>> In some socs the gic can be preceded by a crossbar IP which
>> routes the peripheral interrupts to the gic inputs. The peripheral
>> interrupts are associated with a fixed crossbar input line and th
Javier,
On Monday 23 September 2013 01:07 PM, Tony Lindgren wrote:
> * Javier Martinez Canillas [130923 10:09]:
>> On 09/23/2013 06:45 PM, Tony Lindgren wrote:
>>>
>>> Hmm does this still work for legacy platform data based
>>> drivers that are doing gpio_request() first?
>>>
>>
>> Yes it still w
On Tuesday 24 September 2013 11:45 AM, Balaji T K wrote:
> On Tuesday 24 September 2013 09:10 PM, Tony Lindgren wrote:
>> * Javier Martinez Canillas [130924 01:06]:
>>> The OMAP GPIO controller HW requires a pin to be configured in GPIO
>>> input mode in order to operate as an interrupt input. Sin
1 - 100 of 1304 matches
Mail list logo
