On Tue, Mar 18, 2014 at 12:08:02PM -0500, Paul Handrigan wrote:
> On Tue, 18 Mar 2014, Brian Austin wrote:
> >Driver looks good to me. I think we should name it the cs42xx8 since this
> >actually covers CS42448 and CS42888. The CS42888 is derived from the
> >CS42448.
> V3 looks good. As Brian
On Tue, Mar 18, 2014 at 11:31:36AM -0400, Steven Rostedt wrote:
> On Tue, 18 Mar 2014 11:27:37 -0400
> Steven Rostedt wrote:
>
> > The TP_printk() should never dereference any pointers, because the ring
> > buffer can be read at some unknown time in the future. If a device no
> > longer exists,
On Thu, Feb 27, 2014 at 05:39:48PM +0800, Xiubo Li wrote:
> Changed in V10:
> Fix some bugs and adjust the code from Thierry's comments.
>
>
> Xiubo Li (4):
> pwm: Add Freescale FTM PWM driver support
> ARM: dts: vf610: Add Freescale FTM PWM node.
> ARM: dts: vf610-twr: Enables FTM PWM
On 03/18/2014 11:52 AM, Srivatsa S. Bhat wrote:
On 03/18/2014 08:31 PM, Dirk Brandewie wrote:
On 03/17/2014 10:44 PM, Viresh Kumar wrote:
On Sat, Mar 15, 2014 at 2:33 AM, wrote:
+
static int intel_pstate_cpu_init(struct cpufreq_policy *policy)
{
struct cpudata *cpu;
@@
On Tue, 18 Mar 2014, Marc Kleine-Budde wrote:
> On 03/18/2014 06:19 PM, Thomas Gleixner wrote:
> > The hardware has two message control interfaces, but the code only
> > uses the first one. So on SMP the following can be observed:
> >
> > CPU0CPU1
> > rx_poll()
> > write IF1
On Tue, 18 Mar 2014, Brian Austin wrote:
On Tue, 18 Mar 2014, Mark Brown wrote:
On Tue, Mar 11, 2014 at 07:41:31PM +0800, Nicolin Chen wrote:
This patch adds support for the Cirrus Logic CS42888 Audio CODEC that
has four 24-bit A/D and eight 24-bit D/A converters.
Brian, Paul - any review
First-time poster to LKML, though I've been a Linux user for the past
15+ years. Thanks to you all for your collective efforts at creating
such a great (useful, stable, etc) kernel...
Problem at hand: I'm getting consistent kernel oops (at times,
hard-crashes) on two of my identical servers
With CONFIG_X86_32=y, string_32.h gets pulled in compressed/string.c by
"misch.h". string_32.h defines a macro to map memcmp to __builtin_memcmp().
And that macro in turn changes the name of memcmp() defined here and
converts it to __builtin_memcmp().
I thought that's not the intention though. We
Move optimzied versions of memcpy to compressed/string.c This will allow
any other code to use these functions too if need be in future. Again
trying to put definition in a common place instead of hiding it in misc.c
Signed-off-by: Vivek Goyal
---
arch/x86/boot/compressed/misc.c | 31
On Tue, 18 Mar 2014 08:21:19 -0400
Prarit Bhargava wrote:
>
>
> On 03/13/2014 10:25 AM, Igor Mammedov wrote:
> > Hang is observed on virtual machines during CPU hotplug,
> > especially in big guests with many CPUs. (It happens more
> > often if host is over-committed).
> >
>
> Hey Igor, I
Hi Peter,
I have tried cleaning up a bit the usage of string functions in arch/x86/boot/.
I have created x86/boot/string.h which all the callers can include and by
default they get the built in definition of memcpy, memset and memcmp. Those
who want to use optimized version of these functions,
Try to treat memcmp() in same way as memcpy() and memset(). Provide a
declaration in boot/string.h and by default user gets a memcmp() which
maps to builtin function.
Move optimized definition of memcmp() in boot/string.c. Now a user can
do #undef memcmp and link against string.c to use optimzied
Currently compressed/misc.c needs to link against memset(). I think one of
the reasons of this need is inclusion of various header files which define
static inline functions and use memset() inside these. For example,
include/linux/bitmap.h
I think trying to include "../string.h" and using
Create a separate arch/x86/boot/string.h file to provide declaration of
some of the common string functions.
By default memcpy, memset and memcmp functions will default to gcc
builtin functions. If code wants to use an optimized version of any
of these functions, they need to #undef the
On Tue, Mar 18, 2014 at 03:46:50PM +0100, Jiri Olsa wrote:
> hi,
> this patchset moves thread's map_groups to be dynamically
> allocated and shared within process threads.
>
> The main benefit would be to be able to look up memory
> map from any thread that belongs to the process.
>
> This
On 03/18/2014 12:08 PM, Srivatsa S. Bhat wrote:
On 03/18/2014 10:52 PM, dirk.brande...@gmail.com wrote:
From: Dirk Brandewie
I don't mean to nitpick, but generally its easier to deal with
patchsets if you post the subsequent versions in fresh email threads.
Otherwise it can get a bit
On Tue, 18 Mar 2014, Thomas Gleixner wrote:
> On Tue, 18 Mar 2014, Vince Weaver wrote:
>
> >
> > The perf_fuzzer can quickly cause a machine to lockup with an hrtimer
> > related rb tree related oops. I've had a hard time debugging this in any
> > useful manner, but I can trigger it on both
On Tue, 2014-03-18 at 19:27 +0100, Thomas Gleixner wrote:
> V2: Remove the pointless multiwhile.
fyi, I didn't find another multiwhile in the kernel tree.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
perf_event_open() was renamed to sys_perf_event_open(); update the debug
messages to reflect this.
Cc: David Ahern
Cc: Jiri Olsa
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Ramkumar Ramachandra
---
tools/perf/util/evsel.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Tue, Mar 18, 2014 at 1:45 PM, Jassi Brar wrote:
> Convert the PL320 controller driver to work with the common
> mailbox API. Also convert the only user of PL320, highbank-cpufreq.c
> to work with thee API. Drop the obsoleted driver pl320-ipc.c
>
> Signed-off-by: Jassi Brar
> ---
>
Update the names of some functions and enums in design.txt. The
document still has some stale information, but the motivation behind
this patch is to allow a developer to quickly grep and learn about the
associated structures.
Cc: David Ahern
Cc: Jiri Olsa
Cc: Arnaldo Carvalho de Melo
On Wed, Mar 12, 2014 at 5:53 PM, Steven Rostedt wrote:
> Your timing here isn't that great either, because I leave tomorrow for
> another conference, and I'm currently trying to get everything ready
> for that trip. Could you ping me again on Tuesday?
Hey Steven
It's your friendly reminder to
On 03/18/2014 10:52 PM, dirk.brande...@gmail.com wrote:
> From: Dirk Brandewie
>
I don't mean to nitpick, but generally its easier to deal with
patchsets if you post the subsequent versions in fresh email threads.
Otherwise it can get a bit muddled along with too many other email
discussions in
On 03/18/2014 10:52 PM, dirk.brande...@gmail.com wrote:
> From: Dirk Brandewie
>
> Change to use ->exit_prepare() callback to do clean up during CPU
->stop()
> hotplug. The requested P state for an offline core will be used by the
> hardware coordination function to select the package P state.
Hello gentlemen,
Commit 589a606f9539663f162e4a110d117527833b58a4 ("percpu: add preemption
checks to __this_cpu ops") added preempt check to used in __count_vm_events()
__this_cpu ops, causing the following kswapd warning:
BUG: using __this_cpu_add() in preemptible [] code: kswapd0/56
On 03/17/2014 08:44 PM, Benjamin Herrenschmidt wrote:
> On Mon, 2014-03-17 at 16:36 -0700, H. Peter Anvin wrote:
>> Add predicate functions for having arch_get_random[_seed]*(). The
>> only current use is to avoid the loop in arch_random_refill() when
>> arch_get_random_seed_long() is
On 03/18/2014 08:31 PM, Dirk Brandewie wrote:
> On 03/17/2014 10:44 PM, Viresh Kumar wrote:
>> On Sat, Mar 15, 2014 at 2:33 AM, wrote:
>>> +
>>> static int intel_pstate_cpu_init(struct cpufreq_policy *policy)
>>> {
>>> struct cpudata *cpu;
>>> @@ -818,7 +824,7 @@ static struct
On 03/18/2014 11:17 AM, Sarah Newman wrote:
>
> Should or has there been a review of the current xen PVABI to look for any
> other such deviations?
>
It would be a very good thing to do. First of all, the PVABI needs to
be **documented** because without that there is no hope. I would like
to
From: LeyFoon Tan
Try to delete the timer only if it was init/used.
Signed-off-by: LeyFoon Tan
Signed-off-by: Jassi Brar
---
drivers/mailbox/mailbox.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mailbox/mailbox.c b/drivers/mailbox/mailbox.c
index
From: Suman Anna
The patch 30058677 "ARM / highbank: add support for pl320 IPC"
added a pl320 IPC specific header file as a generic mailbox.h.
This file has been renamed appropriately to allow the
introduction of the generic mailbox API framework.
Acked-by: Mark Langsdorf
Cc: Rafael J. Wysocki
Ping? this is still showing up in -next.
On 03/02/2014 09:13 PM, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next kernel
I've stumbled
on the following spew:
[ 315.799264]
On 03/18/2014 06:19 PM, Thomas Gleixner wrote:
> The hardware has two message control interfaces, but the code only
> uses the first one. So on SMP the following can be observed:
>
> CPU0 CPU1
> rx_poll()
> write IF1 xmit()
> write IF1
> write IF1
>
Introduce common framework for client/protocol drivers and
controller drivers of Inter-Processor-Communication (IPC).
Client driver developers should have a look at
include/linux/mailbox_client.h to understand the part of
the API exposed to client drivers.
Similarly controller driver developers
Convert the PL320 controller driver to work with the common
mailbox API. Also convert the only user of PL320, highbank-cpufreq.c
to work with thee API. Drop the obsoleted driver pl320-ipc.c
Signed-off-by: Jassi Brar
---
drivers/cpufreq/highbank-cpufreq.c | 24 -
drivers/mailbox/Makefile
From: LeyFoon Tan
For fast TX the complete could be called before being initialized as follows
mbox_send_message --> poll_txdone --> tx_tick --> complete(>tx_complete)
Init the completion early enough to fix the race.
Signed-off-by: LeyFoon Tan
Signed-off-by: Jassi Brar
---
Hello Rob,
On Mon, Feb-17-2014 at 01:45:52 AM +0100, Apelete Seketeli wrote:
> Document the process of writing an musb glue layer by taking the
> Ingenic JZ4740 glue layer as an example, as it seems more simple than
> most glue layers due to the basic feature set of the JZ4740 USB device
>
On Tue, 25 Feb 2014, Matthew Wilcox wrote:
> From: Ross Zwisler
>
> This is a port of the DAX functionality found in the current version of
> ext2.
>
> Signed-off-by: Ross Zwisler
> Reviewed-by: Andreas Dilger
> [heavily tweaked]
> Signed-off-by: Matthew Wilcox
...
> diff --git
Hi,
Here is the next revision of Mailbox code.
Changes since v3:
o Change name of symbols from ipc to mbox
o Return real types instead of void *
o Align structures
o Change some symbol names
rxcb -> rx_callback
txcb -> tx_done
o Added kernel-doc for exported API
o Dropped
On 03/18/2014 06:19 PM, Thomas Gleixner wrote:
> The function is broken in several ways:
>
> - The function does not wait for the init to complete.
> That can take quite some microseconds.
>
> - No protection against being called for two chips at the same
> time. SMP is such
Hello Arnd,
On (03/15/14 21:26), Arnd Bergmann wrote:
> On Saturday 15 March 2014, Sergey Senozhatsky wrote:
> > On (03/15/14 10:40), Arnd Bergmann wrote:
> > > The zram driver uses the ERR_PTR macro defined in
> > > and relies on this header to be included implicitly through
> > > other
On Sat, Feb 22, 2014 at 12:53:18PM +0800, Axel Lin wrote:
> Remove checking control_reg in [set|get]_voltage_sel and then convert to use
> regulator_[set|get]_voltage_sel_regmap for [set|get]_voltage_sel callbacks.
Applied, thanks - if there's a problem I guess doing this will shake it
out!
On Tue, Mar 18, 2014 at 06:34:12PM +0100, Krzysztof Kozlowski wrote:
> Lee Jones in his pull request [1] put also my changes for S2MPS14
> support in MFD sec-core driver. They are needed by this patchset for adding
> suppt for regulators on S2MPS14.
> Do you have time to look at these patches
On Tue, Mar 18, 2014 at 02:40:29PM +, Mark Salter wrote:
> On Tue, 2014-03-18 at 12:09 +, Catalin Marinas wrote:
> > On Thu, Mar 13, 2014 at 10:47:04PM +, Leif Lindholm wrote:
> > > --- /dev/null
> > > +++ b/arch/arm64/kernel/efi-entry.S
> > > @@ -0,0 +1,93 @@
> > > +/*
> > > + * EFI
If every other line contains line breaks, that's a clear sign for
indentation level madness. Split out the inner loop and move the code
to a separate function. gcc creates slightly worse code for that, but
we'll fix that in the next step.
Signed-off-by: Thomas Gleixner
---
V2: Remove the
On Fri, Mar 14, 2014 at 03:37:47PM +0900, Minchan Kim wrote:
> Linux doesn't have an ability to free pages lazy while other OS
> already have been supported that named by madvise(MADV_FREE).
>
> The gain is clear that kernel can evict freed pages rather than
> swapping out or OOM if memory
On Tue, 18 Mar 2014, Joe Perches wrote:
> On Tue, 2014-03-18 at 17:19 +, Thomas Gleixner wrote:
>
> [patch]
>
> Hi
>
> The multi-while loop
>
> while ((obj = ffs(pend)) && quota > 0) {
> ...
> } while ((obj = ffs(pend)) && quota > 0);
>
> looks, umm, unusual.
On Tue, 18 Mar 2014, Vince Weaver wrote:
>
> The perf_fuzzer can quickly cause a machine to lockup with an hrtimer
> related rb tree related oops. I've had a hard time debugging this in any
> useful manner, but I can trigger it on both core2 and haswell test systems
> on 3.14-rc7.
>
> This
On Tue, 18 Mar 2014, Marc Kleine-Budde wrote:
> On 03/18/2014 06:19 PM, Thomas Gleixner wrote:
> > According to the documentation the CPU must wait for CONTROL_INIT to
> > be cleared before writing to the baudrate registers.
>
> Thanks for the catch.
> > + return c_can_wait_for_ctrl_init(dev,
On 03/17/2014 10:14 AM, George Dunlap wrote:
> On 03/17/2014 05:05 PM, Jan Beulich wrote:
> On 17.03.14 at 17:55, "H. Peter Anvin" wrote:
>>> So if this interface wasn't an accident it was active negligence and
>>> incompetence.
>> I don't think so - while it (as we now see) disallows certain
Em Tue, Mar 18, 2014 at 05:09:33PM +0100, Adrien BAK escreveu:
> This pull request fixes the following issues :
> * when passing custom arguments to a script, if those arguments are
> not declared within perf, they prevent the execution of perf.
> e.g.
>
> perf script -i path/to/perf.data -s
Em Tue, Mar 18, 2014 at 08:05:33AM -0700, Andi Kleen escreveu:
> > Humm, this unconditionally replaces it with an alternative that limits
> > the buffer to a fixed size :-\
>
> Better than corrupting memory.
Yes, it is better than corrupting memory, use the less ugly, good point.
> I guess you
On 03/18/2014 06:19 PM, Thomas Gleixner wrote:
> According to the documentation the CPU must wait for CONTROL_INIT to
> be cleared before writing to the baudrate registers.
Thanks for the catch.
> Signed-off-by: Benedikt Spranger
> Signed-off-by: Thomas Gleixner
>
> ---
>
On 03/13/2014 10:25 AM, Igor Mammedov wrote:
> Hang is observed on virtual machines during CPU hotplug,
> especially in big guests with many CPUs. (It happens more
> often if host is over-committed).
>
Hey Igor, I like this better than the previous version. Thanks for taking into
account the
On Tue, Mar 18, 2014 at 8:11 AM, Minchan Kim wrote:
> 1) SIGBUS
>
> It's one of the arguable issue because some user want to get a
> SIGBUS(ex, Firefox) while other want a just zero page(ex, Google
> address sanitizer) without signal so it should be option.
>
> int vrange(start, len,
We replace the old way to configure the scheduler topology with a new method
which enables a platform to declare additionnal level (if needed).
We still have a default topology table definition that can be used by platform
that don't want more level than the SMT, MC, CPU and NUMA ones. This table
Create a dedicated topology table for handling asymetric feature of powerpc.
Signed-off-by: Vincent Guittot
---
arch/powerpc/kernel/smp.c | 31 +++
include/linux/sched.h | 2 --
kernel/sched/core.c | 6 --
3 files changed, 23 insertions(+), 16
This pull request fixes the following issues :
* when passing custom arguments to a script, if those arguments are
not declared within perf, they prevent the execution of perf.
e.g.
perf script -i path/to/perf.data -s my_script -arg1 arg_value
perf will issue an error message and no processing
This patchset was previously part of the larger tasks packing patchset [1].
I have splitted the latter in 3 different patchsets (at least) to make the
thing easier.
-configuration of sched_domain topology (this patchset)
-update and consolidation of cpu_power
-tasks packing algorithm
Based on
Set the power domain dependency at SMT level of Power8 but keep the flag
clear at CPU level. The goal is to consolidate tasks on the threads of a
core up to a level as decribed in the link below:
https://lkml.org/lkml/2014/3/12/16
Signed-off-by: Vincent Guittot
---
arch/powerpc/kernel/smp.c | 2
A new flag SD_SHARE_POWERDOMAIN is created to reflect whether groups of CPUs
in a sched_domain level can or not reach different power state. As an example,
the flag should be cleared at CPU level if groups of cores can be power gated
independently. This information can be used to add load
BOOK level is only relevant for s390 so we create a dedicated topology table
with BOOK level and remove it from default table.
Signed-off-by: Vincent Guittot
---
arch/s390/include/asm/topology.h | 11 +--
arch/s390/kernel/topology.c | 20
kernel/sched/core.c
not used since new numa scheduler init sequence
Signed-off-by: Vincent Guittot
---
arch/metag/include/asm/topology.h | 27 ---
1 file changed, 27 deletions(-)
diff --git a/arch/metag/include/asm/topology.h
b/arch/metag/include/asm/topology.h
index 8e9c0b3..e95f874
Create a dedicated topology table for ARM which will create new level to
differentiate CPUs that can or not powergate independantly from others.
The patch gives an example of how to add domain that will take advantage of
SD_SHARE_POWERDOMAIN.
Signed-off-by: Vincent Guittot
---
On 03/15/2014 07:29 PM, Richard Guy Briggs wrote:
> ---
> kernel/audit.c |5 ++---
> kernel/auditsc.c |9 +
> 2 files changed, 7 insertions(+), 7 deletions(-)
Doesn't this also need to be fixed (twice) in security/lsm_audit.c?
> diff --git a/kernel/audit.c b/kernel/audit.c
>
On 03/13/2014 11:37 PM, Minchan Kim wrote:
> This patch is an attempt to support MADV_FREE for Linux.
>
> Rationale is following as.
>
> Allocators call munmap(2) when user call free(3) if ptr is
> in mmaped area. But munmap isn't cheap because it have to clean up
> all pte entries, unlinking a
On 14/03/18, Stephen Smalley wrote:
> On 03/15/2014 07:29 PM, Richard Guy Briggs wrote:
> > ---
> > kernel/audit.c |5 ++---
> > kernel/auditsc.c |9 +
> > 2 files changed, 7 insertions(+), 7 deletions(-)
>
> Doesn't this also need to be fixed (twice) in security/lsm_audit.c?
On Tue, Mar 18, 2014 at 5:24 AM, Michal Hocko wrote:
> On Fri 14-03-14 11:33:30, John Stultz wrote:
> [...]
>> Volatile ranges provides a method for userland to inform the kernel that
>> a range of memory is safe to discard (ie: can be regenerated) but
>> userspace may want to try access it in
On 03/17, One Thousand Gnomes wrote:
>
> > and b) permits userspace to produce surprising results in the kernel,
> > which I suspect is what we're seeing here.
>
> There is enough information for kernel side code to decide whether a
> signal came from kernel or userspace.
Not really. SIGKILL can
On Tue, Mar 18, 2014 at 03:00:02PM +, Gabriel FERNANDEZ wrote:
> This patch adds ST Keyscan driver to use the keypad hw a subset
> of ST boards provide. Specific board setup will be put in the
> given dt.
>
> Signed-off-by: Gabriel Fernandez
> Signed-off-by: Giuseppe Condorelli
> ---
>
minix_i uppercase conversion (like majority of other filesystems).
Signed-off-by: Fabian Frederick
---
fs/minix/bitmap.c | 2 +-
fs/minix/inode.c| 10 +-
fs/minix/itree_v1.c | 2 +-
fs/minix/itree_v2.c | 2 +-
fs/minix/minix.h| 2 +-
5 files changed, 9 insertions(+), 9
On 03/18/14 08:24, David Laight wrote:
From: Behan Webster
On 03/18/14 02:41, David Laight wrote:
From: beh...@converseincode.com
From: Mark Charlebois
Replaced non-standard C use of Variable Length Arrays In Structs (VLAIS) in
xt_repldata.h with a C99 compliant flexible array member and
On 03/17, Andrew Morton wrote:
>
> On Mon, 17 Mar 2014 21:19:19 +0100 Oleg Nesterov wrote:
>
> > > Root cause time: it's wrong for the oom-killer to use SIGKILL.
> >
> > Not sure... what else?
>
> If we really really have to use userspace IPC in the kernel then I
> suppose we could add a new
On Tue, Mar 18, 2014 at 05:22:31PM +, Charles Keepax wrote:
> - /*
> - * LDO1 can only be used to supply DCVDD so if it has no
> - * consumers then DCVDD is supplied externally.
> - */
> - if (arizona->pdata.ldo1 &&
> - arizona->pdata.ldo1->num_consumer_supplies
Hi Mark,
Lee Jones in his pull request [1] put also my changes for S2MPS14
support in MFD sec-core driver. They are needed by this patchset for adding
suppt for regulators on S2MPS14.
Do you have time to look at these patches and apply them if they're OK (or ACK
them)?
Best regards,
Krzysztof
On Tue, Mar 18, 2014 at 02:16:49PM +, Mark Salter wrote:
> On Tue, 2014-03-18 at 12:34 +, Catalin Marinas wrote:
> > On Thu, Mar 13, 2014 at 10:47:06PM +, Leif Lindholm wrote:
> > > --- /dev/null
> > > +++ b/arch/arm64/kernel/efi.c
> > [...]
> > > +/*
> > > + * Called from setup_arch
On Tue, 2014-03-18 at 17:19 +, Thomas Gleixner wrote:
[patch]
Hi
The multi-while loop
while ((obj = ffs(pend)) && quota > 0) {
...
} while ((obj = ffs(pend)) && quota > 0);
looks, umm, unusual.
--
To unsubscribe from this list: send the line "unsubscribe
Currently, MICVDD only binds because it is both the regulator name and
the consumer name and we will always match against the regulator name
regardless of the consumer device. If the regulator was renamed using
the init_data ASoC will no longer be able to locate the supply, as it
will be looking
Some output configurations can require a 50Mhz SYSCLK which requires
DCVDD to be 1.8V. This patch adds the registers necessary for
supporting this operational mode.
Signed-off-by: Charles Keepax
---
drivers/mfd/wm8997-tables.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff
On Tue, Mar 18, 2014 at 03:55:59PM +0100, Arnd Bergmann wrote:
> The tnetv107x platform is getting removed, so this driver
> will not be needed any more.
Applied, thanks.
signature.asc
Description: Digital signature
It is more idiomatic to process things relating to the regulator in its
driver. This patch moves both processing of device tree relating to the
regulator and checking if the regulator is external from arizona-core
into the regulator driver.
Signed-off-by: Charles Keepax
---
Signed-off-by: Charles Keepax
---
Documentation/devicetree/bindings/mfd/arizona.txt |6 ++-
drivers/regulator/arizona-micsupp.c | 50 +
2 files changed, 54 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt
Signed-off-by: Charles Keepax
---
Documentation/devicetree/bindings/mfd/arizona.txt |7 +++
drivers/regulator/arizona-ldo1.c | 46 +++-
2 files changed, 50 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt
This patch does not alter the binding at all it only brings the
documentation up to date with the existing binding.
Signed-off-by: Charles Keepax
---
Documentation/devicetree/bindings/mfd/arizona.txt | 23 +++-
1 files changed, 13 insertions(+), 10 deletions(-)
diff --git
Hi,
This series of patches are small fixes/improvements to the
Arizona regulators. The main thing added is proper device
tree bindings for getting the regulator init_data.
Changes Since v1:
- Added of_node_put for nodes we take references to
- I have removed the last two MFD patches from the
On non-DT systems with device tree built in the current device tree GPIO
reads will overwrite the pdata with zero when they fail. This patch
factors out the reading of GPIOs for the Arizona devices into a helper
function, and ensures that the pdata version will be preserved if the
device tree read
On Tue, 18 Mar 2014, Peter Zijlstra wrote:
> > My gut reaction was that we'd probably be better served by putting
> > resources in to systems with higher core counts rather than lots of RAM.
> > I have encountered the occasional boot bug on my 1TB system, but it's
> > far from a frequent
The lost message handling is broken in several ways.
1) Clearing the message lost flag is done by writing 0 to the
message control register of the object.
#define IF_MCONT_CLR_MSGLST(0 << 14)
That clears the object buffer configuration in the worst case,
which results in a loss
The rx_poll code has the following gem:
if (msg_ctrl_save & IF_MCONT_EOB)
return num_rx_pkts;
The EOB bit is the indicator for the hardware that this is the last
configured FIFO object. But this object can contain valid data, if we
manage to free up objects before the
nameidata was replaced by flags in
00cd8dd3bf95f2 ("stop passing nameidata to ->lookup()")
Signed-off-by: Fabian Frederick
---
fs/freevxfs/vxfs_lookup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/freevxfs/vxfs_lookup.c b/fs/freevxfs/vxfs_lookup.c
index
From: Dirk Brandewie
Change to use ->exit_prepare() callback to do clean up during CPU
hotplug. The requested P state for an offline core will be used by the
hardware coordination function to select the package P state. If the
core is under load when it is offlined it will fix the package P
From: Dirk Brandewie
Changes:
v2->v3
Changed the calling of the ->stop() callback to be conditional on the
core being the last core controlled by a given policy.
v1->2
Change name of callback function added to cpufreq_driver interface.
Some drivers (intel_pstate) need to modify state on a
If every other line contains line breaks, that's a clear sign for
indentation level madness. Split out the inner loop and move the code
to a separate function. gcc creates slightly worse code for that, but
we'll fix that in the next step.
Signed-off-by: Thomas Gleixner
---
We can avoid the HW access in TX cleanup path for retrieving the DLC
of the sent package if we store the DLC in a private array.
Ideally this should be handled in the can_echo_skb functions, but I
leave that exercise to the CAN folks.
Signed-off-by: Thomas Gleixner
---
The function loads the message object from the hardware to get the
payload length. The previous patch stores that information in an
array, so we can avoid the hardware access.
Remove the hardware access and move the led toggle outside of the
spinlocked region. Toggle the led only once when at
When writing to a sysctl string, each write, regardless of VFS position,
began writing the string from the start. This meant the contents of
the last write to the sysctl controlled the string contents instead of
the first:
open("/proc/sys/kernel/modprobe", O_WRONLY) = 1
write(1,
The hardware has two message control interfaces, but the code only
uses the first one. So on SMP the following can be observed:
CPU0CPU1
rx_poll()
write IF1 xmit()
write IF1
write IF1
That results in corrupted message object
This creates a series of tests designed to examine the behavior of sysctl
write behavior, and corrects some unexpected side-effects of the current
file offset handling when writing sysctls. Namely, short appends don't
work and multiple writes (with incremented file position) rewrite the
sysctl
This adds several behavioral tests to sysctl string and number writing
to detect unexpected cases that didn't work correctly before the recent
logic fixes:
[ BEFORE ]
root@localhost:~# make test_num
== Testing sysctl behavior against /proc/sys/kernel/domainname ==
Writing test file ... ok
The network core does not serialize the access to the hardware. The
xmit related code lets the following happen:
CPU0 CPU1
interrupt()
do_poll()
c_can_do_tx()
Fiddle with HW and xmit()
internal data Fiddle with HW and
From: Dirk Brandewie
This callback allows the driver to do clean up before the CPU is
completely down and its state cannot be modified. This is used
by the intel_pstate driver to reduce the requested P state prior to
the core going away. This is required because the requested P state
of the
301 - 400 of 1566 matches
Mail list logo
