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.
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.
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
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
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,
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,
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);
> >
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
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
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
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
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.
>
>
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
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
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
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
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
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
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
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
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.
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
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.
--
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.
--
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
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
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
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
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
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
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
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.
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
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.
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
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
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
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
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
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
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
---
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
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
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
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
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
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
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
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
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
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
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
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,
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,
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:
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
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
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
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
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
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
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
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.
>>
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,
>
>
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,
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,
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
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
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:
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
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
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
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
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:
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
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:
>>
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
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
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
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
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
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
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
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
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
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 - 100 of 1946 matches
Mail list logo