Add support to output level control for the analog high power output
drivers HPOUT and HPCOM.
Signed-off-by: Saravanan Sekar
---
Notes:
Changes in V2:
- Removed power control as it is handled by DAPM
- Added level control for left channel
sound/soc/codecs/tlv320aic3x.c | 9
From: Pankaj Bansal
Generic register bitfield-based multiplexer that controls the multiplexer
producer defined under a parent node.
The driver corresponding to parent node provides register read/write
capabilities.
Signed-off-by: Pankaj Bansal
Signed-off-by: Peter Rosin
---
From: Pankaj Bansal
This adds device tree binding documentation for generic register based
multiplexer controlled by a bitfields in a parent device's register range.
since MMIO mux is a special case of generic register based mux, the
MMIO mux bindings have been subsumed in these bindings.
Hi Greg,
A small addition to the mmio mux so that it can handle non-syscon
regmaps. The bindings patch should probably have had Robs tag,
but after a bit of back and forth I got the impression that it
wasn't really needed, since it's basically just a file rename
plus addition of a compatible [1].
There are no users of set_mms and set_mmss64 as they have all been
converted to set_time and are handling the tm to time conversion on their
own.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/interface.c | 12 +++-
drivers/rtc/systohc.c | 6 +-
include/linux/rtc.h | 2 --
Jacek
On 4/30/19 2:32 PM, Jacek Anaszewski wrote:
> On 4/30/19 9:30 PM, Dan Murphy wrote:
>> Randy
>>
>> On 4/30/19 2:23 PM, Randy Dunlap wrote:
>>> On 4/30/19 12:17 PM, Dan Murphy wrote:
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
index da00b9ed5a5c..3ae24eaf4cde 100644
On 4/30/19 9:30 PM, Dan Murphy wrote:
Randy
On 4/30/19 2:23 PM, Randy Dunlap wrote:
On 4/30/19 12:17 PM, Dan Murphy wrote:
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
index da00b9ed5a5c..3ae24eaf4cde 100644
--- a/drivers/leds/Kconfig
+++ b/drivers/leds/Kconfig
@@ -776,6 +776,14
On 29/04/19 15:58, Konrad Rzeszutek Wilk wrote:
> On Mon, Mar 18, 2019 at 07:16:28PM +, Raslan, KarimAllah wrote:
>> On Mon, 2019-03-18 at 10:22 -0400, Konrad Rzeszutek Wilk wrote:
>>> On Mon, Mar 18, 2019 at 01:10:24PM +, Raslan, KarimAllah wrote:
I guess this patch series
On 29/04/19 15:25, Radim Krčmář wrote:
> This reverts commit 919f6cd8bb2fe7151f8aecebc3b3d1ca2567396e.
>
> The patch was applied twice.
> The first commit is eca6be566d47029f945a5f8e1c94d374e31df2ca.
>
> Reported-by: Cornelia Huck
> Signed-off-by: Radim Krčmář
> ---
>
Randy
On 4/30/19 2:23 PM, Randy Dunlap wrote:
> On 4/30/19 12:17 PM, Dan Murphy wrote:
>> diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
>> index da00b9ed5a5c..3ae24eaf4cde 100644
>> --- a/drivers/leds/Kconfig
>> +++ b/drivers/leds/Kconfig
>> @@ -776,6 +776,14 @@ config LEDS_NIC78BX
>>
On 26/04/19 15:27, Vitaly Kuznetsov wrote:
> Enlightened VMCS is only supported on Intel CPUs but the test shouldn't
> fail completely.
>
> Signed-off-by: Vitaly Kuznetsov
> ---
> tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c | 9 -
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
On 4/30/19 12:17 PM, Dan Murphy wrote:
> diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
> index da00b9ed5a5c..3ae24eaf4cde 100644
> --- a/drivers/leds/Kconfig
> +++ b/drivers/leds/Kconfig
> @@ -776,6 +776,14 @@ config LEDS_NIC78BX
> To compile this driver as a module, choose M
On Tue, Apr 30, 2019 at 12:21:54PM -0400, Joel Fernandes (Google) wrote:
> Other than verifying pidfd based polling, the tests make sure that
> wait semantics are preserved with the pidfd poll. Notably the 2 cases:
> 1. If a thread group leader exits while threads still there, then no
>pidfd
Remove support for the LM3697 from the ti-lmu driver in favor of a
dedicated LED driver.
Acked-for-MFD-by: Lee Jones
Signed-off-by: Dan Murphy
---
v3 - No changes - https://lore.kernel.org/patchwork/patch/1058760/
v2 - Fixed commit message LF, removed leds/Kconfig from patch. -
Hello
I have added the Reviewed-by for dt bindings as well as made the Kconfig change
pointed out for the common code flag
Dan
Dan Murphy (7):
dt-bindings: mfd: LMU: Fix lm3632 dt binding example
dt-bindings: mfd: LMU: Add the ramp up/down property
dt-bindings: mfd: LMU: Add
Introduce the lm3697 LED driver for backlighting and display.
Datasheet location:
http://www.ti.com/lit/ds/symlink/lm3697.pdf
Signed-off-by: Dan Murphy
---
v3 - Moved TI_COMMON_LMU flag above LM3697 flag for inheritance also fixed
removed
REGMAP dependency - v1 comments
Add ti,brightness-resolution to the TI LMU binding to define
whether the device uses 8-bit brightness or 11-bit brightness.
Reviewed-by: Rob Herring
Signed-off-by: Dan Murphy
---
v3 - No changes added Reviewed-by Rob -
https://lore.kernel.org/patchwork/patch/1058763/
v2 - New patch. Add
Document the ramp-up and ramp-down property in the binding.
Removing the "sec" from the property definition as seconds is
implied.
Reviewed-by: Rob Herring
Signed-off-by: Dan Murphy
---
v3 - No changes added Reviewed-by Rob -
https://lore.kernel.org/patchwork/patch/1058759/
v2 - Fixed commit
The LM3697 is a single function LED driver. The single function LED
driver needs to reside in the LED directory as a dedicated LED driver
and not as a MFD device. The device does have common brightness and ramp
features and those can be accomodated by a TI LMU framework.
The LM3697 dt binding
Create a TI LMU common framework for TI LMU devices that share
common features.
Currently the runtime ramp and brightness setting have
been identified as common features with common register settings.
This work is derived from Milo Kims TI LMU MFD code.
Acked-by: Pavel Machek
Signed-off-by:
Fix the lm3632 dt binding examples as the LCM enable GPIOs
are defined as enable GPIOs per the regulator/lm363x-regulator.txt
bindings document.
Reviewed-by: Rob Herring
Signed-off-by: Dan Murphy
---
v3 - No changes added Reviewed-by Rob -
https://lore.kernel.org/patchwork/patch/1058757/
v2 -
On 30/04/2019 18:25:52+0300, Baruch Siach wrote:
> > Yes, this is ok to return a valid value that is higher than range_max.
> > However, at that time, you will not be able to set any alarms anymore as
> > the core doesn't allow to set alarms after range_max.
> >
> > I would think that this is fine
On 23/04/19 13:40, Jiang Biao wrote:
> is_dirty has been renamed to flush, but the comment for it is
> outdated. And the description about @flush parameter for
> kvm_clear_dirty_log_protect() is missing, add it in this patch
> as well.
>
> Signed-off-by: Jiang Biao
> ---
> virt/kvm/kvm_main.c |
On Tue, Apr 30, 2019 at 12:21:53PM -0400, Joel Fernandes (Google) wrote:
> Android low memory killer (LMK) needs to know when a process dies once
> it is sent the kill signal. It does so by checking for the existence of
> /proc/pid which is both racy and slow. For example, if a PID is reused
>
stable-rc/linux-4.14.y boot: 117 boots: 2 failed, 114 passed with 1
untried/unknown (v4.14.114-54-gdb44a158d937)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.114-54-gdb44a158d937/
Full Build Summary:
On Tue, 30 Apr 2019 11:33:21 -0700
Linus Torvalds wrote:
> On Tue, Apr 30, 2019 at 10:49 AM Steven Rostedt wrote:
> >
> > +
> > +asm(
> > + ".text\n"
> > +
> > + /* Trampoline for function update with interrupts enabled */
> > + ".global ftrace_emulate_call_irqoff\n"
> > +
Some hardware configurations might pass on providing an interrupt line.
In that case there is always the option to use a polled input approach.
This patch adapts the driver for it.
The polled approach is only triggered if no interrupt is provided by the
firmware or platform data.
Signed-off-by:
Some devices might not provide an interrupt line for the touchscreen.
In that case the driver defaults to using a polled interface.
Signed-off-by: Nicolas Saenz Julienne
---
.../devicetree/bindings/input/touchscreen/edt-ft5x06.txt | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
On Tue, Apr 30, 2019 at 5:33 AM Borislav Petkov wrote:
> So that die thing has only small relevance to some software, as you say:
>
> "These topology changes primarily impact parts of the kernel and some
> applciations that care about package MSR scope."
>
> So if there's no real need to add it
On Tue, 30 Apr 2019, Stephen Boyd wrote:
> Quoting Paul Walmsley (2019-04-29 22:57:15)
> > On Mon, 29 Apr 2019, Stephen Boyd wrote:
> >
> > > Quoting Paul Walmsley (2019-04-29 12:42:07)
> > > > On Fri, 26 Apr 2019, Paul Walmsley wrote:
> > > > > On Fri, 26 Apr 2019, Stephen Boyd wrote:
> > > > >
On Tue, Apr 30, 2019 at 07:33:26PM +0200, Vitaly Kuznetsov wrote:
> Commit 47c42e6b4192 ("KVM: x86: fix handling of role.cr4_pae and rename it
> to 'gpte_size'") introduced a regression: 32-bit PAE guests stopped
"gpte_is_8_bytes" is really confusing in this case. :-( Unfortunately I
can't think
On Tue, Apr 30, 2019 at 10:49 AM Steven Rostedt wrote:
>
> +
> +asm(
> + ".text\n"
> +
> + /* Trampoline for function update with interrupts enabled */
> + ".global ftrace_emulate_call_irqoff\n"
> + ".type ftrace_emulate_call_irqoff, @function\n"
> +
Hi Mehmet, David,
I came up with an enhancement to the scripts/extract-sys-certs.pl script
in Linux kernel source, so that the system certificates can be extracted
without debugging symbols or System.map file.
The idea is that the DER-format kernel X509 certificate follows some fixed
pattern. So
This patch resolves coding style space ERRORs reported by checkpatch
ERROR: spaces required around that '>' (ctx:VxV)
ERROR: space required after that ',' (ctx:VxO)
ERROR: space required before that '&' (ctx:OxV)
ERROR: spaces required around that '!=' (ctx:VxV)
ERROR: spaces required around that
Quoting Paul Walmsley (2019-04-29 22:57:15)
> On Mon, 29 Apr 2019, Stephen Boyd wrote:
>
> > Quoting Paul Walmsley (2019-04-29 12:42:07)
> > > On Fri, 26 Apr 2019, Paul Walmsley wrote:
> > > > On Fri, 26 Apr 2019, Stephen Boyd wrote:
> > > >
> > > > > Quoting Paul Walmsley (2019-04-11 01:27:32)
The pull request you sent on Mon, 29 Apr 2019 18:55:19 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
> tags/selinux-pr-20190429
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fea27bc7ff43a8beb6bebe6d4fe9eb889e185d4a
Thank you!
--
The pull request you sent on Tue, 30 Apr 2019 16:37:11 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git tags/usb-5.1-rc8
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bf3bd966dfd7d9582f50e9bd08b15922197cd277
Thank you!
--
Deet-doot-dot, I am a
On Tue, Apr 30, 2019 at 12:05:09PM -0600, Keith Busch wrote:
> On Tue, Apr 30, 2019 at 11:11:51AM -0500, Bjorn Helgaas wrote:
> > > I'm not convinced a revert is the best call.
> >
> > I have very limited options at this stage of the release, but I'd be
> > glad to hear suggestions. My concern
On 4/16/19 3:09 AM, Rafael J. Wysocki wrote:
On Tue, Apr 16, 2019 at 5:29 AM Vinod Koul wrote:
On 15-04-19, 10:18, Pierre-Louis Bossart wrote:
Standards such as the MIPI DisCo for SoundWire 1.0 specification
assume the _ADR field is 64 bits.
_ADR is defined as an "Integer" represented as
On Mon, Apr 29, 2019 at 10:32 AM Nick Desaulniers
wrote:
>
> On Fri, Apr 26, 2019 at 12:06 PM Rasmus Villemoes
> wrote:
> >
> > Current versions of clang does not like the %c modifier in inline
> > assembly for targets other than x86, so any DYNAMIC_DEBUG=y build
> > fails on arm64. A fix is
Quoting Gustavo A. R. Silva (2019-04-30 10:28:32)
>
>
> On 4/30/19 12:22 PM, Stephen Boyd wrote:
> > Quoting Gustavo A. R. Silva (2019-04-30 07:32:06)
> >> In preparation to enabling -Wimplicit-fallthrough, mark switch
> >> cases where we are expecting to fall through.
> >>
> >> This patch fixes
Quoting Anson Huang (2019-04-29 18:55:18)
> Fix below fall through build warning:
>
> drivers/clk/imx/clk-pllv3.c:453:21: warning:
> this statement may fall through [-Wimplicit-fallthrough=]
>
>pll->denom_offset = PLL_IMX7_DENOM_OFFSET;
> ^
>
On Tue, Apr 30, 2019 at 11:01 AM Matteo Croce wrote:
>
> In the sysctl code the proc_dointvec_minmax() function is often used to
> validate the user supplied value between an allowed range. This function
> uses the extra1 and extra2 members from struct ctl_table as minimum and
> maximum allowed
On Tue, Apr 30, 2019 at 11:11:51AM -0500, Bjorn Helgaas wrote:
> > I'm not convinced a revert is the best call.
>
> I have very limited options at this stage of the release, but I'd be
> glad to hear suggestions. My concern is that if we release v5.1
> as-is, we'll spend a lot of energy on those
On Tue, Apr 30, 2019 at 9:30 AM Matteo Croce wrote:
>
> On Tue, Apr 30, 2019 at 6:08 PM Matthew Wilcox wrote:
> >
> > On Tue, Apr 30, 2019 at 08:42:42AM -0700, Kees Cook wrote:
> > > On Tue, Apr 30, 2019 at 3:47 AM Matteo Croce wrote:
> > > > On Tue, Apr 30, 2019 at 12:26 AM Matteo Croce
On Mon, Apr 29, 2019 at 10:59:26AM -0600, Alex Williamson wrote:
> On Mon, 29 Apr 2019 09:45:28 -0700
> Sinan Kaya wrote:
>
> > On 4/29/2019 10:51 AM, Alex Williamson wrote:
> > > So where do we go from here? I agree that dmesg is not necessarily a
> > > great choice for these sorts of events
On Tue, Apr 30, 2019 at 10:51 AM Reshetova, Elena
wrote:
> base: Simple syscall: 0.1761 microseconds
> get_random_bytes (4096 bytes per-cpu buffer): 0.1793 microsecons
> get_random_bytes (64 bytes per-cpu buffer): 0.1866 microsecons
The 4096 size seems pretty good.
> Below is a snip of what I
In the sysctl code the proc_dointvec_minmax() function is often used to
validate the user supplied value between an allowed range. This function
uses the extra1 and extra2 members from struct ctl_table as minimum and
maximum allowed value.
On sysctl handler declaration, in every source file there
Thank you for your feedback Vadim. I have addressed your comments.
1) You are correct. This driver is not specific to Mellanox so I
have removed the Mellanox attribute.
2) I have added a documentation file called IPMB.txt which explains
how this module works and how it should be instantiated. It
On Tue, 30 Apr 2019 09:29:40 +0200
Eric Auger wrote:
> Extended Capability Register PSS field (PASID Size Supported)
> corresponds to the PASID bit size -1.
>
> "A value of N in this field indicates hardware supports PASID
> field of N+1 bits (For example, value of 7 in this field,
> indicates
Support receiving IPMB requests on a Satellite MC from the BMC.
Once a response is ready, this driver will send back a response
to the BMC via the IPMB channel.
Signed-off-by: Asmaa Mnebhi
---
Documentation/IPMB.txt | 53 ++
drivers/char/ipmi/Kconfig| 8 +
>
> > On Apr 29, 2019, at 12:46 AM, Reshetova, Elena
> wrote:
> >
> >
> On Apr 26, 2019, at 7:01 AM, Theodore Ts'o wrote:
> >>>
> >
> >> It seems to me
> >> that we should be using the “fast-erasure” construction for all
> get_random_bytes()
> >> invocations. Specifically, we should have a
From: "Steven Rostedt (VMware)"
Nicolai Stange discovered[1] that if live kernel patching is enabled, and the
function tracer started tracing the same function that was patched, the
conversion of the fentry call site during the translation of going from
calling the live kernel patch
-- Forwarded message --
From: charles moulier
Date: Tue, 30 Apr 2019 18:36:12 +0100
Subject:
rrr7.pdf
Description: Adobe PDF document
Hi people,
sadly, I have been tied to bed for a few days now, not in a condition to
really work on I2C, and this will not change until the weekend. I will
try hard to send out another pull request for 5.1, to get things fixed
properly, but only super trivial patches will be applied on top of my
Commit 47c42e6b4192 ("KVM: x86: fix handling of role.cr4_pae and rename it
to 'gpte_size'") introduced a regression: 32-bit PAE guests stopped
working. The issue appears to be: when guest switches (enables) PAE we need
to re-initialize MMU context (set context->root_level, do
On 4/30/19 12:22 PM, Stephen Boyd wrote:
> Quoting Gustavo A. R. Silva (2019-04-30 07:32:06)
>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>> cases where we are expecting to fall through.
>>
>> This patch fixes the following warnings:
>>
>> drivers/clk/imx/clk-pllv3.c: In
-- Forwarded message --
From: charles moulier
Date: Tue, 30 Apr 2019 18:26:14 +0100
Subject:
rrr7.pdf
Description: Adobe PDF document
stable-rc/linux-4.19.y boot: 122 boots: 0 failed, 121 passed with 1 offline
(v4.19.37-101-gf0b5b3d18a2f)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.37-101-gf0b5b3d18a2f/
Full Build Summary:
Quoting Gustavo A. R. Silva (2019-04-30 07:32:06)
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> drivers/clk/imx/clk-pllv3.c: In function ‘imx_clk_pllv3’:
>
On Tue, 30 Apr 2019 13:03:59 -0400
Steven Rostedt wrote:
> I also prefer Josh's stack shift solution, as I personally believe
> that's a cleaner solution. But I went ahead and implemented Linus's
> version to get it working for ftrace. Here's the code, and it survived
> some preliminary tests.
-- Forwarded message --
From: charles moulier
Date: Tue, 30 Apr 2019 18:17:25 +0100
Subject:
rrr7.pdf
Description: Adobe PDF document
On Tue, 30 Apr 2019, Paul Walmsley wrote:
> The above sequence indicates a kerneldoc-style comment, but the format of
> the comment is not in kerneldoc format. Please fix this comment to
> conform with
>
>
On Sun, 28 Apr 2019, Sagar Shrikant Kadam wrote:
> Nor device (is25wp256 mounted on HiFive unleashed Rev A00 board) from ISSI
> have memory blocks guarded by block protection bits BP[0,1,2,3].
>
> Clearing block protection bits,unlocks the flash memory regions
> The unlock scheme is registered
On 30-04-19, 16:58, Arnaud Pouliquen wrote:
> >> Hope that will help to clarify.
> >
> > Yes that helps, maybe we should add these bits in code and changelog..
> > :)I will update the comments and commit message in a V2 in this way
> >
> > And how does this impact non cyclic case where N
Hi Lucas,
On Tue, Apr 30, 2019 at 03:50:04PM +0200, Lucas Stach wrote:
> Am Dienstag, den 30.04.2019, 15:41 +0200 schrieb Guido Günther:
> > Add a node for the irqsteer interrupt controller found on the iMX8MQ
> > SoC.
> >
> > Signed-off-by: Guido Günther
> > ---
> >
Add a node for the irqsteer interrupt controller found on the iMX8MQ
SoC.
Signed-off-by: Guido Günther
Reviewed-by: Lucas Stach
---
Changes from v1 as per comments from Lucas Stach
* Drop interrupt-parent
* Move compatible stings to a single line
arch/arm64/boot/dts/freescale/imx8mq.dtsi |
On Sat 27 Apr 03:22 PDT 2019, Brian Masney wrote:
> Hi Bjorn,
>
> On Fri, Apr 26, 2019 at 10:30:34PM -0700, Bjorn Andersson wrote:
> > On Tue 05 Mar 16:53 PST 2019, Brian Masney wrote:
> >
> > > Here are some patches that fix gpio hogging for all boards that use
> > > spmi-gpio and ssbi-gpio.
On Sun, 28 Apr 2019, Sagar Shrikant Kadam wrote:
> The locking scheme for ISSI devices is based on stm_lock mechanism.
> The is25x devices have 4 bits for selecting the range of blocks to
> be locked for write.
>
> The current implementation, blocks entire 512 blocks of flash memory.
>
>
* Linus Torvalds:
> On Tue, Apr 30, 2019 at 9:19 AM Linus Torvalds
> wrote:
>>
>> Of course, if you *don't* need the exact vfork() semantics, clone
>> itself actually very much supports a callback model with s separate
>> stack. You can basically do this:
>>
>> - allocate new stack for the
stable-rc/linux-5.0.y boot: 128 boots: 6 failed, 118 passed with 2 offline, 1
untried/unknown, 1 conflict (v5.0.10-90-g852cce372723)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.0.y/kernel/v5.0.10-90-g852cce372723/
Full Build Summary:
Add PTRACE_SYSEMU and PTRACE_SYSEMU_SINGLESTEP support on arm64.
We don't need any special handling for PTRACE_SYSEMU_SINGLESTEP.
It's quite difficult to generalize handling PTRACE_SYSEMU cross
architectures and avoid calls to tracehook_report_syscall_entry twice.
Different architecture have
x86 and um use 31 and 32 for PTRACE_SYSEMU and PTRACE_SYSEMU_SINGLESTEP
while powerpc uses different value maybe for legacy reasons.
Though handling of PTRACE_SYSEMU can be made architecture independent,
it's hard to make these definations generic. To add to this existing
mess few architectures
The usage of emulated/_TIF_SYSCALL_EMU flags in syscall_trace_enter
seems to be bit overcomplicated than required. Let's simplify it.
Cc: Andy Lutomirski
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Signed-off-by: Sudeep Holla
---
arch/x86/entry/common.c | 17 ++---
1
While the TIF_SYSCALL_EMU is set in ptrace_resume independent of any
architecture, currently only powerpc and x86 unset the TIF_SYSCALL_EMU
flag in ptrace_disable which gets called from ptrace_detach.
Let's move the clearing of TIF_SYSCALL_EMU flag to __ptrace_unlink
which gets executed from
Hi,
This patchset evolved from the discussion in the thread[0][1]. When we
wanted to add PTRACE_SYSEMU support to ARM64, we thought instead of
duplicating what other architectures like x86 and powerpc have done,
let consolidate the existing support and move it to the core as there's
nothing arch
On Tue, 30 Apr 2019 09:33:51 -0700
Andy Lutomirski wrote:
> Linus, can I ask you to reconsider your opposition to Josh's other
> approach of just shifting the stack on int3 entry? I agree that it's
> ugly, but the ugliness is easily manageable and fairly self-contained.
> We add a little bit
On Sun, 28 Apr 2019, Sagar Shrikant Kadam wrote:
> Update spi_nor_id tablet for is25wp256 (32MB)device from ISSI,
> present on HiFive Unleashed dev board (Rev: A00).
>
> Set method to enable quad mode for ISSI device in flash parameters
> table.
This patch was based on one originally written by
The shortcut for single segment SGL requests did not set the PSDT field
to mark the request as using SGLs.
Fixes: 297910571f08 ("nvme-pci: optimize mapping single segment requests using
SGLs")
Signed-off-by: Klaus Birkelund Jensen
---
drivers/nvme/host/pci.c | 1 +
1 file changed, 1
Intel Comet Lake has the same LPSS than Intel Cannon Lake.
Add the new IDs to the list of supported devices.
Signed-off-by: Andy Shevchenko
---
- update i2c info
drivers/mfd/intel-lpss-pci.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/mfd/intel-lpss-pci.c
> On Apr 30, 2019, at 12:20 PM, Vincent Guittot
> wrote:
>
> Hi Song,
>
> On Tue, 30 Apr 2019 at 08:11, Song Liu wrote:
>>
>>
>>
>>> On Apr 29, 2019, at 8:24 AM, Vincent Guittot
>>> wrote:
>>>
>>> Hi Song,
>>>
>>> On Sun, 28 Apr 2019 at 21:47, Song Liu wrote:
Hi Morten
On Tue, Apr 30, 2019 at 04:37:53PM +0800, Kai-Heng Feng wrote:
> Commit a939bb57cd47 ("pinctrl: intel: implement gpio_irq_enable") was
> added because clearing interrupt status bit is required to avoid
> unexpected behavior.
>
> Turns out the unmask callback also needs the fix, which can solve
On Tue, Apr 30, 2019 at 11:41:50AM -0500, Pierre-Louis Bossart wrote:
> On 4/30/19 11:30 AM, Andy Shevchenko wrote:
> > On Tue, Apr 30, 2019 at 10:52:29AM -0500, Pierre-Louis Bossart wrote:
> > > When the DSDT tables expose devices with subdevices and a set of
> > > hierarchical _DSD properties,
On Thu, Apr 25, 2019 at 4:42 AM Masahiro Yamada
wrote:
>
> Hi Andy,
>
> On Sat, Jun 21, 2014 at 4:23 AM Andy Lutomirski wrote:
> >
> > With this change, doing 'make vdso_install' and telling gdb:
> >
> > set debug-file-directory /lib/modules/KVER/vdso
> >
> > will enable vdso debugging with
On Tue, Apr 30, 2019 at 10:34:09AM +0200, Peter Zijlstra wrote:
> On Mon, Apr 29, 2019 at 10:14:56PM +0200, Andrea Parri wrote:
> > Hello!
> >
> > A relatively common misuse of these barriers is to apply these to
> > operations which are not read-modify-write operations, such as
> > atomic_set()
On Sat, Apr 27, 2019 at 10:47 PM Mike Rapoport wrote:
>
> On Fri, Apr 26, 2019 at 09:42:23AM +0200, Peter Zijlstra wrote:
> > On Fri, Apr 26, 2019 at 12:45:52AM +0300, Mike Rapoport wrote:
> > > If a system call runs in isolated context, it's accesses to kernel code
> > > and
> > > data will be
On 4/30/19 11:30 AM, Andy Shevchenko wrote:
On Tue, Apr 30, 2019 at 10:52:29AM -0500, Pierre-Louis Bossart wrote:
When the DSDT tables expose devices with subdevices and a set of
hierarchical _DSD properties, the data returned by
acpi_get_next_subnode() is incorrect, with the results suggesting
On Tue, Apr 30, 2019 at 9:06 AM Linus Torvalds
wrote:
>
> On Tue, Apr 30, 2019 at 6:56 AM Peter Zijlstra wrote:
> >
>
> Realistically, I don't think you can hit the problem in practice. The
> only way to hit that incredibly small race of "one instruction, *both*
> NMI and interrupts" is to have
On Tue, Apr 30, 2019 at 10:52:29AM -0500, Pierre-Louis Bossart wrote:
> When the DSDT tables expose devices with subdevices and a set of
> hierarchical _DSD properties, the data returned by
> acpi_get_next_subnode() is incorrect, with the results suggesting a bad
> pointer assignment. The parser
On Tue, Apr 30, 2019 at 5:39 AM Oleg Nesterov wrote:
>
> Yes, but I am wondering if man vfork should clarify what "child terminates"
> actually means. I mean, the child can do clone(CLONE_THREAD) + sys_exit(),
> this will wake the parent thread up before the child process exits or execs.
That
On Tue, Apr 30, 2019 at 6:08 PM Matthew Wilcox wrote:
>
> On Tue, Apr 30, 2019 at 08:42:42AM -0700, Kees Cook wrote:
> > On Tue, Apr 30, 2019 at 3:47 AM Matteo Croce wrote:
> > > On Tue, Apr 30, 2019 at 12:26 AM Matteo Croce wrote:
> > > >
> > > > Add a const int array containing the most
On Tue, Apr 30, 2019 at 9:28 AM Nick Desaulniers
wrote:
>
> On Tue, Apr 30, 2019 at 7:58 AM Phong Tran wrote:
> >
> > Now, make the loop explicit to avoid clang warning.
> >
> > ./include/linux/of.h:238:37: warning: multiple unsequenced modifications
> > to 'cell' [-Wunsequenced]
> >
On 4/30/19 9:54 AM, Vfiinod Koul wrote:
On 30-04-19, 08:38, Pierre-Louis Bossart wrote:
On 4/30/19 3:51 AM, Vinod Koul wrote:
On 15-04-19, 08:09, Pierre-Louis Bossart wrote:
Signed-off-by: Pierre-Louis Bossart
---
drivers/soundwire/Kconfig | 2 +-
On Tue, Apr 30, 2019 at 7:58 AM Phong Tran wrote:
>
> Now, make the loop explicit to avoid clang warning.
>
> ./include/linux/of.h:238:37: warning: multiple unsequenced modifications
> to 'cell' [-Wunsequenced]
> r = (r << 32) | be32_to_cpu(*(cell++));
>
On Tue, Apr 30, 2019 at 9:19 AM Linus Torvalds
wrote:
>
> Of course, if you *don't* need the exact vfork() semantics, clone
> itself actually very much supports a callback model with s separate
> stack. You can basically do this:
>
> - allocate new stack for the child
> - in trivial asm
ndefined reference to `soc_device_register'
> aarch64-linux-gnu-ld: soc-imx8.c:(.init.text+0x130): relocation truncated
> to fit: R_AARCH64_CALL26 against undefined symbol `soc_device_register'
> make: *** [Makefile:1051: vmlinux] Error 1
>
> Signed-off-by: Guido Günther
>
> ---
> This was
On Tue, Apr 30, 2019 at 10:22:23AM -0600, Jens Axboe wrote:
> On 4/30/19 10:20 AM, Mark Rutland wrote:
> > - io_mem_free(ctx->sq_ring);
> > - io_mem_free(ctx->sq_sqes);
> > - io_mem_free(ctx->cq_ring);
> > + if (ctx->sq_ring)
> > + io_mem_free(ctx->sq_ring);
> > + if
Other than verifying pidfd based polling, the tests make sure that
wait semantics are preserved with the pidfd poll. Notably the 2 cases:
1. If a thread group leader exits while threads still there, then no
pidfd poll notifcation should happen.
2. If a non-thread group leader does an execve,
Android low memory killer (LMK) needs to know when a process dies once
it is sent the kill signal. It does so by checking for the existence of
/proc/pid which is both racy and slow. For example, if a PID is reused
between when LMK sends a kill signal and checks for existence of the
PID, since the
Hi Song,
On Tue, 30 Apr 2019 at 08:11, Song Liu wrote:
>
>
>
> > On Apr 29, 2019, at 8:24 AM, Vincent Guittot
> > wrote:
> >
> > Hi Song,
> >
> > On Sun, 28 Apr 2019 at 21:47, Song Liu wrote:
> >>
> >> Hi Morten and Vincent,
> >>
> >>> On Apr 22, 2019, at 6:22 PM, Song Liu wrote:
> >>>
> >>>
201 - 300 of 972 matches
Mail list logo
