The upcoming fine grained per task STIBP control needs to be updated on CPU
hotplug as well.
Split out the code which controls the strict mode so the prctl control code
can be added later. Mark the SMP function call argument __unused while at it.
Signed-off-by: Thomas Gleixner
---
v1 -> v2:
If 'prctl' mode of user space protection from spectre v2 is selected
on the kernel command-line, STIBP and IBPB are applied on tasks which
restrict their indirect branch speculation via prctl.
SECCOMP enables the SSBD mitigation for sandboxed tasks already, so it
makes sense to prevent spectre v2
Add command line control for user space indirect branch speculation
mitigations. The new option is: spectre_v2_user=
The initial options are:
- on: Unconditionally enabled
- off: Unconditionally disabled
-auto: Kernel selects mitigation (default off for now)
When the
To avoid the overhead of STIBP always on, it's necessary to allow per task
control of STIBP.
Add a new task flag TIF_SPEC_IB and evaluate it during context switch if
SMT is active and flag evaluation is enabled by the speculation control
code. Add the conditional evaluation to
Provide the possibility to enable IBPB always in combination with 'prctl'
and 'seccomp'.
Add the extra command line options and rework the IBPB selection to
evaluate the command instead of the mode selected by the STIPB switch case.
Signed-off-by: Thomas Gleixner
---
Reorder the code so it is better grouped.
Signed-off-by: Thomas Gleixner
---
arch/x86/kernel/cpu/bugs.c | 168 ++---
1 file changed, 84 insertions(+), 84 deletions(-)
--- a/arch/x86/kernel/cpu/bugs.c
+++ b/arch/x86/kernel/cpu/bugs.c
@@ -124,29 +124,6
Move the conditional invocation of __switch_to_xtra() into an inline
function so the logic can be shared between 32 and 64 bit.
Remove the handthrough of the TSS pointer and retrieve the pointer directly
in the bitmap handling function. Use this_cpu_ptr() instead of the
per_cpu() indirection.
Add command line control for user space indirect branch speculation
mitigations. The new option is: spectre_v2_user=
The initial options are:
- on: Unconditionally enabled
- off: Unconditionally disabled
-auto: Kernel selects mitigation (default off for now)
When the
To avoid the overhead of STIBP always on, it's necessary to allow per task
control of STIBP.
Add a new task flag TIF_SPEC_IB and evaluate it during context switch if
SMT is active and flag evaluation is enabled by the speculation control
code. Add the conditional evaluation to
Provide the possibility to enable IBPB always in combination with 'prctl'
and 'seccomp'.
Add the extra command line options and rework the IBPB selection to
evaluate the command instead of the mode selected by the STIPB switch case.
Signed-off-by: Thomas Gleixner
---
Reorder the code so it is better grouped.
Signed-off-by: Thomas Gleixner
---
arch/x86/kernel/cpu/bugs.c | 168 ++---
1 file changed, 84 insertions(+), 84 deletions(-)
--- a/arch/x86/kernel/cpu/bugs.c
+++ b/arch/x86/kernel/cpu/bugs.c
@@ -124,29 +124,6
Move the conditional invocation of __switch_to_xtra() into an inline
function so the logic can be shared between 32 and 64 bit.
Remove the handthrough of the TSS pointer and retrieve the pointer directly
in the bitmap handling function. Use this_cpu_ptr() instead of the
per_cpu() indirection.
The IBPB control code in x86 removed the usage. Remove the functionality
which was introduced for this.
Signed-off-by: Thomas Gleixner
---
include/linux/ptrace.h | 17 -
kernel/ptrace.c| 10 --
2 files changed, 27 deletions(-)
--- a/include/linux/ptrace.h
The IBPB speculation barrier is issued from switch_mm() when the kernel
switches to a user space task with a different mm than the user space task
which ran last on the same CPU.
An additional optimization is to avoid IBPB when the incoming task can be
ptraced by the outgoing task. This
The IBPB control code in x86 removed the usage. Remove the functionality
which was introduced for this.
Signed-off-by: Thomas Gleixner
---
include/linux/ptrace.h | 17 -
kernel/ptrace.c| 10 --
2 files changed, 27 deletions(-)
--- a/include/linux/ptrace.h
The IBPB speculation barrier is issued from switch_mm() when the kernel
switches to a user space task with a different mm than the user space task
which ran last on the same CPU.
An additional optimization is to avoid IBPB when the incoming task can be
ptraced by the outgoing task. This
If enhanced IBRS is active, STIBP is redundant for mitigating Spectre v2
user space exploits from hyperthread sibling.
Disable STIBP when enhanced IBRS is used.
Signed-off-by: Tim Chen
Signed-off-by: Thomas Gleixner
---
arch/x86/kernel/cpu/bugs.c |7 +++
1 file changed, 7
The Spectre V2 printout in cpu_show_common() handles conditionals for the
various mitigation methods directly in the sprintf() argument list. That's
hard to read and will become unreadable if more complex decisions need to
be made for a particular method.
Move the conditionals for STIBP and IBPB
If enhanced IBRS is active, STIBP is redundant for mitigating Spectre v2
user space exploits from hyperthread sibling.
Disable STIBP when enhanced IBRS is used.
Signed-off-by: Tim Chen
Signed-off-by: Thomas Gleixner
---
arch/x86/kernel/cpu/bugs.c |7 +++
1 file changed, 7
The Spectre V2 printout in cpu_show_common() handles conditionals for the
various mitigation methods directly in the sprintf() argument list. That's
hard to read and will become unreadable if more complex decisions need to
be made for a particular method.
Move the conditionals for STIBP and IBPB
CONFIG_SCHED_SMT is enabled by all distros, so there is not a real point to
have it configurable. The runtime overhead in the core scheduler code is
minimal because the actual SMT scheduling parts are conditional on a static
key.
This allows to expose the scheduler's SMT state static key to the
arch_smt_update() is only called when the sysfs SMT control knob is
changed. This means that when SMT is enabled in the sysfs control knob the
system is considered to have SMT active even if all siblings are offline.
To allow finegrained control of the speculation mitigations, the actual SMT
CONFIG_SCHED_SMT is enabled by all distros, so there is not a real point to
have it configurable. The runtime overhead in the core scheduler code is
minimal because the actual SMT scheduling parts are conditional on a static
key.
This allows to expose the scheduler's SMT state static key to the
arch_smt_update() is only called when the sysfs SMT control knob is
changed. This means that when SMT is enabled in the sysfs control knob the
system is considered to have SMT active even if all siblings are offline.
To allow finegrained control of the speculation mitigations, the actual SMT
On Sun, Nov 25, 2018 at 08:22:35AM -0800, Andy Lutomirski wrote:
Good morning to everyone, I hope the weekend continues to proceed
well.
Proposal follows below for kernel based policy management of enclaves
if people want to skip forward.
> >> On Nov 25, 2018, at 6:53 AM, Jarkko Sakkinen
> >>
On Sun, Nov 25, 2018 at 08:22:35AM -0800, Andy Lutomirski wrote:
Good morning to everyone, I hope the weekend continues to proceed
well.
Proposal follows below for kernel based policy management of enclaves
if people want to skip forward.
> >> On Nov 25, 2018, at 6:53 AM, Jarkko Sakkinen
> >>
On Sat, Nov 24, 2018 at 7:21 PM Hugh Dickins wrote:
>
> Linus, I'm addressing this patch to you because I see from Tim Chen's
> thread that it would interest you, and you were disappointed not to
> root cause the issue back then. I'm not pushing for you to fast-track
> this into 4.20-rc, but I
On Sat, Nov 24, 2018 at 7:21 PM Hugh Dickins wrote:
>
> Linus, I'm addressing this patch to you because I see from Tim Chen's
> thread that it would interest you, and you were disappointed not to
> root cause the issue back then. I'm not pushing for you to fast-track
> this into 4.20-rc, but I
This patch adds clock ID of audio CODEC (ACODEC) for rk3328.
Signed-off-by: Katsuhiro Suzuki
---
include/dt-bindings/clock/rk3328-cru.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dt-bindings/clock/rk3328-cru.h
b/include/dt-bindings/clock/rk3328-cru.h
index
This patch adds small changes into clock gate definition to enable
ACODEC for rk3328.
Signed-off-by: Katsuhiro Suzuki
---
drivers/clk/rockchip/clk-rk3328.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/rockchip/clk-rk3328.c
b/drivers/clk/rockchip/clk-rk3328.c
This patch adds clock ID of audio CODEC (ACODEC) for rk3328.
Signed-off-by: Katsuhiro Suzuki
---
include/dt-bindings/clock/rk3328-cru.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dt-bindings/clock/rk3328-cru.h
b/include/dt-bindings/clock/rk3328-cru.h
index
This patch adds small changes into clock gate definition to enable
ACODEC for rk3328.
Signed-off-by: Katsuhiro Suzuki
---
drivers/clk/rockchip/clk-rk3328.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/rockchip/clk-rk3328.c
b/drivers/clk/rockchip/clk-rk3328.c
For some reason, kvm_x86_ops->write_l1_tsc_offset() skipped trace
of change to active TSC offset in case vCPU is in guest-mode.
This patch changes write_l1_tsc_offset() behavior to trace any change
to active TSC offset to aid debugging. The VMX code is changed to
look more similar to SVM, which
For some reason, kvm_x86_ops->write_l1_tsc_offset() skipped trace
of change to active TSC offset in case vCPU is in guest-mode.
This patch changes write_l1_tsc_offset() behavior to trace any change
to active TSC offset to aid debugging. The VMX code is changed to
look more similar to SVM, which
The pull request you sent on Sun, 25 Nov 2018 03:04:11 +:
> git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.20-4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/17c2f540863a6c0faa3f0ede3c785d9427bcaf80
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 25 Nov 2018 03:04:11 +:
> git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.20-4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/17c2f540863a6c0faa3f0ede3c785d9427bcaf80
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sat, 24 Nov 2018 09:32:09 -0800:
> git://git.infradead.org/users/willy/linux-dax.git xarray
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e2125dac22f2c9c66c412cd8e049a7305af59f73
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sun, 25 Nov 2018 09:35:52 +0100:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-4.20-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d6d460b89378b1bc6715574cdafd748ba59d5a27
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sat, 24 Nov 2018 09:32:09 -0800:
> git://git.infradead.org/users/willy/linux-dax.git xarray
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e2125dac22f2c9c66c412cd8e049a7305af59f73
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sun, 25 Nov 2018 09:35:52 +0100:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-4.20-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d6d460b89378b1bc6715574cdafd748ba59d5a27
Thank you!
--
Deet-doot-dot, I am a
On 08/11/18 04:22, Yi Wang wrote:
> The inline keyword which is not at the beginning of the function
> declaration may trigger the following build warnings, so let's fix it:
>
> arch/x86/kvm/vmx.c:1309:1: warning: ‘inline’ is not at beginning of
> declaration [-Wold-style-declaration]
>
On 08/11/18 04:22, Yi Wang wrote:
> The inline keyword which is not at the beginning of the function
> declaration may trigger the following build warnings, so let's fix it:
>
> arch/x86/kvm/vmx.c:1309:1: warning: ‘inline’ is not at beginning of
> declaration [-Wold-style-declaration]
>
On 08/11/18 09:48, Yi Wang wrote:
> We get the following warnings about empty statements when building
> with 'W=1':
>
> arch/x86/kvm/lapic.c:632:53: warning: suggest braces around empty body in an
> ‘if’ statement [-Wempty-body]
> arch/x86/kvm/lapic.c:1907:42: warning: suggest braces around
On 12/11/18 14:37, j...@8bytes.org wrote:
> On Mon, Nov 12, 2018 at 12:23:14PM +, Suthikulpanit, Suravee wrote:
>> From: Wei Wang
>>
>> There is a race condition when accessing kvm->arch.apic_access_page_done.
>> Due to it, x86_set_memory_region will fail when creating the second vcpu
>> for
On 08/11/18 09:48, Yi Wang wrote:
> We get the following warnings about empty statements when building
> with 'W=1':
>
> arch/x86/kvm/lapic.c:632:53: warning: suggest braces around empty body in an
> ‘if’ statement [-Wempty-body]
> arch/x86/kvm/lapic.c:1907:42: warning: suggest braces around
On 12/11/18 14:37, j...@8bytes.org wrote:
> On Mon, Nov 12, 2018 at 12:23:14PM +, Suthikulpanit, Suravee wrote:
>> From: Wei Wang
>>
>> There is a race condition when accessing kvm->arch.apic_access_page_done.
>> Due to it, x86_set_memory_region will fail when creating the second vcpu
>> for
On 20/11/18 02:39, Wanpeng Li wrote:
> Reported by syzkaller:
>
> BUG: unable to handle kernel NULL pointer dereference at 0014
> PGD 80040410c067 P4D 80040410c067 PUD 40410d067 PMD 0
> Oops: [#1] PREEMPT SMP PTI
> CPU: 3 PID: 2567 Comm: poc Tainted: G OE
On 20/11/18 02:39, Wanpeng Li wrote:
> Reported by syzkaller:
>
> BUG: unable to handle kernel NULL pointer dereference at 0014
> PGD 80040410c067 P4D 80040410c067 PUD 40410d067 PMD 0
> Oops: [#1] PREEMPT SMP PTI
> CPU: 3 PID: 2567 Comm: poc Tainted: G OE
On 20/11/18 09:34, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Reported by syzkaller:
>
> BUG: unable to handle kernel NULL pointer dereference at 01c8
> PGD 8003ec4da067 P4D 8003ec4da067 PUD 3f7bfa067 PMD 0
> Oops: [#1] PREEMPT SMP PTI
> CPU: 7 PID: 5059 Comm: debug
On 20/11/18 09:34, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Reported by syzkaller:
>
> BUG: unable to handle kernel NULL pointer dereference at 01c8
> PGD 8003ec4da067 P4D 8003ec4da067 PUD 3f7bfa067 PMD 0
> Oops: [#1] PREEMPT SMP PTI
> CPU: 7 PID: 5059 Comm: debug
Hi,
On Sun, Nov 25, 2018 at 1:37 AM Brian Masney wrote:
> I bisected the issue to the following commit:
>
> 5451781dadf8 ("regulator: core: Only count load for enabled consumers")
>
> We have to increase the load for the sdhci in device tree in order for
> the phone to boot properly. This change
Hi,
On Sun, Nov 25, 2018 at 1:37 AM Brian Masney wrote:
> I bisected the issue to the following commit:
>
> 5451781dadf8 ("regulator: core: Only count load for enabled consumers")
>
> We have to increase the load for the sdhci in device tree in order for
> the phone to boot properly. This change
* Aaro Koskinen [181125 16:58]:
> Below changes get traffic going with DMA & g_ether...
Oh cool, if you have dma and g_ether working, you should
test it with a variable size ping test loop :) That should
expose any issues within few minutes.
Below is the test script I was using earlier, the
* Aaro Koskinen [181125 16:58]:
> Below changes get traffic going with DMA & g_ether...
Oh cool, if you have dma and g_ether working, you should
test it with a variable size ping test loop :) That should
expose any issues within few minutes.
Below is the test script I was using earlier, the
Some parameters are aligned with parentheses.
Some parentheses was opened at end of line.
Signed-off-by: Cristian Sicilia
---
Changes on v2:
* There was some function that was splitted in two line,
as suggested, is better to keep it in one line.
Some parameters are aligned with parentheses.
Some parentheses was opened at end of line.
Signed-off-by: Cristian Sicilia
---
Changes on v2:
* There was some function that was splitted in two line,
as suggested, is better to keep it in one line.
Hi,
On Sun, Nov 25, 2018 at 11:11:05AM +, Russell King - ARM Linux wrote:
> I think we're better off leaving omap-udc well alone, and if it's
> now broken with DMA, then that's unfortunate - it would require
> someone with the hardware to diagnose the problem and fix it. I
> think trying to
Hi,
On Sun, Nov 25, 2018 at 11:11:05AM +, Russell King - ARM Linux wrote:
> I think we're better off leaving omap-udc well alone, and if it's
> now broken with DMA, then that's unfortunate - it would require
> someone with the hardware to diagnose the problem and fix it. I
> think trying to
I'm taking over the maintainance of Sparse so add myself as
maintainer and move Christopher's info to CREDITS.
Signed-off-by: Luc Van Oostenryck
---
CREDITS | 4
MAINTAINERS | 3 +--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/CREDITS b/CREDITS
index
I'm taking over the maintainance of Sparse so add myself as
maintainer and move Christopher's info to CREDITS.
Signed-off-by: Luc Van Oostenryck
---
CREDITS | 4
MAINTAINERS | 3 +--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/CREDITS b/CREDITS
index
>> On Nov 25, 2018, at 6:53 AM, Jarkko Sakkinen
>> wrote:
>>
>> On Sat, Nov 24, 2018 at 09:21:14AM -0800, Jarkko Sakkinen wrote:
>> On Thu, Nov 22, 2018 at 07:21:08AM -0800, Andy Lutomirski wrote:
At a high level, addressing these issues is straight forward. First,
the driver needs
>> On Nov 25, 2018, at 6:53 AM, Jarkko Sakkinen
>> wrote:
>>
>> On Sat, Nov 24, 2018 at 09:21:14AM -0800, Jarkko Sakkinen wrote:
>> On Thu, Nov 22, 2018 at 07:21:08AM -0800, Andy Lutomirski wrote:
At a high level, addressing these issues is straight forward. First,
the driver needs
When I connect my Displaylink DL-165 adapter to my Debian/testing
machine, the "udl" driver is loaded and the following error messages
appears in kernel logs:
Nov 7 20:47:30 wzdell kernel: [ 205.871354] usb 4-1.2: new high-speed
USB device number 4 using ehci-pci
Nov 7 20:47:35 wzdell kernel:
When I connect my Displaylink DL-165 adapter to my Debian/testing
machine, the "udl" driver is loaded and the following error messages
appears in kernel logs:
Nov 7 20:47:30 wzdell kernel: [ 205.871354] usb 4-1.2: new high-speed
USB device number 4 using ehci-pci
Nov 7 20:47:35 wzdell kernel:
On Sun, Nov 25, 2018 at 06:14:44AM -0800, Matt Ranostay wrote:
> On Sun, Nov 25, 2018 at 6:03 AM Jonathan Cameron
> wrote:
> >
> > On Sun, 25 Nov 2018 05:51:32 -0800
> > Matt Ranostay wrote:
> >
> > > On Sat, Nov 24, 2018 at 2:14 PM Tomasz Duszynski
> > > wrote:
> > > >
> > > > Measuring
On Sun, Nov 25, 2018 at 06:14:44AM -0800, Matt Ranostay wrote:
> On Sun, Nov 25, 2018 at 6:03 AM Jonathan Cameron
> wrote:
> >
> > On Sun, 25 Nov 2018 05:51:32 -0800
> > Matt Ranostay wrote:
> >
> > > On Sat, Nov 24, 2018 at 2:14 PM Tomasz Duszynski
> > > wrote:
> > > >
> > > > Measuring
On Sun, Nov 25, 2018 at 02:03:16PM +, Jonathan Cameron wrote:
> On Sun, 25 Nov 2018 05:51:32 -0800
> Matt Ranostay wrote:
>
> > On Sat, Nov 24, 2018 at 2:14 PM Tomasz Duszynski wrote:
> > >
> > > Measuring particulate matter in ug / m3 (micro-grams per cubic meter)
> > > is de facto
On Sun, Nov 25, 2018 at 02:03:16PM +, Jonathan Cameron wrote:
> On Sun, 25 Nov 2018 05:51:32 -0800
> Matt Ranostay wrote:
>
> > On Sat, Nov 24, 2018 at 2:14 PM Tomasz Duszynski wrote:
> > >
> > > Measuring particulate matter in ug / m3 (micro-grams per cubic meter)
> > > is de facto
Hello,
syzbot found the following crash on:
HEAD commit:aea0a897af9e ptp: Fix pass zero to ERR_PTR() in ptp_clock_..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=101b91d540
kernel config: https://syzkaller.appspot.com/x/.config?x=c36a72af2123e78a
Hello,
syzbot found the following crash on:
HEAD commit:aea0a897af9e ptp: Fix pass zero to ERR_PTR() in ptp_clock_..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=101b91d540
kernel config: https://syzkaller.appspot.com/x/.config?x=c36a72af2123e78a
On Sun, Nov 25, 2018 at 08:35:07AM +, Jonathan Cameron wrote:
> On Sat, 24 Nov 2018 23:14:13 +0100
> Tomasz Duszynski wrote:
>
> > Measuring particulate matter in ug / m3 (micro-grams per cubic meter)
> > is de facto standard. Existing air quality sensors usually follow
> > this convention
On Sun, Nov 25, 2018 at 08:35:07AM +, Jonathan Cameron wrote:
> On Sat, 24 Nov 2018 23:14:13 +0100
> Tomasz Duszynski wrote:
>
> > Measuring particulate matter in ug / m3 (micro-grams per cubic meter)
> > is de facto standard. Existing air quality sensors usually follow
> > this convention
On Sat, Nov 24, 2018 at 09:21:14AM -0800, Jarkko Sakkinen wrote:
> On Thu, Nov 22, 2018 at 07:21:08AM -0800, Andy Lutomirski wrote:
> > > At a high level, addressing these issues is straight forward. First,
> > > the driver needs to support authorization equivalent to that which is
> > >
On Sat, Nov 24, 2018 at 09:21:14AM -0800, Jarkko Sakkinen wrote:
> On Thu, Nov 22, 2018 at 07:21:08AM -0800, Andy Lutomirski wrote:
> > > At a high level, addressing these issues is straight forward. First,
> > > the driver needs to support authorization equivalent to that which is
> > >
On Sun, Nov 25, 2018 at 6:03 AM Jonathan Cameron
wrote:
>
> On Sun, 25 Nov 2018 05:51:32 -0800
> Matt Ranostay wrote:
>
> > On Sat, Nov 24, 2018 at 2:14 PM Tomasz Duszynski wrote:
> > >
> > > Measuring particulate matter in ug / m3 (micro-grams per cubic meter)
> > > is de facto standard.
On Sun, Nov 25, 2018 at 6:03 AM Jonathan Cameron
wrote:
>
> On Sun, 25 Nov 2018 05:51:32 -0800
> Matt Ranostay wrote:
>
> > On Sat, Nov 24, 2018 at 2:14 PM Tomasz Duszynski wrote:
> > >
> > > Measuring particulate matter in ug / m3 (micro-grams per cubic meter)
> > > is de facto standard.
On Sun, 18 Nov 2018 16:27:57 +
Colin King wrote:
> From: Colin Ian King
>
> The statement is indented too much by one level, fix this by
> removing the extraneous tab.
>
> Signed-off-by: Colin Ian King
Applied to the togreg branch of iio.git and pushed out as testing
because lots of
On Sun, 18 Nov 2018 16:27:57 +
Colin King wrote:
> From: Colin Ian King
>
> The statement is indented too much by one level, fix this by
> removing the extraneous tab.
>
> Signed-off-by: Colin Ian King
Applied to the togreg branch of iio.git and pushed out as testing
because lots of
On Sun, 25 Nov 2018 05:51:32 -0800
Matt Ranostay wrote:
> On Sat, Nov 24, 2018 at 2:14 PM Tomasz Duszynski wrote:
> >
> > Measuring particulate matter in ug / m3 (micro-grams per cubic meter)
> > is de facto standard. Existing air quality sensors usually follow
> > this convention and are
On Sun, 25 Nov 2018 05:51:32 -0800
Matt Ranostay wrote:
> On Sat, Nov 24, 2018 at 2:14 PM Tomasz Duszynski wrote:
> >
> > Measuring particulate matter in ug / m3 (micro-grams per cubic meter)
> > is de facto standard. Existing air quality sensors usually follow
> > this convention and are
On Sat, Nov 24, 2018 at 6:06 PM Miguel Ojeda
wrote:
>
> On Fri, Nov 23, 2018 at 10:14 PM Luc Van Oostenryck
> wrote:
> >
> > On Thu, Nov 22, 2018 at 12:14:20PM +0900, Masahiro Yamada wrote:
> > > When I tried to enable BUILD_BUG_ON for Sparse, the kbuild test robot
> > > reported lots of
On Sat, Nov 24, 2018 at 6:06 PM Miguel Ojeda
wrote:
>
> On Fri, Nov 23, 2018 at 10:14 PM Luc Van Oostenryck
> wrote:
> >
> > On Thu, Nov 22, 2018 at 12:14:20PM +0900, Masahiro Yamada wrote:
> > > When I tried to enable BUILD_BUG_ON for Sparse, the kbuild test robot
> > > reported lots of
On Sat, Nov 24, 2018 at 11:16 PM Vinod Koul wrote:
>
> On 12-10-18, 01:41, Masahiro Yamada wrote:
> > 1/2: DT-binding
> > 2/2: driver
>
> Applied this series, thanks
Thanks.
> While building I noticed that we get few warns when compiling with
> C=1, I would prefer you fix them. Please send
On Sat, Nov 24, 2018 at 11:16 PM Vinod Koul wrote:
>
> On 12-10-18, 01:41, Masahiro Yamada wrote:
> > 1/2: DT-binding
> > 2/2: driver
>
> Applied this series, thanks
Thanks.
> While building I noticed that we get few warns when compiling with
> C=1, I would prefer you fix them. Please send
On Sat, Nov 24, 2018 at 2:14 PM Tomasz Duszynski wrote:
>
> Measuring particulate matter in ug / m3 (micro-grams per cubic meter)
> is de facto standard. Existing air quality sensors usually follow
> this convention and are capable of returning measurements using
> this unit.
>
> IIO currently
On Sat, Nov 24, 2018 at 2:14 PM Tomasz Duszynski wrote:
>
> Measuring particulate matter in ug / m3 (micro-grams per cubic meter)
> is de facto standard. Existing air quality sensors usually follow
> this convention and are capable of returning measurements using
> this unit.
>
> IIO currently
On Mon, 19 Nov 2018 12:12:36 +0530
Vignesh R wrote:
> When performing single ended measurements with TSCADC, its recommended
> to set negative input (SEL_INM_SWC_3_0) of ADC step to ADC's VREFN in the
> corresponding STEP_CONFIGx register.
> Also, the positive(SEL_RFP_SWC_2_0) and
On Mon, 19 Nov 2018 12:12:36 +0530
Vignesh R wrote:
> When performing single ended measurements with TSCADC, its recommended
> to set negative input (SEL_INM_SWC_3_0) of ADC step to ADC's VREFN in the
> corresponding STEP_CONFIGx register.
> Also, the positive(SEL_RFP_SWC_2_0) and
On Wed, 21 Nov 2018 13:13:40 +0800
Jian-Hong Pan wrote:
> Denis CIOCCA 於 2018年11月20日 週二 上午3:05寫道：
> >
> > Hi Jian,
> >
> > Not clear to me why should be + instead of *.
> >
> > ODR is expressed in Hz, so (1/Hz) = period in seconds (1 sample sampling
> > time) [s]
> > 1000 * (1/Hz) = period in
On Wed, 21 Nov 2018 13:13:40 +0800
Jian-Hong Pan wrote:
> Denis CIOCCA 於 2018年11月20日 週二 上午3:05寫道：
> >
> > Hi Jian,
> >
> > Not clear to me why should be + instead of *.
> >
> > ODR is expressed in Hz, so (1/Hz) = period in seconds (1 sample sampling
> > time) [s]
> > 1000 * (1/Hz) = period in
On Tue, 20 Nov 2018 11:12:32 +0100
Fabrice Gasnier wrote:
> Switch off ADC when going to low power mode, in case it has been left
> running in buffer mode. Then re-enable it when resuming.
>
> Signed-off-by: Fabrice Gasnier
My suspicion is that we have other drivers not correctly handing this
On Tue, 20 Nov 2018 11:12:32 +0100
Fabrice Gasnier wrote:
> Switch off ADC when going to low power mode, in case it has been left
> running in buffer mode. Then re-enable it when resuming.
>
> Signed-off-by: Fabrice Gasnier
My suspicion is that we have other drivers not correctly handing this
On Tue, 20 Nov 2018 11:12:31 +0100
Fabrice Gasnier wrote:
> Add support for runtime PM & sleep. Move all regulator and clock management
> to dedicated HW start/stop routines. Then rely on (runtime) PM OPS to
> call them.
>
> Signed-off-by: Fabrice Gasnier
Whilst I'll be the first to admit that
On Tue, 20 Nov 2018 11:12:31 +0100
Fabrice Gasnier wrote:
> Add support for runtime PM & sleep. Move all regulator and clock management
> to dedicated HW start/stop routines. Then rely on (runtime) PM OPS to
> call them.
>
> Signed-off-by: Fabrice Gasnier
Whilst I'll be the first to admit that
On Sun, 25 Nov 2018 13:03:39 +
Jonathan Cameron wrote:
> On Tue, 20 Nov 2018 11:12:30 +0100
> Fabrice Gasnier wrote:
>
> > Move self-calibration routine to prepare routine.
> > - This is precursor patch to ease power management handling.
> > - This also allow to factorize few error cases
On Sun, 25 Nov 2018 13:03:39 +
Jonathan Cameron wrote:
> On Tue, 20 Nov 2018 11:12:30 +0100
> Fabrice Gasnier wrote:
>
> > Move self-calibration routine to prepare routine.
> > - This is precursor patch to ease power management handling.
> > - This also allow to factorize few error cases
On 2018/11/25 20:21, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit: e195ca6cb6f2 Merge branch 'for-linus' of git://git.kernel...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1659a62b40
> kernel config:
On 2018/11/25 20:21, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit: e195ca6cb6f2 Merge branch 'for-linus' of git://git.kernel...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1659a62b40
> kernel config:
On Tue, 20 Nov 2018 11:12:30 +0100
Fabrice Gasnier wrote:
> Move self-calibration routine to prepare routine.
> - This is precursor patch to ease power management handling.
> - This also allow to factorize few error cases (error handling).
>
> Signed-off-by: Fabrice Gasnier
one trivial point
On Tue, 20 Nov 2018 11:12:30 +0100
Fabrice Gasnier wrote:
> Move self-calibration routine to prepare routine.
> - This is precursor patch to ease power management handling.
> - This also allow to factorize few error cases (error handling).
>
> Signed-off-by: Fabrice Gasnier
one trivial point
401 - 500 of 574 matches
Mail list logo
