On Fri, Mar 17, 2017 at 10:58:56AM +0100, M'boumba Cedric Madianga wrote:
> This patch adds initial support for the STM32F7 I2C controller.
>
> Signed-off-by: M'boumba Cedric Madianga
So, the STM32F7 has a new I2C IP core compared to STM32F4?
signature.asc
Description: PGP signature
Hi Neil,
On Thu, Mar 23, 2017 at 5:27 PM, Neil Armstrong wrote:
> When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges
> is needed when gpiochip_add_data() is called but in the current implementation
> the ranges are added from the driver afterwards.
>
> A simple solution is
On Thu, Mar 23, 2017 at 10:25 AM, Thomas Garnier wrote:
> This patch ensures a syscall does not return to user-mode with a kernel
> address limit. If that happened, a process can corrupt kernel-mode
> memory and elevate privileges.
>
> For example, it would mitigation this bug:
>
> - https://bugs.
On Thu, Mar 23, 2017 at 09:46:12PM +0200, Andy Shevchenko wrote:
> By some reason acpi_find_gpio() and acpi_gpio_count() have compared connection
> ID to "gpios" when tries to check if suffix is needed or not.
>
> Don't do any assumptions about what connection ID can be and, when defined,
> use
>
On Thu, Mar 23, 2017 at 09:46:14PM +0200, Andy Shevchenko wrote:
> The commit 10cf4899f8af ("gpiolib: tighten up ACPI legacy gpio lookups")
> prevents to getting same resource twice if the driver asks twice using same
s/same/different/
> connection ID.
>
> But the whole idea of fallback might br
On Thu, Mar 23, 2017 at 11:56:56AM +, Jon Hunter wrote:
> Enable the Tegra BPMP I2C adapter by default if the Tegra BPMP itself
> is enabled. This adapter is used as the I2C interface for the PMIC on
> the Tegra186 Jetson-TX2 platform.
>
> Signed-off-by: Jon Hunter
> Acked-by: Thierry Reding
OK, I used gdisk to remove the GPT and MBR from each disk.
mdadm --assemble still doesn't work... says it can't find the
superblock. The mdadm --examine commands also say that no
superblock is detected.
I guess I'll go ahead with --create...
On 3/23/2017 20:59, Lennart Sorensen wrote:
On Thu,
David Miller writes:
>> Dave: Since you queued the firmware patch, mind taking this fix through
>> your tree?
>
> Ok, applied to net-next, thanks.
Great, thanks!
--
Martin K. Petersen Oracle Linux Engineering
Am Donnerstag, 23. März 2017, 13:29:10 CET schrieb Julia Cartwright:
> On Thu, Mar 23, 2017 at 06:55:50PM +0100, Heiko St?bner wrote:
> > Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping:
> > > On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote:
> [..]
>
> > > > [..]
> > > >
On Thu, Mar 23, 2017 at 08:38:08PM +0100, Stephen Mueller wrote:
> Apologies, I should have started this on linux-raid...
>
>
> stephen@fred> sudo gdisk -l /dev/sdc
> GPT fdisk (gdisk) version 1.0.1
>
> Partition table scan:
> MBR: protective
> BSD: not present
> APM: not present
> GPT:
On Thu, Mar 23, 2017 at 08:10:20PM +0100, Uwe Kleine-König wrote:
> On Thu, Mar 23, 2017 at 08:44:41AM -0700, Dmitry Torokhov wrote:
> > On Thu, Mar 23, 2017 at 07:43:25AM -0700, Dmitry Torokhov wrote:
> > > On Thu, Mar 23, 2017 at 02:41:53PM +0100, Linus Walleij wrote:
> > > > On Thu, Mar 23, 2017
From: Luca Abeni
Signed-off-by: Luca Abeni
Tested-by: Daniel Bristot de Oliveira
---
include/uapi/linux/sched.h | 1 +
kernel/sched/core.c| 3 ++-
kernel/sched/deadline.c| 3 ++-
3 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/sched.h b/include/uap
From: Luca Abeni
According to the GRUB (Greedy Reclaimation of Unused Bandwidth)
reclaiming algorithm, the runtime is not decreased as "dq = -dt",
but as "dq = -Uact dt" (where Uact is the per-runqueue active
utilization).
Hence, this commit modifies the runtime accounting rule in
update_curr_dl(
From: Luca Abeni
Active utilization is defined as the total utilization of active
(TASK_RUNNING) tasks queued on a runqueue. Hence, it is increased
when a task wakes up and is decreased when a task blocks.
When a task is migrated from CPUi to CPUj, immediately subtract the
task's utilization fro
From: Luca Abeni
The total rq utilization is defined as the sum of the utilisations of
tasks that are "assigned" to a runqueue, independently from their state
(TASK_RUNNING or blocked)
Signed-off-by: Luca Abeni
Signed-off-by: Claudio Scordino
Tested-by: Daniel Bristot de Oliveira
---
kernel/
From: Luca Abeni
Instead of decreasing the runtime as "dq = -Uact dt" (eventually
divided by the maximum utilization available for deadline tasks),
decrease it as "dq = -(1 - Uinact) dt", where Uinact is the "inactive
utilization".
In this way, the maximum fraction of CPU time that can be reclaim
From: Luca Abeni
Original GRUB tends to reclaim 100% of the CPU time... And this
allows a CPU hog to starve non-deadline tasks.
To address this issue, allow the scheduler to reclaim only a
specified fraction of CPU time.
Signed-off-by: Luca Abeni
Tested-by: Daniel Bristot de Oliveira
---
kern
From: Luca Abeni
Hi all,
here is yet another version of the patchset implementing CPU reclaiming
(using the GRUB algorithm[1]) for SCHED_DEADLINE.
Basically, this feature allows SCHED_DEADLINE tasks to consume more
than their reserved runtime, up to a maximum fraction of the CPU time
(so that ot
From: Luca Abeni
This patch implements a more theoretically sound algorithm for
tracking active utilization: instead of decreasing it when a
task blocks, use a timer (the "inactive timer", named after the
"Inactive" task state of the GRUB algorithm) to decrease the
active utilization at the so ca
From: Luca Abeni
Now that the inactive timer can be armed to fire at the 0-lag time,
it is possible to use inactive_task_timer() to update the total
-deadline utilization (dl_b->total_bw) at the correct time, fixing
dl_overflow() and __setparam_dl().
Signed-off-by: Luca Abeni
Tested-by: Daniel
From: Luca Abeni
This commit introduces a per-runqueue "extra utilization" that can be
reclaimed by deadline tasks. In this way, the maximum fraction of CPU
time that can reclaimed by deadline tasks is fixed (and configurable)
and does not depend on the total deadline utilization.
Signed-off-by:
On Thu, 23 Mar 2017, Thomas Gleixner wrote:
> On Thu, 23 Mar 2017, Nicolas Pitre wrote:
>
> > On Thu, 23 Mar 2017, Daniel Lezcano wrote:
> >
> > > +#define IRQ_TIMINGS_SHIFT5
> > > +#define IRQ_TIMINGS_SIZE (1 << IRQ_TIMINGS_SHIFT)
> > > +#define IRQ_TIMINGS_MASK (IRQ_TIMINGS_SIZE - 1)
>
The commit 10cf4899f8af ("gpiolib: tighten up ACPI legacy gpio lookups")
prevents to getting same resource twice if the driver asks twice using same
connection ID.
But the whole idea of fallback might bring some problems. Imagine the case when
we have two versions of BIOS/hardware where in one _DS
By some reason acpi_find_gpio() and acpi_gpio_count() have compared connection
ID to "gpios" when tries to check if suffix is needed or not.
Don't do any assumptions about what connection ID can be and, when defined, use
it only with suffix as it's done in the device tree version.
Signed-off-by:
Documentation lacks of explanation how we actually use device properties
for GPIO resources.
Add a section to the documentation about that.
Suggested-by: Mika Westerberg
Signed-off-by: Andy Shevchenko
---
Documentation/acpi/gpio-properties.txt | 60 ++
1 file ch
This is preparatory patch for enabling GPIO ACPI to configure a pin
accordingly.
Signed-off-by: Andy Shevchenko
---
drivers/gpio/gpiolib.c | 2 +-
drivers/gpio/gpiolib.h | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index 4a
The helper function acpi_gpio_to_gpiod_flags() will be used later to configure
pin properly whenever it's requested.
While here, introduce a checking error code returned by gpiod_configure_flags()
and bail out if it's not okay.
Signed-off-by: Andy Shevchenko
---
drivers/gpio/gpiolib-acpi.c | 61
If we pass connection ID to the both functions and at the same time
acpi_can_fallback_to_crs() returns false we will get different results, i.e.
the number of GPIO resourses returned by acpi_gpio_count() might be not
correct.
Fix this by calling acpi_can_fallback_to_crs() in acpi_gpio_count() befo
Check that we don't ask for output direction on GpioInt resource in cases with
or without _DSD defined.
Signed-off-by: Andy Shevchenko
---
drivers/gpio/gpiolib-acpi.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib
This allows ACPI GPIO code to modify flags based on
ACPI GpioIo() / GpioInt() resources.
Signed-off-by: Andy Shevchenko
---
drivers/gpio/gpiolib-acpi.c | 50 +++--
drivers/gpio/gpiolib.c | 8 ++--
drivers/gpio/gpiolib.h | 15 --
Currently GPIO ACPI library provides an API to get a GPIO resources
(IO or interrupt) from ACPI tables for the individual drivers.
This library has few flaws which makes some devices not working:
- the library allows to abuse ACPI by using a _CRS fallback mechanism
- the library neglects flags o
On Thu, Mar 16, 2017 at 03:18:57PM +0100, Jason A. Donenfeld wrote:
> The md5_transform function is no longer used any where in the tree,
> except for the crypto api's actual implementation of md5, so we can drop
> the function from lib and put it as a static function of the crypto
> file, where it
On Thu, 23 Mar 2017, Daniel Lezcano wrote:
> + /*
> + * Online variance divided by the number of elements if there
> + * is more than one sample.
> + */
> + if (likely(irqs->count > 1))
> + variance = div_u64(irqs->variance, irqs->count - 1);
Isn't it mostly lik
On Thu, Mar 2, 2017 at 1:02 AM, David Engraf wrote:
> The scheduler clock framework may not use the correct timeout for the clock
> wrap. This happens when a new clock driver calls sched_clock_register()
> after the kernel called sched_clock_postinit(). In this case the clock wrap
> timeout is too
Weisbecker ,Stanislav Kinsburskiy
,Ingo Molnar ,Paolo Bonzini
,Dmitry Safonov ,Borislav Petkov
,Josh Poimboeuf ,Brian Gerst
,Jan Beulich ,Christian Borntraeger
,Fenghua Yu ,He Chen
,Russell King ,Vladimir Murzin
,Will Deacon ,Catalin Marinas
,Mark Rutland ,James Morse
,"David A . Long" ,Pr
From: Eric Dumazet
Dmitry posted a nice reproducer of a bug triggering in neigh_probe()
when dereferencing a NULL neigh->ops->solicit method.
This can happen for arp_direct_ops/ndisc_direct_ops and similar,
which can be used for NUD_NOARP neighbours (created when dev->header_ops
is NULL). Admin
On Thu, 23 Mar 2017, Nicolas Pitre wrote:
> On Thu, 23 Mar 2017, Daniel Lezcano wrote:
>
> > +#define IRQ_TIMINGS_SHIFT 5
> > +#define IRQ_TIMINGS_SIZE (1 << IRQ_TIMINGS_SHIFT)
> > +#define IRQ_TIMINGS_MASK (IRQ_TIMINGS_SIZE - 1)
> > +
> > +struct irq_timing {
> > + u32 irq;
> > + u64 ts
On 03/23/2017 12:41 PM, Dan Carpenter wrote:
> We don't call the remove() function unless probe() succeeds so "oud"
> can't be NULL here. Plus, if it were NULL, we dereference it on the
> next line so it would crash anyway.
>
> Signed-off-by: Dan Carpenter
>
Thanks sure!
ACK-by Boaz Harrosh
Apologies, I should have started this on linux-raid...
stephen@fred> sudo gdisk -l /dev/sdc
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 7814037168 sec
On Thu, 2017-03-23 at 12:00 -0700, David Miller wrote:
> From: Eric Dumazet
> Date: Thu, 23 Mar 2017 09:00:58 -0700
>
> > On Thu, 2017-03-23 at 07:53 -0700, Eric Dumazet wrote:
> >
> >> Nice !
> >>
> >> Looks like neigh->ops->solicit is NULL
> >
> > Apparently we allow admins to do really stup
Neil Armstrong writes:
> Since we know the GXBB and GXL/GXM share more hardware, we can safely move
> the remaining peripheral nodes present in the GXBB dtsi to the common GX dtsi.
> The following patches are small cleanups and helps to uniform the GX common
> dtsi compatible scheme.
>
> Changes
Hi Rafael,
On 03/21/2017 04:08 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> That has been attributed to CPU utilization metric updates on task
> migration that cause the total utilization value for the CPU to be
> reduced by the utilization of the migrated task. If that happens
On Thu, Mar 23, 2017 at 07:09:41PM +0100, r...@mueller.org wrote:
> Thank you very much or your reply.
>
> I naively thought that starting without partitions would be the best
> starting point, given 3 of the disks had been in a RAID5 array
> previously (possibly with partitions, not sure), but th
On Thu, Mar 23, 2017 at 6:15 AM, Geliang Tang wrote:
> Since the vmalloc code has been removed from write_pmsg() in the commit
> "5bf6d1b pstore/pmsg: drop bounce buffer", remove the unused header
> vmalloc.h.
>
> Signed-off-by: Geliang Tang
Thanks! Applied for v4.12.
-Kees
> ---
> fs/pstore/
On Fri, Mar 24, 2017 at 12:05:20AM +0530, simran singhal wrote:
> The IIO subsystem is redefining iio_dev->mlock to be used by
> the IIO core only for protecting device operating mode changes.
> ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes.
>
> In this driver, mlock was being used t
Hi Mark,
On Thu, Mar 23, 2017 at 06:54:52PM +, Mark Rutland wrote:
> Hi Daniel,
>
> On Thu, Mar 23, 2017 at 06:42:01PM +0100, Daniel Lezcano wrote:
> > In the next changes, we track the interrupts but we discard the timers as
> > that does not make sense. The next interrupt on a timer is pred
On Thu, 23 Mar 2017, Daniel Lezcano wrote:
> +#define IRQ_TIMINGS_SHIFT5
> +#define IRQ_TIMINGS_SIZE (1 << IRQ_TIMINGS_SHIFT)
> +#define IRQ_TIMINGS_MASK (IRQ_TIMINGS_SIZE - 1)
> +
> +struct irq_timing {
> + u32 irq;
> + u64 ts;
> +};
> +
> +struct irq_timings {
> + struct
Hello Dmitry,
On 02/22/2017 11:40 AM, Javier Martinez Canillas wrote:
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees. This is working on the assumption that a
> I2C device registered via OF will always match a legacy I2C device ID and
On Thu, Mar 23, 2017 at 09:03:23AM +0100, Marek Szyprowski wrote:
> This patch adds support for retention control for Exynos5433 SoCs. Three
> groups of pins has been defined for retention control: common shared group
> for ALIVE, CPIF, eSE, FINGER, IMEM, NFC, PERIC, TOUCH pin banks and
> separate
On Thu, Mar 23, 2017 at 09:03:22AM +0100, Marek Szyprowski wrote:
> When pin controller device is a part of power domain, there is no guarantee
> that the power domain was not turned off and then on during boot process
> before probing of the pin control driver. If it happened, then pin control
> d
On Thu, Mar 23, 2017 at 12:06 PM, Dmitry Vyukov wrote:
>
> On Thu, Mar 23, 2017 at 8:00 PM, Cong Wang wrote:
> > On Thu, Mar 23, 2017 at 9:06 AM, Dmitry Vyukov wrote:
> >> kasan: CONFIG_KASAN_INLINE enabled
> >> kasan: GPF could be caused by NULL-ptr deref or user memory access
> >> general prot
On Thu, Mar 23, 2017 at 08:44:41AM -0700, Dmitry Torokhov wrote:
> On Thu, Mar 23, 2017 at 07:43:25AM -0700, Dmitry Torokhov wrote:
> > On Thu, Mar 23, 2017 at 02:41:53PM +0100, Linus Walleij wrote:
> > > On Thu, Mar 23, 2017 at 1:34 PM, Uwe Kleine-König
> > > wrote:
> > >
> > > > Maybe we can ma
On Thu, Mar 23, 2017 at 07:55:58PM +0100, Peter Huewe wrote:
>
>
>
>
>
> Am 23. März 2017 19:43:39 MEZ schrieb Guenter Roeck :
> >On Thu, Mar 23, 2017 at 02:03:04PM +0100, Peter Huewe wrote:
> >> This patch replaces the old, deprecated call to hwmon_device_register
> >> with the new hwmon_devi
On Thu, 23 Mar 2017, Daniel Lezcano wrote:
> On Thu, Mar 23, 2017 at 07:35:42PM +0100, Peter Zijlstra wrote:
> > On Thu, Mar 23, 2017 at 06:42:02PM +0100, Daniel Lezcano wrote:
> > > +void irq_timings_enable(void)
> > > +{
> > > + static_branch_inc(&irq_timing_enabled);
> >
> > Do you really need
On Thu, Mar 23, 2017 at 8:00 PM, Cong Wang wrote:
> On Thu, Mar 23, 2017 at 9:06 AM, Dmitry Vyukov wrote:
>> kasan: CONFIG_KASAN_INLINE enabled
>> kasan: GPF could be caused by NULL-ptr deref or user memory access
>> general protection fault: [#1] SMP KASAN
>> Dumping ftrace buffer:
>>(f
On Thu, Mar 23, 2017 at 07:49:53PM +0100, Geert Uytterhoeven wrote:
> I take it you're using v1 of the patchset?
>
> v2 had this change:
>
> - Move backlight mutex initialization before call to
> charlcd_init_display(), to prevent locking an uninitialized mutex
> (reported by 0day).
>
On Thu, 23 Mar 2017 19:19:36 +0100 (CET)
Thomas Gleixner wrote:
> On Thu, 23 Mar 2017, Steven Rostedt wrote:
> > --- a/arch/x86/kernel/ftrace_64.S
> > +++ b/arch/x86/kernel/ftrace_64.S
> > @@ -1,5 +1,5 @@
> > /*
> > - * linux/arch/x86_64/mcount_64.S
> > + * linux/arch/x86_64/ftrace_64.S
>
>
On Thu, Mar 23, 2017 at 07:35:42PM +0100, Peter Zijlstra wrote:
> On Thu, Mar 23, 2017 at 06:42:02PM +0100, Daniel Lezcano wrote:
> > +/*
> > + * The function record_irq_time is only called in one place in the
> > + * interrupts handler. We want this function always inline so the code
> > + * insid
(Adding Pantelis and dgibson to cc.)
On 03/23/17 11:32, Rob Herring wrote:
> On Thu, Mar 23, 2017 at 8:22 AM, Nava kishore Manne
> wrote:
>> Hi,
>>
>>
>>
>> This mail is regarding the DT overlay support in the Linux
>> kernel
>>
>> I am able to make the device-tree
From: Eric Dumazet
Date: Thu, 23 Mar 2017 09:00:58 -0700
> On Thu, 2017-03-23 at 07:53 -0700, Eric Dumazet wrote:
>
>> Nice !
>>
>> Looks like neigh->ops->solicit is NULL
>
> Apparently we allow admins to do really stupid things with neighbours
> on tunnels.
>
> Following patch should avoid t
On Thu, Mar 23, 2017 at 9:06 AM, Dmitry Vyukov wrote:
> kasan: CONFIG_KASAN_INLINE enabled
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: [#1] SMP KASAN
> Dumping ftrace buffer:
>(ftrace buffer empty)
> Modules linked in:
> CPU: 2 PID: 127
On Fri, 24 Mar 2017 00:54:06 +0900
Satoru Takeuchi wrote:
> elkdat is a tool to ease linux kernel development/test. It
> automatically setups linux kernel
> source repository and a VM for linux kernel development and test. In
> addition, It runs
> the following kinds of tests automatically just b
On Thu, Mar 23, 2017 at 8:18 AM, Arnd Bergmann wrote:
> sys_arch_prctl is only provided on x86, and there is no reason
> to add it elsewhere. However, including it on the 32-bit syscall
> table caused a warning for most configurations on non-x86:
>
> :1328:2: warning: #warning syscall arch_prctl n
Am 23. März 2017 19:43:39 MEZ schrieb Guenter Roeck :
>On Thu, Mar 23, 2017 at 02:03:04PM +0100, Peter Huewe wrote:
>> This patch replaces the old, deprecated call to hwmon_device_register
>> with the new hwmon_device_register_with_info and converts the whole
>> driver to the new hwmon interfa
From: "Martin K. Petersen"
Date: Thu, 23 Mar 2017 10:19:03 -0400
> Arnd Bergmann writes:
>
>> gcc points out that we are converting a 16-bit integer into a 32-bit
>> little-endian type and assigning that to 16-bit little-endian
>> will end up with a zero:
>>
>> drivers/scsi/qedf/drv_fcoe_fw_fun
Hi Daniel,
On Thu, Mar 23, 2017 at 06:42:01PM +0100, Daniel Lezcano wrote:
> In the next changes, we track the interrupts but we discard the timers as
> that does not make sense. The next interrupt on a timer is predictable.
Sorry, but I could not parse this.
[...]
> diff --git a/drivers/perf/
Arnd, I only see 2 patches out of 3 and no series header posting.
On Wed, Mar 22, 2017 at 05:15:35PM +, Charles Keepax wrote:
> Use devm_gpiochip_add_data to simplify the error path in
> samsung_gpiolib_register.
>
> Signed-off-by: Charles Keepax
> Reviewed-by: Krzysztof Kozlowski
> ---
>
> No changes since v2.
>
> drivers/pinctrl/samsung/pinctrl-samsun
On Wed, Mar 22, 2017 at 05:15:34PM +, Charles Keepax wrote:
> If we request a GPIO hog, then gpiochip_add_data will attempt
> to request some of its own GPIOs. The driver also uses
> gpiochip_generic_request which means that for any GPIO request to
> succeed the pinctrl needs to be registered.
Hi Willy,
On Thu, Mar 23, 2017 at 6:37 PM, Willy TARREAU wrote:
> On Thu, Mar 23, 2017 at 06:15:01PM +0100, Willy TARREAU wrote:
>> So I finally had the time to give it a try by applying your patchset
>> on top of our 4.9 prod kernel. For now I'm getting a panic at boot :
>>
>> BUG: unable to han
m...@linux-mips.org, "Steven J. Hill" , Ralf
> Baechle
> Subject: Re: next build: 208 builds: 9 failed, 199 passed, 857 errors, 444
> warnings (next-20170323)
> Content-Type: text/plain; charset=UTF-8
>
> On Thu, Mar 23, 2017 at 6:46 AM, kernelci.org bot wrote:
>
On Thu, Mar 23, 2017 at 02:03:04PM +0100, Peter Huewe wrote:
> This patch replaces the old, deprecated call to hwmon_device_register
> with the new hwmon_device_register_with_info and converts the whole
> driver to the new hwmon interface using the hwmon_chip_info methods
> and the attribute_group
9pfs maintainers,
The patch series is fully acked, except for the header import from Xen
(http://marc.info/?l=linux-kernel&m=149020945130417&w=2) which needs to
be acked in Xen first (this is corresponding Xen series:
http://marc.info/?l=xen-devel&m=149013482308654).
Once that happens, the series
Aspeed BMC SoCs include a 16 channel, 10-bit ADC. Low and high threshold
interrupts are supported by the hardware but are not currently implemented.
Signed-off-by: Rick Altherr
---
Changes in v4:
- Avoid copying per-model data to per-instance data
Changes in v3:
- Drop model numbers from descri
Signed-off-by: Rick Altherr
---
Changes in v4: None
Changes in v3:
- Consistently write hex contstants with lowercase letters
- Drop model numbers from description as same IP is used in every generation
Changes in v2:
- Rewritten as an IIO ADC device
.../devicetree/bindings/iio/adc/aspeed_adc.
On Thu, 23 Mar 2017, Pasha Tatashin wrote:
> I will add a condition to tsc_early_init() to check for TSC_ADJUST if it is
> not 0, disable early TSC feature. Does this sound OK?
Not really.
I have strong objections against how this is crammed into the early boot
process along with the code duplica
On 2017-03-23 11:33, Mark Rutland wrote:
Hi Agustin,
Structurally, this looks good to me.
I have a few minor comments below; with those fixed up I think this is
ready to merge.
Thanks Mark, I'll spin V5 ASAP.
Agustin
--
Qualcomm Datacenter Technologies, Inc. on behalf of the Qualcomm
Tech
Hello, Patrick.
On Thu, Mar 23, 2017 at 06:15:33PM +, Patrick Bellasi wrote:
> What is important to notice is that there is a middleware, in between
> the kernel and the applications. This is a special kind of user-space
> where it is still safe for the kernel to delegate some "decisions".
>
From: Kan Liang
When setting FREEZE_WHILE_SMM bit in IA32_DEBUGCTL, all performance
counters will be effected. There is no way to do per-counter freeze
on smi. So it should not use the per-event interface (e.g. ioctl or
event attribute) to set FREEZE_WHILE_SMM bit.
Adds sysfs entry /sys/device/c
From: Kan Liang
Implementing a new --smi-cost mode in perf stat to measure SMI cost.
During the measurement, the /sys/device/cpu/freeze_on_smi will be set.
The measurement can be done with one counter and two free running MSR
counters (IA32_APERF and SMI_COUNT).
The formula to caculate SMI cost
From: Kan Liang
Adding sysfs__write_int function to ease up writing int to sysfs.
New interface is:
int sysfs__write_int(const char *entry, int value);
Also, introducing filename__write_int which is useful for new helpers to
write sysctl values.
Signed-off-by: Kan Liang
---
tools/lib/api/f
From: Kan Liang
Currently, there is no way to measure the time cost in System management
mode (SMM) by perf.
Intel perfmon supports FREEZE_WHILE_SMM bit in IA32_DEBUGCTL. Once it sets,
the PMU core counters will freeze on SMI handler. But it will not have an
effect on free running counters. E.g.
On Thu, Mar 23, 2017 at 06:42:02PM +0100, Daniel Lezcano wrote:
> +/*
> + * The function record_irq_time is only called in one place in the
> + * interrupts handler. We want this function always inline so the code
> + * inside is embedded in the function and the static key branching
> + * code can
The IIO subsystem is redefining iio_dev->mlock to be used by
the IIO core only for protecting device operating mode changes.
ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes.
In this driver, mlock was being used to protect hardware state
changes. Replace it with a lock in the devices g
On 03/23/2017 10:42 AM, Daniel Lezcano wrote:
> In the next changes, we track the interrupts but we discard the timers as
> that does not make sense. The next interrupt on a timer is predictable.
>
> But, the API request_percpu_irq does not allow to pass a flag, hence
> specifying
> if the interru
On Thu, Mar 23, 2017 at 8:22 AM, Nava kishore Manne
wrote:
> Hi,
>
>
>
> This mail is regarding the DT overlay support in the Linux
> kernel
>
> I am able to make the device-tree overlay work out of box by
> using my own dtc complier (I mean I used the dtc compiler
On Mar 23 2017 or thereabouts, Dmitry Torokhov wrote:
> Let's stop using !!x to reduce value of trackstick button expression to 0/1
> and use shift instead. This removes the following sparse warning:
>
> CHECK drivers/input/mouse/synaptics.c
> drivers/input/mouse/synaptics.c:943:79: warning: d
On Fri, Mar 17, 2017 at 3:15 PM, Moritz Fischer wrote:
> The ops are not changing, make them const.
>
> Signed-off-by: Moritz Fischer
Acked-by: Alan Tull
> Cc: Alan Tull
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-f...@vger.kernel.org
> ---
> drivers/fpga/altera-freeze-bridge.c | 2 +-
>
On Thu, Mar 23, 2017 at 06:55:50PM +0100, Heiko St?bner wrote:
> Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping:
> > On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote:
[..]
> > > [..]
> > >
> > > > @@ -1185,17 +1177,14 @@ static int rockchip_set_drive_perpin(struct
> > >
Commit-ID: 56222b212e8edb1cf51f5dd73ff645809b082b40
Gitweb: http://git.kernel.org/tip/56222b212e8edb1cf51f5dd73ff645809b082b40
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:36:00 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:14:59 +0100
futex: Drop hb->lock
Commit-ID: bebe5b514345f09be2c15e414d076b02ecb9cce8
Gitweb: http://git.kernel.org/tip/bebe5b514345f09be2c15e414d076b02ecb9cce8
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:59 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:10 +0100
futex: Futex_unlock_p
Commit-ID: cfafcd117da0216520568c195cb2f6cd1980c4bb
Gitweb: http://git.kernel.org/tip/cfafcd117da0216520568c195cb2f6cd1980c4bb
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:58 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:09 +0100
futex: Rework futex_l
Commit-ID: 38d589f2fd08f1296aea3ce62bebd185125c6d81
Gitweb: http://git.kernel.org/tip/38d589f2fd08f1296aea3ce62bebd185125c6d81
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:57 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:09 +0100
futex,rt_mutex: Restr
On Thu 23-03-17 16:06:13, Arnd Bergmann wrote:
> The latest gcc-7.0.1 snapshot warns about an unintialized variable use:
>
> In file included from fs/reiserfs/lbalance.c:8:0:
> fs/reiserfs/lbalance.c: In function 'leaf_item_bottle.isra.3':
> fs/reiserfs/reiserfs.h:1279:13: error: '*((void *)&n_ih+
Commit-ID: 50809358dd7199aa7ce232f6877dd09ec30ef374
Gitweb: http://git.kernel.org/tip/50809358dd7199aa7ce232f6877dd09ec30ef374
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:56 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:09 +0100
futex,rt_mutex: Intro
Commit-ID: 16ffa12d742534d4ff73e8b3a4e81c1de39196f0
Gitweb: http://git.kernel.org/tip/16ffa12d742534d4ff73e8b3a4e81c1de39196f0
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:55 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:08 +0100
futex: Pull rt_mutex_
Commit-ID: bf92cf3a5100f5a0d5f9834787b130159397cb22
Gitweb: http://git.kernel.org/tip/bf92cf3a5100f5a0d5f9834787b130159397cb22
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:53 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:08 +0100
futex: Cleanup refcou
Commit-ID: 73d786bd043ebc855f349c81ea805f6b11cbf2aa
Gitweb: http://git.kernel.org/tip/73d786bd043ebc855f349c81ea805f6b11cbf2aa
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:54 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:08 +0100
futex: Rework inconsi
Commit-ID: 734009e96d1983ad739e5b656e03430b3660c913
Gitweb: http://git.kernel.org/tip/734009e96d1983ad739e5b656e03430b3660c913
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:52 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:07 +0100
futex: Change locking
Commit-ID: 5293c2efda37775346885c7e924d4ef7018ea60b
Gitweb: http://git.kernel.org/tip/5293c2efda37775346885c7e924d4ef7018ea60b
Author: Peter Zijlstra
AuthorDate: Wed, 22 Mar 2017 11:35:51 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 23 Mar 2017 19:10:07 +0100
futex,rt_mutex: Provi
301 - 400 of 1018 matches
Mail list logo
