Re: [PATCH v6 1/1] acpi: apei: Enable APEI multiple GHES source to share a single external IRQ

On Wed, Jul 26, 2017 at 08:57:03PM +0200, Rafael J. Wysocki wrote: > > Should I apply this or will Tony do that? > > So am I suppsed to drop this? Well, as suggested in another mail, I think it'll be best if Tony and I put ourselves as reviewers for the APEI crap and you still collect it.

Re: [PATCH v6 1/1] acpi: apei: Enable APEI multiple GHES source to share a single external IRQ

On Wed, Jul 26, 2017 at 08:57:03PM +0200, Rafael J. Wysocki wrote: > > Should I apply this or will Tony do that? > > So am I suppsed to drop this? Well, as suggested in another mail, I think it'll be best if Tony and I put ourselves as reviewers for the APEI crap and you still collect it.

Seek a machine named Thinkpad x121e (AMD E-450 APU)

Hi all, Does somebody have the *Thinkpad x121e (AMD E-450 APU)*? I need to do an regression test for a patchset[1]. This test is simple, but really special and only be reproduced in Thinkpad x121e. I have tested it in Thinkpad s430, Lenovo M4340 and Lenovo M4300. Unfortunately, I failed. I

Seek a machine named Thinkpad x121e (AMD E-450 APU)

Hi all, Does somebody have the *Thinkpad x121e (AMD E-450 APU)*? I need to do an regression test for a patchset[1]. This test is simple, but really special and only be reproduced in Thinkpad x121e. I have tested it in Thinkpad s430, Lenovo M4340 and Lenovo M4300. Unfortunately, I failed. I

Re: [PATCH 0/3] EDAC: Convert ghes_edac to a normal module

On Wed, Jul 26, 2017 at 10:48:24AM +0200, Borislav Petkov wrote: > EDAC: Add edac_pr_err/info macros > ACPI/GHES: Add an EDAC notifier chain > EDAC, ghes: Make it a proper module Pushed here: https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=ghes -- Regards/Gruss,

Re: [PATCH 0/3] EDAC: Convert ghes_edac to a normal module

On Wed, Jul 26, 2017 at 10:48:24AM +0200, Borislav Petkov wrote: > EDAC: Add edac_pr_err/info macros > ACPI/GHES: Add an EDAC notifier chain > EDAC, ghes: Make it a proper module Pushed here: https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=ghes -- Regards/Gruss,

Re: [Eas-dev] [PATCH V4 1/3] sched: cpufreq: Allow remote cpufreq callbacks

On 26-07-17, 22:34, Joel Fernandes (Google) wrote: > On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote: > > @@ -221,7 +226,7 @@ static void sugov_update_single(struct update_util_data > > *hook, u64 time, > > sugov_set_iowait_boost(sg_cpu, time, flags); > >

Re: [Eas-dev] [PATCH V4 1/3] sched: cpufreq: Allow remote cpufreq callbacks

On 26-07-17, 22:34, Joel Fernandes (Google) wrote: > On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote: > > @@ -221,7 +226,7 @@ static void sugov_update_single(struct update_util_data > > *hook, u64 time, > > sugov_set_iowait_boost(sg_cpu, time, flags); > > sg_cpu->last_update

Re: [PATCH v2 6/7] mailbox: bcm-flexrm-mailbox: Set msg_queue_len for each channel

On Thu, Jul 27, 2017 at 10:29 AM, Jassi Brar wrote: > On Thu, Jul 27, 2017 at 9:25 AM, Anup Patel wrote: >> On Tue, Jul 25, 2017 at 9:37 PM, Jassi Brar wrote: >>> On Tue, Jul 25, 2017 at 11:11 AM, Anup Patel

Re: [PATCH v2 6/7] mailbox: bcm-flexrm-mailbox: Set msg_queue_len for each channel

On Thu, Jul 27, 2017 at 10:29 AM, Jassi Brar wrote: > On Thu, Jul 27, 2017 at 9:25 AM, Anup Patel wrote: >> On Tue, Jul 25, 2017 at 9:37 PM, Jassi Brar wrote: >>> On Tue, Jul 25, 2017 at 11:11 AM, Anup Patel >>> wrote: On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar wrote: > On

Re: [Eas-dev] [PATCH V4 2/3] cpufreq: schedutil: Process remote callback for shared policies

On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote: > This patch updates the schedutil governor to process cpufreq utilization > update hooks called for remote CPUs where the remote CPU is managed by > the cpufreq policy of the local CPU. > > Based on initial work from

Re: [Eas-dev] [PATCH V4 2/3] cpufreq: schedutil: Process remote callback for shared policies

On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote: > This patch updates the schedutil governor to process cpufreq utilization > update hooks called for remote CPUs where the remote CPU is managed by > the cpufreq policy of the local CPU. > > Based on initial work from Steve Muckle. > >

Re: [Eas-dev] [PATCH V4 0/3] sched: cpufreq: Allow remote callbacks

On 26-07-17, 22:14, Joel Fernandes (Google) wrote: > I think you dropped [1] in your cover-letter. May be you meant to add > it at the end of the cover letter? > > I noticed from your v2 that its: > https://pastebin.com/7LkMSRxE Yeah, I missed it. Thanks :) > Also one more comment about this

Re: [Eas-dev] [PATCH V4 0/3] sched: cpufreq: Allow remote callbacks

On 26-07-17, 22:14, Joel Fernandes (Google) wrote: > I think you dropped [1] in your cover-letter. May be you meant to add > it at the end of the cover letter? > > I noticed from your v2 that its: > https://pastebin.com/7LkMSRxE Yeah, I missed it. Thanks :) > Also one more comment about this

linux-next: Tree for Jul 27

Hi all, Changes since 20170726: Non-merge commits (relative to Linus' tree): 2581 2620 files changed, 92132 insertions(+), 46797 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm

linux-next: Tree for Jul 27

Hi all, Changes since 20170726: Non-merge commits (relative to Linus' tree): 2581 2620 files changed, 92132 insertions(+), 46797 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm

Re: [PATCH 09/12] ima: introduce securityfs interfaces for digest lists

Hi Roberto, [auto build test WARNING on integrity/next] [also build test WARNING on v4.13-rc2 next-20170726] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Roberto-Sassu/ima-measure-digest

Re: [PATCH 09/12] ima: introduce securityfs interfaces for digest lists

Hi Roberto, [auto build test WARNING on integrity/next] [also build test WARNING on v4.13-rc2 next-20170726] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Roberto-Sassu/ima-measure-digest

Re: [f2fs-dev] [PATCH 1/2] f2fs: expose /sys/fs/f2fs/features

On 2017/7/27 5:43, Jaegeuk Kim wrote: > On 07/26, Chao Yu wrote: >> On 2017/7/26 9:29, Jaegeuk Kim wrote: >>> This patch exposes what features are supported by current f2fs build to >>> sysfs >>> entry. >>> >>> Signed-off-by: Jaegeuk Kim >> >> Reviewed-by: Chao Yu

Re: [f2fs-dev] [PATCH 1/2] f2fs: expose /sys/fs/f2fs/features

On 2017/7/27 5:43, Jaegeuk Kim wrote: > On 07/26, Chao Yu wrote: >> On 2017/7/26 9:29, Jaegeuk Kim wrote: >>> This patch exposes what features are supported by current f2fs build to >>> sysfs >>> entry. >>> >>> Signed-off-by: Jaegeuk Kim >> >> Reviewed-by: Chao Yu >> >> Minor thing, can you

Re: [Eas-dev] [PATCH V4 1/3] sched: cpufreq: Allow remote cpufreq callbacks

Hi Viresh, On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote: > We do not call cpufreq callbacks from scheduler core for remote > (non-local) CPUs currently. But there are cases where such remote > callbacks are useful, specially in the case of shared cpufreq policies.

Re: [Eas-dev] [PATCH V4 1/3] sched: cpufreq: Allow remote cpufreq callbacks

Hi Viresh, On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote: > We do not call cpufreq callbacks from scheduler core for remote > (non-local) CPUs currently. But there are cases where such remote > callbacks are useful, specially in the case of shared cpufreq policies. > > This patch updates

Re: [PATCH 3/3] EDAC, ghes: Make it a proper module

On Wed, Jul 26, 2017 at 07:24:59PM +, Kani, Toshimitsu wrote: > Using sb_edac does not change the fact that it is FF. I do not think > you'd see normal CEs on your box. I guess we should add some blurb to EDAC to say that on FF systems, error counts are unreliable or even non-existent. --

Re: [PATCH 3/3] EDAC, ghes: Make it a proper module

On Wed, Jul 26, 2017 at 07:24:59PM +, Kani, Toshimitsu wrote: > Using sb_edac does not change the fact that it is FF. I do not think > you'd see normal CEs on your box. I guess we should add some blurb to EDAC to say that on FF systems, error counts are unreliable or even non-existent. --

Re: [PATCH v2 04/22] fpga: mgr: add region_id to fpga_image_info

On Wed, Jul 26, 2017 at 01:33:53PM -0500, Alan Tull wrote: > On Sun, Jun 25, 2017 at 8:52 PM, Wu Hao wrote: > > Hi Hao, > > > This patch adds region_id to fpga_image_info data structure, it > > allows driver to pass region id information to fpga-mgr via > > fpga_image_info for

Re: [PATCH v2 04/22] fpga: mgr: add region_id to fpga_image_info

On Wed, Jul 26, 2017 at 01:33:53PM -0500, Alan Tull wrote: > On Sun, Jun 25, 2017 at 8:52 PM, Wu Hao wrote: > > Hi Hao, > > > This patch adds region_id to fpga_image_info data structure, it > > allows driver to pass region id information to fpga-mgr via > > fpga_image_info for fpga

Re: [PATCH 06/12] ima: added parser of digest lists metadata

Hi Roberto, [auto build test ERROR on integrity/next] [also build test ERROR on v4.13-rc2 next-20170726] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Roberto-Sassu/ima-measure-digest-lists

Re: [PATCH 06/12] ima: added parser of digest lists metadata

Hi Roberto, [auto build test ERROR on integrity/next] [also build test ERROR on v4.13-rc2 next-20170726] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Roberto-Sassu/ima-measure-digest-lists

[PATCH v4 1/3] include: uapi: usb: Introduce USB charger type and state definition

Introducing USB charger type and state definition can help to support USB charging which will be added in USB phy core. Signed-off-by: Baolin Wang --- include/uapi/linux/usb/charger.h | 31 +++ 1 file changed, 31 insertions(+) create mode

[PATCH v4 1/3] include: uapi: usb: Introduce USB charger type and state definition

Introducing USB charger type and state definition can help to support USB charging which will be added in USB phy core. Signed-off-by: Baolin Wang --- include/uapi/linux/usb/charger.h | 31 +++ 1 file changed, 31 insertions(+) create mode 100644

[PATCH v4 2/3] usb: phy: Add USB charger support

This patch introduces the usb charger support based on usb phy that makes an enhancement to a power driver. The basic conception of the usb charger is that, when one usb charger is added or removed by reporting from the extcon device state change, the usb charger will report to power user to set

[PATCH v4 3/3] power: wm831x_power: Support USB charger current limit management

Integrate with the newly added USB charger interface to limit the current we draw from the USB input based on the input device configuration identified by the USB stack, allowing us to charge more quickly from high current inputs without drawing more current than specified from others.

[PATCH v4 2/3] usb: phy: Add USB charger support

This patch introduces the usb charger support based on usb phy that makes an enhancement to a power driver. The basic conception of the usb charger is that, when one usb charger is added or removed by reporting from the extcon device state change, the usb charger will report to power user to set

[PATCH v4 3/3] power: wm831x_power: Support USB charger current limit management

Integrate with the newly added USB charger interface to limit the current we draw from the USB input based on the input device configuration identified by the USB stack, allowing us to charge more quickly from high current inputs without drawing more current than specified from others.

[PATCH v4 0/3] Introduce USB charger support in USB phy

Currently the Linux kernel does not provide any standard integration of this feature that integrates the USB subsystem with the system power regulation provided by PMICs meaning that either vendors must add this in their kernels or USB gadget devices based on Linux (such as mobile phones) may not

Re: [Eas-dev] [PATCH V4 0/3] sched: cpufreq: Allow remote callbacks

Hi Viresh, On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote: > > With Android UI and benchmarks the latency of cpufreq response to > certain scheduling events can become very critical. Currently, callbacks > into schedutil are only made from the scheduler if the

Re: [Eas-dev] [PATCH V4 0/3] sched: cpufreq: Allow remote callbacks

Hi Viresh, On Wed, Jul 26, 2017 at 2:22 AM, Viresh Kumar wrote: > > With Android UI and benchmarks the latency of cpufreq response to > certain scheduling events can become very critical. Currently, callbacks > into schedutil are only made from the scheduler if the target CPU of the > event is

[PATCH v4 0/3] Introduce USB charger support in USB phy

Currently the Linux kernel does not provide any standard integration of this feature that integrates the USB subsystem with the system power regulation provided by PMICs meaning that either vendors must add this in their kernels or USB gadget devices based on Linux (such as mobile phones) may not

Re: [PATCH v8 1/3] perf: cavium: Support memory controller PMU counters

On Wed, Jul 26, 2017 at 02:02:42PM -0700, David Daney wrote: > Also, if a given configuration disables CONFIG_EDAC there is some hackery > needed to get the perf portion of the driver included. Yes, and we don't do performance counters in EDAC. So you could add a small memory controller driver

Re: [PATCH v8 1/3] perf: cavium: Support memory controller PMU counters

On Wed, Jul 26, 2017 at 02:02:42PM -0700, David Daney wrote: > Also, if a given configuration disables CONFIG_EDAC there is some hackery > needed to get the perf portion of the driver included. Yes, and we don't do performance counters in EDAC. So you could add a small memory controller driver

Re: [RFT 2/2] ASoC: samsung: Add proper error paths to s3c24xx I2S driver

Hi, On Thursday 27 July 2017 12:27 AM, Krzysztof Kozlowski wrote: s3c2412_i2s_probe() might fail so driver has to revert work done by s3c_i2sv2_probe() (clock enabling). Missing doing this would lead to clock enable in-balance. Signed-off-by: Krzysztof Kozlowski ---

Re: [RFT 2/2] ASoC: samsung: Add proper error paths to s3c24xx I2S driver

Hi, On Thursday 27 July 2017 12:27 AM, Krzysztof Kozlowski wrote: s3c2412_i2s_probe() might fail so driver has to revert work done by s3c_i2sv2_probe() (clock enabling). Missing doing this would lead to clock enable in-balance. Signed-off-by: Krzysztof Kozlowski --- Please, kindly test on

Warning: You tried to send an email with blocked content

The UCL E-Mail Virus Protection System has been triggered by a message you sent. One or more of the original e-mail attachments have been removed and replaced with this message. * The attachment may have contained a virus or malware * The attachment may have an extension of a type unacceptable

Warning: You tried to send an email with blocked content

The UCL E-Mail Virus Protection System has been triggered by a message you sent. One or more of the original e-mail attachments have been removed and replaced with this message. * The attachment may have contained a virus or malware * The attachment may have an extension of a type unacceptable

blk_mq_sched_insert_request: inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage

Hi Jens, I'm seeing the lockdep warning below on shutdown on a Power8 machine using IPR. If I'm reading it right it looks like the spin_lock() (non-irq) in blk_mq_sched_insert_request() is the immediate cause. Looking at blk_mq_requeue_work() (the caller), it is doing spin_lock_irqsave(). So is

blk_mq_sched_insert_request: inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage

Hi Jens, I'm seeing the lockdep warning below on shutdown on a Power8 machine using IPR. If I'm reading it right it looks like the spin_lock() (non-irq) in blk_mq_sched_insert_request() is the immediate cause. Looking at blk_mq_requeue_work() (the caller), it is doing spin_lock_irqsave(). So is

Re: [greybus-dev] [PATCH] staging: greybus: Remove unnecessary platform_set_drvdata

On 26-07-17, 23:19, Amitoj Kaur Chawla wrote: > Unnecessary platform_set_drvdata() has been removed since the driver > core clears the driver data to NULL after device release or on > probe failure. There is no need to manually clear the device > driver data to NULL. > > The Coccinelle semantic

Re: [greybus-dev] [PATCH] staging: greybus: Remove unnecessary platform_set_drvdata

On 26-07-17, 23:19, Amitoj Kaur Chawla wrote: > Unnecessary platform_set_drvdata() has been removed since the driver > core clears the driver data to NULL after device release or on > probe failure. There is no need to manually clear the device > driver data to NULL. > > The Coccinelle semantic

Re: [PATCH 08/12] ima: added parser for RPM data type

Hi Roberto, [auto build test WARNING on integrity/next] [also build test WARNING on v4.13-rc2 next-20170726] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Roberto-Sassu/ima-measure-digest

Re: [PATCH 08/12] ima: added parser for RPM data type

Hi Roberto, [auto build test WARNING on integrity/next] [also build test WARNING on v4.13-rc2 next-20170726] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Roberto-Sassu/ima-measure-digest

[PATCH v2 2/3] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI)

Add binding documentation for Allwinner V3s CSI. Signed-off-by: Yong Deng --- .../devicetree/bindings/media/sun6i-csi.txt| 49 ++ 1 file changed, 49 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/sun6i-csi.txt diff

[PATCH v2 2/3] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI)

Add binding documentation for Allwinner V3s CSI. Signed-off-by: Yong Deng --- .../devicetree/bindings/media/sun6i-csi.txt| 49 ++ 1 file changed, 49 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/sun6i-csi.txt diff --git

[PATCH v2 1/3] media: V3s: Add support for Allwinner CSI.

Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface and CSI1 is used for parallel interface. This is not documented in datasheet but by testing and guess. This patch implement a v4l2 framework driver for it. Currently, the driver only support the parallel interface. MIPI-CSI2,

[PATCH v2 1/3] media: V3s: Add support for Allwinner CSI.

Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface and CSI1 is used for parallel interface. This is not documented in datasheet but by testing and guess. This patch implement a v4l2 framework driver for it. Currently, the driver only support the parallel interface. MIPI-CSI2,

[PATCH v2 3/3] media: MAINTAINERS: add entries for Allwinner V3s CSI

Signed-off-by: Yong Deng --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 9826a91..b91fa27 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3686,6 +3686,14 @@ M: Jaya Kumar S:

[PATCH v2 3/3] media: MAINTAINERS: add entries for Allwinner V3s CSI

Signed-off-by: Yong Deng --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 9826a91..b91fa27 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3686,6 +3686,14 @@ M: Jaya Kumar S: Maintained F: sound/pci/cs5535audio/ +CSI

Re: [PATCH] ASoC: samsung: s3c2412: cleanups / fixes for preparation of clocks.

Hi, On Thursday 27 July 2017 12:42 AM, Krzysztof Kozlowski wrote: On Thu, Jul 27, 2017 at 12:28:52AM +0530, Arvind Yadav wrote: -Use devm_clk_get() to make cleanup paths more simple. -clk_prepare_enable() can fail here and we must check its return value. -Add s3c_i2sv2_remove cleanup function

Re: [PATCH] ASoC: samsung: s3c2412: cleanups / fixes for preparation of clocks.

Hi, On Thursday 27 July 2017 12:42 AM, Krzysztof Kozlowski wrote: On Thu, Jul 27, 2017 at 12:28:52AM +0530, Arvind Yadav wrote: -Use devm_clk_get() to make cleanup paths more simple. -clk_prepare_enable() can fail here and we must check its return value. -Add s3c_i2sv2_remove cleanup function

[PATCH v2 0/3] Initial Allwinner V3s CSI Support

Sorry for resend the patch. Delivering to somebody in cc has failed at last time. This patchset add initial support for Allwinner V3s CSI. Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface and CSI1 is used for parallel interface. This is not documented in datasheet but by

[PATCH v2 0/3] Initial Allwinner V3s CSI Support

Sorry for resend the patch. Delivering to somebody in cc has failed at last time. This patchset add initial support for Allwinner V3s CSI. Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface and CSI1 is used for parallel interface. This is not documented in datasheet but by

Re: [PATCH 02/16] fpga: add FPGA device framework

On Wed, Jul 26, 2017 at 05:29:11PM -0500, Alan Tull wrote: > On Wed, Jul 26, 2017 at 9:20 AM, Alan Tull wrote: > > On Wed, Jul 26, 2017 at 4:50 AM, Wu Hao wrote: > >> On Tue, Jul 25, 2017 at 04:32:10PM -0500, Alan Tull wrote: > >>> On Sat, Apr 1, 2017 at 7:18

Re: [PATCH 02/16] fpga: add FPGA device framework

On Wed, Jul 26, 2017 at 05:29:11PM -0500, Alan Tull wrote: > On Wed, Jul 26, 2017 at 9:20 AM, Alan Tull wrote: > > On Wed, Jul 26, 2017 at 4:50 AM, Wu Hao wrote: > >> On Tue, Jul 25, 2017 at 04:32:10PM -0500, Alan Tull wrote: > >>> On Sat, Apr 1, 2017 at 7:18 AM, Wu Hao wrote: > >>> > >>> Hi

Re: [PATCH 4/6] dma: bcm-sba-raid: Break sba_process_deferred_requests() into two parts

On Wed, Jul 26, 2017 at 10:45 PM, Vinod Koul wrote: > On Wed, Jul 26, 2017 at 11:06:42AM +0530, Anup Patel wrote: >> This patch breaks sba_process_deferred_requests() into two parts >> sba_process_received_request() and _sba_process_pending_requests() >> for readability. >>

Re: [PATCH 4/6] dma: bcm-sba-raid: Break sba_process_deferred_requests() into two parts

On Wed, Jul 26, 2017 at 10:45 PM, Vinod Koul wrote: > On Wed, Jul 26, 2017 at 11:06:42AM +0530, Anup Patel wrote: >> This patch breaks sba_process_deferred_requests() into two parts >> sba_process_received_request() and _sba_process_pending_requests() >> for readability. >> >> In addition, > >

Re: [PATCH v2 6/7] mailbox: bcm-flexrm-mailbox: Set msg_queue_len for each channel

On Thu, Jul 27, 2017 at 9:25 AM, Anup Patel wrote: > On Tue, Jul 25, 2017 at 9:37 PM, Jassi Brar wrote: >> On Tue, Jul 25, 2017 at 11:11 AM, Anup Patel wrote: >>> On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar

Re: [PATCH v2 6/7] mailbox: bcm-flexrm-mailbox: Set msg_queue_len for each channel

On Thu, Jul 27, 2017 at 9:25 AM, Anup Patel wrote: > On Tue, Jul 25, 2017 at 9:37 PM, Jassi Brar wrote: >> On Tue, Jul 25, 2017 at 11:11 AM, Anup Patel wrote: >>> On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar >>> wrote: On Mon, Jul 24, 2017 at 9:26 AM, Anup Patel wrote: > Hi

Re: [PATCH 2/6] dma: bcm-sba-raid: Peek mbox when we are left with no free requests

On Wed, Jul 26, 2017 at 10:40 PM, Vinod Koul wrote: > On Wed, Jul 26, 2017 at 11:06:40AM +0530, Anup Patel wrote: >> We should peek mbox channels when we are left with no free >> sba_requests in sba_alloc_request() > > and why is the world should we do that, how does that

Re: [PATCH 2/6] dma: bcm-sba-raid: Peek mbox when we are left with no free requests

On Wed, Jul 26, 2017 at 10:40 PM, Vinod Koul wrote: > On Wed, Jul 26, 2017 at 11:06:40AM +0530, Anup Patel wrote: >> We should peek mbox channels when we are left with no free >> sba_requests in sba_alloc_request() > > and why is the world should we do that, how does that help?? When setting up

Re: [PATCH 1/6] dma: bcm-sba-raid: Improve memory allocation in SBA RAID driver

On Wed, Jul 26, 2017 at 10:39 PM, Vinod Koul wrote: > On Wed, Jul 26, 2017 at 11:06:39AM +0530, Anup Patel wrote: >> This patch improves memory allocation in SBA RAID driver in >> following ways: >> 1. Simplify struct sba_request to reduce memory consumption > > what is the

Re: [PATCH 1/6] dma: bcm-sba-raid: Improve memory allocation in SBA RAID driver

On Wed, Jul 26, 2017 at 10:39 PM, Vinod Koul wrote: > On Wed, Jul 26, 2017 at 11:06:39AM +0530, Anup Patel wrote: >> This patch improves memory allocation in SBA RAID driver in >> following ways: >> 1. Simplify struct sba_request to reduce memory consumption > > what is the simplification?? You

Re: [PATCH 0/6] Broadcom SBA-RAID driver improvements

On Wed, Jul 26, 2017 at 10:33 PM, Vinod Koul wrote: > On Wed, Jul 26, 2017 at 11:06:38AM +0530, Anup Patel wrote: >> This patchset does various improvments to Broadcom SBA-RAID >> driver and also adds SBA-RAID DT nodes for Stingray SOC. >> >> The patches are based on "[PATCH

Re: [PATCH 0/6] Broadcom SBA-RAID driver improvements

On Wed, Jul 26, 2017 at 10:33 PM, Vinod Koul wrote: > On Wed, Jul 26, 2017 at 11:06:38AM +0530, Anup Patel wrote: >> This patchset does various improvments to Broadcom SBA-RAID >> driver and also adds SBA-RAID DT nodes for Stingray SOC. >> >> The patches are based on "[PATCH v2 0/7] FlexRM driver

Re: [PATCH v2 6/7] mailbox: bcm-flexrm-mailbox: Set msg_queue_len for each channel

On Tue, Jul 25, 2017 at 9:37 PM, Jassi Brar wrote: > On Tue, Jul 25, 2017 at 11:11 AM, Anup Patel wrote: >> On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar >> wrote: >>> On Mon, Jul 24, 2017 at 9:26 AM, Anup Patel

Re: [PATCH v2 6/7] mailbox: bcm-flexrm-mailbox: Set msg_queue_len for each channel

On Tue, Jul 25, 2017 at 9:37 PM, Jassi Brar wrote: > On Tue, Jul 25, 2017 at 11:11 AM, Anup Patel wrote: >> On Mon, Jul 24, 2017 at 10:06 PM, Jassi Brar >> wrote: >>> On Mon, Jul 24, 2017 at 9:26 AM, Anup Patel wrote: Hi Jassi, Sorry for the delayed response... On

[PATCH v2 0/3] Initial Allwinner V3s CSI Support

This patchset add initial support for Allwinner V3s CSI. Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface and CSI1 is used for parallel interface. This is not documented in datasheet but by testing and guess. This patchset implement a v4l2 framework driver and add a binding

[PATCH v2 0/3] Initial Allwinner V3s CSI Support

This patchset add initial support for Allwinner V3s CSI. Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface and CSI1 is used for parallel interface. This is not documented in datasheet but by testing and guess. This patchset implement a v4l2 framework driver and add a binding

[PATCH v2 2/3] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI)

Add binding documentation for Allwinner V3s CSI. Signed-off-by: Yong Deng --- .../devicetree/bindings/media/sun6i-csi.txt| 49 ++ 1 file changed, 49 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/sun6i-csi.txt diff

[PATCH v2 2/3] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI)

Add binding documentation for Allwinner V3s CSI. Signed-off-by: Yong Deng --- .../devicetree/bindings/media/sun6i-csi.txt| 49 ++ 1 file changed, 49 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/sun6i-csi.txt diff --git

[PATCH v2 1/3] media: V3s: Add support for Allwinner CSI.

Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface and CSI1 is used for parallel interface. This is not documented in datasheet but by testing and guess. This patch implement a v4l2 framework driver for it. Currently, the driver only support the parallel interface. MIPI-CSI2,

[PATCH v2 1/3] media: V3s: Add support for Allwinner CSI.

Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface and CSI1 is used for parallel interface. This is not documented in datasheet but by testing and guess. This patch implement a v4l2 framework driver for it. Currently, the driver only support the parallel interface. MIPI-CSI2,

Re: [PATCH] cpufreq: intel_pstate: Drop ->get from intel_pstate structure

On 26-07-17, 00:42, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The ->get callback in the intel_pstate structure was mostly there > for the scaling_cur_freq sysfs attribute to work, but after commit > f8475cef9008 (x86: use common aperfmperf_khz_on_cpu() to

Re: [PATCH] cpufreq: intel_pstate: Drop ->get from intel_pstate structure

On 26-07-17, 00:42, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The ->get callback in the intel_pstate structure was mostly there > for the scaling_cur_freq sysfs attribute to work, but after commit > f8475cef9008 (x86: use common aperfmperf_khz_on_cpu() to calculate > KHz using

Re: [PATCH] cpufreq: docs: Add missing cpuinfo_cur_freq description

On 27-07-17, 02:05, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Add a description of the cpuinfo_cur_freq policy attribute in sysfs > to the cpufreq documentation under Documentation/admin-guide/pm/ as > it is missing after commit 2a0e49279850 (cpufreq:

Re: [PATCH] cpufreq: docs: Add missing cpuinfo_cur_freq description

On 27-07-17, 02:05, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Add a description of the cpuinfo_cur_freq policy attribute in sysfs > to the cpufreq documentation under Documentation/admin-guide/pm/ as > it is missing after commit 2a0e49279850 (cpufreq: User/admin > documentation

Re: [PATCH v2 5/5] dt-bindings: PCI: add support for new generation controller

On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > From: Ryder Lee > > Add support for MediaTek new generation controller and update related > properities. > > Signed-off-by: Ryder Lee > Signed-off-by: Honghui Zhang

Re: [PATCH v2 5/5] dt-bindings: PCI: add support for new generation controller

On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > From: Ryder Lee > > Add support for MediaTek new generation controller and update related > properities. > > Signed-off-by: Ryder Lee > Signed-off-by: Honghui Zhang > --- > .../devicetree/bindings/pci/mediatek-pcie.txt

Re: [PATCH v2 5/5] dt-bindings: PCI: add support for new generation controller

On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > From: Ryder Lee > > Add support for MediaTek new generation controller and update related > properities. > > Signed-off-by: Ryder Lee > Signed-off-by: Honghui Zhang

Re: [RFC PATCH] mm: memcg: fix css double put in mem_cgroup_iter

2017-07-26 21:44 GMT+08:00 Michal Hocko : > On Wed 26-07-17 21:07:42, Wenwei Tao wrote: >> From: Wenwei Tao >> >> By removing the child cgroup while the parent cgroup is >> under reclaim, we could trigger the following kernel panic >> on kernel 3.10:

Re: [PATCH v2 5/5] dt-bindings: PCI: add support for new generation controller

On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > From: Ryder Lee > > Add support for MediaTek new generation controller and update related > properities. > > Signed-off-by: Ryder Lee > Signed-off-by: Honghui Zhang > --- > .../devicetree/bindings/pci/mediatek-pcie.txt

Re: [RFC PATCH] mm: memcg: fix css double put in mem_cgroup_iter

2017-07-26 21:44 GMT+08:00 Michal Hocko : > On Wed 26-07-17 21:07:42, Wenwei Tao wrote: >> From: Wenwei Tao >> >> By removing the child cgroup while the parent cgroup is >> under reclaim, we could trigger the following kernel panic >> on kernel 3.10: >>

Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks

On 26-07-17, 14:00, Saravana Kannan wrote: > No, the alternative is to pass it on to the CPU freq driver and let it > decide what it wants to do. That's the whole point if having a CPU freq > driver -- so that the generic code doesn't need to care about HW specific > details. Which is the point I

Re: [Eas-dev] [PATCH V3 1/3] sched: cpufreq: Allow remote cpufreq callbacks

On 26-07-17, 14:00, Saravana Kannan wrote: > No, the alternative is to pass it on to the CPU freq driver and let it > decide what it wants to do. That's the whole point if having a CPU freq > driver -- so that the generic code doesn't need to care about HW specific > details. Which is the point I

Re: [PATCH v2 1/5] PCI: mediatek: Add a structure to abstract the controller generations

On Thu, 2017-07-27 at 11:19 +0800, Honghui Zhang wrote: > On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > > From: Ryder Lee > > > > Introduce a structure "mtk_pcie_soc" to abstract the differences between > > controller generations, and the

Re: [PATCH v2 1/5] PCI: mediatek: Add a structure to abstract the controller generations

On Thu, 2017-07-27 at 11:19 +0800, Honghui Zhang wrote: > On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > > From: Ryder Lee > > > > Introduce a structure "mtk_pcie_soc" to abstract the differences between > > controller generations, and the .startup() hook is used to

Re: [PATCH V4 1/3] sched: cpufreq: Allow remote cpufreq callbacks

On 26-07-17, 19:42, Rafael J. Wysocki wrote: > On Wednesday, July 26, 2017 02:52:32 PM Viresh Kumar wrote: > > + /* Don't allow remote callbacks */ > > + if (smp_processor_id() != data->cpu) > > + return; > > You can do this check against cpu->cpu, however. > > > + /* Don't

Re: [PATCH V4 1/3] sched: cpufreq: Allow remote cpufreq callbacks

On 26-07-17, 19:42, Rafael J. Wysocki wrote: > On Wednesday, July 26, 2017 02:52:32 PM Viresh Kumar wrote: > > + /* Don't allow remote callbacks */ > > + if (smp_processor_id() != data->cpu) > > + return; > > You can do this check against cpu->cpu, however. > > > + /* Don't

[PATCH V2 net] Revert "vhost: cache used event for better performance"

This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it was reported to break vhost_net. We want to cache used event and use it to check for notification. The assumption was that guest won't move the event idx back, but this could happen in fact when 16 bit index wraps around after

[PATCH V2 net] Revert "vhost: cache used event for better performance"

This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it was reported to break vhost_net. We want to cache used event and use it to check for notification. The assumption was that guest won't move the event idx back, but this could happen in fact when 16 bit index wraps around after

Re: [PATCH v2 1/5] PCI: mediatek: Add a structure to abstract the controller generations

On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > From: Ryder Lee > > Introduce a structure "mtk_pcie_soc" to abstract the differences between > controller generations, and the .startup() hook is used to encapsulate > some SoC-dependent related

Re: [PATCH v2 1/5] PCI: mediatek: Add a structure to abstract the controller generations

On Thu, 2017-07-27 at 10:58 +0800, honghui.zh...@mediatek.com wrote: > From: Ryder Lee > > Introduce a structure "mtk_pcie_soc" to abstract the differences between > controller generations, and the .startup() hook is used to encapsulate > some SoC-dependent related setting. In doing so, the

  1   2   3   4   5   6   7   8   9   10   >