On Thursday, October 4, 2018 3:59:33 PM CEST Boris Brezillon wrote:
> On Thu, 04 Oct 2018 15:52:57 +0200
> Janusz Krzysztofik wrote:
>
> > Hi Boris,
> >
> > On Wednesday, October 3, 2018 4:06:34 PM CEST Boris Brezillon wrote:
> > > On Wed, 03 Oct 2018 15:55:25 +0200
> > > Janusz Krzysztofik
On Thursday, October 4, 2018 3:59:33 PM CEST Boris Brezillon wrote:
> On Thu, 04 Oct 2018 15:52:57 +0200
> Janusz Krzysztofik wrote:
>
> > Hi Boris,
> >
> > On Wednesday, October 3, 2018 4:06:34 PM CEST Boris Brezillon wrote:
> > > On Wed, 03 Oct 2018 15:55:25 +0200
> > > Janusz Krzysztofik
On 10/4/2018 3:46 PM, Winkler, Tomas wrote:
On 10/4/2018 1:45 PM, Winkler, Tomas wrote:
-Original Message-
From: Jarkko Sakkinen [mailto:jarkko.sakki...@linux.intel.com]
Sent: Thursday, October 04, 2018 14:35
To: Winkler, Tomas
Cc: Jason Gunthorpe ; Nayna Jain
; Usyskin, Alexander
On 10/4/2018 3:46 PM, Winkler, Tomas wrote:
On 10/4/2018 1:45 PM, Winkler, Tomas wrote:
-Original Message-
From: Jarkko Sakkinen [mailto:jarkko.sakki...@linux.intel.com]
Sent: Thursday, October 04, 2018 14:35
To: Winkler, Tomas
Cc: Jason Gunthorpe ; Nayna Jain
; Usyskin, Alexander
On 2018-10-04 15:46:21 [+0200], Daniel Wagner wrote:
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 6df130a37d41..21f9418d850f 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -42,7 +42,7 @@ config X86
> select ARCH_USE_BUILTIN_BSWAP
> select
On 2018-10-04 15:46:21 [+0200], Daniel Wagner wrote:
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 6df130a37d41..21f9418d850f 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -42,7 +42,7 @@ config X86
> select ARCH_USE_BUILTIN_BSWAP
> select
On 28/09/18 03:32, Coly Li wrote:
On 9/27/18 11:53 PM, Eddie Chapman wrote:
On 27/09/18 16:23, Coly Li wrote:
On 9/27/18 9:45 PM, guoju wrote:
After write SSD completed, bcache schedule journal_write work to
system_wq, that is a public workqueue in system, without WQ_MEM_RECLAIM
flag.
On 28/09/18 03:32, Coly Li wrote:
On 9/27/18 11:53 PM, Eddie Chapman wrote:
On 27/09/18 16:23, Coly Li wrote:
On 9/27/18 9:45 PM, guoju wrote:
After write SSD completed, bcache schedule journal_write work to
system_wq, that is a public workqueue in system, without WQ_MEM_RECLAIM
flag.
There is no user of _TIF_ALLWORK_MASK since commit 21d375b6b34ff
("x86/entry/64: Remove the SYSCALL64 fast path").
Remove unused define _TIF_ALLWORK_MASK.
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/include/asm/thread_info.h | 8
1 file changed, 8 deletions(-)
diff --git
There is no user of _TIF_ALLWORK_MASK since commit 21d375b6b34ff
("x86/entry/64: Remove the SYSCALL64 fast path").
Remove unused define _TIF_ALLWORK_MASK.
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/include/asm/thread_info.h | 8
1 file changed, 8 deletions(-)
diff --git
This is a refurbished series originally started by by Rik van Riel. The
goal is load the FPU registers on return to userland and not on every
context switch. By this optimisation we can:
- avoid loading the registers if the task stays in kernel and does
not return to userland
- make
From: Rik van Riel
While most of a task's FPU state is only needed in user space,
the protection keys need to be in place immediately after a
context switch.
The reason is that any accesses to userspace memory while running
in kernel mode also need to abide by the memory permissions
specified
This is a refurbished series originally started by by Rik van Riel. The
goal is load the FPU registers on return to userland and not on every
context switch. By this optimisation we can:
- avoid loading the registers if the task stays in kernel and does
not return to userland
- make
From: Rik van Riel
While most of a task's FPU state is only needed in user space,
the protection keys need to be in place immediately after a
context switch.
The reason is that any accesses to userspace memory while running
in kernel mode also need to abide by the memory permissions
specified
The variable init_pkru_value isn't used outside of this file.
Make init_pkru_value static.
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/mm/pkeys.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/mm/pkeys.c b/arch/x86/mm/pkeys.c
index 4409ada551c5e..a150984171684 100644
---
Most users of __raw_xsave_addr() use a feature number, shift it to a
mask and then __raw_xsave_addr() shifts it back to the feature number.
Make __raw_xsave_addr() use the feature number as argument.
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/kernel/fpu/xstate.c | 16
The variable init_pkru_value isn't used outside of this file.
Make init_pkru_value static.
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/mm/pkeys.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/mm/pkeys.c b/arch/x86/mm/pkeys.c
index 4409ada551c5e..a150984171684 100644
---
Most users of __raw_xsave_addr() use a feature number, shift it to a
mask and then __raw_xsave_addr() shifts it back to the feature number.
Make __raw_xsave_addr() use the feature number as argument.
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/kernel/fpu/xstate.c | 16
From: Rik van Riel
The fpu->initialized flag should not be changed underneath us. This might be a
fallout during the removal of the LazyFPU support. The FPU is marked
initialized as soon as the state has been set to an initial value. It does not
signal if the CPU's FPU registers are loaded.
The PKRU value is not set for kernel threads because they do not have
the ->initialized value set. As a result the kernel thread has a random
PKRU value set which it inherits from the previous task.
It has been suggested by Paolo Bonzini to set it for kernel threads, too
because it might be a fix.
From: Rik van Riel
The fpu->initialized flag should not be changed underneath us. This might be a
fallout during the removal of the LazyFPU support. The FPU is marked
initialized as soon as the state has been set to an initial value. It does not
signal if the CPU's FPU registers are loaded.
The PKRU value is not set for kernel threads because they do not have
the ->initialized value set. As a result the kernel thread has a random
PKRU value set which it inherits from the previous task.
It has been suggested by Paolo Bonzini to set it for kernel threads, too
because it might be a fix.
Add TIF_LOAD_FPU. This is reserved for loading the FPU registers before
returning to userpace. This flag must not be set for systems without a
FPU.
It is introduced now, so we can add code handling it now before adding
the main feature.
Signed-off-by: Sebastian Andrzej Siewior
---
From: Rik van Riel
copy_fpstate_to_sigframe() has two callers and both invoke the function only if
fpu->initialized is set. So the check in the function for ->initialized makes
no sense. It might be a relict from the lazy-FPU time: If the FPU registers
were "loaded" then we could save them
Add TIF_LOAD_FPU. This is reserved for loading the FPU registers before
returning to userpace. This flag must not be set for systems without a
FPU.
It is introduced now, so we can add code handling it now before adding
the main feature.
Signed-off-by: Sebastian Andrzej Siewior
---
From: Rik van Riel
copy_fpstate_to_sigframe() has two callers and both invoke the function only if
fpu->initialized is set. So the check in the function for ->initialized makes
no sense. It might be a relict from the lazy-FPU time: If the FPU registers
were "loaded" then we could save them
From: Rik van Riel
If TIF_LOAD_FPU is set, then the registers are saved (not loaded). In that case
we skip the saving part.
Signed-off-by: Rik van Riel
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/kernel/fpu/signal.c | 16 ++--
1 file changed, 10 insertions(+), 6
From: Rik van Riel
If TIF_LOAD_FPU is set, then the registers are saved (not loaded). In that case
we skip the saving part.
Signed-off-by: Rik van Riel
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/kernel/fpu/signal.c | 16 ++--
1 file changed, 10 insertions(+), 6
From: Rik van Riel
Defer loading of FPU state until return to userspace. This gives
the kernel the potential to skip loading FPU state for tasks that
stay in kernel mode, or for tasks that end up with repeated
invocations of kernel_fpu_begin.
It also increases the chances that a task's FPU
From: Rik van Riel
Defer loading of FPU state until return to userspace. This gives
the kernel the potential to skip loading FPU state for tasks that
stay in kernel mode, or for tasks that end up with repeated
invocations of kernel_fpu_begin.
It also increases the chances that a task's FPU
From: Rik van Riel
Add helper function that ensures the floating point registers for
the current task are active. Use with preemption disabled.
Signed-off-by: Rik van Riel
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/include/asm/fpu/internal.h | 27 ++-
1
v4.4.148-rt166-rc1 stable review patch.
If anyone has any objections, please let me know.
---
Sebastian writes:
"""
We reproducibly observe cache line starvation on a Core2Duo E6850 (2
cores), a i5-6400 SKL (4 cores) and on a NXP LS2044A ARM Cortex-A72 (4
cores).
The problem can be
From: Rik van Riel
Add helper function that ensures the floating point registers for
the current task are active. Use with preemption disabled.
Signed-off-by: Rik van Riel
Signed-off-by: Sebastian Andrzej Siewior
---
arch/x86/include/asm/fpu/internal.h | 27 ++-
1
v4.4.148-rt166-rc1 stable review patch.
If anyone has any objections, please let me know.
---
Sebastian writes:
"""
We reproducibly observe cache line starvation on a Core2Duo E6850 (2
cores), a i5-6400 SKL (4 cores) and on a NXP LS2044A ARM Cortex-A72 (4
cores).
The problem can be
From: Colin Ian King
The const array addr_list can be made static, saves populating it on
the stack and will make it read-only.
Signed-off-by: Colin Ian King
---
drivers/media/pci/ivtv/ivtv-i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Colin Ian King
The const array addr_list can be made static, saves populating it on
the stack and will make it read-only.
Signed-off-by: Colin Ian King
---
drivers/media/pci/ivtv/ivtv-i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Thu, 4 Oct 2018 15:01:09 +0200
Ricardo Ribalda Delgado wrote:
> Add documentation for gpio-addr-flash. This binding allow creating
> flash devices that are paged using GPIOs.
>
> Cc: devicet...@vger.kernel.org
> Reviewed-by: Rob Herring
> Signed-off-by: Ricardo Ribalda Delgado
> ---
>
On Thu, 4 Oct 2018 15:01:09 +0200
Ricardo Ribalda Delgado wrote:
> Add documentation for gpio-addr-flash. This binding allow creating
> flash devices that are paged using GPIOs.
>
> Cc: devicet...@vger.kernel.org
> Reviewed-by: Rob Herring
> Signed-off-by: Ricardo Ribalda Delgado
> ---
>
On Thu, 04 Oct 2018 15:52:57 +0200
Janusz Krzysztofik wrote:
> Hi Boris,
>
> On Wednesday, October 3, 2018 4:06:34 PM CEST Boris Brezillon wrote:
> > On Wed, 03 Oct 2018 15:55:25 +0200
> > Janusz Krzysztofik wrote:
> >
> > > > >
> > > > > Implementation of NAND_OP_WAITRDY_INSTR has been
On Thu, 04 Oct 2018 15:52:57 +0200
Janusz Krzysztofik wrote:
> Hi Boris,
>
> On Wednesday, October 3, 2018 4:06:34 PM CEST Boris Brezillon wrote:
> > On Wed, 03 Oct 2018 15:55:25 +0200
> > Janusz Krzysztofik wrote:
> >
> > > > >
> > > > > Implementation of NAND_OP_WAITRDY_INSTR has been
> On 4 October 2018 at 11:08, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > If __device_suspend() returns early on an error or pending wakeup
> > and the power.direct_complete flag has been set for the device
> > already, the subsequent device_resume() will be confused by it
> >
> On 4 October 2018 at 11:08, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > If __device_suspend() returns early on an error or pending wakeup
> > and the power.direct_complete flag has been set for the device
> > already, the subsequent device_resume() will be confused by it
> >
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 201510 ("Missing break in switch")
Signed-off-by: Gustavo A. R. Silva
---
drivers/power/supply/max8925_power.c | 1 +
1 file changed, 1 insertion(+)
diff --git
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 201510 ("Missing break in switch")
Signed-off-by: Gustavo A. R. Silva
---
drivers/power/supply/max8925_power.c | 1 +
1 file changed, 1 insertion(+)
diff --git
v4.4.148-rt166-rc1 stable review patch.
If anyone has any objections, please let me know.
---
Signed-off-by: Daniel Wagner
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 2c9cfa2ea86c..f3735ed9a3c0 100644
v4.4.148-rt166-rc1 stable review patch.
If anyone has any objections, please let me know.
---
Signed-off-by: Daniel Wagner
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 2c9cfa2ea86c..f3735ed9a3c0 100644
On Thu, Oct 04, 2018 at 01:32:13PM +0200, Linus Walleij wrote:
> On Thu, Oct 4, 2018 at 12:50 PM Mark Brown wrote:
> > On Thu, Oct 04, 2018 at 11:06:54AM +0200, Linus Walleij wrote:
> > > Optional properties:
> > > -- gpio: gpio to use for enable control
> > > +- gpios: gpio to use for enable
On Thu, Oct 04, 2018 at 01:32:13PM +0200, Linus Walleij wrote:
> On Thu, Oct 4, 2018 at 12:50 PM Mark Brown wrote:
> > On Thu, Oct 04, 2018 at 11:06:54AM +0200, Linus Walleij wrote:
> > > Optional properties:
> > > -- gpio: gpio to use for enable control
> > > +- gpios: gpio to use for enable
Hi Boris,
On Wednesday, October 3, 2018 4:06:34 PM CEST Boris Brezillon wrote:
> On Wed, 03 Oct 2018 15:55:25 +0200
> Janusz Krzysztofik wrote:
>
> > > >
> > > > Implementation of NAND_OP_WAITRDY_INSTR has been based on legacy
> > > > nand_wait_ready(),
> > >
> > > I don't remember what
Hi Boris,
On Wednesday, October 3, 2018 4:06:34 PM CEST Boris Brezillon wrote:
> On Wed, 03 Oct 2018 15:55:25 +0200
> Janusz Krzysztofik wrote:
>
> > > >
> > > > Implementation of NAND_OP_WAITRDY_INSTR has been based on legacy
> > > > nand_wait_ready(),
> > >
> > > I don't remember what
On 9/7/18 5:34 AM, Jirka Hladky wrote:
> We would also be more than happy to test the new patches for the
> performance - please let us know if you are interested. We have a
> pool of 1 NUMA up to 8 NUMA boxes for that, both AMD and Intel,
> covering different CPU generations from Sandy Bridge
On 9/7/18 5:34 AM, Jirka Hladky wrote:
> We would also be more than happy to test the new patches for the
> performance - please let us know if you are interested. We have a
> pool of 1 NUMA up to 8 NUMA boxes for that, both AMD and Intel,
> covering different CPU generations from Sandy Bridge
On 10/4/18 2:53 PM, Alexandre Belloni wrote:
> Hi,
>
> On 04/10/2018 14:35:28+0200, Gustavo A. R. Silva wrote:
>> Replace "Fall" with a proper "Fall through" annotation.
>>
>> This fix is part of the ongoing efforts to enabling
>> -Wimplicit-fallthrough
>>
>
> Can we agree that this is
On 10/4/18 2:53 PM, Alexandre Belloni wrote:
> Hi,
>
> On 04/10/2018 14:35:28+0200, Gustavo A. R. Silva wrote:
>> Replace "Fall" with a proper "Fall through" annotation.
>>
>> This fix is part of the ongoing efforts to enabling
>> -Wimplicit-fallthrough
>>
>
> Can we agree that this is
Hi,
* Ulf Hansson [181003 14:43]:
> + * GENPD_FLAG_IRQ_SAFE: This informs genpd that its backend
> callbacks,
> + * ->power_on|off(), doesn't sleep. Hence, these
> + * can be invoked from within atomic context, which
> + *
Hi,
* Ulf Hansson [181003 14:43]:
> + * GENPD_FLAG_IRQ_SAFE: This informs genpd that its backend
> callbacks,
> + * ->power_on|off(), doesn't sleep. Hence, these
> + * can be invoked from within atomic context, which
> + *
Remove one include of .
No functional changes.
Signed-off-by: Michael Schupikov
---
kernel/sysctl.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index cc02050fd0c4..523cb36b72eb 100644
--- a/kernel/sysctl.c
+++ b/kernel/sysctl.c
@@ -66,7 +66,6 @@
Remove one include of .
No functional changes.
Signed-off-by: Michael Schupikov
---
kernel/sysctl.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index cc02050fd0c4..523cb36b72eb 100644
--- a/kernel/sysctl.c
+++ b/kernel/sysctl.c
@@ -66,7 +66,6 @@
On Thu, Oct 04, 2018 at 06:34:49PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20181003:
>
> The bpf-next tree still had its build failure so I used the version
> from next-20181002.
>
> The kvm-arm tree gained conflicts against the arm64 tree.
>
> The tty tree gained a build
On Thu, Oct 04, 2018 at 06:34:49PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20181003:
>
> The bpf-next tree still had its build failure so I used the version
> from next-20181002.
>
> The kvm-arm tree gained conflicts against the arm64 tree.
>
> The tty tree gained a build
>
> On 10/4/2018 1:45 PM, Winkler, Tomas wrote:
> >
> >
> >> -Original Message-
> >> From: Jarkko Sakkinen [mailto:jarkko.sakki...@linux.intel.com]
> >> Sent: Thursday, October 04, 2018 14:35
> >> To: Winkler, Tomas
> >> Cc: Jason Gunthorpe ; Nayna Jain
> >> ; Usyskin, Alexander
> >> ;
>
> On 10/4/2018 1:45 PM, Winkler, Tomas wrote:
> >
> >
> >> -Original Message-
> >> From: Jarkko Sakkinen [mailto:jarkko.sakki...@linux.intel.com]
> >> Sent: Thursday, October 04, 2018 14:35
> >> To: Winkler, Tomas
> >> Cc: Jason Gunthorpe ; Nayna Jain
> >> ; Usyskin, Alexander
> >> ;
Glink transport support signals to exchange state notification between
local and remote side clients. Adding support to send/receive the signal
command and notify the clients through callback and POLL notification.
Changes since v1:
- Split the patches as per functional areas like core, char,
On 10/04/2018 03:16 AM, Jan Kara wrote:
> On Wed 12-09-18 15:28:52, Waiman Long wrote:
>> From: Davidlohr Bueso
>>
>> Instead of the current O(N) implementation, at the cost
>> of adding an atomic counter, we can convert the call to
>> an atomic_read(). The counter only serves for accounting
>>
Glink transport support signals to exchange state notification between
local and remote side clients. Adding support to send/receive the signal
command and notify the clients through callback and POLL notification.
Changes since v1:
- Split the patches as per functional areas like core, char,
On 10/04/2018 03:16 AM, Jan Kara wrote:
> On Wed 12-09-18 15:28:52, Waiman Long wrote:
>> From: Davidlohr Bueso
>>
>> Instead of the current O(N) implementation, at the cost
>> of adding an atomic counter, we can convert the call to
>> an atomic_read(). The counter only serves for accounting
>>
Add TICOMGET and TIOCMSET ioctl support for rpmsg char device nodes
to get/set the low level transport signals.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_char.c | 54 +++---
1 file changed, 51 insertions(+), 3 deletions(-)
diff --git
Add TICOMGET and TIOCMSET ioctl support for rpmsg char device nodes
to get/set the low level transport signals.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_char.c | 54 +++---
1 file changed, 51 insertions(+), 3 deletions(-)
diff --git
During probe, if there was an error the memory region and the memory
map were not properly released.This can lead a system unusable if
deferred probe is in use.
Replace mem_request and map with devm_ioremap_resource
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/mtd/maps/physmap_of_core.c
During probe, if there was an error the memory region and the memory
map were not properly released.This can lead a system unusable if
deferred probe is in use.
Replace mem_request and map with devm_ioremap_resource
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/mtd/maps/physmap_of_core.c
Remote peripherals send signal notifications over glink with commandID 15.
Add support to send and receive the signal command and convert the signals
from NATIVE to TIOCM while receiving and vice versa while sending.
Signed-off-by: Chris Lew
Signed-off-by: Arun Kumar Neelakantam
---
From: Colin Ian King
The const array rsc_ids can be made static, saves populating it on
the stack and will make it read-only.
Signed-off-by: Colin Ian King
---
drivers/pinctrl/sirf/pinctrl-sirf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Register a callback to get the signal notifications from rpmsg and
send POLLPRI mask to indicate the signal change in POLL system call.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_char.c | 21 +
1 file changed, 21 insertions(+)
diff --git
Some transports like Glink support the state notifications between
clients using signals similar to serial protocol signals.
Signed-off-by: Chris Lew
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_core.c | 42 ++
Remote peripherals send signal notifications over glink with commandID 15.
Add support to send and receive the signal command and convert the signals
from NATIVE to TIOCM while receiving and vice versa while sending.
Signed-off-by: Chris Lew
Signed-off-by: Arun Kumar Neelakantam
---
From: Colin Ian King
The const array rsc_ids can be made static, saves populating it on
the stack and will make it read-only.
Signed-off-by: Colin Ian King
---
drivers/pinctrl/sirf/pinctrl-sirf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Register a callback to get the signal notifications from rpmsg and
send POLLPRI mask to indicate the signal change in POLL system call.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_char.c | 21 +
1 file changed, 21 insertions(+)
diff --git
Some transports like Glink support the state notifications between
clients using signals similar to serial protocol signals.
Signed-off-by: Chris Lew
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_core.c | 42 ++
On Thu, Oct 4, 2018 at 10:42 AM Helge Deller wrote:
> On 04.10.2018 01:02, gregkh wrote:
> > On Wed, Oct 03, 2018 at 09:49:08PM +0200, Arnd Bergmann wrote:
> >> On Wed, Oct 3, 2018 at 8:16 PM Greg Kroah-Hartman
> >> wrote:
> >>> On Wed, Oct 03, 2018 at 04:47:30PM +0200, Helge Deller wrote:
>
On Thu, Oct 4, 2018 at 10:42 AM Helge Deller wrote:
> On 04.10.2018 01:02, gregkh wrote:
> > On Wed, Oct 03, 2018 at 09:49:08PM +0200, Arnd Bergmann wrote:
> >> On Wed, Oct 3, 2018 at 8:16 PM Greg Kroah-Hartman
> >> wrote:
> >>> On Wed, Oct 03, 2018 at 04:47:30PM +0200, Helge Deller wrote:
>
Am Donnerstag, den 04.10.2018, 15:25 +0200 schrieb Philipp Zabel:
> On Thu, 2018-10-04 at 13:20 +, Leonard Crestez wrote:
> > On Thu, 2018-10-04 at 10:59 +0200, Lucas Stach wrote:
> > > Am Montag, den 01.10.2018, 22:53 +0300 schrieb Leonard Crestez:
> > > > When the root complex suspends it
Am Donnerstag, den 04.10.2018, 15:25 +0200 schrieb Philipp Zabel:
> On Thu, 2018-10-04 at 13:20 +, Leonard Crestez wrote:
> > On Thu, 2018-10-04 at 10:59 +0200, Lucas Stach wrote:
> > > Am Montag, den 01.10.2018, 22:53 +0300 schrieb Leonard Crestez:
> > > > When the root complex suspends it
Allow creating gpio-addr-flash via device-tree and not just via platform
data.
Mimic what physmap_of_versatile and physmap_of_gemini does to reduce
code duplicity.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/mtd/maps/Kconfig | 8 +++
drivers/mtd/maps/Makefile | 3 +-
Allow creating gpio-addr-flash via device-tree and not just via platform
data.
Mimic what physmap_of_versatile and physmap_of_gemini does to reduce
code duplicity.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/mtd/maps/Kconfig | 8 +++
drivers/mtd/maps/Makefile | 3 +-
During probe, if there was an error the memory region and the memory
map were not properly released.This can lead a system unusable if
deferred probe is in use.
Replace mem_request and map with devm_ioremap_resource
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/mtd/maps/physmap_of_core.c
During probe, if there was an error the memory region and the memory
map were not properly released.This can lead a system unusable if
deferred probe is in use.
Replace mem_request and map with devm_ioremap_resource
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/mtd/maps/physmap_of_core.c
On 9/7/18 5:39 PM, Jan H. Schönherr wrote:
> The collective context switch from one coscheduled set of tasks to another
> -- while fast -- is not atomic. If a use-case needs the absolute guarantee
> that all tasks of the previous set have stopped executing before any task
> of the next set starts
On 9/7/18 5:39 PM, Jan H. Schönherr wrote:
> The collective context switch from one coscheduled set of tasks to another
> -- while fast -- is not atomic. If a use-case needs the absolute guarantee
> that all tasks of the previous set have stopped executing before any task
> of the next set starts
Jacek
On 10/03/2018 03:46 PM, Jacek Anaszewski wrote:
> On 10/03/2018 03:01 PM, Pavel Machek wrote:
>> On Wed 2018-10-03 07:24:23, Dan Murphy wrote:
>>> Hello
>>>
>>> On 10/02/2018 02:28 AM, Pavel Machek wrote:
On Fri 2018-09-28 13:29:47, Dan Murphy wrote:
> Remove support for the LM3697
Jacek
On 10/03/2018 03:46 PM, Jacek Anaszewski wrote:
> On 10/03/2018 03:01 PM, Pavel Machek wrote:
>> On Wed 2018-10-03 07:24:23, Dan Murphy wrote:
>>> Hello
>>>
>>> On 10/02/2018 02:28 AM, Pavel Machek wrote:
On Fri 2018-09-28 13:29:47, Dan Murphy wrote:
> Remove support for the LM3697
On Thu, 2018-10-04 at 13:20 +, Leonard Crestez wrote:
> On Thu, 2018-10-04 at 10:59 +0200, Lucas Stach wrote:
> > Am Montag, den 01.10.2018, 22:53 +0300 schrieb Leonard Crestez:
> > > When the root complex suspends it must send a PME_Turn_Off TLP.
> > > Implement this by asserting the
On Thu, 2018-10-04 at 13:20 +, Leonard Crestez wrote:
> On Thu, 2018-10-04 at 10:59 +0200, Lucas Stach wrote:
> > Am Montag, den 01.10.2018, 22:53 +0300 schrieb Leonard Crestez:
> > > When the root complex suspends it must send a PME_Turn_Off TLP.
> > > Implement this by asserting the
On 4 October 2018 at 11:08, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> If __device_suspend() returns early on an error or pending wakeup
> and the power.direct_complete flag has been set for the device
> already, the subsequent device_resume() will be confused by it
> and it will
On 4 October 2018 at 11:08, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> If __device_suspend() returns early on an error or pending wakeup
> and the power.direct_complete flag has been set for the device
> already, the subsequent device_resume() will be confused by it
> and it will
On Thu, 2018-10-04 at 10:59 +0200, Lucas Stach wrote:
> Am Montag, den 01.10.2018, 22:53 +0300 schrieb Leonard Crestez:
> > When the root complex suspends it must send a PME_Turn_Off TLP.
> > Implement this by asserting the "turnoff" reset.
> >
> > +static void imx6_pcie_pm_turnoff(struct
On Thu, 2018-10-04 at 10:59 +0200, Lucas Stach wrote:
> Am Montag, den 01.10.2018, 22:53 +0300 schrieb Leonard Crestez:
> > When the root complex suspends it must send a PME_Turn_Off TLP.
> > Implement this by asserting the "turnoff" reset.
> >
> > +static void imx6_pcie_pm_turnoff(struct
On 9/22/2018 1:36 AM, Evan Green wrote:
On Fri, Sep 21, 2018 at 3:32 AM Veerabhadrarao Badiganti
wrote:
Hi Evan,
On 9/21/2018 5:45 AM, Evan Green wrote:
On Wed, Sep 19, 2018 at 11:24 PM Veerabhadrarao Badiganti
wrote:
From: Vijay Viswanath
The load a particular sdhc controller should
On 9/22/2018 1:36 AM, Evan Green wrote:
On Fri, Sep 21, 2018 at 3:32 AM Veerabhadrarao Badiganti
wrote:
Hi Evan,
On 9/21/2018 5:45 AM, Evan Green wrote:
On Wed, Sep 19, 2018 at 11:24 PM Veerabhadrarao Badiganti
wrote:
From: Vijay Viswanath
The load a particular sdhc controller should
On Thu, 4 Oct 2018 15:01:02 +0200
Ricardo Ribalda Delgado wrote:
> This struct does not seem to be used anywhere on the code
>
> Signed-off-by: Ricardo Ribalda Delgado
Already queued that one.
> ---
> drivers/mtd/maps/physmap_of_gemini.c | 5 -
> 1 file changed, 5 deletions(-)
>
>
Changes for v4:
-Updated bindings for lx2160a clockgen and dcfg
-Modified commit message for lx2160a clockgen changes
-Updated interrupt property with macro definition
-Added required enable-method property to each core node with psci value
-Removed unused node syscon in device tree
-Removed blank
701 - 800 of 1300 matches
Mail list logo
