Anirudh Ghayal writes:
> On 11/26/2012 7:17 PM, Mark Brown wrote:
>> On Mon, Nov 26, 2012 at 05:13:37AM -0800, agha...@codeaurora.org wrote:
>>
>>> For example:
>>> Consumer (A) cpu-freq sets the voltage range to {1.275v, 1.375v}. The
>>> regulator framework eventually sets the regulator to 1.275
Sourav Poddar writes:
> OMAP_MAX_HSUART_PORTS is moved to omap_serial header file.
Why?
You started to explain it in the cover letter, but a full description
belongs here for the permanent git history.
Kevin
> Cc: Santosh Shilimkar
> Cc: Felipe Balbi
> Cc: Rajendra nayak
> Signed-off-by:
Hi Frederic,
On 01/07/2013 06:08 PM, Frederic Weisbecker wrote:
> The runqueue clock is supposed to be periodically updated by the
> tick. On full dynticks CPU we call update_nohz_rq_clock() before
> reading it. Now the scheduler code is complicated enough that we
> may miss some update_nohz_rq_cl
This series is a set of prerequistes for getting the new context
tracking subsystem, and adaptive tickless support working on ARM.
Kevin Hilman (3):
cputime_nsecs: use math64.h for nsec resolution conversion helpers
init/Kconfig: virt CPU accounting: drop 64-bit requirment
ARM: Kconfig
For the nsec resolution conversions to be useable on non 64-bit
architectures, the helpers in need to be used so the
right arch-specific 64-bit math helpers can be used (e.g. do_div())
Cc: Frederic Weisbecker
Signed-off-by: Kevin Hilman
---
include/asm-generic/cputime_nsecs.h | 28
The 64-bit requirement can be removed after the conversion of
the conversion of the nsec granularity cputime to work on !64_BIT
Cc: Frederic Weisbecker
Signed-off-by: Kevin Hilman
---
init/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/Kconfig b/init/Kconfig
With the 64-bit requirement removed from virt CPU accounting,
allow ARM platforms to enable it.
Signed-off-by: Kevin Hilman
---
arch/arm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 5b71469..9473d55 100644
--- a/arch/arm/Kconfig
+++ b
Add ARM support for the context tracking subsystem by instrumenting
exception entry/exit points.
Special thanks to Mats Liljegren for testing, collaboration and adding
support for exceptions/faults that were missing in early test versions.
Cc: Mats Liljegren
Signed-off-by: Kevin Hilman
Signed-off-by: Kevin Hilman
---
arch/arm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 9473d55..4028fb2 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -60,6 +60,7 @@ config ARM
select OLD_SIGSUSPEND3
select
syscall_trace_exit() based on commit
2c5594df (rcu: Fix unrecovered RCU user mode in syscall_trace_leave())
for x86.
Special thanks to Mats Liljegren for collaboration and additional
testing.
Cc: Mats Liljegren
Signed-off-by: Kevin Hilman
---
arch/arm/include/asm/thread_info.h | 4 +++-
arch/arm
.
Based on commit edf55fda35c7dc7f2d9241c3abaddaf759b457c6 (x86: Exit
RCU extended QS on notify resume)
Signed-off-by: Kevin Hilman
---
arch/arm/kernel/signal.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/arch/arm/kernel/signal.c b/arch/arm/kernel/signal.c
Both of which are combined on top of Frederic's 3.9-rc1-nohz1 branch
and available here:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux.git
arm-nohz-v2/context-tracking
Using this, I tested adaptive tickless on a 2 CPU ARM SoC (OMAP4
Panda.)
Kevin Hilman (4):
ARM: context
Gleb Natapov writes:
> On Wed, Mar 20, 2013 at 06:58:41PM -0500, Scott Wood wrote:
>> On 03/14/2013 07:13:46 PM, Kevin Hilman wrote:
>> >The new context tracking subsystem unconditionally includes kvm_host.h
>> >headers for the guest enter/exit macros. This causes a c
Grant Likely writes:
> On Fri, 14 Dec 2012 18:05:53 +1100, NeilBrown wrote:
>> On Mon, 10 Sep 2012 10:57:07 -0700 Kevin Hilman
>> wrote:
>>
>>
>> > OK thanks, I'll queue this up for v3.6-rc as this should qualify as a
>> > regression.
>
NeilBrown writes:
> On Mon, 21 Jan 2013 13:38:59 +0200 Igor Grinberg
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi Neil,
>>
>> On 01/21/13 11:28, NeilBrown wrote:
>> >
>> >
>> > The standard suspend sequence involves runtime_resuming
>> > devices before suspending t
lobal declaration) on an
ARM platform (TI OMAP3) with and without CPUidle, and things continue to
work as expected:
Reviewed-by: Kevin Hilman
Tested-by: Kevin Hilman
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...
NeilBrown writes:
> On Tue, 12 Feb 2013 13:03:36 -0800 Kevin Hilman wrote:
>
>> NeilBrown writes:
>>
[...]
>> My patch was fixing a real hang when musb was built-in (or loaded), in
>> host-mode (mini-A cable attached) but no devices attached. I just tried
Sourav Poddar writes:
> Hi Kevin,
> On Wednesday 20 March 2013 05:36 PM, Sourav Poddar wrote:
>> Realised the list to whom the patch was send got dropped. Ccing
>> them all..
>> On Wednesday 20 March 2013 05:18 PM, Sourav Poddar wrote:
>>> Hi Kevin,
>>>
Rajagopal Venkat writes:
> Devfreq core suspend/resume of a device is explicitly handled
> by devfreq driver through devfreq_suspend_device() and
> devfreq_resume_device() apis typically called from runtime
> suspend/resume callbacks. This patch aims to take away this
> from devfreq drivers and h
Sourav Poddar writes:
> With dt boot, uart wakeup after suspend is non functional while using
> "no_console_suspend" in the bootargs. With "no_console_suspend" used, we
> should prevent the runtime suspend of the uart port which is getting used
> as an console.
>
> Cc: Santosh Shilimkar
> Cc: Fel
Frederic Weisbecker writes:
> On Wed, Feb 20, 2013 at 11:41:38AM -0800, Kevin Hilman wrote:
>> So that it can build on !KVM systems too.
>>
>> Signed-off-by: Kevin Hilman
>> ---
>> kernel/context_tracking.c | 4
>> 1 file changed, 4 i
Namhyung Kim writes:
> 2013-02-26 (화), 11:29 -0800, Kevin Hilman:
>> Frederic Weisbecker writes:
>>
>> > On Wed, Feb 20, 2013 at 11:41:38AM -0800, Kevin Hilman wrote:
>> >> So that it can build on !KVM systems too.
>> >>
>> &
Philip Avinash writes:
> With GPMC converted to platform driver recently, adds low power
> transition support in driver itself.
>
> Signed-off-by: Philip Avinash
> ---
> Changes since v1:
> Module disable & enable added using pm_runtime support.
>
> arch/arm/mach-omap2/gpmc.c | 20 +
Frederic Weisbecker writes:
> 2013/2/15 Mats Liljegren :
>> Kevin Hilman wrote:
>> /Mats
>>
>> From e3da56bdb36a3efb5a9869ded20f346039f381f2 Mon Sep 17 00:00:00 2001
>> From: Mats Liljegren
>> Date: Fri, 15 Feb 2013 13:46:29 +0100
>> Subject: [PAT
Frederic Weisbecker writes:
> 2013/2/15 Kevin Hilman :
>> Frederic Weisbecker writes:
>>
>>> Ingo,
>>>
>>> Please pull the new full dynticks cputime accounting code that
>>> can be found at:
>>>
>>> git://git.kernel.org/pub
ybe some simpler wrappers in
kernel_stat.h would make this a bit cleaner?
Kevin
Kevin Hilman (5):
context tracking: conditionalize guest support based on CONFIG_KVM
kernel_cpustat: convert to atomic 64-bit accessors
virt CPU accounting: Kconfig: drop 64-bit requirment
cputime: use do_d
So that it can build on !KVM systems too.
Signed-off-by: Kevin Hilman
---
kernel/context_tracking.c | 4
1 file changed, 4 insertions(+)
diff --git a/kernel/context_tracking.c b/kernel/context_tracking.c
index 74f68f4..6fe96b1 100644
--- a/kernel/context_tracking.c
+++ b/kernel
The 64-bit requirement can be removed after the conversion of
kernel_cpustat accessors to the portable atomic64 accessors.
Signed-off-by: Kevin Hilman
---
init/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/Kconfig b/init/Kconfig
index 3abb019..b13af06 100644
For the nsec resolution conversions to be useful on non 64-bit
architectures, do_div() needs to be used for the 64-bit divisions.
Signed-off-by: Kevin Hilman
---
include/asm-generic/cputime_nsecs.h | 51 +++--
1 file changed, 37 insertions(+), 14 deletions
With the 64-bit requirement removed from virt CPU accounting,
allow ARM platforms to enable it.
Signed-off-by: Kevin Hilman
---
arch/arm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 9bbe760..732f8d3 100644
--- a/arch/arm/Kconfig
+++ b
Use the atomic64_* accessors for all the kernel_cpustat fields to
ensure atomic access on non-64 bit platforms.
Thanks to Mats Liljegren for CGROUP_CPUACCT related fixes.
Cc: Mats Liljegren
Signed-off-by: Kevin Hilman
---
fs/proc/stat.c | 40
Namhyung Kim writes:
> Hi Kevin,
>
> On Wed, Feb 20, 2013 at 11:41:41AM -0800, Kevin Hilman wrote:
>> For the nsec resolution conversions to be useful on non 64-bit
>> architectures, do_div() needs to be used for the 64-bit divisions.
>>
>> Signed-off-by: Kev
Kevin Hilman writes:
> Use the atomic64_* accessors for all the kernel_cpustat fields to
> ensure atomic access on non-64 bit platforms.
>
> Thanks to Mats Liljegren for CGROUP_CPUACCT related fixes.
>
> Cc: Mats Liljegren
> Signed-off-by: Kevin Hilman
The kbuild test bo
e accessor functions, and then converting the accessor
functions to use the atomic64 functions.
Implemented based on idea proposed by Frederic Weisbecker.
Kevin Hilman (2):
cpustat: use accessor functions for get/set/add
cpustat: convert to atomic operations
arch/s390/appldata/appldata_o
used atomic64_set(atomic64_read() + delta), but on
32-bit platforms using the generic 64-bit ops (lib/atomic64.c), that
results in taking a lock twice.
Signed-off-by: Kevin Hilman
---
include/linux/kernel_stat.h | 16
1 file changed, 16 insertions(+)
diff --git a/include/linux
Add some accessor functions in order to facilitate the conversion to
atomic reads/writes of cpustat values.
Signed-off-by: Kevin Hilman
---
arch/s390/appldata/appldata_os.c | 16 +++
drivers/cpufreq/cpufreq_governor.c | 18 -
drivers/cpufreq/cpufreq_ondemand.c | 2
Frederic Weisbecker writes:
> 2013/2/21 Frederic Weisbecker :
>> 2013/2/21 Kevin Hilman :
>>> Subject: [PATCH 2/5] kernel_cpustat: convert to atomic 64-bit accessors
>>>
>>> Use the atomic64_* accessors for all the kernel_cpustat fields to
>>>
Viresh Kumar writes:
> On Fri, Feb 22, 2013 at 11:26 AM, Kevin Hilman wrote:
>> Add some accessor functions in order to facilitate the conversion to
>> atomic reads/writes of cpustat values.
>>
>> Signed-off-by: Kevin Hilman
>> ---
>>
Frederic Weisbecker writes:
> On Fri, Feb 22, 2013 at 06:21:31AM -0800, Eric Dumazet wrote:
>> On Fri, 2013-02-22 at 15:09 +0100, Peter Zijlstra wrote:
>> > On Fri, 2013-02-22 at 13:50 +0100, Frederic Weisbecker wrote:
>> > > > Argh!! at what cost? 64bit atomics are like expensive. Wouldn't
>> >
just noticed this on my Panda boards with CPUidle enabled, and
$SUBJECT patch fixes it.
FWIW,
Tested-by: Kevin Hilman
I agree that this should get queued for v3.9-rc.
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to major
: Frederic Weisbecker
Signed-off-by: Kevin Hilman
---
Applies on v3.9-rc2
include/linux/kvm_host.h | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index cad77fe..a942863 100644
--- a/include/linux/kvm_host.h
+++ b/include
"Poddar, Sourav" writes:
> Hi,
>
> On Tue, Sep 25, 2012 at 2:51 PM, Russell King - ARM Linux
> wrote:
>> On Tue, Sep 25, 2012 at 12:11:14PM +0300, Felipe Balbi wrote:
>>> On Tue, Sep 25, 2012 at 10:12:28AM +0100, Russell King - ARM Linux wrote:
>>> > On Tue, Sep 25, 2012 at 11:31:20AM +0300, Fel
Russell King - ARM Linux writes:
> On Tue, Oct 16, 2012 at 03:07:49PM -0700, Kevin Hilman wrote:
>> From: Thomas Gleixner
>>
>> Attempts to retrigger nested threaded IRQs currently fail because they
>> have no primary handler. In order to support retrigger of nes
The smc_special_locks should also be used when either softIRQs or hard
IRQs are preempted which may lead to the same problems as under SMP.
Signed-off-by: Kevin Hilman <[EMAIL PROTECTED]>
---
drivers/net/smc91x.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/d
ration code
>> together and out of the drivers. IME the SoCs where you need to do
>> different things for different IPs shoudl mostly still get some reuse
>> out of such an approach.
>
> Talking to Kevin Hilman today he was also stressing that
> power domains is a good thi
Linus Walleij writes:
> On Wed, Oct 31, 2012 at 9:10 PM, Kevin Hilman
> wrote:
>
>> Linus Walleij writes:
>
>
>>
>> > piece of hardware, this would be the right thing to do,
>> > and I think the in-kernel examples are all "simple",
On 11/02/2012 09:43 AM, Pantelis Antoniou wrote:
[...]
And then use the standard DT support to create later the platform_device that
does represent the new super-cape devices.
We know this is the ideal case. In fact that's the long term goal and we had
internal discussions about it.
Sinc
Mark Brown writes:
> On Wed, Jul 25, 2012 at 05:38:35PM -0700, Kevin Hilman wrote:
>
>> That being said, I'm not sure why ti,hwmods is being used as an example
>> for powerdomains. hwmods describe the integration of SoC IP blocks
>> (base addr, IRQ, DMA channel etc.
"Poddar, Sourav" writes:
> On Mon, Jul 30, 2012 at 3:04 PM, DebBarma, Tarun Kanti
> wrote:
>> Sourav,
>>
>> On Mon, Jul 30, 2012 at 2:13 PM, Poddar, Sourav wrote:
>>> Hi All,
>>>
>>> I tried using gpio as an interrupt line for my driver
>>> (drivers/staging/iio/light/tsl2x7x_core.c) for omap5.
Alan Stern writes:
> On Fri, 21 Sep 2012, Rafael J. Wysocki wrote:
>
>> > Kevin makes a good case that pm_runtime_resume() and related functions
>> > should succeed even when runtime PM is disabled, if the device is
>> > already in the desired state.
>> >
>> > The same may be true for pm_runti
Greg,
On Tue, Aug 20, 2013 at 8:57 AM, Kevin Hilman wrote:
> + Felipe
>
> On Mon, Jul 8, 2013 at 3:04 AM, Alexander Savchenko
> wrote:
>> From: Dmitry Fink
>>
>> Current logic results in interrupt storm since the fifo
>> is constantly below the threshold le
Greg,
On Tue, Aug 20, 2013 at 8:44 AM, Kevin Hilman wrote:
> +Felipe
>
> On Wed, Jul 17, 2013 at 6:29 AM, Alexander Savchenko
> wrote:
>> From: Ruchika Kharwar
>>
>> Ensure the Interrupt handling routine return IRQ_HANDLED vs
>> IRQ_NONE.
>
> Why?
&g
Benoit Cousson writes:
> + Kevin,
>
> On 27/08/2013 15:53, Sebastian Andrzej Siewior wrote:
>> On 08/27/2013 03:24 PM, Benoit Cousson wrote:
>>> Hi Sebatian,
>>
>> Hi Benoit,
>>
>>> Yes. DT patches are an endless source of merge conflicts if they are
>>> merge throught different trees.
>>
>> Usua
Stephen Rothwell writes:
> Hi all,
>
> Today's linux-next merge of the arm-soc tree got a conflict in
> arch/arm/mach-mvebu/platsmp.c between commit f6cec7cd0777 ("ARM: mvebu:
> remove device tree parsing for cpu nodes") from the tree and commit
> 994c8c94b419 ("ARM: mvebu: Remove the harcoded B
Sebastian Andrzej Siewior writes:
> On 08/27/2013 05:01 PM, Kevin Hilman wrote:
>>>> What do we do now?
>>>
>>> Cannot you just merge the stable arm-soc/dt branch into your branch
>>> before applying your patches?
>>
>> Unfortunately, t
On Wed, Aug 28, 2013 at 12:51 AM, Laurent Pinchart
wrote:
> Hi Lee,
>
> (Dropping Ian Molton from the CC list as the e-
> mail address isn't valid anymore)
>
> On Wednesday 28 August 2013 08:41:26 Lee Jones wrote:
>> > > Since 3af9d15 "mmc: tmio-mmc: Remove .set_pwr() callback from
>> > > platfor
Hi Nishanth,
Nishanth Menon writes:
> The following version 5 of the series arose from trying to use
> BeagleBoard-XM (OMAP3 variant) for doing CPU DVFS using cpufreq-cpu0.
> This series enables the generic cpufreq-cpu0 driver to be used in
> device tree enabled boot while maintaining support of
Nishanth Menon writes:
> fixing Benoit's mail ID.
> On 10/03/2013 11:43 AM, Kevin Hilman wrote:
>> Hi Nishanth,
>>
>> Nishanth Menon writes:
>>
>>> The following version 5 of the series arose from trying to use
>>> BeagleBoard-XM (OMAP3 var
-chip retention and off-mode
during idle are still working fine.
Tested-by: Kevin Hilman
Kevin
> Viresh Kumar (16):
> cpuidle: fix indentation of cpumask
> cpuidle: Fix comments in cpuidle core
> cpuidle: make __cpuidle_get_cpu_driver() inline
> cpuidle: make __cpu
Mika Westerberg writes:
> On Fri, Sep 13, 2013 at 05:50:22PM +0300, Mika Westerberg wrote:
>> On Fri, Sep 13, 2013 at 07:30:55AM -0700, Kevin Hilman wrote:
>> > Mika Westerberg writes:
>> >
>> > > On Thu, Sep 12, 2013 at 02:34:21PM -0700, Kevin Hilman wr
The 64-bit requirement can be removed since the conversion of the nsec
granularity cputime to work on !64_BIT
Cc: Frederic Weisbecker
Signed-off-by: Kevin Hilman
---
init/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/Kconfig b/init/Kconfig
index 18bd9e3
Now that VIRT_CPU_ACCOUNTING_GEN no longer has a 64-bit requirement,
it can be dropped here as well.
Cc: Frederic Weisbecker
Signed-off-by: Kevin Hilman
---
kernel/time/Kconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/time/Kconfig b/kernel/time/Kconfig
index 2b62fe8..a54e3e9
deric Weisbecker
Signed-off-by: Kevin Hilman
---
arch/Kconfig | 11 +++
init/Kconfig | 1 +
2 files changed, 12 insertions(+)
diff --git a/arch/Kconfig b/arch/Kconfig
index 1feb169..3c94a2d 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -356,6 +356,17 @@ config HAVE_CONTEXT_TRACKING
c
With the 64-bit requirement removed from VIRT_CPU_ACCOUNTING_GEN,
allow ARM platforms to enable it. Since VIRT_CPU_ACCOUNTING_GEN is a
dependency for full NO_HZ, this allows ARM platforms to enable full
NO_HZ as well.
Cc: Frederic Weisbecker
Signed-off-by: Kevin Hilman
---
arch/arm/Kconfig
def57)
Kevin
Kevin Hilman (4):
nohz_full: Kconfig: VIRT_CPU_ACCOUNTING_GEN: drop 64-bit requirement
nohz_full: Kconfig: drop requrement on 64-bit
full_nohz: Kconfig: add HAVE_VIRT_CPU_ACCOUNTING_GEN
ARM: Kconfig: allow full nohz CPU accounting
arch/Kconfig| 11 +++
arch/arm/Kc
Signed-off-by: Kevin Hilman
---
kernel/sched/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 4b1fe3e..3d7c80e 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -2203,7 +2203,7 @@ u64
: Kevin Hilman
---
kernel/sched/core.c | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 5ac63c9..4b1fe3e 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -2175,6 +2175,8 @@ void scheduler_tick(void
Alexandre Courbot writes:
> Trusted Foundations is a TrustZone-based secure monitor for ARM that
> can be invoked using the same SMC-based API on all supported
> platforms. This patch adds initial basic support for Trusted
> Foundations using the ARM firmware API. Current features are limited
> t
On Tue, Aug 27, 2013 at 4:52 PM, wrote:
> This mmotm tree contains the following patches against 3.11-rc7:
> (patches marked "*" will be included in linux-next)
[...]
> * mm-munlock-manual-pte-walk-in-fast-path-instead-of-follow_page_mask.patch
As has already been pointed out[1], this one int
On Mon, Sep 9, 2013 at 7:50 AM, Kevin Hilman wrote:
> Koen Kooi writes:
>
>> Op 6 sep. 2013, om 10:51 heeft Koen Kooi het
>> volgende geschreven:
>>
>>>
>>> Op 6 sep. 2013, om 09:10 heeft Koen Kooi het
>>> volgende geschreven:
>>>
Koen Kooi writes:
> Op 6 sep. 2013, om 10:51 heeft Koen Kooi het
> volgende geschreven:
>
>>
>> Op 6 sep. 2013, om 09:10 heeft Koen Kooi het
>> volgende geschreven:
>>
>>>
>>> Op 6 sep. 2013, om 08:57 heeft George Cherian het
>>> volgende geschreven:
>>>
On 9/6/2013 12:03 PM, Koen
On Mon, Sep 2, 2013 at 11:09 AM, Lorenzo Pieralisi
wrote:
> On Thu, Aug 29, 2013 at 06:57:15PM +0100, Olof Johansson wrote:
>> On Thu, Aug 29, 2013 at 06:04:25PM +1000, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > Today's linux-next merge of the arm-soc tree got a conflict in
>> > drivers/cpuidl
Lots of cleanup and refactoring and some SMP additions for Renesas
platforms. Due to some inter-dependencies with other arm-soc
branches, this Renesas stuff was separated out for sending after the
other branches were merged.
Highlights:
- remove unused board support and cleanup of unused headers
These are changes that arrived a little late before the merge window,
or had dependencies on previous branches.
Highlights:
- ux500: misc. cleanup, fixup I2C devices
- exynos: DT updates for RTC; PM updates
- at91: DT updates for NAND; new platforms added to generic defconfig
- sunxi: DT updates:
This branch contains ARM SoC related driver updates for v3.12. The
only thing this cycle are core PM updates and CPUidle support for
ARM's TC2 big.LITTLE development platform.
Conflicts:
One cleanup/reorg conflict with a new entry in
drivers/cpuidle/Makefile. Append the new entry after the exis
Hi Linus,
Here's a 2nd round of changes from ARM SoC land.
The main thing of note (or of potential annoyance factor) here is the
handful of conflicts in PULL 2/3 coming from platform changes
conflicting with driver changes going in to the V4L tree. I've listed
them in detail in that pull request
Linus Torvalds writes:
> On Mon, Sep 9, 2013 at 3:42 PM, Kevin Hilman wrote:
>>
>> The main thing of note (or of potential annoyance factor) here is the
>> handful of conflicts in PULL 2/3 coming from platform changes
>> conflicting with driver changes going in to
Aaron Lu writes:
> On 09/11/2013 06:32 AM, Rafael J. Wysocki wrote:
>> On Tuesday, September 10, 2013 10:35:22 PM Mark Brown wrote:
>>> On Tue, Sep 10, 2013 at 10:04:21PM +0200, Rafael J. Wysocki wrote:
On Tuesday, September 10, 2013 05:13:21 PM Mark Brown wrote:
>>>
> OK, that is very m
Mika Westerberg writes:
> From: Aaron Lu
>
> This patch adds runtime PM support for the I2C bus in a similar way that
> has been done for PCI bus already. This means that the I2C bus core
> prepares runtime PM for a client device just before a driver is about to be
> bound to it. Devices that ar
On Thu, Sep 12, 2013 at 2:34 PM, Kevin Hilman wrote:
> Mika Westerberg writes:
>
>> From: Aaron Lu
>>
>> This patch adds runtime PM support for the I2C bus in a similar way that
>> has been done for PCI bus already. This means that the I2C bus core
>> pre
able as a git branch at
> https://github.com/koenkooi/linux/commits/mainline
FWIW, tested this branch on BB black/white with MMC rootfs.
Tested-by: Kevin Hilman
Koen, Thanks for your persistence getting this stuff merged.
Kevin
--
To unsubscribe from this list: send the line "unsu
Mika Westerberg writes:
> On Thu, Sep 12, 2013 at 02:34:21PM -0700, Kevin Hilman wrote:
>> > diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
>> > index f32ca29..44374b4 100644
>> > --- a/drivers/i2c/i2c-core.c
>> > +++ b/drivers/i2c/i2c-core.
Alexandre Courbot writes:
> Trusted Foundations is a TrustZone-based secure monitor for ARM that
> can be invoked using the same SMC-based API on all supported
> platforms. This patch adds initial basic support for Trusted
> Foundations using the ARM firmware API. Current features are limited
> t
Alexandre Courbot writes:
> On Wed, Oct 9, 2013 at 4:47 PM, Olof Johansson wrote:
>> On Fri, Oct 4, 2013 at 9:37 AM, Alexandre Courbot
>> wrote:
[...]
>>> +static inline void register_trusted_foundations(
>>> + struct trusted_foundations_platform_data
>>> *p
[+Olof who had mentioned lock recursion BUG in -next]
On Tue, Sep 3, 2013 at 5:10 AM, Linus Walleij wrote:
> On Tue, Sep 3, 2013 at 12:39 PM, Thierry Reding
> wrote:
>
>> Return an error if neither the ->set() nor the ->set_debounce() function
>> is implemented by the chip. Furthermore move lock
ut() definition in preparation for the
> next patch that setups the controller's irq_chip driver when
> a caller requests an interrupt line.
>
> Signed-off-by: Javier Martinez Canillas
I'm fine with this appproach. For both patches:
Reviewed-by: Kevin Hilman
Also, I gave i
on't have a middle state that loose the
> dependency in the middle of
> the patchset. Probablyt no big deal but it looks more natural this way.
>
> * Refined a few changelogs.
>
> If you're ok I'll send a pull request to Ingo.
Looks good
Maxime Ripard writes:
> Hi everyone,
>
> Here is a few patches adding support for the High Speed Timers running on the
> Allwinner SoCs.
>
> These timers are 64 bits timers running at a much higher speed than the timers
> used for now on these SoCs, since they are no longer wired to the 24MHz
> o
Olof Johansson writes:
> On Wed, Sep 25, 2013 at 11:13 AM, Kevin Hilman wrote:
>
>>> However, the A20 and A31 come with 4 of these high speed timers,
>>> while the A10s
>>> and A13 only have two, hence why we introduce two different compatibles.
>>
&g
Felipe Balbi writes:
> nobody needs to access the uart_omap_port structure
> other than omap-serial.c file. Let's move that
> structure definition to the C source file in order
> to prevent anyone from accessing our structure.
>
> Tested-by: Shubhrajyoti D
> Acked-by: Tony Lindgren
> Signed-off
Felipe Balbi writes:
> Hi guys,
>
> here's v4 of the omap uart patchset. No changes other than a rebase on top of
> Greg's tty-next branch and Tony's Acked-by being added to a couple patches
>
> Note: I'm resending the series with Vikram's Software Flow Control fix anyway
> as it can just be igno
Felipe Balbi writes:
> Hi,
>
> On Thu, Sep 06, 2012 at 03:44:13PM -0700, Kevin Hilman wrote:
>> Felipe Balbi writes:
>>
>> > Hi guys,
>> >
>> > here's v4 of the omap uart patchset. No changes other than a rebase on top
>> > of
&g
78225021413022c164cb99fbc5e
> gpio/omap: remove suspend_wakeup field from struct gpio_bank
>
> and makes some minor changes so that we have separate flags for "GPIO
> should wake from deep idle" and "GPIO should wake from suspend".
>
> With this patch, the GPIO
"Shilimkar, Santosh" writes:
> On Sat, Sep 8, 2012 at 3:07 AM, Kevin Hilman
> wrote:
>> Hi Neil,
>>
>> NeilBrown writes:
>>
>>> On Thu, 6 Sep 2012 11:18:09 +0530 "Shilimkar, Santosh"
>>> wrote:
>>>
>>>> O
fbc5e
> gpio/omap: remove suspend_wakeup field from struct gpio_bank
>
> and makes some minor changes so that we have separate flags for "GPIO
> should wake from deep idle" and "GPIO should wake from suspend".
>
> With this patch, the GPIO from my touch s
From: Kevin Hilman
commit 6b8029fab64164b5895d58d23229b75c82e3a6fc (rtc: kconfig: remove
unnecessary dependencies) removed various 'depends on RTC_CLASS'
dependencies but also removed a few 'default RTC_CLASS' statements,
which actually changed default behavior.
This resulte
, the changelog should describe that the patch not only changes the
meaning of return values, but also converts devfreq to use the new
values.
Otherwise, implementation looks fine.
Reviewed-by: Kevin Hilman
> Cc: MyungJoo Ham
> Cc: Kyungmin Park
> Cc: "Rafael J. Wysocki"
>
Barry Song <21cn...@gmail.com> writes:
> 2012/7/18 Colin Cross :
>> Many clocks that are used to provide sched_clock will reset during
>> suspend. If read_sched_clock returns 0 after suspend, sched_clock will
>> appear to jump forward. This patch resets cd.epoch_cyc to the current
>> value of re
+Colin Cross, Barry Song also
Felipe Balbi writes:
> The scheduler imposes a requirement to sched_clock()
> which is to stop the clock during suspend, if we don't
> do that IRQ threads will be rescheduled in the future
> which might cause transfers to timeout depending on
> how driver is written
ompared to the suspend/resume dependencies.
I haven't been able to do any testing with this yet (I'm away from my
hardware for a bit), but I totally support this change.
Reviewed-by: Kevin Hilman
Thanks!
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux
1 - 100 of 1706 matches
Mail list logo
