Re: [RFC PATCH v2 3/7] sched/idle: Add poll before enter real idle path

on 2017/8/29 20:45, Peter Zijlstra wrote: On Tue, Aug 29, 2017 at 11:46:37AM +, Yang Zhang wrote: Add poll in do_idle. For UP VM, if there are running task, it will not goes into idle path, so we only enable poll in SMP VM. Signed-off-by: Yang Zhang

Re: [RFC PATCH v2 3/7] sched/idle: Add poll before enter real idle path

on 2017/8/29 20:45, Peter Zijlstra wrote: On Tue, Aug 29, 2017 at 11:46:37AM +, Yang Zhang wrote: Add poll in do_idle. For UP VM, if there are running task, it will not goes into idle path, so we only enable poll in SMP VM. Signed-off-by: Yang Zhang Signed-off-by: Quan Xu Broken SoB

[PATCH v2] arm64: fix unwind_frame() for filtered out fn for function graph tracing

do_task_stat() calls get_wchan(), which further does unbind_frame(). unbind_frame() restores frame->pc to original value in case function graph tracer has modified a return address (LR) in a stack frame to hook a function return. However, if function graph tracer has hit a filtered function, then

[PATCH v2] arm64: fix unwind_frame() for filtered out fn for function graph tracing

do_task_stat() calls get_wchan(), which further does unbind_frame(). unbind_frame() restores frame->pc to original value in case function graph tracer has modified a return address (LR) in a stack frame to hook a function return. However, if function graph tracer has hit a filtered function, then

Re: [PATCH v7 9/9] sparc64: Add support for ADI (Application Data Integrity)

Hi Khalid, > On Aug 30, 2017, at 3:27 PM, Khalid Aziz wrote: > > Hi Anthony, > > Thanks for taking the time to provide feedback. My comments inline below. > > On 08/25/2017 04:31 PM, Anthony Yznaga wrote: >>> On Aug 9, 2017, at 2:26 PM, Khalid Aziz

Re: [PATCH v7 9/9] sparc64: Add support for ADI (Application Data Integrity)

Hi Khalid, > On Aug 30, 2017, at 3:27 PM, Khalid Aziz wrote: > > Hi Anthony, > > Thanks for taking the time to provide feedback. My comments inline below. > > On 08/25/2017 04:31 PM, Anthony Yznaga wrote: >>> On Aug 9, 2017, at 2:26 PM, Khalid Aziz wrote: >>> ..deleted.. >>>

[PATCH v2] leds: pca955x: Don't invert requested value in pca955x_gpio_set_value()

The PCA9552 lines can be used either for driving LEDs or as GPIOs. The manual states that for LEDs, the operation is open-drain: The LSn LED select registers determine the source of the LED data. 00 = output is set LOW (LED on) 01 = output is set high-impedance

[PATCH v2] leds: pca955x: Don't invert requested value in pca955x_gpio_set_value()

The PCA9552 lines can be used either for driving LEDs or as GPIOs. The manual states that for LEDs, the operation is open-drain: The LSn LED select registers determine the source of the LED data. 00 = output is set LOW (LED on) 01 = output is set high-impedance

Re: [PATCH] md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list

On Mon, Aug 28, 2017 at 08:01:59PM +0800, Dennis Yang wrote: > break_stripe_batch_list() did not preserve STRIPE_ON_UNPLUG_LIST which is > set when a stripe_head gets queued to the stripe_head list maintained by > raid5_plug_cb and waiting for releasing after blk_unplug(). > > In

Re: [PATCH] md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list

On Mon, Aug 28, 2017 at 08:01:59PM +0800, Dennis Yang wrote: > break_stripe_batch_list() did not preserve STRIPE_ON_UNPLUG_LIST which is > set when a stripe_head gets queued to the stripe_head list maintained by > raid5_plug_cb and waiting for releasing after blk_unplug(). > > In

SMB3 security upgrade -fix warning messages on CIFS mount when mounting to older servers

There have been some questions about the upgrade of the default client dialect for cifs.ko from CIFS (SMB1) to SMB3 (discussed in earlier email threads), but also requests for clarification of some of the warning messages relating to the default dialect upgrade. While additional changes can be

SMB3 security upgrade -fix warning messages on CIFS mount when mounting to older servers

There have been some questions about the upgrade of the default client dialect for cifs.ko from CIFS (SMB1) to SMB3 (discussed in earlier email threads), but also requests for clarification of some of the warning messages relating to the default dialect upgrade. While additional changes can be

Re: mmotm 2017-08-31-16-13 uploaded (x86/kernel/eisa.c)

On 08/31/17 16:13, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2017-08-31-16-13 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my

Re: mmotm 2017-08-31-16-13 uploaded (x86/kernel/eisa.c)

On 08/31/17 16:13, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2017-08-31-16-13 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my

Re: [RFC/PATCH] drivers/of/platform: Add powerpc 4xx embedded busses to default list

On Fri, Sep 01, 2017 at 01:51:01PM +1000, Benjamin Herrenschmidt wrote: > This allow to (slowly) migrate those embedded platforms > to of_platform_default_populate() > > Signed-off-by: Benjamin Herrenschmidt > --- > > I'm here to collect acks (or comments :-) I'd like

Re: [RFC/PATCH] drivers/of/platform: Add powerpc 4xx embedded busses to default list

On Fri, Sep 01, 2017 at 01:51:01PM +1000, Benjamin Herrenschmidt wrote: > This allow to (slowly) migrate those embedded platforms > to of_platform_default_populate() > > Signed-off-by: Benjamin Herrenschmidt > --- > > I'm here to collect acks (or comments :-) I'd like this to go via > the

Re: [PATCH 26/31] staging/comedi/das16: Make timer initialization unconditional

On Thu, Aug 31, 2017 at 04:29:38PM -0700, Kees Cook wrote: > With timer initialization made unconditional, there is no reason to > make del_timer_sync() calls conditionally, there by removing the test > of the .data field. > > Cc: Ian Abbott > Cc: H Hartley Sweeten

Re: [PATCH 26/31] staging/comedi/das16: Make timer initialization unconditional

On Thu, Aug 31, 2017 at 04:29:38PM -0700, Kees Cook wrote: > With timer initialization made unconditional, there is no reason to > make del_timer_sync() calls conditionally, there by removing the test > of the .data field. > > Cc: Ian Abbott > Cc: H Hartley Sweeten > Cc: Greg Kroah-Hartman >

Re: [PATCH] uprobe: Warn if unable to install breakpoint

"Naveen N. Rao" writes: > When we try to install a uprobe breakpoint in uprobe_mmap(), we ignore > all errors encountered in the process per this comment at the top of > the function: > /* > * Called from mmap_region/vma_adjust with mm->mmap_sem

Re: [PATCH] uprobe: Warn if unable to install breakpoint

"Naveen N. Rao" writes: > When we try to install a uprobe breakpoint in uprobe_mmap(), we ignore > all errors encountered in the process per this comment at the top of > the function: > /* > * Called from mmap_region/vma_adjust with mm->mmap_sem acquired. > * > * Currently we

Re: [PATCH 13/31] timer: Remove meaningless .data/.function assignments

On Thu, Aug 31, 2017 at 04:29:25PM -0700, Kees Cook wrote: > Several timer users needlessly reset their .function/.data fields during > their timer callback, but nothing else changes them. Some users do not > use their .data field at all. Each instance is removed here. > > Cc: Krzysztof Halasa

Re: [PATCH 13/31] timer: Remove meaningless .data/.function assignments

On Thu, Aug 31, 2017 at 04:29:25PM -0700, Kees Cook wrote: > Several timer users needlessly reset their .function/.data fields during > their timer callback, but nothing else changes them. Some users do not > use their .data field at all. Each instance is removed here. > > Cc: Krzysztof Halasa >

Re: [PATCH] kernfs: checking for IS_ERR() instead of NULL

On Thu, Aug 31, 2017 at 01:56:40PM -0600, Jens Axboe wrote: > On 08/31/2017 10:52 AM, Greg Kroah-Hartman wrote: > > On Wed, Aug 30, 2017 at 05:04:56PM +0300, Dan Carpenter wrote: > >> The kernfs_get_inode() returns NULL on error, it never returns error > >> pointers. > >> > >> Fixes: aa8188253474

Re: [PATCH] kernfs: checking for IS_ERR() instead of NULL

On Thu, Aug 31, 2017 at 01:56:40PM -0600, Jens Axboe wrote: > On 08/31/2017 10:52 AM, Greg Kroah-Hartman wrote: > > On Wed, Aug 30, 2017 at 05:04:56PM +0300, Dan Carpenter wrote: > >> The kernfs_get_inode() returns NULL on error, it never returns error > >> pointers. > >> > >> Fixes: aa8188253474

Re: [PATCH 4.9 00/12] 4.9.47-stable review

On Thu, Aug 31, 2017 at 01:08:33PM -0600, Shuah Khan wrote: > On 08/31/2017 09:44 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.47 release. > > There are 12 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.9 00/12] 4.9.47-stable review

On Thu, Aug 31, 2017 at 01:08:33PM -0600, Shuah Khan wrote: > On 08/31/2017 09:44 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.47 release. > > There are 12 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH 3/4] x86/apic: Introduce the per vector cpumask array

This array is a bitmap for sorting the number of vectors assigned on each CPU, thus to quickly retrieve the CPU which have assigned the least amount of vectors, then choose that CPU as a hint to spread the vectors among multiple CPUs. Cc: Thomas Gleixner Cc: Ingo Molnar

[PATCH 3/4] x86/apic: Introduce the per vector cpumask array

This array is a bitmap for sorting the number of vectors assigned on each CPU, thus to quickly retrieve the CPU which have assigned the least amount of vectors, then choose that CPU as a hint to spread the vectors among multiple CPUs. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin"

[PATCH 1/4][RFC v2] x86/apic: Extend the defination for vector_irq

Introduce a variable inside the vector_irq, to record the number of vectors assigned per CPU. This is to prepare for the vector spreading work. No functional change. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: "Rafael J.

Re: [PATCH 3.18 00/24] 3.18.69-stable review

On Thu, Aug 31, 2017 at 07:30:37PM -0700, Guenter Roeck wrote: > On Thu, Aug 31, 2017 at 05:43:36PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.69 release. > > There are 24 patches in this series, all will be posted as a response > > to this one.

[PATCH 4/4][RFC v2] x86/apic: Spread the vectors by choosing the idlest CPU

This is the major logic to spread the vectors on different CPUs. The main idea is to choose the 'idlest' CPU which has assigned the least number of vectors as the candidate/hint for the vector allocation domain, in the hope that the vector allocation domain could leverage this hint to generate

[PATCH 1/4][RFC v2] x86/apic: Extend the defination for vector_irq

Introduce a variable inside the vector_irq, to record the number of vectors assigned per CPU. This is to prepare for the vector spreading work. No functional change. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: "Rafael J. Wysocki" Cc: Len Brown Cc: Dan Williams

Re: [PATCH 3.18 00/24] 3.18.69-stable review

On Thu, Aug 31, 2017 at 07:30:37PM -0700, Guenter Roeck wrote: > On Thu, Aug 31, 2017 at 05:43:36PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.69 release. > > There are 24 patches in this series, all will be posted as a response > > to this one.

[PATCH 4/4][RFC v2] x86/apic: Spread the vectors by choosing the idlest CPU

This is the major logic to spread the vectors on different CPUs. The main idea is to choose the 'idlest' CPU which has assigned the least number of vectors as the candidate/hint for the vector allocation domain, in the hope that the vector allocation domain could leverage this hint to generate

[PATCH 2/4][RFC v2] x86/apic: Record the number of vectors assigned on a CPU

Update the number of vectors assigned on each CPU during vector allocation/free process. This is to prepare for the vector spreading work that, we can find out the CPU with least vectors assigned. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin"

[PATCH 2/4][RFC v2] x86/apic: Record the number of vectors assigned on a CPU

Update the number of vectors assigned on each CPU during vector allocation/free process. This is to prepare for the vector spreading work that, we can find out the CPU with least vectors assigned. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc: "Rafael J. Wysocki" Cc: Len Brown

[PATCH 0/4][RFC v2] x86/irq: Spread vectors on different CPUs

This patch set tries to spread the vectors assigned on different CPUs as much as possible. The requirement to do this came from a hibernation issue encountered on a vector-heavily-used system which has many multi queue devices on that, the CPUs failed to be brought offline due to insufficient free

[PATCH 0/4][RFC v2] x86/irq: Spread vectors on different CPUs

This patch set tries to spread the vectors assigned on different CPUs as much as possible. The requirement to do this came from a hibernation issue encountered on a vector-heavily-used system which has many multi queue devices on that, the CPUs failed to be brought offline due to insufficient free

Re: [PATCH 2/2] mm, page_owner: Skip unnecessary stack_trace entries

On 8/31/2017 1:04 PM, Vlastimil Babka wrote: On 08/30/2017 09:32 AM, Prakash Gupta wrote: The page_owner stacktrace always begin as follows: [] save_stack+0x40/0xc8 [] __set_page_owner+0x3c/0x6c Hmm, on x86_64 it looks like this: save_stack_trace+0x16/0x20 save_stack+0x43/0xe0

Re: [PATCH 2/2] mm, page_owner: Skip unnecessary stack_trace entries

On 8/31/2017 1:04 PM, Vlastimil Babka wrote: On 08/30/2017 09:32 AM, Prakash Gupta wrote: The page_owner stacktrace always begin as follows: [] save_stack+0x40/0xc8 [] __set_page_owner+0x3c/0x6c Hmm, on x86_64 it looks like this: save_stack_trace+0x16/0x20 save_stack+0x43/0xe0

linux-next: manual merge of the scsi-mkp tree with Linus' tree

Hi all, Today's linux-next merge of the scsi-mkp tree got a conflict in: include/scsi/scsi_cmnd.h between commit: 70e42fd02c46 ("scsi: sd_zbc: Write unlock zone from sd_uninit_cmnd()") from Linus' tree and commit: 64104f703212 ("scsi: Call scsi_initialize_rq() for filesystem requests")

linux-next: manual merge of the scsi-mkp tree with Linus' tree

Hi all, Today's linux-next merge of the scsi-mkp tree got a conflict in: include/scsi/scsi_cmnd.h between commit: 70e42fd02c46 ("scsi: sd_zbc: Write unlock zone from sd_uninit_cmnd()") from Linus' tree and commit: 64104f703212 ("scsi: Call scsi_initialize_rq() for filesystem requests")

Re: [PATCH v2] PCIe AER: report uncorrectable errors only to the functions that logged the errors

On Thu, Aug 31, 2017 at 03:03:44PM -0500, Bjorn Helgaas wrote: > On Fri, Aug 18, 2017 at 12:02:21PM +0100, Gabriele Paoloni wrote: > > Currently if an uncorrectable error is reported by an EP the AER > > driver walks over all the devices connected to the upstream port > > bus and in turns call the

Re: [PATCH v2] PCIe AER: report uncorrectable errors only to the functions that logged the errors

On Thu, Aug 31, 2017 at 03:03:44PM -0500, Bjorn Helgaas wrote: > On Fri, Aug 18, 2017 at 12:02:21PM +0100, Gabriele Paoloni wrote: > > Currently if an uncorrectable error is reported by an EP the AER > > driver walks over all the devices connected to the upstream port > > bus and in turns call the

Re: [patch 00/29] lockup_detector: Cure hotplug deadlocks and replace duct tape

On Thu, 31 Aug 2017 18:10:14 -0400 Don Zickus wrote: > On Thu, Aug 31, 2017 at 09:15:58AM +0200, Thomas Gleixner wrote: > > The lockup detector is broken is several ways: > > > > - It's deadlock prone vs. CPU hotplug in various ways. Some of these > > are due to

Re: [patch 00/29] lockup_detector: Cure hotplug deadlocks and replace duct tape

On Thu, 31 Aug 2017 18:10:14 -0400 Don Zickus wrote: > On Thu, Aug 31, 2017 at 09:15:58AM +0200, Thomas Gleixner wrote: > > The lockup detector is broken is several ways: > > > > - It's deadlock prone vs. CPU hotplug in various ways. Some of these > > are due to recursive

[PATCH] cpuidle: fix broadcast control when broadcast can not be entered

When failing to enter broadcast timer mode for an idle state that requires it, a new state is selected that does not require broadcast, but the broadcast variable remains set. This causes tick_broadcast_exit to be called despite not having entered broadcast mode. This causes the

[PATCH] cpuidle: fix broadcast control when broadcast can not be entered

When failing to enter broadcast timer mode for an idle state that requires it, a new state is selected that does not require broadcast, but the broadcast variable remains set. This causes tick_broadcast_exit to be called despite not having entered broadcast mode. This causes the

[ANNOUNCE]: SCST 3.3 pre-release freeze

Hi All, I'm glad to announce SCST 3.3 pre-release code freeze in the SCST SVN branch 3.3.x. You can get it by command: $ svn co https://scst.svn.sourceforge.net/svnroot/scst/branches/3.3.x It is going to be released after few weeks of testing, if no significant issues found. SCST is

[ANNOUNCE]: SCST 3.3 pre-release freeze

Hi All, I'm glad to announce SCST 3.3 pre-release code freeze in the SCST SVN branch 3.3.x. You can get it by command: $ svn co https://scst.svn.sourceforge.net/svnroot/scst/branches/3.3.x It is going to be released after few weeks of testing, if no significant issues found. SCST is

Re: [PATCH 0/2] start using spin primitives in sched and locking

Hi guys, Any thoughts on these? Thanks, Nick On Sun, 20 Aug 2017 19:25:00 +1000 Nicholas Piggin wrote: > Nicholas Piggin (2): > locking: Use spin primitives for busy loops > sched/idle: Use spin loop primitives for polling idle > > include/linux/bit_spinlock.h

Re: [PATCH 0/2] start using spin primitives in sched and locking

Hi guys, Any thoughts on these? Thanks, Nick On Sun, 20 Aug 2017 19:25:00 +1000 Nicholas Piggin wrote: > Nicholas Piggin (2): > locking: Use spin primitives for busy loops > sched/idle: Use spin loop primitives for polling idle > > include/linux/bit_spinlock.h| 5 ++--- >

[RFC] tools: selftests: psock_tpacket: skip un-supported tpacket_v3 test

The TPACKET_V3 test of PACKET_TX_RING will fail with kernel version lower than v4.11. Supported code of tx ring was add with commit id <7f953ab2ba46: af_packet: TX_RING support for TPACKET_V3> at Jan. 3 of 2017. So skip this item test instead of reporting failing for old kernels. Signed-off-by:

[RFC] tools: selftests: psock_tpacket: skip un-supported tpacket_v3 test

The TPACKET_V3 test of PACKET_TX_RING will fail with kernel version lower than v4.11. Supported code of tx ring was add with commit id <7f953ab2ba46: af_packet: TX_RING support for TPACKET_V3> at Jan. 3 of 2017. So skip this item test instead of reporting failing for old kernels. Signed-off-by:

[RFC/PATCH] drivers/of/platform: Add powerpc 4xx embedded busses to default list

This allow to (slowly) migrate those embedded platforms to of_platform_default_populate() Signed-off-by: Benjamin Herrenschmidt --- I'm here to collect acks (or comments :-) I'd like this to go via the powerpc tree along with the patches converting some of the

[RFC/PATCH] drivers/of/platform: Add powerpc 4xx embedded busses to default list

This allow to (slowly) migrate those embedded platforms to of_platform_default_populate() Signed-off-by: Benjamin Herrenschmidt --- I'm here to collect acks (or comments :-) I'd like this to go via the powerpc tree along with the patches converting some of the platforms. I'll be adding more bus

Re: virtio_net: ethtool supported link modes

On 2017年09月01日 01:04, Radu Rendec wrote: Hello, Looking at the code in virtnet_set_link_ksettings, it seems the speed and duplex can be set to any valid value. The driver will "remember" them and report them back in virtnet_get_link_ksettings. However, the supported link modes

Re: virtio_net: ethtool supported link modes

On 2017年09月01日 01:04, Radu Rendec wrote: Hello, Looking at the code in virtnet_set_link_ksettings, it seems the speed and duplex can be set to any valid value. The driver will "remember" them and report them back in virtnet_get_link_ksettings. However, the supported link modes

high latency in CFS when disable autogroup, bug or not?

I have a programe to test CFS latency or fairness on high load, the test shows CFS has high latency when disable autogroup the program is in https://gist.github.com/anonymous/af21ae289cfa5c6310eeac73b7a478ff. the programe creates many threads, every thread does thing like: do { now

high latency in CFS when disable autogroup, bug or not?

I have a programe to test CFS latency or fairness on high load, the test shows CFS has high latency when disable autogroup the program is in https://gist.github.com/anonymous/af21ae289cfa5c6310eeac73b7a478ff. the programe creates many threads, every thread does thing like: do { now

Re: [PATCH v4 00/14] mpt3sas driver NVMe support:

Hi Suganath, > Let me explain - NVME device fast path is possible in two ways. IEEE > SGL and PRP SGL. Due to h/w constraint we choose IEEE SGL only for > smaller IO size. Both above is true h/w Fast Path and no firmware > involvement. > Agree with you. We are planning to see if we can keep

Re: [PATCH v4 00/14] mpt3sas driver NVMe support:

Hi Suganath, > Let me explain - NVME device fast path is possible in two ways. IEEE > SGL and PRP SGL. Due to h/w constraint we choose IEEE SGL only for > smaller IO size. Both above is true h/w Fast Path and no firmware > involvement. > Agree with you. We are planning to see if we can keep

Re: [PATCH 1/3] media: atmel-isc: Not support RBG format from sensor.

Hi Hans, On 2017/8/24 14:41, Hans Verkuil wrote: On 08/24/2017 08:25 AM, Yang, Wenyou wrote: On 2017/8/23 18:37, Hans Verkuil wrote: On 08/22/17 09:30, wenyou.y...@microchip.com wrote: Hi Hans, -Original Message- From: Hans Verkuil [mailto:hverk...@xs4all.nl] Sent: 2017年8月22日

Re: [PATCH 1/3] media: atmel-isc: Not support RBG format from sensor.

Hi Hans, On 2017/8/24 14:41, Hans Verkuil wrote: On 08/24/2017 08:25 AM, Yang, Wenyou wrote: On 2017/8/23 18:37, Hans Verkuil wrote: On 08/22/17 09:30, wenyou.y...@microchip.com wrote: Hi Hans, -Original Message- From: Hans Verkuil [mailto:hverk...@xs4all.nl] Sent: 2017年8月22日

[PATCH 4/4] media: atmel-isc: Rework the format list

To improve the readability of code, split the format array into two, one for the format description, other for the register configuration. Meanwhile, add the flag member to indicate the format can be achieved from the sensor or be produced by the controller, and rename members related to the

[PATCH 4/4] media: atmel-isc: Rework the format list

To improve the readability of code, split the format array into two, one for the format description, other for the register configuration. Meanwhile, add the flag member to indicate the format can be achieved from the sensor or be produced by the controller, and rename members related to the

[PATCH 2/4] media: atmel-isc: Add prepare and unprepare ops

A software write operation to the ISC_CLKEN or ISC_CLKDIS register requires double clock domain synchronization and is not permitted when the ISC_SR.SIP is asserted. So add the .prepare and .unprepare ops to make sure the ISC_CLKSR.SIP is unasserted before the write operation to the ISC_CLKEN or

[PATCH 2/4] media: atmel-isc: Add prepare and unprepare ops

A software write operation to the ISC_CLKEN or ISC_CLKDIS register requires double clock domain synchronization and is not permitted when the ISC_SR.SIP is asserted. So add the .prepare and .unprepare ops to make sure the ISC_CLKSR.SIP is unasserted before the write operation to the ISC_CLKEN or

[PATCH 3/4] media: atmel-isc: Enable the clocks during probe

To meet the relationship, enable the HCLOCK and ispck during the device probe, "isc_pck frequency is less than or equal to isc_ispck, and isc_ispck is greater than or equal to HCLOCK." Meanwhile, call the pm_runtime_enable() in the right place. Signed-off-by: Wenyou Yang

[PATCH 3/4] media: atmel-isc: Enable the clocks during probe

To meet the relationship, enable the HCLOCK and ispck during the device probe, "isc_pck frequency is less than or equal to isc_ispck, and isc_ispck is greater than or equal to HCLOCK." Meanwhile, call the pm_runtime_enable() in the right place. Signed-off-by: Wenyou Yang ---

[PATCH 1/4] media: atmel_isc: Add spin lock for clock enable ops

Add the spin lock for the clock enable and disable operations. Signed-off-by: Wenyou Yang --- drivers/media/platform/atmel/atmel-isc.c | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/drivers/media/platform/atmel/atmel-isc.c

[PATCH 1/4] media: atmel_isc: Add spin lock for clock enable ops

Add the spin lock for the clock enable and disable operations. Signed-off-by: Wenyou Yang --- drivers/media/platform/atmel/atmel-isc.c | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/drivers/media/platform/atmel/atmel-isc.c

[PATCH 0/4] media: atmel-isc: Rework the format list and the clock

To improve the readability of code, rework the format list table, split the format array into two. And fix the clock operation issue. Wenyou Yang (4): media: atmel_isc: Add spin lock for clock enable ops media: atmel-isc: Add prepare and unprepare ops media: atmel-isc: Enable the clocks

[PATCH 0/4] media: atmel-isc: Rework the format list and the clock

To improve the readability of code, rework the format list table, split the format array into two. And fix the clock operation issue. Wenyou Yang (4): media: atmel_isc: Add spin lock for clock enable ops media: atmel-isc: Add prepare and unprepare ops media: atmel-isc: Enable the clocks

Re: [PATCH 1/3] dmaengine: sun6i: Correct DMA support on H3

On Donnerstag, 31. August 2017 16:51:35 CEST Maxime Ripard wrote: > Hi, > > On Thu, Aug 31, 2017 at 01:36:07AM +0200, Stefan Brüns wrote: > > +/* Between SoC generations, there are some significant differences: > > + * - A23 added a clock gate register > > + * - the H3 burst length field has a

Re: [PATCH 1/3] dmaengine: sun6i: Correct DMA support on H3

On Donnerstag, 31. August 2017 16:51:35 CEST Maxime Ripard wrote: > Hi, > > On Thu, Aug 31, 2017 at 01:36:07AM +0200, Stefan Brüns wrote: > > +/* Between SoC generations, there are some significant differences: > > + * - A23 added a clock gate register > > + * - the H3 burst length field has a

Re: [PATCH V2] spmi: pmic-arb: Enforce the ownership check optionally

On Thu, Aug 31, 2017 at 06:30:48PM -0700, Stephen Boyd wrote: > On 08/31, Shawn Guo wrote: > > On Wed, Aug 30, 2017 at 02:02:03PM -0700, Stephen Boyd wrote: > > > On 08/26, Shawn Guo wrote: > > > > On Fri, Aug 25, 2017 at 04:18:18PM -0700, Stephen Boyd wrote: > > > > > > > > > > Right. Does the

Re: [PATCH V2] spmi: pmic-arb: Enforce the ownership check optionally

On Thu, Aug 31, 2017 at 06:30:48PM -0700, Stephen Boyd wrote: > On 08/31, Shawn Guo wrote: > > On Wed, Aug 30, 2017 at 02:02:03PM -0700, Stephen Boyd wrote: > > > On 08/26, Shawn Guo wrote: > > > > On Fri, Aug 25, 2017 at 04:18:18PM -0700, Stephen Boyd wrote: > > > > > > > > > > Right. Does the

[PATCH v2 7/7] asm-generic: numa: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in generic situation is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang

[PATCH v2 7/7] asm-generic: numa: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in generic situation is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang Cc: Arnd Bergmann Cc:

[PATCH v2 6/7] tile/topology: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in tile platform is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang

[PATCH v2 3/7] s390/topology: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in S390 platform is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang

[PATCH v2 6/7] tile/topology: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in tile platform is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang Acked-by: Chris Metcalf Cc: Chris

[PATCH v2 3/7] s390/topology: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in S390 platform is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang Acked-by: Heiko Carstens Cc:

[PATCH v2 2/7] MIPS: numa: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macros in both IP27 and Loongson64 are unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang

[PATCH v2 2/7] MIPS: numa: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macros in both IP27 and Loongson64 are unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang Cc: Ralf Baechle Cc:

[PATCH v2 5/7] sparc64/topology: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in SPARC64 platform is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang

[PATCH v2 5/7] sparc64/topology: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in SPARC64 platform is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang Acked-by: David S. Miller Cc:

[PATCH v2 0/7] Remove the parent_node() for each arch

Changelog: v1 --> v2: --Remove the patches which have been add to each arch tree individually. [01/11] arm64 ...Has been added to arm64 tree, Queued for 4.14 [03/11] metag ...Has been added to the -mm tree [05/11] powerpc ...Has been added to the powerpc tree

[PATCH v2 0/7] Remove the parent_node() for each arch

Changelog: v1 --> v2: --Remove the patches which have been add to each arch tree individually. [01/11] arm64 ...Has been added to arm64 tree, Queued for 4.14 [03/11] metag ...Has been added to the -mm tree [05/11] powerpc ...Has been added to the powerpc tree

[PATCH v2 1/7] ia64: topology: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in IA64(Itanium) platform is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang

[PATCH v2 1/7] ia64: topology: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in IA64(Itanium) platform is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang Cc: Tony Luck Cc:

[PATCH v2 4/7] sh/numa: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in SUPERH platform is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang

[PATCH v2 4/7] sh/numa: Remove the unused parent_node() macro

Commit a7be6e5a7f8d ("mm: drop useless local parameters of __register_one_node()") removes the last user of parent_node(). The parent_node() macro in SUPERH platform is unnecessary. Remove it for cleanup. Reported-by: Michael Ellerman Signed-off-by: Dou Liyang Cc: Yoshinori Sato Cc: Rich

RE: [PATCHv4 1/9] irqchip/ls-scfg-msi: fix typo of MSI compatible strings

Hi Marc, > -Original Message- > From: Marc Zyngier [mailto:marc.zyng...@arm.com] > Sent: 2017年8月31日 23:16 > To: Z.q. Hou ; linux-arm-ker...@lists.infradead.org; > devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; t...@linutronix.de; > ja...@lakedaemon.net;

RE: [PATCHv4 1/9] irqchip/ls-scfg-msi: fix typo of MSI compatible strings

Hi Marc, > -Original Message- > From: Marc Zyngier [mailto:marc.zyng...@arm.com] > Sent: 2017年8月31日 23:16 > To: Z.q. Hou ; linux-arm-ker...@lists.infradead.org; > devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; t...@linutronix.de; > ja...@lakedaemon.net; robh...@kernel.org;

[PATCH v3 3/4] phy: rcar-gen3-usb2: add SoC-specific parameter for dedicated pins

This patch adds SoC-specific parameter to avoid reading/writing specific registers wrongly if this driver runs on a SoC which doesn't have dedicated pins (e.g. R-Car D3). Signed-off-by: Yoshihiro Shimoda --- drivers/phy/renesas/phy-rcar-gen3-usb2.c | 24

[PATCH v3 3/4] phy: rcar-gen3-usb2: add SoC-specific parameter for dedicated pins

This patch adds SoC-specific parameter to avoid reading/writing specific registers wrongly if this driver runs on a SoC which doesn't have dedicated pins (e.g. R-Car D3). Signed-off-by: Yoshihiro Shimoda --- drivers/phy/renesas/phy-rcar-gen3-usb2.c | 24 +++- 1 file changed,

[PATCH v3 0/4] phy: rcar-gen3-usb2: add support for r8a77995

This patch set is based on the latest phy.git / next branch (the commit id = d9c51f4c53ae2af03aa8bd001d46f21b0adcdab8). After this patch set is applied, a usb 2.0 host node that is combined with usb 2.0 peripheral needs 'dr_mode = "otg";' property. Changes from v2: - Revise the commit log

[PATCH v3 0/4] phy: rcar-gen3-usb2: add support for r8a77995

This patch set is based on the latest phy.git / next branch (the commit id = d9c51f4c53ae2af03aa8bd001d46f21b0adcdab8). After this patch set is applied, a usb 2.0 host node that is combined with usb 2.0 peripheral needs 'dr_mode = "otg";' property. Changes from v2: - Revise the commit log

  1   2   3   4   5   6   7   8   9   10   >