Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

> >And when the filesystem says no because the fs devs don't want to >have to deal with broken apps because app devs learn that "this is a >go fast knob" and data integrity be damned? It's "fsync is slow so I >won't use it" all over again... ... > >And, please keep in mind: many application

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

> >And when the filesystem says no because the fs devs don't want to >have to deal with broken apps because app devs learn that "this is a >go fast knob" and data integrity be damned? It's "fsync is slow so I >won't use it" all over again... ... > >And, please keep in mind: many application

[PATCH 08/11] f2fs: inject ENOSPC failures

This patch injects ENOSPC failures. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 7 +++ fs/f2fs/dir.c| 4 fs/f2fs/f2fs.h | 10 ++ fs/f2fs/node.c | 4 fs/f2fs/super.c | 4 5 files changed, 29 insertions(+) diff

[PATCH 04/11] f2fs: use f2fs_grab_cache_page instead of grab_cache_page

This patch converts grab_cache_page to f2fs_grab_cache_page. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 7 --- fs/f2fs/inline.c | 4 ++-- fs/f2fs/node.c | 8 3 files changed, 10 insertions(+), 9 deletions(-) diff --git

[PATCH 05/11] f2fs: add mount option to select fault injection ratio

This patch adds a mount option to select fault ratio. Signed-off-by: Jaegeuk Kim --- fs/f2fs/Kconfig | 8 fs/f2fs/f2fs.h | 1 + fs/f2fs/super.c | 16 3 files changed, 25 insertions(+) diff --git a/fs/f2fs/Kconfig b/fs/f2fs/Kconfig index

Re: [PATCH 3.14 00/37] 3.14.68-stable review

On Tue, May 03, 2016 at 12:19:09AM -0700, Guenter Roeck wrote: > On 05/02/2016 05:11 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.14.68 release. > > There are 37 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH 08/11] f2fs: inject ENOSPC failures

This patch injects ENOSPC failures. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 7 +++ fs/f2fs/dir.c| 4 fs/f2fs/f2fs.h | 10 ++ fs/f2fs/node.c | 4 fs/f2fs/super.c | 4 5 files changed, 29 insertions(+) diff --git

[PATCH 04/11] f2fs: use f2fs_grab_cache_page instead of grab_cache_page

This patch converts grab_cache_page to f2fs_grab_cache_page. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 7 --- fs/f2fs/inline.c | 4 ++-- fs/f2fs/node.c | 8 3 files changed, 10 insertions(+), 9 deletions(-) diff --git a/fs/f2fs/checkpoint.c

[PATCH 05/11] f2fs: add mount option to select fault injection ratio

This patch adds a mount option to select fault ratio. Signed-off-by: Jaegeuk Kim --- fs/f2fs/Kconfig | 8 fs/f2fs/f2fs.h | 1 + fs/f2fs/super.c | 16 3 files changed, 25 insertions(+) diff --git a/fs/f2fs/Kconfig b/fs/f2fs/Kconfig index 1f8982a..378c221 100644 ---

Re: [PATCH 3.14 00/37] 3.14.68-stable review

On Tue, May 03, 2016 at 12:19:09AM -0700, Guenter Roeck wrote: > On 05/02/2016 05:11 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.14.68 release. > > There are 37 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH 03/11] f2fs: introduce f2fs_kmalloc to wrap kmalloc

This patch adds f2fs_kmalloc. Signed-off-by: Jaegeuk Kim --- fs/f2fs/acl.c| 4 ++-- fs/f2fs/dir.c| 2 +- fs/f2fs/f2fs.h | 5 + fs/f2fs/gc.c | 2 +- fs/f2fs/inline.c | 2 +- 5 files changed, 10 insertions(+), 5 deletions(-) diff --git a/fs/f2fs/acl.c

[PATCH 03/11] f2fs: introduce f2fs_kmalloc to wrap kmalloc

This patch adds f2fs_kmalloc. Signed-off-by: Jaegeuk Kim --- fs/f2fs/acl.c| 4 ++-- fs/f2fs/dir.c| 2 +- fs/f2fs/f2fs.h | 5 + fs/f2fs/gc.c | 2 +- fs/f2fs/inline.c | 2 +- 5 files changed, 10 insertions(+), 5 deletions(-) diff --git a/fs/f2fs/acl.c b/fs/f2fs/acl.c index

Re: sched: tweak select_idle_sibling to look for idle threads

On Tue, May 03, 2016 at 01:31:31PM +0200, Peter Zijlstra wrote: > Then flip on the last_idle tracking in select_idle_core(): > > root@ivb-ep:~/bench/sysbench# for i in NO_OLD_IDLE NO_ORDER_IDLE IDLE_CORE > NO_FORCE_CORE IDLE IDLE_SMT IDLE_LAST NO_IDLE_FIRST ; do echo $i > >

[PATCH 07/11] f2fs: inject page allocation failures

This patch adds page allocation failures. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 9 + fs/f2fs/super.c | 1 + 2 files changed, 10 insertions(+) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 60098df..02c2c96 100644 --- a/fs/f2fs/f2fs.h +++

Re: sched: tweak select_idle_sibling to look for idle threads

On Tue, May 03, 2016 at 01:31:31PM +0200, Peter Zijlstra wrote: > Then flip on the last_idle tracking in select_idle_core(): > > root@ivb-ep:~/bench/sysbench# for i in NO_OLD_IDLE NO_ORDER_IDLE IDLE_CORE > NO_FORCE_CORE IDLE IDLE_SMT IDLE_LAST NO_IDLE_FIRST ; do echo $i > >

[PATCH 07/11] f2fs: inject page allocation failures

This patch adds page allocation failures. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 9 + fs/f2fs/super.c | 1 + 2 files changed, 10 insertions(+) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 60098df..02c2c96 100644 --- a/fs/f2fs/f2fs.h +++ b/fs/f2fs/f2fs.h @@ -40,6 +40,7

Re: [PATCH 1/3] dt-bindings: bus: Add documentation for Tegra210 ACONNECT

On Fri, Apr 29, 2016 at 02:53:45PM +0100, Jon Hunter wrote: > Add binding documentation for the Tegra ACONNECT bus that is part of the > Audio Processing Engine (APE) on Tegra210. The ACONNECT bus is used to > access devices within the APE subsystem. The APE is located in a > separate power domain

Re: [PATCH 1/3] dt-bindings: bus: Add documentation for Tegra210 ACONNECT

On Fri, Apr 29, 2016 at 02:53:45PM +0100, Jon Hunter wrote: > Add binding documentation for the Tegra ACONNECT bus that is part of the > Audio Processing Engine (APE) on Tegra210. The ACONNECT bus is used to > access devices within the APE subsystem. The APE is located in a > separate power domain

[PATCH 01/11] f2fs: introduce macros for proc entries

This adds macros to be used multiple proc entries. Signed-off-by: Jaegeuk Kim --- fs/f2fs/super.c | 25 ++--- 1 file changed, 14 insertions(+), 11 deletions(-) diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c index 19a85cf..b006de6 100644 ---

[PATCH 02/11] f2fs: add proc entry to show valid block bitmap

This patch adds a new proc entry to show segment information in more detail. Signed-off-by: Jaegeuk Kim --- fs/f2fs/super.c | 32 +++- 1 file changed, 31 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c index

[PATCH 10/11] f2fs: fix leak of orphan inode objects

When unmounting filesystem, we should release all the ino entries. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 6 +++--- fs/f2fs/f2fs.h | 2 +- fs/f2fs/super.c | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/fs/f2fs/checkpoint.c

Re: [PATCH 4.5 000/200] 4.5.3-stable review

On Tue, May 03, 2016 at 12:39:51AM -0700, Guenter Roeck wrote: > On 05/02/2016 05:09 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.5.3 release. > > There are 200 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH 06/11] f2fs: inject kmalloc failure

This patch injects kmalloc failure given a fault injection rate. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 29 + fs/f2fs/super.c | 6 ++ 2 files changed, 35 insertions(+) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index

[PATCH 01/11] f2fs: introduce macros for proc entries

This adds macros to be used multiple proc entries. Signed-off-by: Jaegeuk Kim --- fs/f2fs/super.c | 25 ++--- 1 file changed, 14 insertions(+), 11 deletions(-) diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c index 19a85cf..b006de6 100644 --- a/fs/f2fs/super.c +++

[PATCH 02/11] f2fs: add proc entry to show valid block bitmap

This patch adds a new proc entry to show segment information in more detail. Signed-off-by: Jaegeuk Kim --- fs/f2fs/super.c | 32 +++- 1 file changed, 31 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c index b006de6..90d4b86 100644 ---

[PATCH 10/11] f2fs: fix leak of orphan inode objects

When unmounting filesystem, we should release all the ino entries. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 6 +++--- fs/f2fs/f2fs.h | 2 +- fs/f2fs/super.c | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c

Re: [PATCH 4.5 000/200] 4.5.3-stable review

On Tue, May 03, 2016 at 12:39:51AM -0700, Guenter Roeck wrote: > On 05/02/2016 05:09 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.5.3 release. > > There are 200 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH 06/11] f2fs: inject kmalloc failure

This patch injects kmalloc failure given a fault injection rate. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 29 + fs/f2fs/super.c | 6 ++ 2 files changed, 35 insertions(+) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 0684d3e..60098df 100644 ---

[PATCH 09/11] f2fs: revisit error handling flows

This patch fixes a couple of bugs regarding to orphan inodes when handling errors. This tries to - call alloc_nid_done with add_orphan_inode in handle_failed_inode - let truncate blocks in f2fs_evict_inode - not make a bad inode due to i_mode change Signed-off-by: Jaegeuk Kim

[PATCH 11/11] f2fs: retry to truncate blocks in -ENOMEM case

This patch modifies to retry truncating node blocks in -ENOMEM case. Signed-off-by: Jaegeuk Kim --- fs/f2fs/inode.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c index f4ac851..5cccd7a 100644 --- a/fs/f2fs/inode.c

[PATCH 09/11] f2fs: revisit error handling flows

This patch fixes a couple of bugs regarding to orphan inodes when handling errors. This tries to - call alloc_nid_done with add_orphan_inode in handle_failed_inode - let truncate blocks in f2fs_evict_inode - not make a bad inode due to i_mode change Signed-off-by: Jaegeuk Kim ---

[PATCH 11/11] f2fs: retry to truncate blocks in -ENOMEM case

This patch modifies to retry truncating node blocks in -ENOMEM case. Signed-off-by: Jaegeuk Kim --- fs/f2fs/inode.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c index f4ac851..5cccd7a 100644 --- a/fs/f2fs/inode.c +++

Re: [PATCH 4.4 000/163] 4.4.9-stable review

On Tue, May 03, 2016 at 12:27:09AM -0700, Guenter Roeck wrote: > On 05/02/2016 05:10 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.9 release. > > There are 163 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.4 000/163] 4.4.9-stable review

On Tue, May 03, 2016 at 12:27:09AM -0700, Guenter Roeck wrote: > On 05/02/2016 05:10 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.9 release. > > There are 163 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: linux-next: manual merge of the staging tree with the vfs tree

On Tue, May 03, 2016 at 04:44:22PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the staging tree got a conflict in: > > drivers/staging/lustre/lustre/llite/rw26.c > > between commit: > > c8b8e32d700f ("direct-io: eliminate the offset argument to ->direct_IO") >

Re: [PATCH 4.5 000/200] 4.5.3-stable review

On Tue, May 03, 2016 at 08:59:18AM -0600, Shuah Khan wrote: > On 05/02/2016 06:09 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.5.3 release. > > There are 200 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH] usb: host: ehci-tegra: Avoid getting the same reset twice

get+0x16c/0x23c > [3.382151] Modules linked in: > [ 3.385214] CPU: 0 PID: 1 Comm: swapper/0 Not tainted > 4.6.0-rc6-next-20160503 #140 > [3.392769] Hardware name: NVIDIA Tegra SoC (Flattened Device Tree) > [3.399046] [] (unwind_backtrace) from [] > (sh

Re: linux-next: manual merge of the staging tree with the vfs tree

On Tue, May 03, 2016 at 04:44:22PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the staging tree got a conflict in: > > drivers/staging/lustre/lustre/llite/rw26.c > > between commit: > > c8b8e32d700f ("direct-io: eliminate the offset argument to ->direct_IO") >

Re: [PATCH 4.5 000/200] 4.5.3-stable review

On Tue, May 03, 2016 at 08:59:18AM -0600, Shuah Khan wrote: > On 05/02/2016 06:09 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.5.3 release. > > There are 200 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH] usb: host: ehci-tegra: Avoid getting the same reset twice

3.382151] Modules linked in: > [3.385214] CPU: 0 PID: 1 Comm: swapper/0 Not tainted > 4.6.0-rc6-next-20160503 #140 > [3.392769] Hardware name: NVIDIA Tegra SoC (Flattened Device Tree) > [3.399046] [] (unwind_backtrace) from [] > (show_stack+0x10/0x14) > [3.406787]

Re: [PATCH 4.4 60/67] powerpc/tm: Check for already reclaimed tasks

On Tue, May 03, 2016 at 09:04:17PM +1000, Michael Neuling wrote: > On Tue, 2016-05-03 at 08:32 +0200, Jiri Slaby wrote: > > On 01/27/2016, 07:12 PM, Greg Kroah-Hartman wrote: > > > > > > 4.4-stable review patch.  If anyone has any objections, please let me > > > know. > > > > > >

Re: [PATCH 4.4 60/67] powerpc/tm: Check for already reclaimed tasks

On Tue, May 03, 2016 at 09:04:17PM +1000, Michael Neuling wrote: > On Tue, 2016-05-03 at 08:32 +0200, Jiri Slaby wrote: > > On 01/27/2016, 07:12 PM, Greg Kroah-Hartman wrote: > > > > > > 4.4-stable review patch.  If anyone has any objections, please let me > > > know. > > > > > >

Re: [PATCH v2 2/2] nbd: Fix checkpatch errors.

On Tue, May 03, 2016 at 07:38:27PM +0300, Pranay Kr. Srivastava wrote: > Signed-off-by: Pranay Kr. Srivastava You have to have a changelog text. And try doing one-patch-per-checkpatch-warning-type. That's all I will accept for drivers/staging/ files, but maybe the nbd.c

Re: [PATCH v2 2/2] nbd: Fix checkpatch errors.

On Tue, May 03, 2016 at 07:38:27PM +0300, Pranay Kr. Srivastava wrote: > Signed-off-by: Pranay Kr. Srivastava You have to have a changelog text. And try doing one-patch-per-checkpatch-warning-type. That's all I will accept for drivers/staging/ files, but maybe the nbd.c maintainer has

Re: [PATCH] procfs: fixes pthread cross-thread naming if !PR_DUMPABLE

On 03/05/16 18:42, Kees Cook wrote: On Tue, May 3, 2016 at 10:25 AM, Janis Danisevskis wrote: On 26/04/16 21:14, Kees Cook wrote: On Tue, Apr 26, 2016 at 10:20 AM, Janis Danisevskis wrote: The PR_DUMPABLE flag causes the pid related paths of the

Re: [PATCH] procfs: fixes pthread cross-thread naming if !PR_DUMPABLE

On 03/05/16 18:42, Kees Cook wrote: On Tue, May 3, 2016 at 10:25 AM, Janis Danisevskis wrote: On 26/04/16 21:14, Kees Cook wrote: On Tue, Apr 26, 2016 at 10:20 AM, Janis Danisevskis wrote: The PR_DUMPABLE flag causes the pid related paths of the proc file system to be owned by ROOT.

Re: [PATCH v2 2/3] ARM: DRA7x: dts: Update the OSC_32K_CLK frequency

On 03/05/16 20:49, J.D. Schroeder wrote: On 05/03/2016 12:32 PM, Tero Kristo wrote: Personally I would not recommend using this clock for any timing sensitive applications. May I ask why you are interested in the exact clock rate of this clock anyway? I'm not interested in using this clock

Re: [PATCH 0/3] idle, Honor Hardware Disabled States

On 04/29/2016 05:36 AM, Len Brown wrote: > But above is all cosmetic. The real "bug" that users are running into is > that they can't get into deep c-states when they are enabled. > Linux (and Intel) need to do a much better job enabling diagnosis of > that condition. > Okay, I geddit.

Re: [PATCH 0/3] idle, Honor Hardware Disabled States

On 04/29/2016 05:36 AM, Len Brown wrote: > But above is all cosmetic. The real "bug" that users are running into is > that they can't get into deep c-states when they are enabled. > Linux (and Intel) need to do a much better job enabling diagnosis of > that condition. > Okay, I geddit.

Re: [PATCH v2 2/3] ARM: DRA7x: dts: Update the OSC_32K_CLK frequency

On 03/05/16 20:49, J.D. Schroeder wrote: On 05/03/2016 12:32 PM, Tero Kristo wrote: Personally I would not recommend using this clock for any timing sensitive applications. May I ask why you are interested in the exact clock rate of this clock anyway? I'm not interested in using this clock

Re: [PATCH 7/8] wbt: add general throttling mechanism

On 05/03/2016 10:59 AM, Jens Axboe wrote: On 05/03/2016 09:48 AM, Jan Kara wrote: On Tue 03-05-16 17:40:32, Jan Kara wrote: On Tue 03-05-16 11:34:10, Jan Kara wrote: Yeah, once I'll hunt down that regression with old disk, I can have a look into how writeback throttling plays together with

Re: [PATCH 7/8] wbt: add general throttling mechanism

On 05/03/2016 10:59 AM, Jens Axboe wrote: On 05/03/2016 09:48 AM, Jan Kara wrote: On Tue 03-05-16 17:40:32, Jan Kara wrote: On Tue 03-05-16 11:34:10, Jan Kara wrote: Yeah, once I'll hunt down that regression with old disk, I can have a look into how writeback throttling plays together with

Re: [RFC v2 3/7] firmware: port built-in section to linker table

On Tue, May 03, 2016 at 10:10:24AM -0700, Luis R. Rodriguez wrote: > On Tue, May 3, 2016 at 10:07 AM, Luis R. Rodriguez wrote: > > Thanks! Can you confirm if any Android or Brillo builds are already using > > it? > > Also more importantly, any chance you can provide any

Re: [RFC v2 3/7] firmware: port built-in section to linker table

On Tue, May 03, 2016 at 10:10:24AM -0700, Luis R. Rodriguez wrote: > On Tue, May 3, 2016 at 10:07 AM, Luis R. Rodriguez wrote: > > Thanks! Can you confirm if any Android or Brillo builds are already using > > it? > > Also more importantly, any chance you can provide any technical > reasons why

Re: [PATCH v4 1/2] PM / OPP: add non-OF versions of dev_pm_opp_{cpumask_,}remove_table

On 05/03, Sudeep Holla wrote: > Functions dev_pm_opp_of_{cpumask_,}remove_table removes/frees all the > static OPP entries associated with the device and/or all cpus(in case > of cpumask) that are created from DT. > > However the OPP entries are populated reading from the firmware or some >

Re: [PATCH v4 1/2] PM / OPP: add non-OF versions of dev_pm_opp_{cpumask_,}remove_table

On 05/03, Sudeep Holla wrote: > Functions dev_pm_opp_of_{cpumask_,}remove_table removes/frees all the > static OPP entries associated with the device and/or all cpus(in case > of cpumask) that are created from DT. > > However the OPP entries are populated reading from the firmware or some >

[PATCH] [REGRESSION] md: md.c: fix oops in mddev_suspend for raid0

From: Heinz Mauelshagen Introduced by upstream commit 70d9798b95562abac005d4ba71d28820f9a201eb The raid0 personality does not create mddev->thread as oposed to other personalities leading to its unconditional access in mddev_suspend() causing an oops. Patch checks for

[PATCH] [REGRESSION] md: md.c: fix oops in mddev_suspend for raid0

From: Heinz Mauelshagen Introduced by upstream commit 70d9798b95562abac005d4ba71d28820f9a201eb The raid0 personality does not create mddev->thread as oposed to other personalities leading to its unconditional access in mddev_suspend() causing an oops. Patch checks for mddev->thread in order to

Re: [PATCH RESEND] x86/asm/entry/32: simplify pushes of zeroed pt_regs->REGs

On Tue, May 3, 2016 at 1:55 PM, Andy Lutomirski wrote: > On Tue, May 3, 2016 at 10:45 AM, Brian Gerst wrote: >> On Mon, May 2, 2016 at 10:56 AM, Denys Vlasenko wrote: >>> Use of a temporary R8 register here seems to be unnecessary.

Re: [PATCH RESEND] x86/asm/entry/32: simplify pushes of zeroed pt_regs->REGs

On Tue, May 3, 2016 at 1:55 PM, Andy Lutomirski wrote: > On Tue, May 3, 2016 at 10:45 AM, Brian Gerst wrote: >> On Mon, May 2, 2016 at 10:56 AM, Denys Vlasenko wrote: >>> Use of a temporary R8 register here seems to be unnecessary. >>> >>> "push %r8" is a two-byte insn (it needs REX prefix to

Re: [PATCH v2 2/3] ARM: DRA7x: dts: Update the OSC_32K_CLK frequency

* J.D. Schroeder [160503 10:50]: > On 05/03/2016 12:32 PM, Tero Kristo wrote: > > Personally I would not recommend using this clock for any timing sensitive > > applications. May I ask why you are interested in the exact clock rate of > > this > > clock anyway? > > I'm not

Re: [PATCH v2 2/3] ARM: DRA7x: dts: Update the OSC_32K_CLK frequency

* J.D. Schroeder [160503 10:50]: > On 05/03/2016 12:32 PM, Tero Kristo wrote: > > Personally I would not recommend using this clock for any timing sensitive > > applications. May I ask why you are interested in the exact clock rate of > > this > > clock anyway? > > I'm not interested in using

[PATCH] usb: host: ehci-tegra: Avoid getting the same reset twice

driver for Tegra: [3.365019] [ cut here ] [3.369639] WARNING: CPU: 0 PID: 1 at drivers/reset/core.c:187 __of_reset_control_get+0x16c/0x23c [3.382151] Modules linked in: [3.385214] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.6.0-rc6-next-20160503 #140 [3.39276

[PATCH] usb: host: ehci-tegra: Avoid getting the same reset twice

3.365019] [ cut here ] [3.369639] WARNING: CPU: 0 PID: 1 at drivers/reset/core.c:187 __of_reset_control_get+0x16c/0x23c [3.382151] Modules linked in: [3.385214] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.6.0-rc6-next-20160503 #140 [3.392769] Hardware name: NVIDIA

[PATCH v2] media: fix use-after-free in cdev_put() when app exits after driver unbind

When driver unbinds while media_ioctl is in progress, cdev_put() fails with when app exits after driver unbinds. Add devnode struct device kobj as the cdev parent kobject. cdev_add() holds a reference to it and releases the reference in cdev_del() ensuring that the media_devnode is not

[PATCH v2] media: fix use-after-free in cdev_put() when app exits after driver unbind

When driver unbinds while media_ioctl is in progress, cdev_put() fails with when app exits after driver unbinds. Add devnode struct device kobj as the cdev parent kobject. cdev_add() holds a reference to it and releases the reference in cdev_del() ensuring that the media_devnode is not

Re: [PATCH v2 02/11] serial: sh-sci: Update DT binding documentation for dedicated RTS/CTS

On Fri, Apr 29, 2016 at 02:58:25PM +0200, Geert Uytterhoeven wrote: > Some Renesas SCIF UARTs have dedicated lines for RTS/CTS hardware flow > control. Whether these lines exist depends on SoC and UART instance > inside the SoC. Whether these lines can be used for hardware flow > control depends

Re: [PATCH v2 02/11] serial: sh-sci: Update DT binding documentation for dedicated RTS/CTS

On Fri, Apr 29, 2016 at 02:58:25PM +0200, Geert Uytterhoeven wrote: > Some Renesas SCIF UARTs have dedicated lines for RTS/CTS hardware flow > control. Whether these lines exist depends on SoC and UART instance > inside the SoC. Whether these lines can be used for hardware flow > control depends

[PATCH] cyclictest: stop any tracing after hitting a breaktrace threshold

John, This patch is against the devel/v0.98 branch. It turns off tracing in the tracemark() so that we don't lose information about what was going on when we hit the latency: The current logic of using --tracemark and --notrace works for running cyclictest with trace-cmd, but even if we are

[PATCH] cyclictest: stop any tracing after hitting a breaktrace threshold

John, This patch is against the devel/v0.98 branch. It turns off tracing in the tracemark() so that we don't lose information about what was going on when we hit the latency: The current logic of using --tracemark and --notrace works for running cyclictest with trace-cmd, but even if we are

Re: [RFT PATCH 1/3] usb: misc: usb3503: Fix HUB mode after bootloader initialization

On Mon, May 02, 2016 at 11:55:01AM +0100, Mark Brown wrote: > On Mon, May 02, 2016 at 11:49:12AM +0200, Krzysztof Kozlowski wrote: > > > This VDD regulator supply actually is not a usb3503 USB HUB regulator > > supply... but a supply to the LAN attached to this HUB. Regulator off/on > > is needed

Re: [RFT PATCH 1/3] usb: misc: usb3503: Fix HUB mode after bootloader initialization

On Mon, May 02, 2016 at 11:55:01AM +0100, Mark Brown wrote: > On Mon, May 02, 2016 at 11:49:12AM +0200, Krzysztof Kozlowski wrote: > > > This VDD regulator supply actually is not a usb3503 USB HUB regulator > > supply... but a supply to the LAN attached to this HUB. Regulator off/on > > is needed

[RFC PATCH 02/12] dt-bindings: clock: Add PWM clock ID to Exynos5410

Add ID for PWM clock to Exynos5410. Use the same number as for Exynos5420. Signed-off-by: Krzysztof Kozlowski --- A question: does it make sense to stick to same IDs? --- include/dt-bindings/clock/exynos5410.h | 2 ++ 1 file changed, 2 insertions(+) diff --git

[RFC PATCH 02/12] dt-bindings: clock: Add PWM clock ID to Exynos5410

Add ID for PWM clock to Exynos5410. Use the same number as for Exynos5420. Signed-off-by: Krzysztof Kozlowski --- A question: does it make sense to stick to same IDs? --- include/dt-bindings/clock/exynos5410.h | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [RESEND PATCH v2 04/13] eeprom: at24: make locking more fine-grained

2016-04-16 22:56 GMT+02:00 Wolfram Sang : > On Mon, Apr 11, 2016 at 11:57:20AM -0700, Bartosz Golaszewski wrote: >> The only field in struct at24_data that needs locking in the module >> code is u8 *writebuf. Other data is already protected by i2c core. >> >> Rename the lock in

Re: [RESEND PATCH v2 04/13] eeprom: at24: make locking more fine-grained

2016-04-16 22:56 GMT+02:00 Wolfram Sang : > On Mon, Apr 11, 2016 at 11:57:20AM -0700, Bartosz Golaszewski wrote: >> The only field in struct at24_data that needs locking in the module >> code is u8 *writebuf. Other data is already protected by i2c core. >> >> Rename the lock in at24_data to

Re: [PATCH RESEND] x86/asm/entry/32: simplify pushes of zeroed pt_regs->REGs

On Tue, May 3, 2016 at 10:45 AM, Brian Gerst wrote: > On Mon, May 2, 2016 at 10:56 AM, Denys Vlasenko wrote: >> Use of a temporary R8 register here seems to be unnecessary. >> >> "push %r8" is a two-byte insn (it needs REX prefix to specify R8), >> "push

Re: [PATCH RESEND] x86/asm/entry/32: simplify pushes of zeroed pt_regs->REGs

On Tue, May 3, 2016 at 10:45 AM, Brian Gerst wrote: > On Mon, May 2, 2016 at 10:56 AM, Denys Vlasenko wrote: >> Use of a temporary R8 register here seems to be unnecessary. >> >> "push %r8" is a two-byte insn (it needs REX prefix to specify R8), >> "push $0" is two-byte too. It seems just using

[RFC PATCH 07/12] ARM: dts: exynos: Move common nodes to exynos5.dtsi

Exynos5420 and Exynos5250 share some nodes: the PWM and syscon (sysreg_system_controller). Move them to parent DTSI to avoid duplication. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5.dtsi| 12 arch/arm/boot/dts/exynos5250.dtsi | 19

[RFC PATCH 07/12] ARM: dts: exynos: Move common nodes to exynos5.dtsi

Exynos5420 and Exynos5250 share some nodes: the PWM and syscon (sysreg_system_controller). Move them to parent DTSI to avoid duplication. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5.dtsi| 12 arch/arm/boot/dts/exynos5250.dtsi | 19 +--

[RFC PATCH 12/12] ARM: dts: exynos: Enable UART3 on Exynos5410

Just like other Exynos5 family SoCs, this one has four UARTs. Configure clocks for UART3 and enable it. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5410.dtsi | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[RFC PATCH 05/12] ARM: dts: exynos: Configure Exynos5410 pinctrl for eMMC and SD card

Configure the pinctrl for MMC0 (eMMC) and MMC2 (microSD card). Signed-off-by: Krzysztof Kozlowski --- I am not sure about sd0_rclk. Also I wonder whether this should go to board DTS... --- arch/arm/boot/dts/exynos5410-pinctrl.dtsi | 87 +++ 1 file

[RFC PATCH 08/12] ARM: dts: exynos: Prepare for inclusion of exynos5.dtsi in exynos5410.dtsi

Add 'sromc' label to SROM memory controller in common exynos5.dtsi so it can be referenced by ihneriting DTSI. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[RFC PATCH 04/12] ARM: dts: exynos: Use lowercase for Exynos5410 CPU node labels

Fro consistency lowercase node labels are used. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5410.dtsi | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/exynos5410.dtsi b/arch/arm/boot/dts/exynos5410.dtsi index

[RFC PATCH 12/12] ARM: dts: exynos: Enable UART3 on Exynos5410

Just like other Exynos5 family SoCs, this one has four UARTs. Configure clocks for UART3 and enable it. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5410.dtsi | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/exynos5410.dtsi

[RFC PATCH 05/12] ARM: dts: exynos: Configure Exynos5410 pinctrl for eMMC and SD card

Configure the pinctrl for MMC0 (eMMC) and MMC2 (microSD card). Signed-off-by: Krzysztof Kozlowski --- I am not sure about sd0_rclk. Also I wonder whether this should go to board DTS... --- arch/arm/boot/dts/exynos5410-pinctrl.dtsi | 87 +++ 1 file changed, 87

[RFC PATCH 08/12] ARM: dts: exynos: Prepare for inclusion of exynos5.dtsi in exynos5410.dtsi

Add 'sromc' label to SROM memory controller in common exynos5.dtsi so it can be referenced by ihneriting DTSI. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/exynos5.dtsi

[RFC PATCH 04/12] ARM: dts: exynos: Use lowercase for Exynos5410 CPU node labels

Fro consistency lowercase node labels are used. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5410.dtsi | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/exynos5410.dtsi b/arch/arm/boot/dts/exynos5410.dtsi index

[RFC PATCH 06/12] ARM: dts: exynos: Split Odroid XU3 LEDs to separate DTSI

The LED nodes can be shared between Odroid XU3, XU3-Lite and XU (not yet added) thus removing duplication. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5422-odroidxu3-lite.dts | 35 + arch/arm/boot/dts/exynos5422-odroidxu3.dts | 35

[RFC PATCH 06/12] ARM: dts: exynos: Split Odroid XU3 LEDs to separate DTSI

The LED nodes can be shared between Odroid XU3, XU3-Lite and XU (not yet added) thus removing duplication. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5422-odroidxu3-lite.dts | 35 + arch/arm/boot/dts/exynos5422-odroidxu3.dts | 35 +

[RFC PATCH 03/12] ARM: dts: exynos: Re-order alphabetically Exynos5420 SD0/SD1 pinctrl nodes

The 'sd0_rclk' was put in the middle of SD1 nodes. Remove the confusion. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5420-pinctrl.dtsi | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/arm/boot/dts/exynos5420-pinctrl.dtsi

[RFC PATCH 10/12] ARM: dts: exynos: Move Exynos5250 and Exynos5420 nodes under soc

The conventions it to put SoC devices under 'soc' node. In fact other our DTSes (like exynos3250.dtsi or exynos5410.dtsi) already follows it. Adjust exynos5250 and exynos5420 DTSI to follow this convention. This is also necessary for the upcoming change in exynos5410.dtsi to inherit from common

[RFC PATCH 03/12] ARM: dts: exynos: Re-order alphabetically Exynos5420 SD0/SD1 pinctrl nodes

The 'sd0_rclk' was put in the middle of SD1 nodes. Remove the confusion. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos5420-pinctrl.dtsi | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/arm/boot/dts/exynos5420-pinctrl.dtsi

[RFC PATCH 10/12] ARM: dts: exynos: Move Exynos5250 and Exynos5420 nodes under soc

The conventions it to put SoC devices under 'soc' node. In fact other our DTSes (like exynos3250.dtsi or exynos5410.dtsi) already follows it. Adjust exynos5250 and exynos5420 DTSI to follow this convention. This is also necessary for the upcoming change in exynos5410.dtsi to inherit from common

[RFC PATCH 09/12] ARM: dts: exynos: Use phandle to get parent node in exynos5250-snow

The i2c-arbitrator node in exynos5250-snow-common used absolute path to reference other node (the i2c parent). Use phandle instead, because the depth of the other node may be changed (like moving it under 'soc' node). Signed-off-by: Krzysztof Kozlowski ---

[RFC PATCH 11/12] ARM: dts: exynos: Include common exynos5 in exynos5410.dtsi

The exynos5.dtsi is used for common nodes shared between Exynos5250 and Exynos542x. Since Exynos5410 is very similar to Exynos5420 it can include the common file as well to remove duplication and make everything more consistent. Signed-off-by: Krzysztof Kozlowski ---

[RFC PATCH 09/12] ARM: dts: exynos: Use phandle to get parent node in exynos5250-snow

The i2c-arbitrator node in exynos5250-snow-common used absolute path to reference other node (the i2c parent). Use phandle instead, because the depth of the other node may be changed (like moving it under 'soc' node). Signed-off-by: Krzysztof Kozlowski ---

[RFC PATCH 11/12] ARM: dts: exynos: Include common exynos5 in exynos5410.dtsi

The exynos5.dtsi is used for common nodes shared between Exynos5250 and Exynos542x. Since Exynos5410 is very similar to Exynos5420 it can include the common file as well to remove duplication and make everything more consistent. Signed-off-by: Krzysztof Kozlowski ---

[RFC PATCH 00/12] ARM: dts: exynos: Reorganize before adding Odroid XU board

Hi, I am in the middle (or beginning) of adding DTS for Odroid XU. This patchset is a preparation for that. I still did not figure out two things: 1. clock IDs, should we follow Exynos5420 (or maybe reuse entirely?) see patch 1. 2. sd0_rclk - see patch 5. The Odroid XU board is based on

[RFC PATCH 00/12] ARM: dts: exynos: Reorganize before adding Odroid XU board

Hi, I am in the middle (or beginning) of adding DTS for Odroid XU. This patchset is a preparation for that. I still did not figure out two things: 1. clock IDs, should we follow Exynos5420 (or maybe reuse entirely?) see patch 1. 2. sd0_rclk - see patch 5. The Odroid XU board is based on

<    1   2   3   4   5   6   7   8   9   10   >