[PATCH 07/12] drivers/media: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Hans Verkuil Cc: Andy Walls

[PATCH 06/12] HID,wacom: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Jiri Kosina Signed-off-by: Davidlohr Bueso

[PATCH 6/8] arm64: dts: db820c: add support to LS-SPI0

This patch adds support to SPI on LS expansion connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 07/12] drivers/media: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Hans Verkuil Cc: Andy Walls Cc: linux-me...@vger.kernel.org

[PATCH 06/12] HID,wacom: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Jiri Kosina Signed-off-by: Davidlohr Bueso --- drivers/hid/wacom_sys.c |

[PATCH 6/8] arm64: dts: db820c: add support to LS-SPI0

This patch adds support to SPI on LS expansion connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi b/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 7/8] arm64: dts: db820c: add support to SPI on HS

This patch adds support to SPI on HS expansion connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 0/8] arm64: dts: db820c: Add basic board support

Hi Andy, This patchset adds basic board support with uart/i2c/spi/sd card for db820c board based on apq8096. I have tested this patchset on top of msm8996 patches at [1]. With this patchset am able to boot the board with sdcard and able to play with i2c devices. Thanks, srini [1]

[PATCH 0/8] arm64: dts: db820c: Add basic board support

Hi Andy, This patchset adds basic board support with uart/i2c/spi/sd card for db820c board based on apq8096. I have tested this patchset on top of msm8996 patches at [1]. With this patchset am able to boot the board with sdcard and able to play with i2c devices. Thanks, srini [1]

[PATCH 7/8] arm64: dts: db820c: add support to SPI on HS

This patch adds support to SPI on HS expansion connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi b/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 5/8] arm64: dts: db820c: add support to I2C on HS

This patch adds support to i2c bus on High speed connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 5/8] arm64: dts: db820c: add support to I2C on HS

This patch adds support to i2c bus on High speed connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi b/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 3/8] arm64: dts: db820c: add support to LS-I2C0

This patch adds support to LS-I2C0 on LS expansion connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 3/8] arm64: dts: db820c: add support to LS-I2C0

This patch adds support to LS-I2C0 on LS expansion connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 4/8] arm64: dts: db820c: add support to LS-I2C1

This patch adds support to LS_I2C1 on LS expansion connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 4/8] arm64: dts: db820c: add support to LS-I2C1

This patch adds support to LS_I2C1 on LS expansion connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 2/8] arm64: dts: db820c: add support to LS-UART0

This patch adds support to 4 pin UART0 on LS expansion connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 2/8] arm64: dts: db820c: add support to LS-UART0

This patch adds support to 4 pin UART0 on LS expansion connector. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

[PATCH 1/8] arm64: dts: db820c: add basic board support

This patch adds apq8096 db820c basic support with serial port. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/Makefile| 2 +- arch/arm64/boot/dts/qcom/apq8096-db820c.dts | 21 +

[PATCH 1/8] arm64: dts: db820c: add basic board support

This patch adds apq8096 db820c basic support with serial port. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/Makefile| 2 +- arch/arm64/boot/dts/qcom/apq8096-db820c.dts | 21 + arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi | 34

[PATCH 11/12] scsi: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: "James E.J. Bottomley" Cc: "Martin

[PATCH 12/12] dma-buf/fence: Employ atomic_fetch_add

Now that we have fetch_add() we can stop using add_return() - num. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Sumit Semwal Signed-off-by: Davidlohr Bueso

[PATCH 11/12] scsi: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: "James E.J. Bottomley" Cc: "Martin K. Petersen" Signed-off-by: Davidlohr

[PATCH 12/12] dma-buf/fence: Employ atomic_fetch_add

Now that we have fetch_add() we can stop using add_return() - num. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Sumit Semwal Signed-off-by: Davidlohr Bueso ---

[PATCH 08/12] infiniband: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Doug Ledford Cc: Sean Hefty

[PATCH 08/12] infiniband: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Doug Ledford Cc: Sean Hefty Cc: Hal Rosenstock Signed-off-by: Davidlohr

[PATCH 09/12] drivers/hv: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: "K. Y. Srinivasan" Cc: Haiyang Zhang

[PATCH 05/12] tty/serial: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Greg Kroah-Hartman Cc: Pat Gefre

Re: [v3,1/4] mfd: cros_ec: Add cros_ec_cmd_xfer_status helper

Hi, On Mon, Jun 20, 2016 at 10:44:55AM -0700, Brian Norris wrote: > On Mon, Jun 20, 2016 at 09:46:57AM -0400, Javier Martinez Canillas wrote: > > On 06/18/2016 01:09 PM, Guenter Roeck wrote: > > > On 06/17/2016 06:08 PM, Brian Norris wrote: > > >> How do you propose we do that? Do all of the

[PATCH 03/12] PM,devfreq: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Chanwoo Choi Cc: linux...@vger.kernel.org

[PATCH 09/12] drivers/hv: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: "K. Y. Srinivasan" Cc: Haiyang Zhang Signed-off-by: Davidlohr Bueso ---

[PATCH 05/12] tty/serial: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Greg Kroah-Hartman Cc: Pat Gefre Signed-off-by: Davidlohr Bueso ---

Re: [v3,1/4] mfd: cros_ec: Add cros_ec_cmd_xfer_status helper

Hi, On Mon, Jun 20, 2016 at 10:44:55AM -0700, Brian Norris wrote: > On Mon, Jun 20, 2016 at 09:46:57AM -0400, Javier Martinez Canillas wrote: > > On 06/18/2016 01:09 PM, Guenter Roeck wrote: > > > On 06/17/2016 06:08 PM, Brian Norris wrote: > > >> How do you propose we do that? Do all of the

[PATCH 03/12] PM,devfreq: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Chanwoo Choi Cc: linux...@vger.kernel.org Signed-off-by: Davidlohr Bueso

[PATCH 10/12] s390/scm_block: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Martin Schwidefsky Cc: Heiko Carstens

[PATCH 02/12] net/neighbour: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: David S. Miller Signed-off-by: Davidlohr Bueso

[PATCH 10/12] s390/scm_block: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Martin Schwidefsky Cc: Heiko Carstens Signed-off-by: Davidlohr Bueso ---

[PATCH 02/12] net/neighbour: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: David S. Miller Signed-off-by: Davidlohr Bueso --- net/core/neighbour.c

[PATCH 04/12] EDAC: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Doug Thompson Cc: Borislav Petkov

[PATCH 04/12] EDAC: Employ atomic_fetch_inc()

Now that we have fetch_inc() we can stop using inc_return() - 1. These are very similar to the existing OP-RETURN primitives we already have, except they return the value of the atomic variable _before_ modification. Cc: Doug Thompson Cc: Borislav Petkov Cc: Mauro Carvalho Chehab

[PATCH 01/12] locking/atomic: Introduce inc/dec calls for FETCH-OP flavors

With the inclusion of atomic FETCH-OP variants, many places in the kernel can make use of atomic_fetch_$op() to avoid the hacky callers that need to compute the value/state _before_ the operation. Peter laid out the machinery but we are still missing the simpler dec,inc calls (which future patches

[PATCH 01/12] locking/atomic: Introduce inc/dec calls for FETCH-OP flavors

With the inclusion of atomic FETCH-OP variants, many places in the kernel can make use of atomic_fetch_$op() to avoid the hacky callers that need to compute the value/state _before_ the operation. Peter laid out the machinery but we are still missing the simpler dec,inc calls (which future patches

[PATCH] blktrace: reword comment about time overflow

Jeff Moyer looked up the blktrace source to see if an overflow might happen. The situation is as follows: - The time stamp is not used by the program itself, only for printing human-readable output. - We normally don't print the timestamp at all, except when an undocumented format option is

[PATCH] blktrace: reword comment about time overflow

Jeff Moyer looked up the blktrace source to see if an overflow might happen. The situation is as follows: - The time stamp is not used by the program itself, only for printing human-readable output. - We normally don't print the timestamp at all, except when an undocumented format option is

[PATCH] scripts/gdb: add constants.py to .gitignore

From: Omar Sandoval Since scripts/gdb/linux/constants.py is autogenerated, this should have been added to .gitignore when it was introduced. Fixes: f197d75fcad1 ("scripts/gdb: provide linux constants") Signed-off-by: Omar Sandoval --- .gitignore | 3 +++ 1 file

[PATCH] scripts/gdb: add constants.py to .gitignore

From: Omar Sandoval Since scripts/gdb/linux/constants.py is autogenerated, this should have been added to .gitignore when it was introduced. Fixes: f197d75fcad1 ("scripts/gdb: provide linux constants") Signed-off-by: Omar Sandoval --- .gitignore | 3 +++ 1 file changed, 3 insertions(+) diff

Re: [Y2038] [PATCH] blktrace: avoid using timespec

On Monday, June 20, 2016 3:37:10 PM CEST Jeff Moyer wrote: > > > Ok. Thanks a lot for the information. I think we can update the > > comment as in the incremental patch below. Jens, can you fold that > > into the original patch, or should I submit this as a new (or > > incremental) patch with an

Re: [Y2038] [PATCH] blktrace: avoid using timespec

On Monday, June 20, 2016 3:37:10 PM CEST Jeff Moyer wrote: > > > Ok. Thanks a lot for the information. I think we can update the > > comment as in the incremental patch below. Jens, can you fold that > > into the original patch, or should I submit this as a new (or > > incremental) patch with an

Re: [PATCH] rcutorture: Remove outdated config option description

On Mon, Jun 20, 2016 at 07:51:22AM +0900, SeongJae Park wrote: > CONFIG_RCU_TORTURE_TEST_RUNNABLE has removed by commit 4e9a073f60367 > ("torture: Remove CONFIG_RCU_TORTURE_TEST_RUNNABLE, simplify code") > entirely but the document has not updated. This commit updates the > document to remove the

Re: [PATCH] rcutorture: Remove outdated config option description

On Mon, Jun 20, 2016 at 07:51:22AM +0900, SeongJae Park wrote: > CONFIG_RCU_TORTURE_TEST_RUNNABLE has removed by commit 4e9a073f60367 > ("torture: Remove CONFIG_RCU_TORTURE_TEST_RUNNABLE, simplify code") > entirely but the document has not updated. This commit updates the > document to remove the

Re: [PATCH v9 07/12] kthread: Add kthread_destroy_worker()

On Thu, Jun 16, 2016 at 01:17:26PM +0200, Petr Mladek wrote: > The current kthread worker users call flush() and stop() explicitly. > This function drains the worker, stops it, and frees the kthread_worker > struct in one call. > > It is supposed to be used together with kthread_create_worker*()

Re: [PATCH v9 07/12] kthread: Add kthread_destroy_worker()

On Thu, Jun 16, 2016 at 01:17:26PM +0200, Petr Mladek wrote: > The current kthread worker users call flush() and stop() explicitly. > This function drains the worker, stops it, and frees the kthread_worker > struct in one call. > > It is supposed to be used together with kthread_create_worker*()

[PATCH 5/6] time: Avoid timespec in udelay_test

From: Arnd Bergmann udelay_test_single() uses ktime_get_ts() to get two timespec values and calculate the difference between them, while udelay_test_show() uses the same to printk() the current monotonic time. Both of these are y2038 safe on all machines, but we want to get rid

Re: [PATCH v9 06/12] kthread: Add kthread_drain_worker()

On Thu, Jun 16, 2016 at 01:17:25PM +0200, Petr Mladek wrote: > kthread_flush_worker() returns when the currently queued works are proceed. > But some other works might have been queued in the meantime. > > This patch adds kthread_drain_worker() that is inspired by > drain_workqueue(). It returns

[PATCH 5/6] time: Avoid timespec in udelay_test

From: Arnd Bergmann udelay_test_single() uses ktime_get_ts() to get two timespec values and calculate the difference between them, while udelay_test_show() uses the same to printk() the current monotonic time. Both of these are y2038 safe on all machines, but we want to get rid of struct

Re: [PATCH v9 06/12] kthread: Add kthread_drain_worker()

On Thu, Jun 16, 2016 at 01:17:25PM +0200, Petr Mladek wrote: > kthread_flush_worker() returns when the currently queued works are proceed. > But some other works might have been queued in the meantime. > > This patch adds kthread_drain_worker() that is inspired by > drain_workqueue(). It returns

[PATCH 1/6] clocksource: Make clocksource insert entry more efficient

From: Minfei Huang In clocksource_enqueue(), it is unnecessary to continue looping the list, if we find there is an entry that the value of rating is smaller than the new one. It is safe to be out the loop, because all of entry are inserted in descending order. Cc: Prarit

[PATCH 6/6] timer: Avoid using timespec

From: Arnd Bergmann The tstats_show() function prints a ktime_t variable by converting it to struct timespec first. The algorithm is ok, but we want to stop using timespec in general because of the 32-bit time_t overflow problem. This changes the code to use struct timespec64,

[PATCH 4/6] time: Add time64_to_tm()

From: Deepa Dinamani time_to_tm() takes time_t as an argument. time_t is not y2038 safe. Add time64_to_tm() that takes time64_t as an argument which is y2038 safe. The plan is to eventually replace all calls to time_to_tm() by time64_to_tm(). Cc: Prarit Bhargava

[PATCH 3/6] alarmtimer: Fix comments describing structure fields

From: Pratyush Patel Updated struct alarm and struct alarm_timer descriptions. Cc: Prarit Bhargava Cc: Richard Cochran Cc: Thomas Gleixner Cc: Ingo Molnar Signed-off-by: Pratyush

[PATCH 2/6] timekeeping: Fix 1ns/tick drift with GENERIC_TIME_VSYSCALL_OLD

From: Thomas Graziadei The user notices the problem in a raw and real time drift, calling clock_gettime with CLOCK_REALTIME / CLOCK_MONOTONIC_RAW on a system with no ntp correction taking place (no ntpd or ptp stuff running). The problem is, that

[PATCH 1/6] clocksource: Make clocksource insert entry more efficient

From: Minfei Huang In clocksource_enqueue(), it is unnecessary to continue looping the list, if we find there is an entry that the value of rating is smaller than the new one. It is safe to be out the loop, because all of entry are inserted in descending order. Cc: Prarit Bhargava Cc: Richard

[PATCH 6/6] timer: Avoid using timespec

From: Arnd Bergmann The tstats_show() function prints a ktime_t variable by converting it to struct timespec first. The algorithm is ok, but we want to stop using timespec in general because of the 32-bit time_t overflow problem. This changes the code to use struct timespec64, without any

[PATCH 4/6] time: Add time64_to_tm()

From: Deepa Dinamani time_to_tm() takes time_t as an argument. time_t is not y2038 safe. Add time64_to_tm() that takes time64_t as an argument which is y2038 safe. The plan is to eventually replace all calls to time_to_tm() by time64_to_tm(). Cc: Prarit Bhargava Cc: Richard Cochran Cc: Thomas

[PATCH 3/6] alarmtimer: Fix comments describing structure fields

From: Pratyush Patel Updated struct alarm and struct alarm_timer descriptions. Cc: Prarit Bhargava Cc: Richard Cochran Cc: Thomas Gleixner Cc: Ingo Molnar Signed-off-by: Pratyush Patel Signed-off-by: John Stultz --- include/linux/alarmtimer.h | 6 +++--- kernel/time/alarmtimer.c | 1 -

[PATCH 2/6] timekeeping: Fix 1ns/tick drift with GENERIC_TIME_VSYSCALL_OLD

From: Thomas Graziadei The user notices the problem in a raw and real time drift, calling clock_gettime with CLOCK_REALTIME / CLOCK_MONOTONIC_RAW on a system with no ntp correction taking place (no ntpd or ptp stuff running). The problem is, that old_vsyscall_fixup adds an extra 1ns even though

[GIT PULL][PATCH 0/6] Timekeeping changes for tip/timers/core

Hey Thomas, Ingo, Here is my current queue of timekeeping changes for 4.8. Most of them are small cleanups and core y2038 changes. Let me know if you have any objections. thanks -john Cc: Prarit Bhargava Cc: Richard Cochran Cc: Thomas Gleixner

[GIT PULL][PATCH 0/6] Timekeeping changes for tip/timers/core

Hey Thomas, Ingo, Here is my current queue of timekeeping changes for 4.8. Most of them are small cleanups and core y2038 changes. Let me know if you have any objections. thanks -john Cc: Prarit Bhargava Cc: Richard Cochran Cc: Thomas Gleixner Cc: Ingo Molnar You can also grab it via a

[PATCH v3 07/15] Documentation: mmc: sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs

As can be seen in Arasan's datasheet [1] there are several "corecfg" settings in their SDHCI IP Block that are supposed to be controlled by software. Although the datasheet referenced is a bit vague about how to access corecfg, in Figure 5 you can see that for Arasan's PHY (a separate component

Re: [PATCH v9 05/12] kthread: Add kthread_create_worker*()

On Thu, Jun 16, 2016 at 01:17:24PM +0200, Petr Mladek wrote: > Kthread workers are currently created using the classic kthread API, > namely kthread_run(). kthread_worker_fn() is passed as the @threadfn > parameter. > > This patch defines kthread_create_worker() and >

[PATCH v3 07/15] Documentation: mmc: sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs

As can be seen in Arasan's datasheet [1] there are several "corecfg" settings in their SDHCI IP Block that are supposed to be controlled by software. Although the datasheet referenced is a bit vague about how to access corecfg, in Figure 5 you can see that for Arasan's PHY (a separate component

Re: [PATCH v9 05/12] kthread: Add kthread_create_worker*()

On Thu, Jun 16, 2016 at 01:17:24PM +0200, Petr Mladek wrote: > Kthread workers are currently created using the classic kthread API, > namely kthread_run(). kthread_worker_fn() is passed as the @threadfn > parameter. > > This patch defines kthread_create_worker() and >

Re: [patch] ext4: underflow in alignment check

On Mon, Jun 20, 2016 at 06:02:04PM +0200, Jan Kara wrote: > On Thu 16-06-16 10:07:09, Dan Carpenter wrote: > > My static checker complains that this can underflow if arg is negative > > which is true. > > > > Signed-off-by: Dan Carpenter > > How come? (1 << 30) fits

Re: [PATCH v9 04/12] kthread: Allow to call __kthread_create_on_node() with va_list args

On Thu, Jun 16, 2016 at 01:17:23PM +0200, Petr Mladek wrote: > kthread_create_on_node() implements a bunch of logic to create > the kthread. It is already called by kthread_create_on_cpu(). > > We are going to extend the kthread worker API and will > need to call kthread_create_on_node() with

Re: [PATCH] memcg: mem_cgroup_migrate() may be called with irq disabled

On Mon, Jun 20, 2016 at 02:41:58PM -0400, Tejun Heo wrote: > mem_cgroup_migrate() uses local_irq_disable/enable() but can be called > with irq disabled from migrate_page_copy(). This ends up enabling irq > while holding a irq context lock triggering the following lockdep > warning. Fix it by

Re: [patch] ext4: underflow in alignment check

On Mon, Jun 20, 2016 at 06:02:04PM +0200, Jan Kara wrote: > On Thu 16-06-16 10:07:09, Dan Carpenter wrote: > > My static checker complains that this can underflow if arg is negative > > which is true. > > > > Signed-off-by: Dan Carpenter > > How come? (1 << 30) fits even into 32-bit signed

Re: [PATCH v9 04/12] kthread: Allow to call __kthread_create_on_node() with va_list args

On Thu, Jun 16, 2016 at 01:17:23PM +0200, Petr Mladek wrote: > kthread_create_on_node() implements a bunch of logic to create > the kthread. It is already called by kthread_create_on_cpu(). > > We are going to extend the kthread worker API and will > need to call kthread_create_on_node() with

Re: [PATCH] memcg: mem_cgroup_migrate() may be called with irq disabled

On Mon, Jun 20, 2016 at 02:41:58PM -0400, Tejun Heo wrote: > mem_cgroup_migrate() uses local_irq_disable/enable() but can be called > with irq disabled from migrate_page_copy(). This ends up enabling irq > while holding a irq context lock triggering the following lockdep > warning. Fix it by

Re: [PATCH v2 2/2] pci: host: new driver for Axis ARTPEC-6 PCIe controller

On Mon, May 9, 2016 at 7:49 AM, Niklas Cassel wrote: > From: Niklas Cassel > > The Axis ARTPEC-6 SoC integrates a PCIe controller from Synopsys. > This commit adds a new driver that provides the small glue > needed to use the existing Designware

Re: [PATCH v2 2/2] pci: host: new driver for Axis ARTPEC-6 PCIe controller

On Mon, May 9, 2016 at 7:49 AM, Niklas Cassel wrote: > From: Niklas Cassel > > The Axis ARTPEC-6 SoC integrates a PCIe controller from Synopsys. > This commit adds a new driver that provides the small glue > needed to use the existing Designware driver to make it work on > the Axis ARTPEC-6 SoC.

Re: [PATCH v2 4/5] ASoC: tpa6130a2: Add DAPM support

> + /* before widget power up */ > + if (SND_SOC_DAPM_EVENT_ON(event)) { > + /* Turn on the chip */ > + tpa6130a2_power(data, true); > + /* Sync the registers */ > + ret = regcache_sync(data->regmap); > + if (ret < 0) { > +

Re: [PATCH v2 4/5] ASoC: tpa6130a2: Add DAPM support

> + /* before widget power up */ > + if (SND_SOC_DAPM_EVENT_ON(event)) { > + /* Turn on the chip */ > + tpa6130a2_power(data, true); > + /* Sync the registers */ > + ret = regcache_sync(data->regmap); > + if (ret < 0) { > +

Re: [PATCH v3 01/15] phy: rockchip-emmc: give DLL some extra time to be ready

On Mon, Jun 20, 2016 at 12:30 PM, Doug Anderson wrote: > Hi, > > On Mon, Jun 20, 2016 at 12:23 PM, Guenter Roeck wrote: >> On Mon, Jun 20, 2016 at 10:56 AM, Douglas Anderson >> wrote: >>> From: Shawn Lin

Re: [PATCH v3 01/15] phy: rockchip-emmc: give DLL some extra time to be ready

On Mon, Jun 20, 2016 at 12:30 PM, Doug Anderson wrote: > Hi, > > On Mon, Jun 20, 2016 at 12:23 PM, Guenter Roeck wrote: >> On Mon, Jun 20, 2016 at 10:56 AM, Douglas Anderson >> wrote: >>> From: Shawn Lin >>> >>> According to the databook, 10.2us is the max time for dll to be ready to >>> work.

Re: [PATCH v2] x86/ptrace: Stop setting TS_COMPAT in ptrace code

On Mon, Jun 20, 2016 at 9:29 AM, Andy Lutomirski wrote: > Setting TS_COMPAT in ptrace is wrong: if we happen to do it during > syscall entry, then we'll confuse seccomp and audit. (The former > isn't a security problem: seccomp is currently entirely insecure if a > malicious

Re: [PATCH v2] x86/ptrace: Stop setting TS_COMPAT in ptrace code

On Mon, Jun 20, 2016 at 9:29 AM, Andy Lutomirski wrote: > Setting TS_COMPAT in ptrace is wrong: if we happen to do it during > syscall entry, then we'll confuse seccomp and audit. (The former > isn't a security problem: seccomp is currently entirely insecure if a > malicious ptracer is

[PATCH] ALSA: hda - Remove compilation warning

Remove the warning: warning: ‘err’ may be used uninitialized in this function [-Wmaybe-uninitialized] Signed-off-by: Helen Koike --- sound/hda/hdac_regmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/hda/hdac_regmap.c

[PATCH] ALSA: hda - Remove compilation warning

Remove the warning: warning: ‘err’ may be used uninitialized in this function [-Wmaybe-uninitialized] Signed-off-by: Helen Koike --- sound/hda/hdac_regmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/hda/hdac_regmap.c b/sound/hda/hdac_regmap.c index

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

On Mon, Jun 20 2016 at 2:31pm -0400, Kani, Toshimitsu wrote: > On Mon, 2016-06-20 at 14:00 -0400, Mike Snitzer wrote: > > > > I rebased your patches on linux-dm.git's 'for-next' (which includes what > > I've already staged for the 4.8 merge window).  And I folded/changed > >

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

On Mon, Jun 20 2016 at 2:31pm -0400, Kani, Toshimitsu wrote: > On Mon, 2016-06-20 at 14:00 -0400, Mike Snitzer wrote: > > > > I rebased your patches on linux-dm.git's 'for-next' (which includes what > > I've already staged for the 4.8 merge window).  And I folded/changed > > some of the DM

[PATCH] ASoC: max9877: Remove unused function declaration

Remove unused function declaration from header Signed-off-by: Helen Koike --- sound/soc/codecs/max9877.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/sound/soc/codecs/max9877.h b/sound/soc/codecs/max9877.h index 6da7229..368343f 100644 ---

[PATCH] ASoC: max9877: Remove unused function declaration

Remove unused function declaration from header Signed-off-by: Helen Koike --- sound/soc/codecs/max9877.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/sound/soc/codecs/max9877.h b/sound/soc/codecs/max9877.h index 6da7229..368343f 100644 --- a/sound/soc/codecs/max9877.h +++

Re: [PATCH v3 05/15] phy: rockchip-emmc: Increase lock time allowance

On Mon, Jun 20, 2016 at 12:36 PM, Doug Anderson wrote: > Hi, > > On Mon, Jun 20, 2016 at 12:29 PM, Guenter Roeck wrote: >> On Mon, Jun 20, 2016 at 10:56 AM, Douglas Anderson >> wrote: >>> Previous PHY code waited a fixed amount of

Re: [PATCH v3 05/15] phy: rockchip-emmc: Increase lock time allowance

On Mon, Jun 20, 2016 at 12:36 PM, Doug Anderson wrote: > Hi, > > On Mon, Jun 20, 2016 at 12:29 PM, Guenter Roeck wrote: >> On Mon, Jun 20, 2016 at 10:56 AM, Douglas Anderson >> wrote: >>> Previous PHY code waited a fixed amount of time for the DLL to lock at >>> power on time. Unfortunately,

Re: [PATCH v3 01/15] phy: rockchip-emmc: give DLL some extra time to be ready

Hi, On Mon, Jun 20, 2016 at 12:36 PM, Guenter Roeck wrote: > On Mon, Jun 20, 2016 at 12:30 PM, Doug Anderson wrote: >> Hi, >> >> On Mon, Jun 20, 2016 at 12:23 PM, Guenter Roeck wrote: >>> On Mon, Jun 20, 2016 at 10:56 AM, Douglas

Re: [PATCH v3 01/15] phy: rockchip-emmc: give DLL some extra time to be ready

Hi, On Mon, Jun 20, 2016 at 12:36 PM, Guenter Roeck wrote: > On Mon, Jun 20, 2016 at 12:30 PM, Doug Anderson wrote: >> Hi, >> >> On Mon, Jun 20, 2016 at 12:23 PM, Guenter Roeck wrote: >>> On Mon, Jun 20, 2016 at 10:56 AM, Douglas Anderson >>> wrote: From: Shawn Lin According

Re: [PATCH v3 05/15] phy: rockchip-emmc: Increase lock time allowance

Hi, On Mon, Jun 20, 2016 at 12:29 PM, Guenter Roeck wrote: > On Mon, Jun 20, 2016 at 10:56 AM, Douglas Anderson > wrote: >> Previous PHY code waited a fixed amount of time for the DLL to lock at >> power on time. Unfortunately, the time for the DLL to

Re: [PATCH v3 05/15] phy: rockchip-emmc: Increase lock time allowance

Hi, On Mon, Jun 20, 2016 at 12:29 PM, Guenter Roeck wrote: > On Mon, Jun 20, 2016 at 10:56 AM, Douglas Anderson > wrote: >> Previous PHY code waited a fixed amount of time for the DLL to lock at >> power on time. Unfortunately, the time for the DLL to lock is actually >> a bit more dynamic and

Re: [PATCH] blktrace: avoid using timespec

Arnd Bergmann writes: > On Monday, June 20, 2016 10:59:14 AM CEST Jeff Moyer wrote: >> struct timespec abs_start_time; [snip] > I assume that abs_start_time is a timespec, implying that It is. You didn't have to assume that, though, as I also included its definition

Re: [PATCH] blktrace: avoid using timespec

Arnd Bergmann writes: > On Monday, June 20, 2016 10:59:14 AM CEST Jeff Moyer wrote: >> struct timespec abs_start_time; [snip] > I assume that abs_start_time is a timespec, implying that It is. You didn't have to assume that, though, as I also included its definition above. ;-) > Ok.

<    3   4   5   6   7   8   9   10   11   12   >