> "Alexey" == Alexey Brodkin writes:
Alexey> Hi Aaron,
Alexey> On Sat, 2016-07-09 at 07:47 -0400, Aaron Z wrote:
>> On Sat, Jul 9, 2016 at 4:37 AM, Alexey Brodkin
>> wrote:
>> >
>> > Hello,
>> >
>> > I was playing with quite simple bridged setup on different boards
>> with > very recent ke
This driver is to add reset support for nuc900 series,
currently, it only supports nuc970 SoC reset.
Signed-off-by: Wan Zongshun
---
drivers/power/reset/Kconfig| 7 +++
drivers/power/reset/Makefile | 1 +
drivers/power/reset/nuc900-reset.c | 93 +++
This patch is to add nuc970 clock Macros header file
into include/dt-bindings/clock.
Signed-off-by: Wan Zongshun
---
include/dt-bindings/clock/nuc970-clock.h | 233 +++
1 file changed, 233 insertions(+)
create mode 100644 include/dt-bindings/clock/nuc970-clock.h
dif
This patch is to add SoC specific driver for nuc970 SoC,
it is for getting nuc970 version id and chip id.
Signed-off-by: Wan Zongshun
---
drivers/soc/Kconfig | 1 +
drivers/soc/Makefile | 1 +
drivers/soc/nuvoton/Kconfig | 10
drivers/soc/nuvoton/Makefile
This patch is to add nuc970 clocksource driver support.
NUC970 general timer controller includes five channels, TIMER0, TIMER1,
TIMER2, TIMER3, and TIMER4, which allow user to easily implement a
counting scheme or timing control for applications.The timer possesses
features such as adjustable reso
This patch is to add irqchip driver support for nuc900 plat,
current this driver only supports nuc970 SoC.
Signed-off-by: Wan Zongshun
---
arch/arm/mach-w90x900/include/mach/irqs.h | 5 +
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-nuc900.c | 150 +++
NUC970 is a new SoC of Nuvoton nuc900 series, this patch is
to add machine file support for it.
Signed-off-by: Wan Zongshun
---
arch/arm/mach-w90x900/Kconfig | 20
arch/arm/mach-w90x900/Makefile | 3 +++
arch/arm/mach-w90x900/nuc900.c | 41 +
Hi,
This patch series added Nuvoton new SoC NUC970 development board
support, this nuc970 belongs to nuc900 series, but many features are
not compatible with old nuc900 SoCs like nuc910, nuc920.
Those patches are basing on old w90x900 codes, and are using standard
linux subsystem interface, such
This patch is to add clock framework driver for nuc970.
The clock controller generates all clocks for Video, Audio,
CPU, system bus and all functionalities, nuc970 includes
two PLL modules.
Signed-off-by: Wan Zongshun
---
drivers/clk/Makefile| 1 +
drivers/clk/nuc900/Makefile |
This patch is to add dts description for nuc900 platform.
Signed-off-by: Wan Zongshun
---
.../devicetree/bindings/arm/nuvoton/nuc970.txt | 12
.../bindings/clock/nuvoton,nuc970-clk.txt | 13 +
.../interrupt-controller/nuvoton,nuc900-aic.txt| 15 +
This patch is to add dts support for nuc970 platform.
Signed-off-by: Wan Zongshun
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/nuc970-evb.dts | 34
arch/arm/boot/dts/nuc970.dtsi| 88
3 files changed, 123 insertions(+
Add nuc970_defconfig file support.
Signed-off-by: Wan Zongshun
---
arch/arm/configs/nuc970_defconfig | 76 +++
1 file changed, 76 insertions(+)
create mode 100644 arch/arm/configs/nuc970_defconfig
diff --git a/arch/arm/configs/nuc970_defconfig
b/arch/arm/co
On Sun, 2016-07-10 at 08:49 +0200, Borislav Petkov wrote:
> On Sat, Jul 09, 2016 at 10:56:55AM -0700, Joe Perches wrote:
> >
> > defconfigs both with and without CONFIG_PRINTK build
> > properly with the proposed change to this specific patch.
> Did you try latest tip/master?
Assuming tip is incl
Add support for using with both wl12xx and wl18xx.
- all wilink family needs special init command for entering wspi mode.
extra clock cycles should be sent after the spi init command while the
cs pin is high.
- Use inverted chip select for sending a dummy 4 bytes command that
completes the i
On Sat, Jul 9, 2016 at 10:53 PM, Tejun Heo wrote:
> Hello, Ming.
>
> On Fri, Jul 08, 2016 at 06:35:06PM +0800, Ming Lei wrote:
>> I am wondering why REQ_THROTTLED is cleared for the original bio
>> even it has been charged and will be issued to driver, and is it allowed
>> to throttle and charge t
On 07/08/16 09:13, Petr Mladek wrote:
> On Thu 2016-07-07 20:27:13, Topi Miettinen wrote:
>> On 07/07/16 09:16, Petr Mladek wrote:
>>> On Sun 2016-07-03 15:08:07, Topi Miettinen wrote:
The attached patch would make any uses of capabilities generate audit
messages. It works for simple test
On Sat, Jul 09, 2016 at 12:25:09AM +0200, Peter Zijlstra wrote:
> On Sat, Jul 09, 2016 at 12:00:47AM +0200, Peter Zijlstra wrote:
> > Yes, you're right. Let me try and see if I can make that better.
>
> Something like so?
yep, seems good ;-)
jirka
>
> ---
> --- a/arch/x86/events/intel/ds.c
> +
Hi Ingo,
I am sorry the previous post didn't contain formal patch log. I made a
new one as below. The boot crash could not only happen with certain
memory. Because of this code bug the regions which need be avoided like
the zipped kernel with its unzipping running code, initrd, kernel
command line
Add watchdog specific driver for Amlogic Meson GXBB SoC.
Signed-off-by: Neil Armstrong
---
drivers/watchdog/Kconfig | 10 ++
drivers/watchdog/Makefile | 1 +
drivers/watchdog/meson_gxbb_wdt.c | 270 ++
3 files changed, 281 insertions(+)
cr
Acked-by: Rob Herring
Signed-off-by: Neil Armstrong
---
.../devicetree/bindings/watchdog/meson-gxbb-wdt.txt | 16
1 file changed, 16 insertions(+)
create mode 100644
Documentation/devicetree/bindings/watchdog/meson-gxbb-wdt.txt
diff --git a/Documentation/devicetree/bindi
Adds support for the Amlogic Meson GXBB SoC Watchdog Timer.
It differs from the meson6/meson8b HW, so need for a separate driver.
The HW provides a divider capable of having a 1ms timebase thus simplifying
the counter update.
The restart call is not provided even if the HW is capable of triggering
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
index 832815d..bcca82f 100644
--- a/arch/arm64/boot/dts/amlogic/meson-
Op 08-07-16 om 17:44 schreef Gustavo Padovan:
> From: Gustavo Padovan
>
> Signalling doesn't need to be enabled at sync_file creation, it is only
> required if userspace waiting the fence to signal through poll().
>
> Thus we delay fence_add_callback() until poll is called. It only adds the
> call
Given a Kconfig.sample, implementing 2 empty and 2 non-empty menu
entries:
menu EMPTY_MENU
endmenu
menu NONEMPTY_MENU
config DUMMY_1
bool "desc-1"
endmenu
menuconfig EMPTY_MENUCONFIG
bool "desc-2"
menuconfig NONEMPTY_MENUCONFIG
bool "desc-3"
if NONEMPTY_MENUCONFIG
config DUMMY_2
* PaX Team wrote:
> On 9 Jul 2016 at 14:27, Andy Lutomirski wrote:
>
> > I like the series, but I have one minor nit to pick. The effect of this
> > series is to harden usercopy, but most of the code is really about
> > infrastructure to validate that a pointed-to object is valid.
>
> actua
Subject: [PATCH v2 0/4] pwm: Add Amlogic Meson SoC PWM Controller
Add support for the PWM controller found in Amlogic Meson SoCs.
This controller provides a dual PWM output with 4 selectable clock source
and a two level divider to achieve a better PWM range.
Currently Meson8b and GXBB SoCs are su
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 28
1 file changed, 28 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
index 806b903..2eacef0 100644
--- a/arch/arm64
Signed-off-by: Neil Armstrong
---
arch/arm/boot/dts/meson8b.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/meson8b.dtsi b/arch/arm/boot/dts/meson8b.dtsi
index fc4080d..41fd536 100644
--- a/arch/arm/boot/dts/meson8b.dtsi
+++ b/arch/arm/boot/dts/me
Add bindings for the Amlogic PWM Controller in Meson8b and GXBB SoCs.
Signed-off-by: Neil Armstrong
---
Documentation/devicetree/bindings/pwm/pwm-meson.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pwm/pwm-meson.txt
diff -
Add support for the PWM controller found in the Amlogic SoCs.
This driver supports the Meson8b and GXBB SoCs.
Signed-off-by: Neil Armstrong
---
drivers/pwm/Kconfig | 9 +
drivers/pwm/Makefile| 1 +
drivers/pwm/pwm-meson.c | 491
3 file
Meelis Roos writes:
> > > Just got this on bootup of my Sun T2000:
> > >...
> > > I have not seen it before, this includes 4.6.0 4.6.0-08907-g7639dad
> > > 4.7.0-rc1-00094-g6b15d66 4.7.0-rc4-00014-g67016f6.
> > >
> > > It is not reproducible, did not appear on next reboot of the same
> > > k
Em Sat, 9 Jul 2016 23:22:22 -0600
Jonathan Corbet escreveu:
> On Tue, 5 Jul 2016 14:55:09 -0300
> Mauro Carvalho Chehab wrote:
>
> > I hope you don't mind. I'm merging those three patches on my tree
> > (for now, they're on an experimental tree that I can easily rebase, if
> > needed). If OK fo
Hi Rafael!
On 08.07.2016 01:43, Rafael J. Wysocki wrote:
>
> Please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
> acpi-4.7-rc7
>
> to receive ACPI fixes for v4.7-rc7 with top-most commit
> […]
> All of these fix recent regressions in ACPICA, in the ACPI PC
It will be used outside of evlist.c object
in folowing patches.
Link: http://lkml.kernel.org/n/tip-m4jswtxn3ff3jn5qoo5h6...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/evlist.c | 4 ++--
tools/perf/util/evlist.h | 3 +++
2 files changed, 5 insertions(+), 2 deletions(-)
diff --gi
Currently 0 is passed as perf_event_attr::size,
which could block usage of new features.
Link: http://lkml.kernel.org/n/tip-kyzkn52sg75mcqrhsjbfe...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/python.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/util/python.c b
To be able to find out event configuration info
during sample parsing.
Link: http://lkml.kernel.org/n/tip-b63rh6l44ort2t76etobv...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/python.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/py
To show how to open tracepoint and access its fields.
Reported-and-tested-by: Jiri Pirko
Link: http://lkml.kernel.org/n/tip-7xt9nvyl45qwbg9237f46...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/python/tracepoint.py | 47 +
1 file changed, 47 ins
Adding tp_getattro callback for sample event. It resolves
tracepoint fields in runtime.
It's now possible to access tracepoint fields in normal
fashion like hardcoded ones (see the example in the next
patch).
Reported-and-tested-by: Jiri Pirko
Link: http://lkml.kernel.org/n/tip-0jmugogczg6xkgyie
To get id of the tracepoint from subsystem and
name strings. The interface is:
id = perf.tracepoint(sys, name)
In case of error -1 is returned.
It will be used to get python tracepoint event's
config value for tracepoint event.
Link: http://lkml.kernel.org/n/tip-ssizvbkk2lds6bti2z69t...@git.k
Jirka reported that python code returns all arrays as strings.
This makes impossible to get all items for byte array tracepoint
field containing 0x00 value item.
Fixing this by scanning full length of the array and returning
it as PyByteArray object in case non printable byte is found.
Cc: Steven
Make perf.event object parts of the perf module
dictionary so we can address them by name.
Following objects/names are added:
mmap_event
lost_event
comm_event
task_event
throttle_event
task_event
read_event
sample_event
switch_event
We can now use it in python script like:
...
To get struct event_format object from tracepoint ID.
It will be used in following patches.
Link: http://lkml.kernel.org/n/tip-0omstcxuxa8npi3otondl...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/trace-event.c | 9 +
tools/perf/util/trace-event.h | 2 ++
2 files changed,
hi,
adding support to access tracepoint fields in python scripts.
With this patchset it's possible to access tracepoint fields
in event python object like:
print "time %u prev_comm=%s prev_pid=%d prev_prio=%d prev_state=0x%x ==>
next_comm=%s next_pid=%d next_prio=%d" % (
event.sample_
We can't consume the event before parsing it. Under heavy
load we could get caught by kernel writer overwriting the
event we're trying to parse.
Link: http://lkml.kernel.org/n/tip-8dbalvrufeisa4cioyd9k...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/python.c | 6 --
1 file cha
* Baoquan He wrote:
> Hi Ingo,
>
> I am sorry the previous post didn't contain formal patch log. I made a new
> one
> as below. The boot crash could not only happen with certain memory. Because
> of
> this code bug the regions which need be avoided like the zipped kernel with
> its
> unzi
The global mutex of 'gdp_mutex' is used to serialize creating/querying
glue dir and its cleanup. Turns out it isn't a perfect way because
part(kobj_kset_leave()) of the actual cleanup action() is done inside
the release handler of the glue dir kobject. That means gdp_mutex has
to be held before rel
Commit-ID: a11836fa5a67ba56d8338138e37b42384af73e5e
Gitweb: http://git.kernel.org/tip/a11836fa5a67ba56d8338138e37b42384af73e5e
Author: Andy Shevchenko
AuthorDate: Sat, 9 Jul 2016 16:45:29 +0300
Committer: Ingo Molnar
CommitDate: Sun, 10 Jul 2016 10:33:41 +0200
x86/platform/intel-mid: M
* Borislav Petkov wrote:
> tip-bot for Paolo Bonzini wrote:
>
> >Commit-ID: eec4b1227db153ca16f8f5f285d01fefdce05438
> >Gitweb:
> >http://git.kernel.org/tip/eec4b1227db153ca16f8f5f285d01fefdce05438
> >Author: Paolo Bonzini
> >AuthorDate: Mon, 20 Jun 2016 16:58:30 +0200
> >Committer:
Commit-ID: 2e9d1e150abf88cb63e5d34ca286edbb95b4c53d
Gitweb: http://git.kernel.org/tip/2e9d1e150abf88cb63e5d34ca286edbb95b4c53d
Author: Paolo Bonzini
AuthorDate: Mon, 20 Jun 2016 16:58:29 +0200
Committer: Ingo Molnar
CommitDate: Sun, 10 Jul 2016 13:33:02 +0200
x86/entry: Avoid interrupt
Commit-ID: be8a18e2e98e04a5def5887d913b267865562448
Gitweb: http://git.kernel.org/tip/be8a18e2e98e04a5def5887d913b267865562448
Author: Paolo Bonzini
AuthorDate: Mon, 20 Jun 2016 16:58:30 +0200
Committer: Ingo Molnar
CommitDate: Sun, 10 Jul 2016 13:33:02 +0200
x86/entry: Inline enter_fr
On 2016年07月07日 00:00, Joerg Roedel wrote:
From: Joerg Roedel
There is a race condition in the AMD IOMMU init code that
causes requested unity mappings to be blocked by the IOMMU
for a short period of time. This results on boot failures
and IO_PAGE_FAULTs on some machines.
Fix this by making
On 10 Jul 2016 at 11:16, Ingo Molnar wrote:
> * PaX Team wrote:
>
> > On 9 Jul 2016 at 14:27, Andy Lutomirski wrote:
> >
> > > I like the series, but I have one minor nit to pick. The effect of this
> > > series is to harden usercopy, but most of the code is really about
> > > infrastructure
On Sun, Jul 10, 2016 at 01:23:51AM -0700, Joe Perches wrote:
> Assuming tip is included in linux-next as of july 8, yes.
Try one which has
http://git.kernel.org/tip/81c2949f7fdcf8ff681326669afde24962232670
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
On Thu, Jul 07, 2016 at 08:35:17AM -0600, Jens Axboe wrote:
> Thanks Arnd, applied.
Actually I think we should replace the select with the depends. In
fact I though I had done that a while ago, but I must have messed it up.
Btw - do you plan to grab patches directly from the list now or
do you w
The TSC deadline clockevent devices' configuration and registration
happens before the TSC frequency calibration is refined in
tsc_refine_calibration_work().
This results in the TSC clocksource and the TSC deadline clockevent
devices being configured with slightly different frequencies: the former
With NOHZ_FULL and one single well-isolated, CPU consumptive task, one
would expect approximately one clockevent interrupt per second. However, on
my Intel Haswell where the monotonic clock is the TSC monotonic clock and
the clockevent device is the TSC deadline device, it turns out that every
seco
In setup_APIC_timer(), the registered clockevent device's frequency
is calculated by first dividing tsc_khz by TSC_DIVISOR and multiplying
it with 1000 afterwards.
The multiplication with 1000 is done for converting from kHz to Hz and the
division by TSC_DIVISOR is carried out in order to make sur
With a single task running on a NOHZ CPU on an Intel Haswell, I recognized
that I did not only get the one expected local_timer APIC interrupt, but
two per second at minimum.
Further tracing showed that the first one preceedes the programmed deadline
by up to ~50us and hence, it did nothing except
In order to avoid overflowing an u32, the TSC deadline clockevent device's
frequency is divided by TSC_DIVISOR at registration.
The TSC_DIVISOR is currently defined as equaling 32 which allows for a
TSC frequency as high as 2^32 / 10^9ns * 32 = 137 GHz.
OTOH, larger values of TSC_DIVISOR introduc
Hi,
On 2016 M06 30, Thu 14:02:02 CEST Pranay Kr. Srivastava wrote:
> spinlocked ranges should be small and not contain calls into huge
> subfunctions. Fix my mistake and just get the pointer to the socket
> instead of doing everything with spinlock held.
>
> Reported-by: Mikulas Patocka
> Signed
On Sun, 2016-07-10 at 14:06 +0200, Borislav Petkov wrote:
> On Sun, Jul 10, 2016 at 01:23:51AM -0700, Joe Perches wrote:
> >
> > Assuming tip is included in linux-next as of july 8, yes.
> Try one which has http://git.kernel.org/tip/81c2949f7fdcf8ff681326669a
> fde24962232670
That commit isn't in
On Sun, Jul 10, 2016 at 5:03 AM, PaX Team wrote:
> On 10 Jul 2016 at 11:16, Ingo Molnar wrote:
>
>> * PaX Team wrote:
>>
>> > On 9 Jul 2016 at 14:27, Andy Lutomirski wrote:
>> >
>> > > I like the series, but I have one minor nit to pick. The effect of this
>> > > series is to harden usercopy, bu
On Thu, Jul 7, 2016 at 4:11 AM, Dmitry Safonov wrote:
> On 07/06/2016 05:30 PM, Andy Lutomirski wrote:
>>
>> On Wed, Jun 29, 2016 at 3:57 AM, Dmitry Safonov
>> wrote:
>>>
>>> Add API to change vdso blob type with arch_prctl.
>>> As this is usefull only by needs of CRIU, expose
>>> this interface
/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
Hi all-
I found two nasty issues with virtually mapped stacks if KASAN is
enabled. The first issue is a crash: the first non-init stack is
allocated and accessed before KASAN initializes its zero shadow
AFAICT, which means that we switch to that stack and then blow up when
we start recursively fa
On 2016 M06 30, Thu 14:02:03 CEST Pranay Kr. Srivastava wrote:
> When a timeout occurs or a recv fails, then
> instead of abruplty killing nbd block device
> wait for its users to finish.
>
> This is more required when filesystem(s) like
> ext2 or ext3 don't expect their buffer heads to
> disappea
Including more members.
On Sat, Jul 9, 2016 at 5:22 PM, Pratik Prajapati
wrote:
> Hi,
>
> I am trying to add support of adjusting IR led current in vcnl4000
> driver (has IR led current register for doing the same).
>
> Below is what I have done till now:
>
> 1) Added Current channel in the vcnl4
/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914
config: i386-randconfig-s1-201628 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by
On 03/07/16 22:04, Alison Schofield wrote:
> IIO driver, perhaps a reference driver, since this sensor is already
> supported in hwmon/jc42 driver.
>
> Driver supports continuous conversion, resolution changes and
> suspend/resume power ops.
>
> Signed-off-by: Alison Schofield
> Cc: Daniel Balut
On Sun, Jul 10, 2016 at 1:43 AM, Brooks Moses wrote:
> On Sat, Jul 9, 2016 at 10:36 AM, Brooks Moses wrote:
>> I've been attempting to qualify the Linux 4.5.2 user-space headers for
>> a toolchain release, and ran into what looks like a missing include
>> file in include/uapi/linux/errqueue.h. I
/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914
config: sh-sh7785lcr_32bit_defconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O
Add documentation for the cookie argument in try_to_wake_up_local()
This caused the following warning when building documentation:
kernel/sched/core.c:2088: warning: No description found for parameter 'cookie'
Fixes: e7904a28f533 ("ilocking/lockdep, sched/core: Implement a better lock
pinning sc
The workqueue "wk" serves as a queue for carrying out execution
of requests. It has a single work item(&drv_data->work) and hence doesn't
require ordering. Also, it is not being used on a memory reclaim path.
Hence, the singlethreaded workqueue has been replaced with the use of
system_wq.
System w
/avoid-double-timer-interrupt-with-nohz-and-Intel-TSC/20160710-202914
config: frv-defconfig (attached as .config)
compiler: frv-linux-gcc (GCC) 4.9.0
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin
The workqueue has a single workitem(&ss->ws) and hence doesn't require
ordering. Also, it is not being used on a memory reclaim path. Hence, the
singlethreaded workqueue has been replaced with the use of system_wq.
System workqueues have been able to handle high level of concurrency
for a long tim
On 10/07/16 14:11, Pratik Prajapati wrote:
> Including more members.
>
> On Sat, Jul 9, 2016 at 5:22 PM, Pratik Prajapati
> wrote:
>> Hi,
hi Pratik,
>>
>> I am trying to add support of adjusting IR led current in vcnl4000
>> driver (has IR led current register for doing the same).
This is always
On Sun, Jul 10, 2016 at 07:17:19AM +0200, Peter Zijlstra wrote:
>
>
> On 10 July 2016 06:26:39 CEST, "Paul E. McKenney"
> wrote:
> >Hello!
> >
> >So I ran a quick benchmark which showed stair-step results. I
> >immediately
> >thought "Ah, this is due to CPU 0 and 1, 2 and 3, 4 and 5, and 6 and
On 09/07/16 02:24, Alexandre Belloni wrote:
> A common way of multiplexing buttons on a single input in cheap devices is
> to use a resistor ladder on an ADC. This driver supports that configuration
> by polling an ADC channel provided by IIO.
>
> Signed-off-by: Alexandre Belloni
Acked-by: Jonath
On 09/07/16 02:24, Alexandre Belloni wrote:
> Add documentation for ADC keys
>
> Signed-off-by: Alexandre Belloni
I'm seeing a few more properties in the driver. They may be generic
input ones, but should still be listed here...
autorepeat for example.
> ---
> Changes in v2:
> - fix title
>
Commit-ID: 99e9d958726c04cec3e36902d8583fdd8cb5b1bb
Gitweb: http://git.kernel.org/tip/99e9d958726c04cec3e36902d8583fdd8cb5b1bb
Author: John Kacur
AuthorDate: Fri, 17 Jun 2016 15:05:15 +0200
Committer: Ingo Molnar
CommitDate: Sun, 10 Jul 2016 16:55:04 +0200
irq/Documentation: Correct re
On 07/10/16 at 01:24pm, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > Hi Ingo,
> >
> > I am sorry the previous post didn't contain formal patch log. I made a new
> > one
> > as below. The boot crash could not only happen with certain memory. Because
> > of
> > this code bug the regions w
Hi! Here is my fifth regression report for Linux 4.7. It lists 10
regressions I'm currently aware of; 2 of them are new; 1 of those
seems to be a a side effect of a fix for another regression.
The report also mentions 3 regression that I removed from the list, as
it looks like those issues are no
On Sun, Jul 10, 2016 at 9:56 AM, Willem de Bruijn wrote:
> On Sun, Jul 10, 2016 at 1:43 AM, Brooks Moses wrote:
>> On Sat, Jul 9, 2016 at 10:36 AM, Brooks Moses wrote:
>>> I've been attempting to qualify the Linux 4.5.2 user-space headers for
>>> a toolchain release, and ran into what looks like
Em Sun, 22 May 2016 11:06:05 +0200
Geert Uytterhoeven escreveu:
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.
I'm assuming that this patch will go via DT git tree, so:
>
> Signed-off-by: Geert Uytterhoeven
> Cc: Mauro Carvalho
On Sun, Jul 10, 2016 at 4:00 AM, Thorsten Leemhuis
wrote:
>
> FYI, it seems these changes lead to a new regression. Quoting
> https://bugzilla.kernel.org/show_bug.cgi?id=121701
I wrote a comment on that, to see if the git issue that kept things
from bisecting into the merge can be worked around.
On 26/06/16 04:26, Guenter Roeck wrote:
> Up to now, each hwmon driver has to implement its own sysfs attributes.
> This requires a lot of template code, and distracts from the driver's core
> function to read and write chip registers.
>
> To be able to reduce driver complexity, move sensor attrib
On 26/06/16 04:26, Guenter Roeck wrote:
> Describe the new registration API function as well as the data
> structures it requires.
>
> Signed-off-by: Guenter Roeck
Nice docs. Couple of typos inline.
Jonathan
> ---
> Documentation/hwmon/hwmon-kernel-api.txt | 229
> +
On 26/06/16 04:26, Guenter Roeck wrote:
> Up to now, each hwmon driver has to implement its own sysfs attributes.
> This requires a lot of template code, and distracts from the driver's
> core function to read and write chip registers.
>
> To be able to reduce driver complexity, move sensor attrib
On Sun, Jul 10, 2016 at 6:32 PM, Markus Pargmann wrote:
> On 2016 M06 30, Thu 14:02:03 CEST Pranay Kr. Srivastava wrote:
>> When a timeout occurs or a recv fails, then
>> instead of abruplty killing nbd block device
>> wait for its users to finish.
>>
>> This is more required when filesystem(s) li
On 07/10/2016 02:11 AM, Neil Armstrong wrote:
Acked-by: Rob Herring
Signed-off-by: Neil Armstrong
Reviewed-by: Guenter Roeck
---
.../devicetree/bindings/watchdog/meson-gxbb-wdt.txt | 16
1 file changed, 16 insertions(+)
create mode 100644
Documentation/devicetre
On 07/10/2016 02:11 AM, Neil Armstrong wrote:
Add watchdog specific driver for Amlogic Meson GXBB SoC.
Signed-off-by: Neil Armstrong
Reviewed-by: Guenter Roeck
---
drivers/watchdog/Kconfig | 10 ++
drivers/watchdog/Makefile | 1 +
drivers/watchdog/meson_gxbb_wdt.c |
On 07/10/2016 02:11 AM, Neil Armstrong wrote:
Signed-off-by: Neil Armstrong
Reviewed-by: Guenter Roeck
Would this go in through one of the arm trees ?
Guenter
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/a
Mario Kleiner writes:
> Hi Eric,
>
> thanks for all the infos and help! Both your patches look good and i
> have successfully tested them on top of with my vblank timestamping patch.
>
> So for both:
>
> Reviewed-and-tested-by: Mario Kleiner
>
> Will you squash 2/2 into my patch or should i res
On 07/08/2016 10:34 AM, Philipp Zabel wrote:
Am Donnerstag, den 07.07.2016, 16:03 -0700 schrieb Steve Longerbeam:
From: Suresh Dhandapani
This patch will change the register IPU_CSI0_CCIR_CODE_2 value from
0x40596 to 0x405A6. The change is related to the Start of field 1
first blanking line
Signed-off-by: Alec Missine
---
drivers/staging/dgnc/dgnc_driver.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/dgnc/dgnc_driver.h
b/drivers/staging/dgnc/dgnc_driver.h
index 95ec729..8c0432a 100644
--- a/drivers/staging/dgnc/dgnc_driver.h
+++ b/drivers/stag
Can we discuss business here? its important.
On Jul 4, 2016, at 10:25 PM, Al Viro wrote:
> BTW, could you take a look at
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git#sendmsg.lustre?
> It's a bunch of simplifications that became possible once sendmsg()/recvmsg()
> switched to iov_iter, stopped mangling the iovecs and went for
This showed up as "6Failed to access..." here.
Fixes: 1b74dde7c47c ("x86/cpu: Convert printk(KERN_ ...) to
pr_(...)")
Cc: Chen Yucong
Signed-off-by: Vegard Nossum
---
arch/x86/events/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/events/core.c b/arch/x86/ev
Commit-ID: ba8268330dc18d309a39175ea4d2c5d86c2cef09
Gitweb: http://git.kernel.org/tip/ba8268330dc18d309a39175ea4d2c5d86c2cef09
Author: Len Brown
AuthorDate: Fri, 17 Jun 2016 01:22:44 -0400
Committer: Ingo Molnar
CommitDate: Sun, 10 Jul 2016 17:00:12 +0200
x86/tsc_msr: Identify Intel-sp
Commit-ID: fc5f3ac24720012909c224a63ca3217f4759967d
Gitweb: http://git.kernel.org/tip/fc5f3ac24720012909c224a63ca3217f4759967d
Author: Len Brown
AuthorDate: Fri, 17 Jun 2016 01:22:43 -0400
Committer: Ingo Molnar
CommitDate: Sun, 10 Jul 2016 17:00:12 +0200
Revert "x86/tsc: Add missing C
1 - 100 of 268 matches
Mail list logo