Kees Cook wrote:
> On Mon, Sep 16, 2013 at 1:09 AM, Geert Uytterhoeven
> wrote:
> > On Mon, Sep 16, 2013 at 9:43 AM, Kees Cook wrote:
> >> All users of %n are calculating padding size when using seq_file, so
> >> instead use the new last_len member for discovering the length of the
> >> written
On 09/17/2013 01:09 AM, Rob Herring wrote:
> From: Rob Herring
>
> Convert microblaze to use new early_init_dt_scan function.
>
> Signed-off-by: Rob Herring
> Cc: Michal Simek
> Cc: microblaze-ucli...@itee.uq.edu.au
> ---
> arch/microblaze/kernel/prom.c | 17 +++--
>
On Tue, 2013-09-17 at 17:23 +0800, Aaron Lu wrote:
> According to Matthew Garrett, "Windows 8 leaves backlight control up
> to individual graphics drivers rather than making ACPI calls itself.
> There's plenty of evidence to suggest that the Intel driver for
> Windows 8 doesn't use the ACPI
Hi Thierry,
On 09/16/2013 11:32 AM, Thierry Reding wrote:> Interrupt references are
currently resolved very early (when a device is
> created). This has the disadvantage that it will fail in cases where the
> interrupt parent hasn't been probed and no IRQ domain for it has been
> registered yet.
Hi Tomasz,
On 17-09-2013 11:18, Tomasz Figa wrote:
Hi José,
Please see my comments below.
On Wednesday 11 of September 2013 11:08:27 José Miguel Gonçalves wrote:
The Samsung serial driver currently does not support setting the
RTS pin with an ioctl(TIOCMSET) call. This patch adds this
On Tue, 2013-09-17 at 17:23 +0800, Aaron Lu wrote:
> Introduce a new API for modules to query if a specific type of backlight
> device has been registered. This is useful for some backlight device
> provider module(e.g. ACPI video) to know if a native control
> interface(e.g. the interface created
On Tue, 2013-09-17 at 17:23 +0800, Aaron Lu wrote:
> The backlight control and event delivery functionality provided by ACPI
> video module is mixed together and registered all during video device
> enumeration time. As a result, the two functionality are also removed
> together on module unload
On Sun, Sep 01, 2013 at 08:32:45PM -0700, Kuninori Morimoto wrote:
> +void rsnd_write(struct rsnd_priv *priv,
> + struct rsnd_mod *mod,
> + enum rsnd_reg reg, u32 data)
> +{
> + struct rsnd_gen *gen = rsnd_priv_to_gen(priv);
> +
> + if
(* Apologies if this is a duplicate: I screw up the plain text before *)
Hello all,
I've designed and implemented a tool similar to sparse and CQUAL that
does type inference of user specified type qualifiers, e.g. iomem. It
receives an API specification with the type qualifiers and also a
On Tue, Sep 17, 2013 at 3:46 AM, Catalin Marinas
wrote:
> On 17 Sep 2013, at 00:09, Rob Herring wrote:
>> --- a/arch/arm64/kernel/setup.c
>> +++ b/arch/arm64/kernel/setup.c
>> @@ -147,24 +147,6 @@ static void __init setup_machine_fdt(phys_addr_t
>> dt_phys)
>> pr_info("Machine: %s\n",
On Sun, Sep 01, 2013 at 08:31:16PM -0700, Kuninori Morimoto wrote:
> Current rsnd_gen_ops didn't care about .probe and .remove
> functions, but it was not good sense.
> This patch tidyup it
Applied, thanks.
signature.asc
Description: Digital signature
On Tue, Sep 17, 2013 at 3:01 AM, Stephen Rothwell wrote:
> Hi all,
>
> This message is bcc'd to each of the contacts for the trees listed below,
> so apologies if you get two copies.
>
> I have been inspired to check the ages of the trees included in
> linux-next. Below I have listed all the
On Wed, Sep 4, 2013 at 9:03 AM, George Cherian wrote:
> This patch series
> - removes the irq_demux_work
> - Uses devm_request_threaded_irq
> - Call the user handler iff gpio_to_irq is done.
>
> v1 --> v2
> Split v1 to 3 patches
> v2 --> v3
> Remove the
It is Private
I am George Daniels, a Banker and credit system programmer (HSBC bank).
I saw your email address while browsing through the bank D.T.C Screen in my
office yesterday so I decided to use this very chance to know you. I believe we
should use every opportunity to know each other
On Sun, Sep 01, 2013 at 08:30:50PM -0700, Kuninori Morimoto wrote:
> Current Linux kernel is supporting regmap_field method
> and it is very useful feature.
> It needs one regmap_filed for one register access.
Applied, thanks. I did make one update:
> + * A non-zero will be returned when fields
This patch adds support for and demonstrates the usage of an embedded
position independent executable (PIE). The goal is to allow the use of C
code in situations where carefully written position independent assembly
was previously required.
The example used is the suspend/resume code for the
This commit adds support for embedding PIEs into the kernel, loading them
into genalloc sections, performing necessary relocations, and running code
from them. This allows platforms that need to run code from SRAM, such
an during suspend/resume, to develop that code in C instead of assembly.
This is necessary for platforms that use SRAM to execute suspend/resume stubs.
Signed-off-by: Russ Dill
---
Documentation/devicetree/bindings/misc/sram.txt | 4
drivers/misc/sram.c | 13 -
include/linux/platform_data/sram.h | 8
Now that there is an _exec version of ioremap, add devm support for it.
Signed-off-by: Russ Dill
---
include/linux/device.h | 17 -
include/linux/io.h | 4 +++
lib/devres.c | 97 --
3 files changed, 114 insertions(+), 4
If code is to be copied into and area (such as SRAM) and run,
it needs to be marked as exec. Currently only an ARM version
of this exists.
Signed-off-by: Russ Dill
---
arch/arm/include/asm/io.h | 2 ++
include/asm-generic/iomap.h | 5 +
2 files changed, 7 insertions(+)
diff --git
Under certain arches (ARM) function pointers cannot be
used naively. Specifically, for thumb functions, their 0 bit
is set, but they are contained on a word aligned address.
Add a fncpy macro to perform function copies correctly
along with two helpers, fnptr_to_address, and fnptr_translate.
This adds support for updating PIE relocations under ARM. This
is necessary in the case that the same PIE must run both with
virtual mapping (MMU enabled) and physical mapping (MMU
disabled).
Signed-off-by: Russ Dill
---
arch/arm/include/asm/pie.h | 42 +
The SRAM is for use by the MPU. Marking it as such makes it
easier for PM initialization code to locate the SRAM in order to
load a PIE section into it.
Additionally, set the map-exec flag to allow code to be run
from SRAM. This is necessary for suspend/resume.
Signed-off-by: Russ Dill
---
Add support to ARM for embedding PIEs into the kernel, loading them into
genalloc pools (such as SRAM) and executing them. Support for ARM means
performing R_ARM_RELATIVE fixups within the .rel.dyn section.
Signed-off-by: Russ Dill
---
arch/arm/Kconfig | 1 +
arch/arm/Makefile
From: Vaibhav Bedia
AM335x supports various low power modes as documented
in section 8.1.4.3 of the AM335x TRM which is available
@ http://www.ti.com/litv/pdf/spruh73f
DeepSleep0 mode offers the lowest power mode with limited
wakeup sources without a system reboot and is mapped as
the suspend
Add a helper that generates a short snippet of code that updates PIE
relocations, loads the stack pointer and calls a C (or asm) function.
The code gets placed into a PIE section.
Signed-off-by: Russ Dill
---
arch/arm/include/asm/suspend.h | 25 +
1 file changed, 25
This enables CONFIG_PIE for omap2plus_defconfig and adds
an am33xx PIE section group. This is necessary for am33xx
suspend/resume code as it is written in C.
Signed-off-by: Russ Dill
---
arch/arm/configs/omap2plus_defconfig | 1 +
arch/arm/kernel/pie.lds.S| 1 +
2 files changed, 2
On Tue, Sep 17, 2013 at 01:20:39PM +0200, Alexandre Belloni wrote:
> Hi Thierry,
>
> On 16/09/2013 10:31, Thierry Reding wrote:
> > Hi,
> >
> > This small series allows interrupt references from the device tree to be
> > resolved at driver probe time, rather than at device creation time. The
> >
Hi, Mike
There are two designs in my mind
regarding the formatting cache.
You said
> administer the writeboost devices. There is no need for this. Just
> have a normal DM target whose .ctr takes care of validation and
> determines whether a device needs formatting, etc.
makes me wonder
Mike,
First, thank you for your commenting.
I was looking forward to your comments.
I suppose you are sensing some "smell" in my design.
You are worrying that dm-writeboost will not only confuse users
but also fall into worst situation of giving up backward-compatibility
after merging into
Hi Chander,
On Monday 16 of September 2013 11:01:22 Chander Kashyap wrote:
> Pass '0' in place of hardcoded "irq_base" value as "first_irq" parameter
> to "irq_domain_add_simple" in order to use linear irq domain.
>
> Signed-off-by: Chander Kashyap
> ---
> drivers/irqchip/exynos-combiner.c |
Dne 15.9.2013 06:39, Guenter Roeck napsal(a):
> Commit ea4054a23 (modpost: handle huge numbers of modules) added
> support for building a large number of modules.
>
> Unfortunately, the commit changed the semantics of the makefile: Instead of
> passing only existing object files to modpost, make
On Fri, Sep 13, 2013 at 4:24 PM, Thomas Gleixner wrote:
> So why can't you make use of irq domains and have the whole routing
> business implemented sanely?
>
> What's needed is in gic_init_bases():
>
>if (of_property_read(node, "routable_irqs", _routable_irqs) {
>
On Mon, 2013-09-16 at 18:09 -0500, Rob Herring wrote:
> From: Rob Herring
>
> Convert c6x to use new early_init_dt_scan function.
>
> Signed-off-by: Rob Herring
> Cc: Mark Salter
> Cc: Aurelien Jacquiot
> Cc: linux-c6x-...@linux-c6x.org
> ---
> arch/c6x/kernel/devicetree.c | 19
On Mon, Sep 9, 2013 at 6:03 PM, Guennadi Liakhovetski
wrote:
> There are four I2C interfaces on r8a7790, each of them can be connected to
> one of the two respective I2C controllers, e.g. interface #0 can be
> configured to work with I2C0 or with IIC0. Additionally some of those
> interfaces can
Hi,
I am running the perf record and report commands, which are running OK
but I do not get any kernel symbol resolved when using a built and
installed kernel.
Using the distro installed kernel is OK though.
The setup is: Marvell ARMv7 quad core, Linaro Ubuntu release.
Here are the commands in
On Tuesday 17 September 2013 05:33 PM, Laxman Dewangan wrote:
On Tuesday 17 September 2013 04:54 PM, Mark Brown wrote:
* PGP Signed by an unknown key
On Tue, Sep 17, 2013 at 12:15:35PM +0530, Laxman Dewangan wrote:
+MFD driver adds following mfd devices with their compatible values:
+static int as3722_ldo_get_voltage_sel(struct regulator_dev *rdev)
+{
+ int ret;
+
+ ret = regulator_get_voltage_sel_regmap(rdev);
+ if (ret >= 0x40)
+ ret -= 0x1B;
+ return ret;
+}
This looks very strange. What's going on here? A gap in the selectors?
On 09/13/2013 05:14 PM, Viresh Kumar wrote:
> On 4 September 2013 01:10, Rafael J. Wysocki wrote:
>> On Tuesday, September 03, 2013 06:50:05 PM Srivatsa S. Bhat wrote:
>
>>> This doesn't solve the problem completely: it prevents the store_*() task
>>> from continuing *only* when it concurrently
On Tue, Sep 17, 2013 at 12:16:56PM +0200, Miklos Szeredi wrote:
> Just one. This needs to be removed, since this condition is now
> explicitly allowed and later checked for:
>
> if (WARN_ON(excl && !(*opened & FILE_CREATED)))
> *opened |= FILE_CREATED;
D'oh... Fixed and pushed.
--
Allow the measurement of thread versus process context switch performance.
The default stays at 'process' based measurement, like lmbench's lat_ctx
benchmark.
Sample output:
comet:~/tip/tools/perf> taskset 1 ./perf bench sched pipe --threaded 0
# Running sched/pipe benchmark...
# Executed
On Tue, Sep 17, 2013 at 12:15:38PM +0530, Laxman Dewangan wrote:
> +Optional properties:
> +---
> +ams,enable_clk32k_out: Enable CLK32K output.
This looks like it should be being supported via the clock API? This
sort of thing is one of the reasons why I'm not too keen on
On Tuesday 17 September 2013 04:54 PM, Mark Brown wrote:
* PGP Signed by an unknown key
On Tue, Sep 17, 2013 at 12:15:35PM +0530, Laxman Dewangan wrote:
+MFD driver adds following mfd devices with their compatible values:
+as3722-gpio: The compatible value of this as3722 gpio driver is
+
On Tue, Sep 17, 2013 at 12:15:37PM +0530, Laxman Dewangan wrote:
> + ams,enable-oc-config: Enable overcurrent configuration of the
> + ams,oc-trip-threshold-perphase: Overcurrent trip threshold
> + ams,oc-alarm-threshold-perphase: Overcurrent alarm
[expanding CC list and bumping since the merge window is now over]
On Mon, Sep 09, 2013 at 12:44:49PM +0100, Will Deacon wrote:
> Hello,
>
> During the review of a recent patch to add support for atomic MMIO
> read-modify-write sequences between drivers on ARM, it was suggested
> that this code
On Tue, 17 Sep 2013, Russell King - ARM Linux wrote:
> On Tue, Sep 17, 2013 at 11:56:00AM +0200, Ludovic Desroches wrote:
> > Any reason to not do this:
> >
> > --- a/drivers/clocksource/tcb_clksrc.c
> > +++ b/drivers/clocksource/tcb_clksrc.c
> > @@ -144,6 +144,9 @@ static void tc_mode(enum
On Tue, Sep 17, 2013 at 12:15:35PM +0530, Laxman Dewangan wrote:
> +MFD driver adds following mfd devices with their compatible values:
> +as3722-gpio: The compatible value of this as3722 gpio driver is
> + "ams,as3722-gpio";
> +as3722-regulator: The compatible value of this as3722
The Turn-on time of the regulator depends on the regulator device's
electrical characteristics. Sometimes regulator turn-on time also
depends on the capacitive load on the given platform and it can be
more than the datasheet value.
The driver provides the enable-time as per datasheet.
Add
Dell Latitude E6510, CONFIG_DRM_NOUVEAU, 64-bit Fedora 17 user-space, Xorg
drivers, and
01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev
a2).
With 3.11 X starts fine, with 3.12-rc1 it fails with the following in
Xorg.0.log:
...
[56.819] (II) Loading
On Tue, Sep 17, 2013 at 12:53:44PM +0200, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
> > These patches optimize preempt_enable by firstly folding the preempt and
> > need_resched tests into one -- this should work for all architectures. And
> > secondly by providing per-arch preempt_count
Hi Thierry,
On 16/09/2013 10:31, Thierry Reding wrote:
> Hi,
>
> This small series allows interrupt references from the device tree to be
> resolved at driver probe time, rather than at device creation time. The
> current implementation resolves such references while devices are added
> during
> CC: "Michal Hocko" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI Motohiro"
> , linux...@kvack.org,
> cgro...@vger.kernel.org, x...@kernel.org, linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
>On Mon, Sep 16, 2013 at 10:52:46PM +0200, azurIt wrote:
>> >
On Sat, Aug 3, 2013 at 11:57 AM, Caizhiyong wrote:
> From: Cai Zhiyong
>
> Read block device partition table from command line.
> The partition used for fixed block device (eMMC) embedded device.
> It is no MBR, save storage space. Bootloader can be easily accessed by
> absolute address of data
__
> Od: Johannes Weiner
> Komu: azurIt
> Dátum: 17.09.2013 02:02
> Predmet: Re: [patch 0/7] improve memcg oom killer robustness v2
>
> CC: "Michal Hocko" , "Andrew Morton"
> , "David Rientjes" ,
> "KAMEZAWA Hiroyuki" , "KOSAKI
This patch fixes lack of license, otherwise x509_key_parser.ko taints kernel.
Signed-off-by: Konstantin Khlebnikov
---
crypto/asymmetric_keys/x509_public_key.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/crypto/asymmetric_keys/x509_public_key.c
This patch fixes lack of license, otherwise mpi.ko taints kernel.
Signed-off-by: Konstantin Khlebnikov
---
lib/mpi/mpiutil.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/mpi/mpiutil.c b/lib/mpi/mpiutil.c
index 657979f..bf076d2 100644
--- a/lib/mpi/mpiutil.c
+++
Hi Stephen,
On Tuesday 17 September 2013 12:31 PM, Stephen Rothwell wrote:
> Hi all,
>
> This message is bcc'd to each of the contacts for the trees listed below,
> so apologies if you get two copies.
>
> I have been inspired to check the ages of the trees included in
> linux-next. Below I
On Tue, Sep 17, 2013 at 05:15:13PM +0800, baisong zhong wrote:
> From: zhongbaisong
>
> Signed-off-by: zhongbaisong
I need a changelog description in here, as to why you are making this
change, your Subject: is not descriptive at all. What is being made
"clear"?
> ---
> fs/sysfs/mount.c |
On 09/16/2013 10:47 AM, Mika Westerberg wrote:
> I'm actually thinking that it is probably better now if we don't touch the
> client runtime PM at all in the I2C core.
>
> I proposed a less intrusive solution in this same thread where we power the
> I2C controller briefly at the client ->probe()
Adding the number of bios in a remapped request to 'block_rq_remap'
tracepoint.
Request remapper clones bios in a request to track the completion
status of each bio. So the number of bios can be useful information
for investigation.
Related discussions:
On Mon, Sep 16, 2013 at 09:07:07PM +0200, Rafael J. Wysocki wrote:
> On Monday, September 16, 2013 11:47:08 AM Mika Westerberg wrote:
> > On Sun, Sep 15, 2013 at 03:48:12PM +0200, Sylwester Nawrocki wrote:
> > > On 09/13/2013 05:40 PM, Mika Westerberg wrote:
> > > [...]
> > > >>>The call to
* Peter Zijlstra wrote:
> These patches optimize preempt_enable by firstly folding the preempt and
> need_resched tests into one -- this should work for all architectures. And
> secondly by providing per-arch preempt_count implementations; with x86 using
> per-cpu preempt_count for fastest
On Tue, Sep 17, 2013 at 03:25:25AM +0200, Rafael J. Wysocki wrote:
> On Tuesday, September 17, 2013 12:31:11 AM Mark Brown wrote:
> > It shouldn't even need to do that, it should just be able to rely on the
> > controller to power itself up when asked to do work. This is how the
> > existing
sizeof() is already size_t so there is no need to cast here. Generally,
casting inside the min() macro instead of using min_t() is considered
bad style.
Signed-off-by: Dan Carpenter
diff --git a/drivers/pinctrl/pinconf.c b/drivers/pinctrl/pinconf.c
index a138965..abe66d4 100644
---
PS:Adding linux kernel for a larger forum comments
Hi Linaro,
I am trying to attach interrupt handlers to the push buttons on the
arndale board.
Your patch adds in dts information on the push buttons
menu {
+ label = "SW-TACT2";
+ gpios = < 4 1>;
+
The functions clocksource_updatefreq_hz() and clocksource_updatefreq_khz()
do not exist, The proper ones are __clocksource_updatefreq_hz() and
__clocksource_updatefreq_khz().
Signed-off-by: Xie XiuQi
---
kernel/time/clocksource.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
Oh, sorry, I lost the [PATCH] prefix on the Subject. Please ignore this
mail and I'll resend it soon.
On 2013/9/17 17:11, Xie XiuQi wrote:
> The functions clocksource_updatefreq_hz() and clocksource_updatefreq_khz()
> do not exist. The proper ones are __clocksource_updatefreq_hz() and
>
On Mon, Sep 16, 2013 at 06:08:02PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix fatal kernel-doc error in :
>
> Error(include/linux/regulator/driver.h:52): cannot understand prototype:
> 'struct regulator_linear_range '
Applied with the first line redone, but this seems like really
On Fri, Sep 13, 2013 at 01:58:42PM +0800, Xiubo Li wrote:
> This adds the Document for Freescale FTM PWM driver under
> Documentation/devicetree/bindings/pwm/.
>
> Signed-off-by: Xiubo Li
> ---
> .../devicetree/bindings/pwm/pwm-fsl-ftm.txt| 36
> ++
> 1 file
Arnaldo, Ingo,
On Mon, Sep 16, 2013 at 10:17:32AM +0100, Jean Pihet wrote:
> The newly added dwarf unwinding feature [1] requires:
> . a recent version (>= 1.1) of libunwind,
> . libunwind to be configured with --enable-debug-frame.
>
> [1] http://www.spinics.net/lists/kernel/msg1598951.html
>
Hi José,
Please see my comments below.
On Wednesday 11 of September 2013 11:08:27 José Miguel Gonçalves wrote:
> The Samsung serial driver currently does not support setting the
> RTS pin with an ioctl(TIOCMSET) call. This patch adds this support.
>
> Signed-off-by: José Miguel Gonçalves
> ---
On Tue, Sep 17, 2013 at 1:28 AM, Al Viro wrote:
> On Mon, Sep 16, 2013 at 11:02:41PM +0100, Al Viro wrote:
>> On Mon, Sep 16, 2013 at 10:09:46PM +0200, Miklos Szeredi wrote:
>>
>> > > I would definitely prefer EEXIST logics dealt with in fs/namei.c - if
>> > > nothing
>> > > else, it had been
On Tue, Sep 17, 2013 at 11:56:00AM +0200, Ludovic Desroches wrote:
> Any reason to not do this:
>
> --- a/drivers/clocksource/tcb_clksrc.c
> +++ b/drivers/clocksource/tcb_clksrc.c
> @@ -144,6 +144,9 @@ static void tc_mode(enum clock_event_mode m, struct
> clock_event_device *d)
>
> static int
Add an optional output parameter to slurp_file_len() so it can return the
actual number of bytes read.
Signed-off-by: Geert Uytterhoeven
---
kexec/arch/i386/crashdump-x86.c |5 ++---
kexec/kexec.c |4 +++-
kexec/kexec.h |2 +-
3 files changed, 6
On Tue, Sep 17, 2013 at 12:36:19PM +0300, Gleb Natapov wrote:
> On Mon, Sep 16, 2013 at 05:22:26PM +0200, Andrew Jones wrote:
> > On Mon, Sep 16, 2013 at 05:41:18PM +0300, Gleb Natapov wrote:
> > > On Mon, Sep 16, 2013 at 01:47:26PM +0200, Andrew Jones wrote:
> > > > On Mon, Sep 16, 2013 at
Signed-off-by: Geert Uytterhoeven
---
configure.ac |2 +-
kexec/Makefile |1 +
kexec/arch/m68k/Makefile | 15 +++
kexec/arch/m68k/bootinfo.c | 208
kexec/arch/m68k/bootinfo.h
Signed-off-by: Geert Uytterhoeven
---
arch/m68k/Kconfig | 17
arch/m68k/include/asm/kexec.h | 29 +
arch/m68k/kernel/Makefile |2 +
arch/m68k/kernel/machine_kexec.c | 71
Add optional support to export the bootinfo used to boot the kernel in a
"bootinfo" file in procfs. This is useful with kexec.
This is based on the similar feature for ATAGS on ARM.
Signed-off-by: Geert Uytterhoeven
---
arch/m68k/Kconfig|7
We've resisted adding System RAM to /proc/iomem because it is the wrong
place for it. Unfortunately we continue to find tools that rely on this
behaviour (e.g. kdump) so give up and add it in.
As the ST-RAM Pool is now a child of the first System RAM resource, it must
be switched from
This is a preliminary set of patches to add kexec support for m68k.
- Kexec only, no kdump support yet (do you have enough RAM to keep a
crashdump kernel in memory at all times? ;-)
- Tested on ARAnyM only. No support for other CPU/MMUs than 68040.
- Although the code contains some
On 06/03/2013 08:14 PM, Marcus Overhagen wrote:
Using correct transfer interval as specified by the USB endpoint
when doing the interrupt transfer fixes the warning printed by
xhci USB core on every transfer that resulted in spamming
"xhci_queue_intr_tx: 74 callbacks suppressed" to syslog
every
> No problem sorry the commit message was a little vague there.
> Seems I accidentally generated the first version of this patch
> against the ASoC tree, but this got me thinking now you are
> looking after MFD patches which tree should I be generating them
> against?
That depends. If you are
On Tue, Sep 17, 2013 at 02:29:22PM +0530, Adil Mujeeb wrote:
> Hi,
>
>
> >- PowerData = (1 << 31) | (0 << 30) | (24 << 24) |
> BitReverse(w89rf242_txvga_data[i][0], 24);
> >+ PowerData = (1 << 31) | (0 << 30) | (24 << 24)
> >+ |
Add cc John Stultz
On 2013/9/17 17:11, Xie XiuQi wrote:
> The functions clocksource_updatefreq_hz() and clocksource_updatefreq_khz()
> do not exist. The proper ones are __clocksource_updatefreq_hz() and
> __clocksource_updatefreq_khz().
>
> Signed-off-by: Xie XiuQi
> ---
>
Hi Mike,
On Thu, Sep 12, 2013 at 11:35:52AM -0700, Mike Dunn wrote:
> Currently the driver assumes that the values specified in the
> brightness-levels
> device tree property increase as they are parsed from left to right. But
> boards
> that invert the signal between the PWM output and the
On Mon, Sep 16, 2013 at 05:22:26PM +0200, Andrew Jones wrote:
> On Mon, Sep 16, 2013 at 05:41:18PM +0300, Gleb Natapov wrote:
> > On Mon, Sep 16, 2013 at 01:47:26PM +0200, Andrew Jones wrote:
> > > On Mon, Sep 16, 2013 at 11:55:17AM +0300, Gleb Natapov wrote:
> > > > On Mon, Sep 16, 2013 at
On Tue, 2013-09-17 at 10:22 +0530, Viresh Kumar wrote:
> Current code looks like this:
>
> WARN_ON(lock_policy_rwsem_write(cpu));
> update_policy_cpu(policy, new_cpu);
> unlock_policy_rwsem_write(cpu);
>
> {lock|unlock}_policy_rwsem_write(cpu) takes/releases policy->cpu's
v1 has the subject of "Rework ACPI video driver" and is posted here:
http://lkml.org/lkml/2013/9/9/74
Since the objective is really to fix Win8 backlight issues, I changed
the subject in this version, sorry about that.
This patchset has three patches, the first introduced a new API named
According to Matthew Garrett, "Windows 8 leaves backlight control up
to individual graphics drivers rather than making ACPI calls itself.
There's plenty of evidence to suggest that the Intel driver for
Windows 8 doesn't use the ACPI interface, including the fact that
it's broken on a bunch of
Introduce a new API for modules to query if a specific type of backlight
device has been registered. This is useful for some backlight device
provider module(e.g. ACPI video) to know if a native control
interface(e.g. the interface created by i915) is available and then do
things accordingly(e.g.
The backlight control and event delivery functionality provided by ACPI
video module is mixed together and registered all during video device
enumeration time. As a result, the two functionality are also removed
together on module unload time or by the acpi_video_unregister function.
The two
Remove the bloat of the C calling convention out of the
preempt_enable() sites by creating an ASM wrapper which allows us to
do an asm("call ___preempt_schedule") instead.
calling.h bits by Andi Kleen
Suggested-by: Linus Torvalds
Signed-off-by: Peter Zijlstra
---
Convert x86 to use a per-cpu preemption count. The reason for doing so
is that accessing per-cpu variables is a lot cheaper than accessing
thread_info variables.
We still need to save/restore the actual preemption count due to
PREEMPT_ACTIVE so we place the per-cpu __preempt_count variable in the
No problem sorry the commit message was a little vague there.
Seems I accidentally generated the first version of this patch
against the ASoC tree, but this got me thinking now you are
looking after MFD patches which tree should I be generating them
against?
Thanks,
Charles
On Tue, Sep 17, 2013
These patches optimize preempt_enable by firstly folding the preempt and
need_resched tests into one -- this should work for all architectures. And
secondly by providing per-arch preempt_count implementations; with x86 using
per-cpu preempt_count for fastest access.
These patches have been boot
In order to prepare to per-arch implementations of preempt_count move
the required bits into an asm-generic header and use this for all
archs.
Signed-off-by: Peter Zijlstra
---
arch/alpha/include/asm/Kbuild |1
arch/arc/include/asm/Kbuild|1
arch/arm/include/asm/Kbuild
In order to combine the preemption and need_resched test we need to
fold the need_resched information into the preempt_count value.
Since the NEED_RESCHED flag is set across CPUs this needs to be an
atomic operation, however we very much want to avoid making
preempt_count atomic, therefore we
We're going to deprecate and remove set_need_resched() for it will do
the wrong thing. Make an exception for RCU and allow it to use
resched_cpu() which will do the right thing.
Cc: Paul McKenney
Signed-off-by: Peter Zijlstra
---
kernel/rcutree.c| 15 ++-
kernel/sched/core.c
Rewrite the preempt_count macros in order to extract the 3 basic
preempt_count value modifiers:
__preempt_count_add()
__preempt_count_sub()
and the new:
__preempt_count_dec_and_test()
And since we're at it anyway, replace the unconventional
$op_preempt_count names with the more
Mike reported that commit 7d1a9417 ("x86: Use generic idle loop")
regressed several workloads and caused excessive reschedule
interrupts.
The patch in question failed to notice that the x86 code had an
inverted sense of the polling state versus the new generic code (x86:
default polling, generic:
301 - 400 of 928 matches
Mail list logo
