On Tue, 24 Jul 2018 at 19:11, Shuah Khan wrote:
>
> On 07/23/2018 02:49 PM, Anders Roxell wrote:
> > On Thu, 7 Jun 2018 at 13:09, Anders Roxell wrote:
> >>
> >> If the kernel headers aren't installed we can't build all the tests.
> >> Add a new make target rule 'khdr' in the file lib.mk to
On Tue, 24 Jul 2018 at 19:11, Shuah Khan wrote:
>
> On 07/23/2018 02:49 PM, Anders Roxell wrote:
> > On Thu, 7 Jun 2018 at 13:09, Anders Roxell wrote:
> >>
> >> If the kernel headers aren't installed we can't build all the tests.
> >> Add a new make target rule 'khdr' in the file lib.mk to
On Tue, Jul 24, 2018 at 04:04:48PM +0100, Will Deacon wrote:
> On Mon, Jul 23, 2018 at 12:27:35PM -0400, Johannes Weiner wrote:
> > On Mon, Jul 23, 2018 at 05:35:35PM +0200, Arnd Bergmann wrote:
> > > On Mon, Jul 23, 2018 at 5:23 PM, Johannes Weiner
> > > wrote:
> > > > diff --git
On Tue, Jul 24, 2018 at 04:04:48PM +0100, Will Deacon wrote:
> On Mon, Jul 23, 2018 at 12:27:35PM -0400, Johannes Weiner wrote:
> > On Mon, Jul 23, 2018 at 05:35:35PM +0200, Arnd Bergmann wrote:
> > > On Mon, Jul 23, 2018 at 5:23 PM, Johannes Weiner
> > > wrote:
> > > > diff --git
On 07/23, Eric W. Biederman wrote:
>
> signal: Add calculate_sigpending()
> fork: Have new threads join on-going signal group stops
> signal: Don't restart fork when signals come in.
Oh, I need to re-read these patches tomorrow. I have some concerns, but perhaps
I am wrong. Will
On 07/23, Eric W. Biederman wrote:
>
> signal: Add calculate_sigpending()
> fork: Have new threads join on-going signal group stops
> signal: Don't restart fork when signals come in.
Oh, I need to re-read these patches tomorrow. I have some concerns, but perhaps
I am wrong. Will
On Wed, Jul 18, 2018 at 01:57:09PM +0800, Jisheng Zhang wrote:
> Add as370 to existing berlin pinctrl device tree binding.
>
> Signed-off-by: Jisheng Zhang
> ---
> Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
On Wed, Jul 18, 2018 at 01:57:09PM +0800, Jisheng Zhang wrote:
> Add as370 to existing berlin pinctrl device tree binding.
>
> Signed-off-by: Jisheng Zhang
> ---
> Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
On Tue, Jul 17, 2018 at 08:16:26PM +0200, Paweł Chmiel wrote:
> Document new optional voltage regulators, which can be used
> to power down/up touchscreen.
>
> Signed-off-by: Paweł Chmiel
> ---
> Documentation/devicetree/bindings/input/atmel,maxtouch.txt | 8
> 1 file changed, 8
On Tue, Jul 17, 2018 at 08:16:26PM +0200, Paweł Chmiel wrote:
> Document new optional voltage regulators, which can be used
> to power down/up touchscreen.
>
> Signed-off-by: Paweł Chmiel
> ---
> Documentation/devicetree/bindings/input/atmel,maxtouch.txt | 8
> 1 file changed, 8
Murilo Opsfelder Araujo a écrit :
Move show_instructions() declaration to arch/powerpc/include/asm/stacktrace.h
and include asm/stracktrace.h in arch/powerpc/kernel/process.c,
which contains
the implementation.
Modify show_instructions() not to call __kernel_text_address(), allowing
On Tue, Jul 17, 2018 at 04:41:55AM -0400, Brian Masney wrote:
> Remove the tsl2772 driver from trivial-devices.txt. A separate
> patch added the binding information to the file
> Documentation/devicetree/bindings/iio/light/tsl2772.txt.
>
> Signed-off-by: Brian Masney
> ---
>
Murilo Opsfelder Araujo a écrit :
Move show_instructions() declaration to arch/powerpc/include/asm/stacktrace.h
and include asm/stracktrace.h in arch/powerpc/kernel/process.c,
which contains
the implementation.
Modify show_instructions() not to call __kernel_text_address(), allowing
On Tue, Jul 17, 2018 at 04:41:55AM -0400, Brian Masney wrote:
> Remove the tsl2772 driver from trivial-devices.txt. A separate
> patch added the binding information to the file
> Documentation/devicetree/bindings/iio/light/tsl2772.txt.
>
> Signed-off-by: Brian Masney
> ---
>
On Tue, Jul 24, 2018 at 10:45:12AM -0700, Douglas Anderson wrote:
> These clocks will need to be defined in the clock driver and
> referenced in device tree files.
>
> Signed-off-by: Douglas Anderson
> ---
>
> Changes in v3: None
> Changes in v2: None
>
>
Hi Steve,
On 7/24/2018 4:30 PM, Steven Rostedt wrote:
On Tue, 24 Jul 2018 16:49:59 -0400
Steven Rostedt wrote:
Hmm it seems we should review the register_trigger() implementation.
It should return the return value of trace_event_trigger_enable_disable(),
shouldn't it?
Yeah, that's not
On Tue, Jul 24, 2018 at 10:45:12AM -0700, Douglas Anderson wrote:
> These clocks will need to be defined in the clock driver and
> referenced in device tree files.
>
> Signed-off-by: Douglas Anderson
> ---
>
> Changes in v3: None
> Changes in v2: None
>
>
Hi Steve,
On 7/24/2018 4:30 PM, Steven Rostedt wrote:
On Tue, 24 Jul 2018 16:49:59 -0400
Steven Rostedt wrote:
Hmm it seems we should review the register_trigger() implementation.
It should return the return value of trace_event_trigger_enable_disable(),
shouldn't it?
Yeah, that's not
The bindings for s2mps11/s5m8767 clocks driver require a compatible for
clocks node. Parent MFD sec-core driver will also use it when
instantiating children.
The compatible is not needed for proper working because device will be
anyway created by parent MFD device. Add it for correctness.
The bindings for s2mps11/s5m8767 clocks driver require a compatible for
clocks node. Parent MFD sec-core driver will also use it when
instantiating children.
The compatible is not needed for proper working because device will be
anyway created by parent MFD device. Add it for correctness.
The bindings for s2mps11/s5m8767 clocks driver require a compatible for
clocks node. Parent MFD sec-core driver will also use it when
instantiating children.
The compatible is not needed for proper working because device will be
anyway created by parent MFD device. Add it for correctness.
When driver is built as module and DT node contains clocks compatible
(e.g. "samsung,s2mps11-clk"), the module will not be autoloaded because
module aliases won't match.
The modalias from uevent: of:NclocksTCsamsung,s2mps11-clk
The modalias from driver: platform:s2mps11-clk
The devices are
The bindings for s2mps11/s5m8767 clocks driver require a compatible for
clocks node. Parent MFD sec-core driver will also use it when
instantiating children.
The compatible is not needed for proper working because device will be
anyway created by parent MFD device. Add it for correctness.
When driver is built as module and DT node contains clocks compatible
(e.g. "samsung,s2mps11-clk"), the module will not be autoloaded because
module aliases won't match.
The modalias from uevent: of:NclocksTCsamsung,s2mps11-clk
The modalias from driver: platform:s2mps11-clk
The devices are
Hi,
The DTS patches depend on 1st clock patch. I will take them through
samsung-soc tree in next release.
Best regards,
Krzysztof
Krzysztof Kozlowski (3):
clk: s2mps11: Fix matching when built as module and DT node contains
compatible
ARM: dts: exynos: Add compatible for s2mps11
Hi,
The DTS patches depend on 1st clock patch. I will take them through
samsung-soc tree in next release.
Best regards,
Krzysztof
Krzysztof Kozlowski (3):
clk: s2mps11: Fix matching when built as module and DT node contains
compatible
ARM: dts: exynos: Add compatible for s2mps11
+++ Martijn Coenen [24/07/18 09:56 +0200]:
I did find an issue with my approach:
On Mon, Jul 16, 2018 at 2:21 PM, Martijn Coenen wrote:
The ELF symbols are renamed to include the namespace with an asm label;
for example, symbol 'usb_stor_suspend' in namespace USB_STORAGE becomes
+++ Martijn Coenen [24/07/18 09:56 +0200]:
I did find an issue with my approach:
On Mon, Jul 16, 2018 at 2:21 PM, Martijn Coenen wrote:
The ELF symbols are renamed to include the namespace with an asm label;
for example, symbol 'usb_stor_suspend' in namespace USB_STORAGE becomes
On Wed, Jul 25, 2018 at 02:45:12PM +0100, Will Deacon wrote:
> arch/arm/ defines a SIGMINSTKSZ of 2k, so we should use the same value
> for compat tasks.
>
> Cc: Arnd Bergmann
> Cc: Dominik Brodowski
> Cc: "Eric W. Biederman"
> Cc: Andrew Morton
> Cc: Al Viro
> Cc: Oleg Nesterov
>
On Wed, Jul 25, 2018 at 02:45:12PM +0100, Will Deacon wrote:
> arch/arm/ defines a SIGMINSTKSZ of 2k, so we should use the same value
> for compat tasks.
>
> Cc: Arnd Bergmann
> Cc: Dominik Brodowski
> Cc: "Eric W. Biederman"
> Cc: Andrew Morton
> Cc: Al Viro
> Cc: Oleg Nesterov
>
On 07/24/2018 11:44 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180724:
>
on i386:
net/ipv4/netfilter/nft_chain_nat_ipv4.o: In function `nft_nat_do_chain':
nft_chain_nat_ipv4.c:(.text+0x67): undefined reference to `nft_do_chain'
net/ipv4/netfilter/nft_chain_nat_ipv4.o: In
On 07/24/2018 11:44 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180724:
>
on i386:
net/ipv4/netfilter/nft_chain_nat_ipv4.o: In function `nft_nat_do_chain':
nft_chain_nat_ipv4.c:(.text+0x67): undefined reference to `nft_do_chain'
net/ipv4/netfilter/nft_chain_nat_ipv4.o: In
On Wed, Jul 25, 2018 at 02:45:11PM +0100, Will Deacon wrote:
> The sigaltstack(2) system call fails with -ENOMEM if the new alternative
> signal stack is found to be smaller than SIGMINSTKSZ. On architectures
> such as arm64, where the native value for SIGMINSTKSZ is larger than
> the compat
On Wed, Jul 25, 2018 at 02:45:11PM +0100, Will Deacon wrote:
> The sigaltstack(2) system call fails with -ENOMEM if the new alternative
> signal stack is found to be smaller than SIGMINSTKSZ. On architectures
> such as arm64, where the native value for SIGMINSTKSZ is larger than
> the compat
In case of Device Tree platforms, even though the Samsung PMIC sec
device is instantiated from DT, the driver is still matched through I2C
module alias. That is because I2C core always reports an I2C module
alias instead of DT one.
This could change in the future so export DT module alias.
In case of Device Tree platforms, even though the Samsung PMIC sec
device is instantiated from DT, the driver is still matched through I2C
module alias. That is because I2C core always reports an I2C module
alias instead of DT one.
This could change in the future so export DT module alias.
On 2018-07-03 11:19, Jarkko Sakkinen wrote:
+/* IOCTL return values */
+#define SGX_POWER_LOST_ENCLAVE 0x4000
+#define SGX_LE_ROLLBACK0x4001
I don't think SGX_LE_ROLLBACK is used anymore.
Jethro Beekman | Fortanix
smime.p7s
Description: S/MIME
On 2018-07-03 11:19, Jarkko Sakkinen wrote:
+/* IOCTL return values */
+#define SGX_POWER_LOST_ENCLAVE 0x4000
+#define SGX_LE_ROLLBACK0x4001
I don't think SGX_LE_ROLLBACK is used anymore.
Jethro Beekman | Fortanix
smime.p7s
Description: S/MIME
>-Original Message-
>From: Andy Shevchenko [mailto:andy.shevche...@gmail.com]
>Sent: Wednesday, July 25, 2018 8:55 PM
>To: Anurag Kumar Vulisha
>Cc: Felipe Balbi ; Greg Kroah-Hartman
>; v.anuragku...@gmail.com; USB u...@vger.kernel.org>; Linux Kernel Mailing List
>Subject: Re: [PATCH
>-Original Message-
>From: Andy Shevchenko [mailto:andy.shevche...@gmail.com]
>Sent: Wednesday, July 25, 2018 8:55 PM
>To: Anurag Kumar Vulisha
>Cc: Felipe Balbi ; Greg Kroah-Hartman
>; v.anuragku...@gmail.com; USB u...@vger.kernel.org>; Linux Kernel Mailing List
>Subject: Re: [PATCH
On 2018/7/25 11:22, Jaegeuk Kim wrote:
> The f2fs_gc() called by f2fs_balance_fs() requires to be called outside of
> fi->i_gc_rwsem[WRITE], since f2fs_gc() can try to grab it in a loop.
It seems there are other paths having the same issue, how about fixing all of
them in this patch?
Thanks,
>
On 2018/7/25 11:22, Jaegeuk Kim wrote:
> The f2fs_gc() called by f2fs_balance_fs() requires to be called outside of
> fi->i_gc_rwsem[WRITE], since f2fs_gc() can try to grab it in a loop.
It seems there are other paths having the same issue, how about fixing all of
them in this patch?
Thanks,
>
Murilo Opsfelder Araujo a écrit :
This adds a human-readable name in the unhandled signal message.
Before this patch, a page fault looked like:
Jul 11 16:04:11 localhost kernel: pandafault[6303]: unhandled
signal 11 at 17d0 nip 161c lr
7fff93c55100 code 2
Murilo Opsfelder Araujo a écrit :
This adds a human-readable name in the unhandled signal message.
Before this patch, a page fault looked like:
Jul 11 16:04:11 localhost kernel: pandafault[6303]: unhandled
signal 11 at 17d0 nip 161c lr
7fff93c55100 code 2
On 2018/7/24 23:19, Yunlong Song wrote:
>
>
> On 2018/7/24 22:17, Chao Yu wrote:
>> On 2018/7/24 21:39, Yunlong Song wrote:
>>>
>>> On 2018/7/24 21:11, Chao Yu wrote:
On 2018/7/23 22:10, Yunlong Song wrote:
> If f2fs aborts BG_GC, then the section bit of victim_secmap will be set,
>
On 7/24/2018 10:39 PM, Ian Kent wrote:
> On Tue, 2018-07-24 at 11:57 -0700, Casey Schaufler wrote:
>> On 7/24/2018 9:00 AM, David Howells wrote:
>>> Casey Schaufler wrote:
>>>
> (1) Mount topology and reconfiguration change events.
With the possibility of unprivileged mounting you're
On 2018/7/24 23:19, Yunlong Song wrote:
>
>
> On 2018/7/24 22:17, Chao Yu wrote:
>> On 2018/7/24 21:39, Yunlong Song wrote:
>>>
>>> On 2018/7/24 21:11, Chao Yu wrote:
On 2018/7/23 22:10, Yunlong Song wrote:
> If f2fs aborts BG_GC, then the section bit of victim_secmap will be set,
>
On 7/24/2018 10:39 PM, Ian Kent wrote:
> On Tue, 2018-07-24 at 11:57 -0700, Casey Schaufler wrote:
>> On 7/24/2018 9:00 AM, David Howells wrote:
>>> Casey Schaufler wrote:
>>>
> (1) Mount topology and reconfiguration change events.
With the possibility of unprivileged mounting you're
From: Joerg Roedel
It is perfectly okay to take page-faults, especially on the
vmalloc area while executing an NMI handler. Remove the
warning.
Signed-off-by: Joerg Roedel
---
arch/x86/mm/fault.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
From: Joerg Roedel
It is perfectly okay to take page-faults, especially on the
vmalloc area while executing an NMI handler. Remove the
warning.
Signed-off-by: Joerg Roedel
---
arch/x86/mm/fault.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
From: Joerg Roedel
Fuzzing the PTI-x86-32 code with trinity showed unhandled
kernel paging request oops-messages that looked a lot like
silent data corruption.
Lot's of debugging and testing lead to the kexec-32bit code,
which is still allocating 4k PGDs when PTI is enabled. But
since it uses
From: Joerg Roedel
Fuzzing the PTI-x86-32 code with trinity showed unhandled
kernel paging request oops-messages that looked a lot like
silent data corruption.
Lot's of debugging and testing lead to the kexec-32bit code,
which is still allocating 4k PGDs when PTI is enabled. But
since it uses
From: Joerg Roedel
This reverts commit 77754cfa09a6c528c38cbca9ee4cc4f7cf6ad6f2.
The patch was necessary to silence a WARN_ON_ONCE(in_nmi())
that triggered in the vmalloc_fault() function when PTI was
enabled on x86-32.
Faulting in an NMI handler turned out to be safe and the
warning in
From: Joerg Roedel
This reverts commit 77754cfa09a6c528c38cbca9ee4cc4f7cf6ad6f2.
The patch was necessary to silence a WARN_ON_ONCE(in_nmi())
that triggered in the vmalloc_fault() function when PTI was
enabled on x86-32.
Faulting in an NMI handler turned out to be safe and the
warning in
Hi,
here are three patches on-top of tip/x86/pti to update the
vmallo_fault() fix and also with another important fix.
The first two patches remove the WARN_ON_ONCE(in_nmi) from
the vmalloc_fault() function and revert the previous fix, as
discussed at the last patch-set.
The third patch is an
Hi,
here are three patches on-top of tip/x86/pti to update the
vmallo_fault() fix and also with another important fix.
The first two patches remove the WARN_ON_ONCE(in_nmi) from
the vmalloc_fault() function and revert the previous fix, as
discussed at the last patch-set.
The third patch is an
On Wed, 25 Jul 2018 08:57:40 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> Running the following:
>
> # cd /sys/kernel/debug/tracing
> # echo 50 > buffer_size_kb
> [ Or some other number that takes up most of memory ]
> # echo snapshot >
On Wed, 25 Jul 2018 08:57:40 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> Running the following:
>
> # cd /sys/kernel/debug/tracing
> # echo 50 > buffer_size_kb
> [ Or some other number that takes up most of memory ]
> # echo snapshot >
On Wed, 25 Jul 2018 10:35:57 -0500
Josh Poimboeuf wrote:
> On Wed, Jul 25, 2018 at 04:20:38PM +0200, Artem Savkov wrote:
> > If enable_trace_kprobe fails to enable the probe in enable_k(ret)probe
> > it returns an error, but does not unset the tp flags it set previously.
> > This results in a
On Wed, 25 Jul 2018 10:35:57 -0500
Josh Poimboeuf wrote:
> On Wed, Jul 25, 2018 at 04:20:38PM +0200, Artem Savkov wrote:
> > If enable_trace_kprobe fails to enable the probe in enable_k(ret)probe
> > it returns an error, but does not unset the tp flags it set previously.
> > This results in a
On Thu, 26 Jul 2018 00:41:13 +0900
Masami Hiramatsu wrote:
> On Wed, 25 Jul 2018 16:20:38 +0200
> Artem Savkov wrote:
>
> > If enable_trace_kprobe fails to enable the probe in enable_k(ret)probe
> > it returns an error, but does not unset the tp flags it set previously.
> > This results in a
On Thu, 26 Jul 2018 00:41:13 +0900
Masami Hiramatsu wrote:
> On Wed, 25 Jul 2018 16:20:38 +0200
> Artem Savkov wrote:
>
> > If enable_trace_kprobe fails to enable the probe in enable_k(ret)probe
> > it returns an error, but does not unset the tp flags it set previously.
> > This results in a
Murilo Opsfelder Araujo a écrit :
Modify logic of show_signal_msg() to return early, if possible. Replace
printk_ratelimited() by printk() and a default rate limit burst to limit
displaying unhandled signals messages.
Can you explain more the benefits of this change ?
Christophe
Murilo Opsfelder Araujo a écrit :
Modify logic of show_signal_msg() to return early, if possible. Replace
printk_ratelimited() by printk() and a default rate limit burst to limit
displaying unhandled signals messages.
Can you explain more the benefits of this change ?
Christophe
On Wed, 25 Jul 2018 16:20:38 +0200
Artem Savkov wrote:
> If enable_trace_kprobe fails to enable the probe in enable_k(ret)probe
> it returns an error, but does not unset the tp flags it set previously.
> This results in a probe being considered enabled and failures like being
> unable to remove
On Wed, 25 Jul 2018 16:20:38 +0200
Artem Savkov wrote:
> If enable_trace_kprobe fails to enable the probe in enable_k(ret)probe
> it returns an error, but does not unset the tp flags it set previously.
> This results in a probe being considered enabled and failures like being
> unable to remove
From: Chao Yu
Like quota_ino feature, we need to reject mounting RDWR with image
which enables project_quota feature when there is no CONFIG_QUOTA
be set in kernel.
Signed-off-by: Chao Yu
---
fs/f2fs/super.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/fs/f2fs/super.c
From: Chao Yu
Like quota_ino feature, we need to reject mounting RDWR with image
which enables project_quota feature when there is no CONFIG_QUOTA
be set in kernel.
Signed-off-by: Chao Yu
---
fs/f2fs/super.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/fs/f2fs/super.c
于 2018年7月25日 GMT+08:00 下午11:31:26, Rob Herring 写到:
>On Sun, Jul 22, 2018 at 02:10:33PM +0800, Chen-Yu Tsai wrote:
>> On Sun, Jul 22, 2018 at 1:57 PM, Icenowy Zheng
>wrote:
>> > The new Allwinner H6 SoC contains a USB3 PHY that is wired to the
>> > external USB3 pins of the SoC.
>> >
>> > Add
于 2018年7月25日 GMT+08:00 下午11:31:26, Rob Herring 写到:
>On Sun, Jul 22, 2018 at 02:10:33PM +0800, Chen-Yu Tsai wrote:
>> On Sun, Jul 22, 2018 at 1:57 PM, Icenowy Zheng
>wrote:
>> > The new Allwinner H6 SoC contains a USB3 PHY that is wired to the
>> > external USB3 pins of the SoC.
>> >
>> > Add
On Wed, Jul 25, 2018 at 04:20:38PM +0200, Artem Savkov wrote:
> If enable_trace_kprobe fails to enable the probe in enable_k(ret)probe
> it returns an error, but does not unset the tp flags it set previously.
> This results in a probe being considered enabled and failures like being
> unable to
On Wed, Jul 25, 2018 at 04:20:38PM +0200, Artem Savkov wrote:
> If enable_trace_kprobe fails to enable the probe in enable_k(ret)probe
> it returns an error, but does not unset the tp flags it set previously.
> This results in a probe being considered enabled and failures like being
> unable to
On Wed, Jul 25, 2018 at 4:12 AM, Appana Durga Kedareswara Rao
wrote:
> Hi Alan,
>
> Thanks for the review...
>
>
>> >
>> >
>> >> > +static bool readback_type;
>> >> > +module_param(readback_type, bool, 0644);
>> >> > +MODULE_PARM_DESC(readback_type,
>> >> > +
On Wed, Jul 25, 2018 at 4:12 AM, Appana Durga Kedareswara Rao
wrote:
> Hi Alan,
>
> Thanks for the review...
>
>
>> >
>> >
>> >> > +static bool readback_type;
>> >> > +module_param(readback_type, bool, 0644);
>> >> > +MODULE_PARM_DESC(readback_type,
>> >> > +
On Wed, 25 Jul 2018 09:21:51 -0400
Steven Rostedt wrote:
>
> [ Adding Masami to Cc ]
>
> On Wed, 25 Jul 2018 12:28:26 +0200
> Artem Savkov wrote:
>
> > If enable_trace_kprobe fails to enable the probe in enable_k(ret)probe
> > it returns an error, but does not unset the tp flags it set
On Wed, 25 Jul 2018 09:21:51 -0400
Steven Rostedt wrote:
>
> [ Adding Masami to Cc ]
>
> On Wed, 25 Jul 2018 12:28:26 +0200
> Artem Savkov wrote:
>
> > If enable_trace_kprobe fails to enable the probe in enable_k(ret)probe
> > it returns an error, but does not unset the tp flags it set
On Tue, Jul 24, 2018 at 09:25:41AM -0400, Peter Geis wrote:
> Added support for the CPCAP power management regulator functions on
> Tegra based Motorola Xoom devices.
> Added sw2_sw4 value tables, which provide power to the Tegra core and
> aux devices.
> Added the Xoom init tables and device tree
On Tue, Jul 24, 2018 at 09:25:41AM -0400, Peter Geis wrote:
> Added support for the CPCAP power management regulator functions on
> Tegra based Motorola Xoom devices.
> Added sw2_sw4 value tables, which provide power to the Tegra core and
> aux devices.
> Added the Xoom init tables and device tree
On Wed, 2018-07-25 at 15:12 +0200, Arnd Bergmann wrote:
> tools/perf/tests/.gitignore:
> LLVM byte-codes, uncompressed
> On Wed, Jul 25, 2018 at 2:55 AM, Andrew Morton
> wrote:
> > On Tue, 24 Jul 2018 17:13:20 -0700 Joe Perches wrote:
> >
> > > On Tue, 2018-07-24 at
On Wed, 2018-07-25 at 15:12 +0200, Arnd Bergmann wrote:
> tools/perf/tests/.gitignore:
> LLVM byte-codes, uncompressed
> On Wed, Jul 25, 2018 at 2:55 AM, Andrew Morton
> wrote:
> > On Tue, 24 Jul 2018 17:13:20 -0700 Joe Perches wrote:
> >
> > > On Tue, 2018-07-24 at
On Mon, Jul 23, 2018 at 09:47:46AM +0200, Marco Felsch wrote:
> This binding is used to keep the backward compatibility with the current
> dtb's [1]. The binding informs the driver that the unused switch regulators
> can be disabled.
> If it is not specified, the driver doesn't disable the switch
On Mon, Jul 23, 2018 at 09:47:46AM +0200, Marco Felsch wrote:
> This binding is used to keep the backward compatibility with the current
> dtb's [1]. The binding informs the driver that the unused switch regulators
> can be disabled.
> If it is not specified, the driver doesn't disable the switch
On Sun, Jul 22, 2018 at 02:10:33PM +0800, Chen-Yu Tsai wrote:
> On Sun, Jul 22, 2018 at 1:57 PM, Icenowy Zheng wrote:
> > The new Allwinner H6 SoC contains a USB3 PHY that is wired to the
> > external USB3 pins of the SoC.
> >
> > Add a device tree binding for the PHY.
> >
> > Signed-off-by:
On Sun, Jul 22, 2018 at 02:10:33PM +0800, Chen-Yu Tsai wrote:
> On Sun, Jul 22, 2018 at 1:57 PM, Icenowy Zheng wrote:
> > The new Allwinner H6 SoC contains a USB3 PHY that is wired to the
> > external USB3 pins of the SoC.
> >
> > Add a device tree binding for the PHY.
> >
> > Signed-off-by:
On (07/25/18 10:22), Gustavo A. R. Silva wrote:
> Currently, code at label *out* is unreachable. Fix this by updating
> variable *ret* with -EINVAL, so the jump to *out* can be properly
> executed instead of directly returning from function.
>
> Addresses-Coverity-ID: 1472059 ("Structurally dead
On (07/25/18 10:22), Gustavo A. R. Silva wrote:
> Currently, code at label *out* is unreachable. Fix this by updating
> variable *ret* with -EINVAL, so the jump to *out* can be properly
> executed instead of directly returning from function.
>
> Addresses-Coverity-ID: 1472059 ("Structurally dead
On Tue, 24 Jul 2018 17:12:13 +0200
Snild Dolkow wrote:
> There is a window for racing when printing directly to task->comm,
> allowing other threads to see a non-terminated string. The vsnprintf
> function fills the buffer, counts the truncated chars, then finally
> writes the \0 at the end.
>
On Tue, 24 Jul 2018 17:12:13 +0200
Snild Dolkow wrote:
> There is a window for racing when printing directly to task->comm,
> allowing other threads to see a non-terminated string. The vsnprintf
> function fills the buffer, counts the truncated chars, then finally
> writes the \0 at the end.
>
There's a long power-on delay at the end of rtsx_usb_ms_set_param().
This delay is noticeable right before system suspend.
To prevent already suspended memstick host from getting powered on by PM
core, use DPM_FLAG_SMART_SUSPEND to avoid the situation.
Signed-off-by: Kai-Heng Feng
---
There's a long power-on delay at the end of rtsx_usb_ms_set_param().
This delay is noticeable right before system suspend.
To prevent already suspended memstick host from getting powered on by PM
core, use DPM_FLAG_SMART_SUSPEND to avoid the situation.
Signed-off-by: Kai-Heng Feng
---
In order to let host's parent device, rtsx_usb, to use USB remote wake
up signaling to do card detection, it needs to be suspended. Hence it's
necessary to add runtime PM support for the memstick host.
To keep memstick host stays suspended when it's not in use, convert the
card detection function
In order to let host's parent device, rtsx_usb, to use USB remote wake
up signaling to do card detection, it needs to be suspended. Hence it's
necessary to add runtime PM support for the memstick host.
To keep memstick host stays suspended when it's not in use, convert the
card detection function
Use ms_dev() helper for consistency.
Signed-off-by: Kai-Heng Feng
---
drivers/memstick/host/rtsx_usb_ms.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/memstick/host/rtsx_usb_ms.c
b/drivers/memstick/host/rtsx_usb_ms.c
index 4f64563df7de..cd12f3d1c088 100644
We can use MEMSTICK_POWER_{ON,OFF} along with pm_runtime_{get,put}
helpers to let memstick host support runtime pm.
There's a small window between memstick_detect_change() and its queued
work, memstick_check(). In this window the rpm count may go down to zero
before the memstick host powers on,
Use ms_dev() helper for consistency.
Signed-off-by: Kai-Heng Feng
---
drivers/memstick/host/rtsx_usb_ms.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/memstick/host/rtsx_usb_ms.c
b/drivers/memstick/host/rtsx_usb_ms.c
index 4f64563df7de..cd12f3d1c088 100644
We can use MEMSTICK_POWER_{ON,OFF} along with pm_runtime_{get,put}
helpers to let memstick host support runtime pm.
There's a small window between memstick_detect_change() and its queued
work, memstick_check(). In this window the rpm count may go down to zero
before the memstick host powers on,
Hi,
This is based on Ulf's work [1] [2].
This patch series can keep rtsx_usb suspended, to save ~0.5W on Intel
platforms and ~1.5W on AMD platforms.
[1] https://patchwork.kernel.org/patch/10440583/
[2] https://patchwork.kernel.org/patch/10445725/
Kai-Heng Feng (5):
misc: rtsx_usb: Use USB
Hi,
This is based on Ulf's work [1] [2].
This patch series can keep rtsx_usb suspended, to save ~0.5W on Intel
platforms and ~1.5W on AMD platforms.
[1] https://patchwork.kernel.org/patch/10440583/
[2] https://patchwork.kernel.org/patch/10445725/
Kai-Heng Feng (5):
misc: rtsx_usb: Use USB
Although rtsx_usb doesn't support card removal detection, card insertion
will resume rtsx_usb by USB remote wakeup signaling.
When rtsx_usb gets resumed, also resumes its child devices,
rtsx_usb_sdmmc and rtsx_usb_ms, to notify them there's a card in its
slot.
Signed-off-by: Kai-Heng Feng
---
Although rtsx_usb doesn't support card removal detection, card insertion
will resume rtsx_usb by USB remote wakeup signaling.
When rtsx_usb gets resumed, also resumes its child devices,
rtsx_usb_sdmmc and rtsx_usb_ms, to notify them there's a card in its
slot.
Signed-off-by: Kai-Heng Feng
---
901 - 1000 of 1900 matches
Mail list logo
