On Wed, 25 Feb 2015 11:35:35 +0100
Peter Zijlstra wrote:
> On Tue, Feb 24, 2015 at 01:39:46PM -0500, Steven Rostedt wrote:
> > Index: linux-rt.git/kernel/sched/rt.c
> > ===
> > --- linux-rt.git.orig/kernel/sched/rt.c 2015-02-24 1
On Wednesday 25 February 2015 10:36:20 Pranith Kumar wrote:
> This patch adds support for a half-word xchg() for ARM using ldrexh/strexh
> instructions. It also fixes an asm comment for __cmpxchg2.
>
> Currently using a half-word xchg() results in the following splat on an ARMv7
> machine.
>
> [
On 02/25/2015 03:24 PM, David Vrabel wrote:
On 24/02/15 06:27, Juergen Gross wrote:
On 02/19/2015 07:07 PM, David Vrabel wrote:
On 18/02/2015 06:51, Juergen Gross wrote:
+{
+unsigned long pfn;
+unsigned long area_start, area_end;
+unsigned i;
+
+for (i = 0; i < XEN_N_RESERVED_A
On Mon, Nov 24, 2014 at 04:17:12PM -0800, Andrew Bresticker wrote:
> This series adds support for xHCI on NVIDIA Tegra SoCs. This includes:
> - patches 1, 2, and 3: minor cleanups for mailbox framework and xHCI,
> - patches 4 and 5: adding a driver for the mailbox used to communicate
>with t
Hi,
commit in $Subject breaks my kvm guest on AMD host, causing it to do the
following below. Mouse doesn't work anymore in the guest, network is
gone too.
Reverting it fixes the issue.
---
...
[4.849095] Freeing unused kernel memory: 2972K (81aee000 -
81dd5000)
[7.016
On Wed, 25 Feb 2015 16:40:49 +0100
Denys Vlasenko wrote:
> >> The downside would be that if we ever grow past 1024
> >> syscall entries we'll be in trouble if new userspace calls
> >> syscall 513 on an old kernel and gets syscall 1.
> >
> > What if we test against ~0x3ff and jump to sys_ni if any
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-qup.c | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/drivers/i2c/busses/i2c-qup.c b/drivers/i2c/busses/i2c-qup.c
index 4dad23bdffbe90..fdcbdab808e9fc 100644
--- a/drivers/i2c/b
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-cpm.c | 20 +---
1 file changed, 9 insertions(+), 11 deletions(-)
diff --git a/drivers/i2c/busses/i2c-cpm.c b/drivers/i2c/busses/i2c-cpm.c
index 2d466538b2e2c9..714bdc837769fd 100644
--- a/drivers/i2c/bus
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-viperboard.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-viperboard.c
b/drivers/i2c/busses/i2c-viperboard.c
index 7533fa34d73711..47e88adf2011e1 100644
--- a/driv
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-powermac.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/i2c/busses/i2c-powermac.c
b/drivers/i2c/busses/i2c-powermac.c
index 60a53c169ed2b3..6abcf696e3594b 100644
--- a/drivers/i2
On 02/24/2015 08:53 PM, Bjorn Helgaas wrote:
On Thu, Feb 05, 2015 at 04:52:58PM -0500, Murali Karicheri wrote:
If there is a DT node available for the root bridge's parent device,
use the dma configuration from that device node. For example, keystone
PCI devices would require dma_pfn_offset to b
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-pmcmsp.c | 42 -
1 file changed, 16 insertions(+), 26 deletions(-)
diff --git a/drivers/i2c/busses/i2c-pmcmsp.c b/drivers/i2c/busses/i2c-pmcmsp.c
index d37d9db6681e7b..2c40edbf6224
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-bcm-iproc.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/drivers/i2c/busses/i2c-bcm-iproc.c
b/drivers/i2c/busses/i2c-bcm-iproc.c
index d3c89157b33774..f9f2c2082151e2 100644
--- a/dr
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-axxia.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/i2c/busses/i2c-axxia.c b/drivers/i2c/busses/i2c-axxia.c
index 768a598d8d03ad..488c5d3bf9dba7 100644
--- a/drivers/i2c/busses/
From: Wolfram Sang
Let the core do the checks if HW quirks prevent a transfer. Saves code
from drivers and adds consistency.
Signed-off-by: Wolfram Sang
---
drivers/i2c/i2c-core.c | 62 ++
1 file changed, 62 insertions(+)
diff --git a/drivers/i2
From: Wolfram Sang
The number of I2C adapters which are not fully I2C compatible is rising,
sadly. Drivers usually do handle the flaws, still the user receives only
some errno for a transfer which normally can be expected to work. This
patch introduces a formal description of flaws. One advantage
From: Wolfram Sang
Here is the second version of the patch series to describe i2c adapter quirks
in a generic way. For the motivation, please read description of patch 1. This
is still RFC because I would like to do some more tests on my own, but I need
to write a tool for that. However, I'd real
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-dln2.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/i2c/busses/i2c-dln2.c b/drivers/i2c/busses/i2c-dln2.c
index b3fb86af4cbb14..b6f9ba7eb17564 100644
--- a/drivers/i2c/busses/i2
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-at91.c | 32 +++-
1 file changed, 11 insertions(+), 21 deletions(-)
diff --git a/drivers/i2c/busses/i2c-at91.c b/drivers/i2c/busses/i2c-at91.c
index 636fd2efad8850..b3a70e8fc653c5 100644
--- a
From: Wolfram Sang
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-opal.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/i2c/busses/i2c-opal.c b/drivers/i2c/busses/i2c-opal.c
index 16f90b1a750894..b2788ecad5b3cb 100644
--- a/drivers/i
On Wed, Feb 25, 2015 at 11:01:29AM -0500, Steven Rostedt wrote:
> I'm just curious, do all these micro optimizations have any real impact
> on real use cases?
>
> That is, if we are going to make the system less robust, shouldn't we
> show that it has real benefit?
I'm wondering the same thing th
On Tue, Feb 24, 2015 at 3:45 AM, Denys Vlasenko wrote:
> On 02/24/2015 12:58 AM, Andy Lutomirski wrote:
>>> - Next possible change is to use PUSH insns to build the stack. Something
>>> along the lines of
>>> swapgs
>>> mov %rsp,%gs:old_rsp
>>> mov %gs:kernel_stack
Robert,
On 25/02/15 17:17, Robert Abel wrote:
> Hi Roger,
>
> On 25 Feb 2015 11:44, Roger Quadros wrote:
>> typo ATTCHEDDEVICEPAGELENGTH->ATTACHEDDEVICEPAGELENGTH
> Yep.
>>> +/** DEVICESIZE Max Value */
>>> +#define GPMC_CONFIG1_DEVICESIZE_MAX GPMC_CONFIG1_DEVICESIZE_16
>> Shouldn't this be
On Wednesday 25 February 2015 11:03:02 Murali Karicheri wrote:
>
> > (I don't know exactly how these patches all fit together, so that's
> > probably not accurate, but that's the *sort* of thing I'd like to include.)
> >
> > If that actually *is* what's going on, I have to wonder why this isn't
>
Hi Tyler, Eduardo,
On 24/02/2015 20:56, Tyler Hall wrote:
> Eduardo,
>
> On Tue, Feb 24, 2015 at 1:36 PM, Eduardo Valentin wrote:
>> The fix seams reasonable. Although, it remains the question what is
>> applicability to other Armada chips? Besides, shouldn't we simply use it
>> by default? Also
On Wed, Feb 25, 2015 at 10:58 AM, Arnd Bergmann wrote:
> On Wednesday 25 February 2015 10:36:20 Pranith Kumar wrote:
>> This patch adds support for a half-word xchg() for ARM using ldrexh/strexh
>> instructions. It also fixes an asm comment for __cmpxchg2.
>>
>> Currently using a half-word xchg()
On Wed 25-02-15 14:31:08, SeongJae Park wrote:
> Hello Michal,
>
> Thanks for your comment :)
>
> On Tue, 24 Feb 2015, Michal Hocko wrote:
>
> >On Tue 24-02-15 04:54:18, SeongJae Park wrote:
> >[...]
> >> include/linux/cma.h |4 +
> >> include/linux/gcma.h | 64 +++
> >> mm/Kconfig
To cleanly restore an SMP VM we need to ensure that the current pause
state of each vcpu is correctly recorded. Things could get confused if
the CPU starts running after migration restore completes when it was
paused before it state was captured.
We use the existing KVM_GET/SET_MP_STATE ioctl to d
From: Christoffer Dall
There is an interesting bug in the vgic code, which manifests itself
when the KVM run loop has a signal pending or needs a vmid generation
rollover after having disabled interrupts but before actually switching
to the guest.
In this case, we flush the vgic as usual, but we
From: Christoffer Dall
When a VCPU is no longer running, we currently check to see if it has a
timer scheduled in the future, and if it does, we schedule a host
hrtimer to notify is in case the timer expires while the VCPU is still
not running. When the hrtimer fires, we mask the guest's timer a
From: Christoffer Dall
Migrating active interrupts causes the active state to be lost
completely. This implements some additional bitmaps to track the active
state on the distributor and export this to user space.
Signed-off-by: Christoffer Dall
Signed-off-by: Alex Bennée
---
AJB:
- fixed
In Intel Quark SoC X1000, there is one on-die digital temperature sensor(DTS).
The DTS offers both hot & critical trip points.
However, in current distribution of UEFI BIOS for Quark platform, only
critical trip point is configured to be 105 degree Celsius (based on Quark
SW ver1.0.1 and hot trip
On Wed, Feb 25, 2015 at 1:45 AM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> - BUG_ON(((current_stack_pointer() ^
>> this_cpu_read_stable(kernel_stack))
>> + BUG_ON(((current_stack_pointer() ^
>> +(this_cpu_read_stable(kernel_stack) - 1))
>> &
Robert,
On 25/02/15 17:06, Robert Abel wrote:
> Hi Roger,
>
> On 25 Feb 2015 13:02, Roger Quadros wrote:
>> This creates platform devices for the children of child, but what about
>> platform device for the child itself?
> It seems my first try in the other patch set wasn't so wrong after all. M
Dear maintainers,
This patch introduces DTS thermal driver for Intel Quark X1000.
The code implementation is based on intel_soc_dts_thermal.c.
Intel Quark X1000 has one on-die DTS with two configurable trip points:
critical and hot trip points. However, todate, UEFI BIOS for Quark X1000
uses only
GICv2 specific ACPI boot support
Hanjun Guo
20150225
[PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
Marc Zyngier
20150223
"In my queue" means it's queued up for review, nothing more.
I'm certain there are patches for consideration for this cycle w
Hi Roger,
On 25 Feb 2015 17:18, Roger Quadros wrote:
OK. Would be interesting to see how unconditional call to
of_platform_decide_create() behaves
for your case.
I'm not able to test today, so results will be in tomorrow. If that
doesn't work, I'll just resubmit my first patch with the conditi
Hi Tony,
On 25 Feb 2015 16:23, Tony Lindgren wrote:
* Roger Quadros [150225 05:28]:
On 24/02/15 22:05, Robert ABEL wrote:
DTS output was formatted to require additional work when copy-pasting into DTS.
Nano-second timings were removed, because they were not a confidence interval
nor
an indic
On 02/25/2015 02:38 AM, Ingo Molnar wrote:
> * Jason Baron wrote:
>
>> Hi,
>>
>> When we are sharing a wakeup source among multiple epoll
>> fds, we end up with thundering herd wakeups, since there
>> is currently no way to add to the wakeup source
>> exclusively. This series introduces a new E
On 25/02/15 18:23, Robert Abel wrote:
> Hi Roger,
>
> On 25 Feb 2015 17:18, Roger Quadros wrote:
>> OK. Would be interesting to see how unconditional call to
>> of_platform_decide_create() behaves
>> for your case.
> I'm not able to test today, so results will be in tomorrow. If that doesn't
> w
On 2/24/2015 9:47 PM, Ethan Zhao wrote:
Viresh,
Will do that when I get the test box.
Thanks Ethan.
On Wed, Feb 25, 2015 at 12:35 PM, viresh kumar wrote:
On Wednesday 25 February 2015 08:54 AM, Ethan Zhao wrote:
Viresh,
With this patch applied, still got the following warning and
On Wed, Feb 25, 2015 at 09:28:36PM +0800, zhangfei wrote:
> +static void hi6220_detect_work(struct work_struct *work)
> +{
> + struct hi6220_priv *priv =
> + container_of(work, struct hi6220_priv, work.work);
> + int gpio_id, gpio_vbus;
>
On 24/02/15 22:05, Robert ABEL wrote:
> The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
> even though the access is defined as asynchronous, and no GPMC_CLK clock
> is provided to the external device. Still, GPMCFCLKDIVIDER is used as a
> divider
> for the GPMC clock, so
else if at line 406 has the same condition as the else if at line 404.
i chosed 0x5 because it's half 0xb (just a rate controller)
Signed-off-by : Ameen Ali
---
drivers/staging/rtl8188eu/hal/Hal8188ERateAdaptive.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/stagin
Maxime Coquelin wrote:
> > Is support for this in upstream binutils and gcc? What's the preferred
> > target tuple? I'll add support to Fedora's cross-binutils and cross-gcc
> > sets if I can.
>
> I just rebuilt using latest upstream binutils and gcc.
> To compile Kernel and bootloader, I buil
* Scott Wood | 2015-02-23 17:27:31 [-0600]:
>This isn't a host PIC driver. It's guest PIC emulation, some of which
>is indeed not suitable for a rawlock (in particular, openpic_update_irq
>which loops on the number of vcpus, with a loop body that calls
>IRQ_check() which loops over all pending IR
From: Rik van Riel
The previous patch makes it so the code skips over isolcpus when
building scheduler load balancing domains. This makes it hard to
see for a user which of the CPUs in a cpuset are participating in
load balancing, and which ones are isolated cpus.
Add a cpuset.isolcpus file with
From: Rik van Riel
Ensure that cpus specified with the isolcpus= boot commandline
option stay outside of the load balancing in the kernel scheduler.
Operations like load balancing can introduce unwanted latencies,
which is exactly what the isolcpus= commandline is there to prevent.
Previously,
-v2 addresses the conflict David Rientjes spotted between my previous
patches and commit e8e6d97c9b ("cpuset: use %*pb[l] to print bitmaps
including cpumasks and nodemasks")
Ensure that cpus specified with the isolcpus= boot commandline
option stay outside of the load balancing in the kernel sched
> The CAT thing was annoying already, but at least one can find that in
> the SDM, this RDT thing, not a single mention.
The problems of development at the bleeding edge. Would you rather Linux
sat on the sidelines until there are enough Google hits from other users of
new features?
I did get one
On Tue, Feb 24, 2015 at 06:09:52PM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.70 release.
> There are 16 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Wed, 25 Feb 2015, Michal Hocko wrote:
On Wed 25-02-15 14:31:08, SeongJae Park wrote:
Hello Michal,
Thanks for your comment :)
On Tue, 24 Feb 2015, Michal Hocko wrote:
On Tue 24-02-15 04:54:18, SeongJae Park wrote:
[...]
include/linux/cma.h |4 +
include/linux/gcma.h | 64 +++
mm/
On Tue, Feb 24, 2015 at 06:10:02PM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.34 release.
> There are 17 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
So here is the v2 of the patch set to support the Bamboo PAD.
It has been tested by Josep (thanks!) on the wired version and I
developped it on the wireless version. I guess it should be good
to go if the reviews goes well.
Cheers,
Benjamin
Benjamin Tissoires (2):
HID: wacom: store the hid_dev
This patch adds support for the global clock controller found on the MSM8916
based devices. It allows the various device drivers to probe and control
their clocks and resets.
Signed-off-by: Georgi Djakov
---
Changes since v1:
* Addressed comments from Stephen Boyd and Archit Taneja
* Fixed som
The Bamboo PAD in debug mode needs to re-route events from the debug
interface to the Pen interface. This can be easily done with
hid_input_report(), but that means that we need to keep a reference to
the various hid_devices.
There should be only one touch and one pen interface per physical tablet
The stylus of this device works just fine out of the box.
The touch is seen by default as a mouse with relative events and some
gestures.
The wireless and the wired version have slightly different firmwares, but
the debug mode 2 on the feature 2 is common to the 2 devices. In this mode,
all the rep
On Tue, Feb 24, 2015 at 06:10:15PM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.8 release.
> There are 20 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Tue, 24 Feb 2015, Jaewon Kim wrote:
> This patch adds MAX77843 core/irq driver to support PMIC,
> MUIC(Micro USB Interface Controller), Charger, Fuel Gauge,
> LED and Haptic device.
>
> Cc: Lee Jones
> Signed-off-by: Jaewon Kim
> Signed-off-by: Beomho Seo
> ---
> drivers/mfd/Kconfig
On Wed, 25 Feb 2015, Russell King - ARM Linux wrote:
> On Thu, Feb 05, 2015 at 04:11:00PM +, Russell King - ARM Linux wrote:
> > On Thu, Feb 05, 2015 at 06:29:18AM -0800, Paul E. McKenney wrote:
> > > Works for me, assuming no hidden uses of RCU in the IPI code. ;-)
> >
> > Sigh... I kind'a
On 2/24/15 4:13 PM, Andi Kleen wrote:
--- a/tools/perf/Documentation/perf-record.txt
+++ b/tools/perf/Documentation/perf-record.txt
@@ -241,6 +241,9 @@ Capture machine state (registers) at interrupt, i.e., on
counter overflows for
each sample. List of captured registers depends on the architec
On 02/25/2015 01:37 PM, Andrey Wagin wrote:
> Hello Denys,
>
> My test vm doesn't boot with this patch. Could you help to investigate
> this issue?
>
> I have attached a kernel config and console log.
>
> [2.508252] traps: systemd-cgroups[380] general protection ip:7f68ad096028
> sp:7fffba2
KY Srinivasan writes:
>> -Original Message-
>> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
>> Sent: Thursday, February 19, 2015 8:27 AM
>> To: KY Srinivasan; de...@linuxdriverproject.org
>> Cc: Haiyang Zhang; linux-kernel@vger.kernel.org; Dexuan Cui
>> Subject: [PATCH 1/2] Drivers
Robert,
On 24/02/15 22:05, Robert ABEL wrote:
> The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
> even though the access is defined as asynchronous, and no GPMC_CLK clock
> is provided to the external device. Still, GPMCFCLKDIVIDER is used as a
> divider
> for the GPMC c
On Wednesday 25 February 2015 11:11:28 Pranith Kumar wrote:
> On Wed, Feb 25, 2015 at 10:58 AM, Arnd Bergmann wrote:
> > On Wednesday 25 February 2015 10:36:20 Pranith Kumar wrote:
> >> This patch adds support for a half-word xchg() for ARM using ldrexh/strexh
> >> instructions. It also fixes an a
On 24 February 2015 at 12:23, Ashwin Chaugule
wrote:
> On 20 February 2015 at 15:16, Stephen Boyd wrote:
>> On 02/20, Will Deacon wrote:
>>> On Fri, Feb 13, 2015 at 06:24:09PM +, Stephen Boyd wrote:
>>>
>>> > +static void scorpion_evt_setup(int idx, u32 config_base)
>>> > +{
>>> > + u32
On Wed, Feb 25, 2015 at 11:47:48AM -0500, Nicolas Pitre wrote:
> I completely agree with the r/w spinlock. Something like this ought to
> be sufficient to make gic_raise_softirq() reentrant which is the issue
> here, right? I've been stress-testing it for a while with no problems
> so far.
No.
On Wed, Feb 25, 2015 at 04:19:45PM +0100, Richard Cochran wrote:
> Let me suggest another approach that stays in line with the existing
> frame work. Based on the device's limitations and your own example,
> it seems clear that the intended use case is synchronization for AVB
> applications using
Hi Tyler,
On 10/02/2015 23:50, Tyler Hall wrote:
> The current register being used to read the temperature returns a noisy value
> that is prone to variance and occasional outliers. The value in the thermal
> manager control and status register appears to have the same scale but much
> less variab
On Wed, Feb 25, 2015 at 04:58:35PM +0100, Arnd Bergmann wrote:
> On Wednesday 25 February 2015 10:36:20 Pranith Kumar wrote:
> > This patch adds support for a half-word xchg() for ARM using ldrexh/strexh
> > instructions. It also fixes an asm comment for __cmpxchg2.
> >
> > Currently using a half
Hi Roger,
On 25 Feb 2015 17:58, Roger Quadros wrote:
static unsigned int gpmc_ticks_to_ps(unsigned int ticks)
@@ -346,16 +395,22 @@ static void gpmc_cs_bool_timings(int cs, const struct
gpmc_bool_timings *p)
* @st_bit Start Bit
* @end_bit End Bit. Must be >= @st_bit.
* @nameDTS no
The WaRP Board is a Wearable Reference Plaform. The board features:
- Freescale i.MX6 SoloLite processor with 512MB of RAM
- Freescale FXOS8700CQ 6-axis Xtrinsic sensor
- Freescale Kinetis KL16 MCU
- Freescale Xtrinsic MMA955xL intelligent motion sensing platform
The board implements a hybrid
Beaglebone Black doesn't have AES and SHAM enabled like the
original Beaglebone White dts. This breaks applications that
leverage the crypto blocks so fix this by enabling these nodes.
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/am335x-boneblack.dts | 8
1 file changed, 8 insertion
On 5 February 2015 at 04:27, Paul Bolle wrote:
> On Wed, 2015-02-04 at 15:22 -0700, mathieu.poir...@linaro.org wrote:
>> From: Pratik Patel
>>
>> This driver adds support for the STM CoreSight IP block,
>> allowing any system compoment (HW or SW) to log and
>> aggregate messages via a single enti
During the research for my masters thesis i came across the
OMAP4_ERRATA_I688 option and realized, it is never possible to enable
this option.
The a62a6e98 commit added the "&& !ARCH_MULTIPLATFORM" dependency to
disable this option for multiplatforms. However, because of enclosing
dependencies, th
Hi Richard,
On 25/02/15 17:01, Richard Cochran wrote:
On Wed, Feb 25, 2015 at 04:19:45PM +0100, Richard Cochran wrote:
Let me suggest another approach that stays in line with the existing
frame work. Based on the device's limitations and your own example,
it seems clear that the intended use c
On Wed, Feb 25, 2015 at 10:51:16AM -0500, Steven Rostedt wrote:
> > > +static void try_to_push_tasks(void *arg)
> > > +{
> > > + struct rt_rq *rt_rq = arg;
> > > + struct rq *rq, *next_rq;
> > > + int next_cpu = -1;
> > > + int next_prio = MAX_PRIO + 1;
> > > + int this_prio;
> > > + int src_prio;
On Fri, Feb 20, 2015 at 10:58:15AM -0800, Andy Lutomirski wrote:
> - /* Auto enable eagerfpu for xsaveopt */
> - if (cpu_has_xsaveopt && eagerfpu != DISABLE)
> + /* Auto enable eagerfpu for everyone */
> + if (eagerfpu != DISABLE)
> eagerfpu = ENABLE;
So Mel did run s
On Wed, Feb 25, 2015 at 05:21:54PM +0100, Arnd Bergmann wrote:
> On Wednesday 25 February 2015 11:11:28 Pranith Kumar wrote:
> > On Wed, Feb 25, 2015 at 10:58 AM, Arnd Bergmann wrote:
> > > On Wednesday 25 February 2015 10:36:20 Pranith Kumar wrote:
> > >> This patch adds support for a half-word x
On Thu, Feb 05, 2015 at 12:27:31PM +0100, Paul Bolle wrote:
> I'm _guessing_ that CPU_32v4 and CPU_32v4T are needed for the ldrd and
> strd assembler instructions. If that's right a next _guess_ would be
> that you also need to mention CPU_32v3 here.
No. Double word instructions are available in
On Wed, Feb 25, 2015 at 04:34:16PM +0100, Lukasz Majewski wrote:
> Presented patches add support for Odroid's U3 optional CPU FAN, which uses PWM
> subsystem for low level control.
>
> After successful probe it registers itself as a cooling device for thermal
> subsystem.
>
> This driver also sup
On Wed, Feb 25, 2015 at 2:02 PM, Otavio Salvador
wrote:
> The WaRP Board is a Wearable Reference Plaform. The board features:
>
> - Freescale i.MX6 SoloLite processor with 512MB of RAM
> - Freescale FXOS8700CQ 6-axis Xtrinsic sensor
> - Freescale Kinetis KL16 MCU
> - Freescale Xtrinsic MMA955x
Hi,
Adding Santosh to Cc on this one.
* Stefan Hengelein [150225 09:13]:
> During the research for my masters thesis i came across the
> OMAP4_ERRATA_I688 option and realized, it is never possible to enable
> this option.
>
> The a62a6e98 commit added the "&& !ARCH_MULTIPLATFORM" dependency to
Robert,
On 25/02/15 19:07, Robert Abel wrote:
> Hi Roger,
>
> On 25 Feb 2015 17:58, Roger Quadros wrote:
>>> static unsigned int gpmc_ticks_to_ps(unsigned int ticks)
>>> @@ -346,16 +395,22 @@ static void gpmc_cs_bool_timings(int cs, const struct
>>> gpmc_bool_timings *p)
>>>* @st_bit Start
Robert,
On 25/02/15 18:33, Roger Quadros wrote:
> On 24/02/15 22:05, Robert ABEL wrote:
>> The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
>> even though the access is defined as asynchronous, and no GPMC_CLK clock
>> is provided to the external device. Still, GPMCFCLKDIV
Hi Roger,
On 25 Feb 2015 17:33, Roger Quadros wrote:
./scripts/checkpatch.pl detects some styling errors.
Well, there's like a million lines over 80 characters. I'm also a
heathen and don't use an 80 character terminal either.
I'll fix the more serious issues checkpatch finds, but some styling
On Wed, Feb 25, 2015 at 05:12:08PM +, Stathis Voukelatos wrote:
> Regarding this last point, the actual counter that generates the
> timestamps is not part of the sniffer H/W module. Timestamps are
> provided to the sniffer externally in H/W by a different module.
> Apart of that there is not e
On 25 Feb 2015 18:20, Roger Quadros wrote:
Need to patch mach-omap2/usb-tusb6010.c as well. else we get
arch/arm/mach-omap2/usb-tusb6010.c: In function ‘tusb_set_async_mode’:
arch/arm/mach-omap2/usb-tusb6010.c:74:2: error: too few arguments to function
‘gpmc_cs_set_timings’
In file included fro
Hi Roger,
On 25 Feb 2015 18:17, Roger Quadros wrote:
How will the user know by looking at the kernel log that it was really an error?
We don't fail probe if set_gpmc_timing_reg() fails so I feel it is necessary to
clearly show an Error message.
You can probably reword it like "%s: Error!! GPMC
On Wed, Feb 25, 2015 at 12:02 PM, Russell King - ARM Linux
wrote:
>> Unfortunately, the BUG message seems incomplete, can you reproduce this
>> with CONFIG_DEBUG_BUGVERBOSE enabled?
>
> That isn't because CONFIG_DEBUG_BUGVERBOSE isn't set. It's because
> the message author decided that the remain
On 25/02/15 19:22, Robert Abel wrote:
> Hi Roger,
>
> On 25 Feb 2015 18:17, Roger Quadros wrote:
>> How will the user know by looking at the kernel log that it was really an
>> error?
>> We don't fail probe if set_gpmc_timing_reg() fails so I feel it is necessary
>> to
>> clearly show an Error m
On 2/25/2015 9:14 AM, Tony Lindgren wrote:
Hi,
Adding Santosh to Cc on this one.
* Stefan Hengelein [150225 09:13]:
During the research for my masters thesis i came across the
OMAP4_ERRATA_I688 option and realized, it is never possible to enable
this option.
The a62a6e98 commit added the "&&
On Wed, Feb 25, 2015 at 12:14 PM, Russell King - ARM Linux
wrote:
> Actually, I think we ought to get rid of __bad_xchg() so that cases
> like this cause a link error instead of a runtime error, just like we
> do in other cases as well.
>
> That's something that goes back ages (it used to be calle
Hi Thierry,
> Sorry for taking so awfully long to look at this. I've spent some time
> looking at various pieces of documentation and I concluded that
> representing the port assignment as muxing options doesn't seem right
> after all. Instead I've come up with an alternate proposal (attached).
>
On Wed, Feb 25, 2015 at 12:34:35PM -0500, Pranith Kumar wrote:
> On Wed, Feb 25, 2015 at 12:14 PM, Russell King - ARM Linux
> wrote:
> > Actually, I think we ought to get rid of __bad_xchg() so that cases
> > like this cause a link error instead of a runtime error, just like we
> > do in other cas
On Wed, Feb 25, 2015 at 11:21 AM, Arnd Bergmann wrote:
>>
>> More information:
>> [ 45.833303] xchg: bad data size: pc 0xbe806020, ptr 0xeb18deee, size 2
>> [ 45.833324] [ cut here ]
>> [ 45.837939] kernel BUG at
>> /dvs/git/dirty/git-master_linux/kernel/arch/arm/kern
Remove this configuration bit in crtc driver as the rising edge clock is widely
used.
Signed-off-by: Boris BREZILLON
Signed-off-by: Nicolas Ferre
---
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/atmel-hlcdc/at
On 02/25/15 03:30, Masanari Iida wrote:
> This patch fix spelling typos in Documentations/input.
>
> Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Thanks.
> ---
> Documentation/input/alps.txt| 4 ++--
> Documentation/input/event-codes.txt | 2 +-
> Documentation/input/g
On Wed, Feb 25, 2015 at 08:46:29AM -0800, Guenter Roeck wrote:
> On Tue, Feb 24, 2015 at 06:10:15PM -0800, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.18.8 release.
> > There are 20 patches in this series, all will be posted as a response
> > to this one. I
Hi Al,
commit 3b994d98a815d934ab6a77a380882865982c14f9 (get rid of the second
argument of acct_kill()) added a new build warning when building
kernel/acct.c. Warning can be seen below. Revert of that commit is
non-trivial, so I haven't tried to check if reverting it fixes the
warning.
One one to
301 - 400 of 878 matches
Mail list logo
