Hi Marek,
>This patch adds runtime pm implementation, which is based on previous
>suspend/resume code. SYSMMU controller is now being enabled/disabled mainly
>from the runtime pm callbacks. System sleep callbacks relies on generic
>pm_runtime_force_suspend/pm_runtime_force_resume helpers. To
Hi Marek,
>This patch adds runtime pm implementation, which is based on previous
>suspend/resume code. SYSMMU controller is now being enabled/disabled mainly
>from the runtime pm callbacks. System sleep callbacks relies on generic
>pm_runtime_force_suspend/pm_runtime_force_resume helpers. To
On 2016-10-21 09:17, ji...@kernel.org wrote:
> On 20.10.2016 19:17, Peter Rosin wrote:
>> On 2016-10-20 19:37, Jonathan Cameron wrote:
>>> On 20 October 2016 18:30:19 BST, Jonathan Cameron
>>> wrote:
On 20 October 2016 13:55:12 BST, Lars-Peter Clausen
On 2016-10-21 09:17, ji...@kernel.org wrote:
> On 20.10.2016 19:17, Peter Rosin wrote:
>> On 2016-10-20 19:37, Jonathan Cameron wrote:
>>> On 20 October 2016 18:30:19 BST, Jonathan Cameron
>>> wrote:
On 20 October 2016 13:55:12 BST, Lars-Peter Clausen
wrote:
> On 10/20/2016 11:25
On 2016.10.21 17:25:50 +0200, Arnd Bergmann wrote:
> Two functions in the newly added gvt render code are obviously
> broken, as they reference a variable without initialization and
> don't reference another variable at all:
>
> drivers/gpu/drm/i915/gvt/render.c: In function
>
On 2016.10.21 17:25:50 +0200, Arnd Bergmann wrote:
> Two functions in the newly added gvt render code are obviously
> broken, as they reference a variable without initialization and
> don't reference another variable at all:
>
> drivers/gpu/drm/i915/gvt/render.c: In function
>
On Sat, Oct 22, 2016 at 05:43:36AM +0200, Stephan Mueller wrote:
> Hi Ted,
>
> as mentioned, I looked a bit deeper into the issue of adding the blocking
> behavior of getrandom to /dev/urandom.
>
> As you and I already identified, moving that blocking behavior to
> /dev/urandom
> simply does
On Sat, Oct 22, 2016 at 05:43:36AM +0200, Stephan Mueller wrote:
> Hi Ted,
>
> as mentioned, I looked a bit deeper into the issue of adding the blocking
> behavior of getrandom to /dev/urandom.
>
> As you and I already identified, moving that blocking behavior to
> /dev/urandom
> simply does
On 2016.10.21 17:25:49 +0200, Arnd Bergmann wrote:
> The newly added gvt code produces lots of serious warnings and errors
> when either built on 32-bit x86, or built with ACPI disabled, e.g.
>
> drivers/gpu/drm/i915/gvt/gtt.c: In function ???read_pte64???:
> drivers/gpu/drm/i915/gvt/gtt.c:277:2:
On 2016.10.21 17:25:49 +0200, Arnd Bergmann wrote:
> The newly added gvt code produces lots of serious warnings and errors
> when either built on 32-bit x86, or built with ACPI disabled, e.g.
>
> drivers/gpu/drm/i915/gvt/gtt.c: In function ???read_pte64???:
> drivers/gpu/drm/i915/gvt/gtt.c:277:2:
On 10/21/2016 04:25 PM, Heiko Stuebner wrote:
Am Donnerstag, 20. Oktober 2016, 15:47:56 CEST schrieb Tomeu Vizoso:
On 10/20/2016 03:45 PM, Heiko Stübner wrote:
Am Donnerstag, 20. Oktober 2016, 10:07:25 schrieb Tomeu Vizoso:
Add an empty 'i2c-bus' subnode to the edp node just so that the I2C
On 10/21/2016 04:25 PM, Heiko Stuebner wrote:
Am Donnerstag, 20. Oktober 2016, 15:47:56 CEST schrieb Tomeu Vizoso:
On 10/20/2016 03:45 PM, Heiko Stübner wrote:
Am Donnerstag, 20. Oktober 2016, 10:07:25 schrieb Tomeu Vizoso:
Add an empty 'i2c-bus' subnode to the edp node just so that the I2C
Hi Ted,
as mentioned, I looked a bit deeper into the issue of adding the blocking
behavior of getrandom to /dev/urandom.
As you and I already identified, moving that blocking behavior to /dev/urandom
simply does not work. The system does not boot.
The reason to this issue is actually quite
Hi Ted,
as mentioned, I looked a bit deeper into the issue of adding the blocking
behavior of getrandom to /dev/urandom.
As you and I already identified, moving that blocking behavior to /dev/urandom
simply does not work. The system does not boot.
The reason to this issue is actually quite
On Mon, Sep 19, 2016 at 10:41:53AM +0530, Sanchayan Maity wrote:
> Use enable-gpios property of PWM backlight driver for backlight
> control.
>
> Signed-off-by: Sanchayan Maity
Applied, thanks.
On Mon, Sep 19, 2016 at 10:41:53AM +0530, Sanchayan Maity wrote:
> Use enable-gpios property of PWM backlight driver for backlight
> control.
>
> Signed-off-by: Sanchayan Maity
Applied, thanks.
On Mon, Sep 19, 2016 at 10:41:52AM +0530, Sanchayan Maity wrote:
> Remove use of pwm-leds and use the standard /sys/class/pwm
> interface from PWM subsystem.
>
> Signed-off-by: Sanchayan Maity
> Acked-by: Marcel Ziswiler
Applied, thanks.
On Mon, Sep 19, 2016 at 10:41:52AM +0530, Sanchayan Maity wrote:
> Remove use of pwm-leds and use the standard /sys/class/pwm
> interface from PWM subsystem.
>
> Signed-off-by: Sanchayan Maity
> Acked-by: Marcel Ziswiler
Applied, thanks.
Bjorn,
sorry for the delay in getting back to you. The first patch was incomplete.
The patch was not a
complete unit. There was a second patch that has the callers of the
routines in question.
Appended are the two patches merged into one new patch. And here is an
explanation from
Bjorn,
sorry for the delay in getting back to you. The first patch was incomplete.
The patch was not a
complete unit. There was a second patch that has the callers of the
routines in question.
Appended are the two patches merged into one new patch. And here is an
explanation from
On Mon, Sep 19, 2016 at 10:41:51AM +0530, Sanchayan Maity wrote:
> Remove the use of DDC I2C bus bitbang to support reading of EDID
> and rely on support from internal HDMI I2C master controller instead.
> As a result remove the device tree property ddc-i2c-bus.
>
> Signed-off-by: Sanchayan Maity
On Mon, Sep 19, 2016 at 10:41:51AM +0530, Sanchayan Maity wrote:
> Remove the use of DDC I2C bus bitbang to support reading of EDID
> and rely on support from internal HDMI I2C master controller instead.
> As a result remove the device tree property ddc-i2c-bus.
>
> Signed-off-by: Sanchayan Maity
On Wed, Sep 21, 2016 at 04:54:38PM +0530, Sanchayan Maity wrote:
> Add support for Toradex Colibri iMX6 module.
>
> Signed-off-by: Sanchayan Maity
Applied, thanks.
On Wed, Sep 21, 2016 at 04:54:38PM +0530, Sanchayan Maity wrote:
> Add support for Toradex Colibri iMX6 module.
>
> Signed-off-by: Sanchayan Maity
Applied, thanks.
This is on an AMD a10 system. With paranoid=1. Think it's
probably unrelated to the (unreseolved) AMD IBS issues.
This is 4.9-rc0 just before rc1 (can't get actual rc1 to boot)
Machine locks hard after this.
[ 8098.085662] BAD LUCK: lost 42 message(s) from NMI context!
[ 8098.085663]
This is on an AMD a10 system. With paranoid=1. Think it's
probably unrelated to the (unreseolved) AMD IBS issues.
This is 4.9-rc0 just before rc1 (can't get actual rc1 to boot)
Machine locks hard after this.
[ 8098.085662] BAD LUCK: lost 42 message(s) from NMI context!
[ 8098.085663]
Hi Chen Yu,
On Thu, Oct 20, 2016 at 04:14:52PM +0800, Chen Yu wrote:
> On some platforms, there is occasional panic triggered when
> trying to resume from hibernation, a typical panic looks like:
>
> "BUG: unable to handle kernel paging request at 880085894000
> IP: []
Hi Chen Yu,
On Thu, Oct 20, 2016 at 04:14:52PM +0800, Chen Yu wrote:
> On some platforms, there is occasional panic triggered when
> trying to resume from hibernation, a typical panic looks like:
>
> "BUG: unable to handle kernel paging request at 880085894000
> IP: []
--
Geschäftsvorschlag!!!
Ich vermute das diese E-Mail eine Überraschung für Sie sein wird, aber
es ist wahr.Ich bin bei einer routinen Überprüfung in meiner Bank (First
National Bank von Süd Afrika) wo ich arbeite, auf einem Konto
gestoßen,was nicht in anspruch genommen worden ist, wo
--
Geschäftsvorschlag!!!
Ich vermute das diese E-Mail eine Überraschung für Sie sein wird, aber
es ist wahr.Ich bin bei einer routinen Überprüfung in meiner Bank (First
National Bank von Süd Afrika) wo ich arbeite, auf einem Konto
gestoßen,was nicht in anspruch genommen worden ist, wo
From: Ville Syrjälä
Apparently trying to poke a disabled or non-existent APIC
leads to a box that doesn't even boot. Let's not do that.
No real clue if this is the right fix, but at least my
P3 machine boots again.
Cc: sta...@vger.kernel.org
Cc: Ingo Molnar
From: Ville Syrjälä
Apparently trying to poke a disabled or non-existent APIC
leads to a box that doesn't even boot. Let's not do that.
No real clue if this is the right fix, but at least my
P3 machine boots again.
Cc: sta...@vger.kernel.org
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc:
On Fri, Oct 21, 2016 at 9:31 AM, Jiri Pirko wrote:
>
> I don't see how vlan could be used uninitialized. But I understand that
> this is impossible for gcc to track it. Please just use uninitialized_var()
Actually, I think we should never use "uninitialized_var()" except
On Fri, Oct 21, 2016 at 9:31 AM, Jiri Pirko wrote:
>
> I don't see how vlan could be used uninitialized. But I understand that
> this is impossible for gcc to track it. Please just use uninitialized_var()
Actually, I think we should never use "uninitialized_var()" except
possibly for arrays or
> -Original Message-
> From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com]
> Sent: Monday, October 17, 2016 5:37 PM
> To: Lipengcheng; johny...@synopsys.com
> Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org;
> linux-kernel@vger.kernel.org; Xuejiancheng; Lidongpo;
> -Original Message-
> From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com]
> Sent: Monday, October 17, 2016 5:37 PM
> To: Lipengcheng; johny...@synopsys.com
> Cc: gre...@linuxfoundation.org; linux-...@vger.kernel.org;
> linux-kernel@vger.kernel.org; Xuejiancheng; Lidongpo;
On Sat, Oct 22, 2016 at 5:47 AM, Jonathan Corbet wrote:
> On Sat, 22 Oct 2016 00:19:45 +0900
> SeongJae Park wrote:
>
>> This patchset applies ReST conversion effort for HOWTO document to its Korean
>> translation. It also contains fixup of trivial nitpicks
On Sat, Oct 22, 2016 at 5:47 AM, Jonathan Corbet wrote:
> On Sat, 22 Oct 2016 00:19:45 +0900
> SeongJae Park wrote:
>
>> This patchset applies ReST conversion effort for HOWTO document to its Korean
>> translation. It also contains fixup of trivial nitpicks in the document and
>> the
Use get_target_pstate_use_cpu_load() to calculate target P-State for
devices, which uses preferred power management profile as PM_MOBILE
in ACPI FADT.
This may help in resolving some thermal issues caused by low sustained
cpu bound workloads. The current algorithm tend to over provision in this
Use get_target_pstate_use_cpu_load() to calculate target P-State for
devices, which uses preferred power management profile as PM_MOBILE
in ACPI FADT.
This may help in resolving some thermal issues caused by low sustained
cpu bound workloads. The current algorithm tend to over provision in this
On 10/22/16 06:53, Chen Gang wrote:
>
> On 10/21/16 11:41, Andrew Morton wrote:
>> On Wed, 5 Oct 2016 21:40:10 +0800 cheng...@emindsoft.com.cn wrote:
>>
>>> In api itself, kernel does not use it -- it is divided into ac_etime_hi
>>> and ac_etime_lo. So kernel side only need generate the correct
On 10/22/16 06:53, Chen Gang wrote:
>
> On 10/21/16 11:41, Andrew Morton wrote:
>> On Wed, 5 Oct 2016 21:40:10 +0800 cheng...@emindsoft.com.cn wrote:
>>
>>> In api itself, kernel does not use it -- it is divided into ac_etime_hi
>>> and ac_etime_lo. So kernel side only need generate the correct
On 2016/10/22 4:00, John Youn wrote:
> On 10/20/2016 5:43 PM, Chen Yu wrote:
>> On 2016/10/19 6:21, John Youn wrote:
>>> On 10/16/2016 7:42 PM, Chen Yu wrote:
On 2016/10/15 3:37, John Youn wrote:
> On 10/13/2016 4:36 PM, John Stultz wrote:
>> From: Chen Yu
On 2016/10/22 4:00, John Youn wrote:
> On 10/20/2016 5:43 PM, Chen Yu wrote:
>> On 2016/10/19 6:21, John Youn wrote:
>>> On 10/16/2016 7:42 PM, Chen Yu wrote:
On 2016/10/15 3:37, John Youn wrote:
> On 10/13/2016 4:36 PM, John Stultz wrote:
>> From: Chen Yu
>>
>> The
On Sat, Oct 22, 2016 at 3:50 AM, Xo Wang wrote:
> Add the RXD-to-RXC skew (delay) time bit in the Miscellaneous Control
> shadow register and a mask for the shadow selector field.
>
> Remove a re-definition of MII_BCM54XX_AUXCTL_SHDWSEL_AUXCTL.
>
> Signed-off-by: Xo Wang
On Sat, Oct 22, 2016 at 3:50 AM, Xo Wang wrote:
> Add the RXD-to-RXC skew (delay) time bit in the Miscellaneous Control
> shadow register and a mask for the shadow selector field.
>
> Remove a re-definition of MII_BCM54XX_AUXCTL_SHDWSEL_AUXCTL.
>
> Signed-off-by: Xo Wang
Reviewed-by: Joel
On Sat, Oct 22, 2016 at 3:50 AM, Xo Wang wrote:
> This PHY has internal delays enabled after reset. This clears the
> internal delay enables unless the interface specifically requests them.
>
> Signed-off-by: Xo Wang
Reviewed-by: Joel Stanley
On Sat, Oct 22, 2016 at 3:50 AM, Xo Wang wrote:
> This PHY has internal delays enabled after reset. This clears the
> internal delay enables unless the interface specifically requests them.
>
> Signed-off-by: Xo Wang
Reviewed-by: Joel Stanley
Cheers,
Joel
> ---
> drivers/net/phy/broadcom.c
Modify cpufeatures.h to add new AVX512 instruction groups/features
for enuermation in /proc/cpuinfo: AVX512IFMA and AVX512VBMI
Also modify the xstate.c to clear the flags in
fpu__xstate_clear_all_cpu_caps().
CPUID.(EAX=7,ECX=0):EBX[bit 21] AVX512IFMA
CPUID.(Eax=7,ECX=0):ECX[bit 1] AVX512VBMI
Modify cpufeatures.h to add new AVX512 instruction groups/features
for enuermation in /proc/cpuinfo: AVX512IFMA and AVX512VBMI
Also modify the xstate.c to clear the flags in
fpu__xstate_clear_all_cpu_caps().
CPUID.(EAX=7,ECX=0):EBX[bit 21] AVX512IFMA
CPUID.(Eax=7,ECX=0):ECX[bit 1] AVX512VBMI
On Oct 21, 2016 5:32 AM, "Matt Fleming" wrote:
>
> On Wed, 24 Aug, at 06:03:04AM, tip-bot for Andy Lutomirski wrote:
> > Commit-ID: e37e43a497d5a8b7c0cc1736d56986f432c394c9
> > Gitweb:
> > http://git.kernel.org/tip/e37e43a497d5a8b7c0cc1736d56986f432c394c9
> >
On Oct 21, 2016 5:32 AM, "Matt Fleming" wrote:
>
> On Wed, 24 Aug, at 06:03:04AM, tip-bot for Andy Lutomirski wrote:
> > Commit-ID: e37e43a497d5a8b7c0cc1736d56986f432c394c9
> > Gitweb:
> > http://git.kernel.org/tip/e37e43a497d5a8b7c0cc1736d56986f432c394c9
> > Author: Andy Lutomirski
>
On Fri, 21 Oct 2016 14:05:36 +0200
Peter Zijlstra wrote:
> On Fri, Oct 21, 2016 at 01:58:55PM +0200, Christian Borntraeger wrote:
> > stop_machine can take a very long time if the hypervisor does
> > overcommitment for guest CPUs. When waiting for "the one", lets
> > give
On Fri, 21 Oct 2016 14:05:36 +0200
Peter Zijlstra wrote:
> On Fri, Oct 21, 2016 at 01:58:55PM +0200, Christian Borntraeger wrote:
> > stop_machine can take a very long time if the hypervisor does
> > overcommitment for guest CPUs. When waiting for "the one", lets
> > give up our CPU by using the
On Fri, 21 Oct 2016 12:17:59 -0400
Steven Rostedt wrote:
> Commit 784d5699eddc5 ("x86: move exports to actual definitions") removed the
> EXPORT_SYMBOL(__fentry__) and EXPORT_SYMBOL(mcount) from x8664_ksyms_64.c,
> and added EXPORT_SYMBOL(function_hook) in mcount_64.S
On Fri, 21 Oct 2016 12:17:59 -0400
Steven Rostedt wrote:
> Commit 784d5699eddc5 ("x86: move exports to actual definitions") removed the
> EXPORT_SYMBOL(__fentry__) and EXPORT_SYMBOL(mcount) from x8664_ksyms_64.c,
> and added EXPORT_SYMBOL(function_hook) in mcount_64.S instead. The problem
> is
On Sat, Oct 22, 2016 at 09:50:13AM +1100, Dave Chinner wrote:
> On Fri, Oct 21, 2016 at 06:00:07PM +0300, Kirill A. Shutemov wrote:
> > On Fri, Oct 21, 2016 at 04:01:18PM +1100, Dave Chinner wrote:
> > > On Thu, Oct 20, 2016 at 07:01:16PM -0700, Andi Kleen wrote:
> > > > > Ugh, no, please don't
On Sat, Oct 22, 2016 at 09:50:13AM +1100, Dave Chinner wrote:
> On Fri, Oct 21, 2016 at 06:00:07PM +0300, Kirill A. Shutemov wrote:
> > On Fri, Oct 21, 2016 at 04:01:18PM +1100, Dave Chinner wrote:
> > > On Thu, Oct 20, 2016 at 07:01:16PM -0700, Andi Kleen wrote:
> > > > > Ugh, no, please don't
Hi Prashanth,
On Fri, Oct 21, 2016 at 9:13 AM, Prakash, Prashanth
wrote:
> Hi Hoan,
>
> On 10/18/2016 1:00 AM, Hoan Tran wrote:
>> This patch fixes the lockdep warning below
>>
>> [7.229767] DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
>> [7.229776]
Hi Prashanth,
On Fri, Oct 21, 2016 at 9:13 AM, Prakash, Prashanth
wrote:
> Hi Hoan,
>
> On 10/18/2016 1:00 AM, Hoan Tran wrote:
>> This patch fixes the lockdep warning below
>>
>> [7.229767] DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
>> [7.229776] [ cut here
From: Bjorn Andersson
Add SMEM and TCSR DT nodes on MSM8996.
Signed-off-by: Bjorn Andersson
Signed-off-by: Sarangdhar Joshi
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 17 +
1 file changed, 17
On Fri, Oct 21, 2016 at 1:20 PM, Matt Fleming wrote:
> On Fri, 21 Oct, at 04:41:29PM, Matt Fleming wrote:
>>
>> FYI, I've been able to reproduce some crash when using your EFI memory
>> map layout under Qemu and forcing the ESRT driver to reserve the space.
>
> Nope,
From: Bjorn Andersson
Add SMEM and TCSR DT nodes on MSM8996.
Signed-off-by: Bjorn Andersson
Signed-off-by: Sarangdhar Joshi
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
On Fri, Oct 21, 2016 at 1:20 PM, Matt Fleming wrote:
> On Fri, 21 Oct, at 04:41:29PM, Matt Fleming wrote:
>>
>> FYI, I've been able to reproduce some crash when using your EFI memory
>> map layout under Qemu and forcing the ESRT driver to reserve the space.
>
> Nope, that was a bug in my hack. I
Add reserve-memory nodes required for Qualcomm
Peripheral Image Loaders
Acked-by: Bjorn Andersson
Signed-off-by: Sarangdhar Joshi
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 25 +
1 file changed, 25 insertions(+)
diff
Add DT node to carveout memory for shared memory region.
Reviewed-by: Bjorn Andersson
Signed-off-by: Sarangdhar Joshi
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git
Add reserve-memory nodes required for Qualcomm
Peripheral Image Loaders
Acked-by: Bjorn Andersson
Signed-off-by: Sarangdhar Joshi
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 25 +
1 file changed, 25 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
Add DT node to carveout memory for shared memory region.
Reviewed-by: Bjorn Andersson
Signed-off-by: Sarangdhar Joshi
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
Add SMP2P and APCS DT nodes required for Qualcomm ADSP
Peripheral Image Loader.
Acked-by: Bjorn Andersson
Signed-off-by: Sarangdhar Joshi
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 29 +
1 file changed, 29
Add SMP2P and APCS DT nodes required for Qualcomm ADSP
Peripheral Image Loader.
Acked-by: Bjorn Andersson
Signed-off-by: Sarangdhar Joshi
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 29 +
1 file changed, 29 insertions(+)
diff --git
Add various device tree nodes to lay the groundwork for
Qualcomm ADSP Peripheral Image Loader.
Sorry, I didn't send any cover letter for v1.
Changes since v2:
- Remove empty lines from smem DT node (Stephen)
Changes since v1:
- Move hwlock DT node under root (/) (Bjorn and Andy)
- Rename
Add various device tree nodes to lay the groundwork for
Qualcomm ADSP Peripheral Image Loader.
Sorry, I didn't send any cover letter for v1.
Changes since v2:
- Remove empty lines from smem DT node (Stephen)
Changes since v1:
- Move hwlock DT node under root (/) (Bjorn and Andy)
- Rename
On 10/20/2016 04:54 PM, Stephen Boyd wrote:
On 10/20, Sarangdhar Joshi wrote:
Add xo clock support required for Qualcomm ADSP
Peripheral Image Loader.
Yes but why is xo needed?
It is required to boot up the ADSP processor. The remoteproc driver
keeps the xo clock enabled until the driver
On 10/20/2016 04:54 PM, Stephen Boyd wrote:
On 10/20, Sarangdhar Joshi wrote:
Add xo clock support required for Qualcomm ADSP
Peripheral Image Loader.
Yes but why is xo needed?
It is required to boot up the ADSP processor. The remoteproc driver
keeps the xo clock enabled until the driver
We've got a delay loop waiting for secondary CPUs. That loop uses
loops_per_jiffy. However, loops_per_jiffy doesn't actually mean how
many tight loops make up a jiffy on all architectures. It is quite
common to see things like this in the boot log:
Calibrating delay loop (skipped), value
We've got a delay loop waiting for secondary CPUs. That loop uses
loops_per_jiffy. However, loops_per_jiffy doesn't actually mean how
many tight loops make up a jiffy on all architectures. It is quite
common to see things like this in the boot log:
Calibrating delay loop (skipped), value
On Fri, Oct 21, 2016 at 03:42:50PM -0700, Michael Scott wrote:
> Initial pinctrl driver for QCOM msm8994 platforms.
>
> In order to continue the initial board support for QCOM msm8994/msm8992
> presented in patches from Jeremy McNicoll , let's put
> a proper pinctrl driver in
On Fri, Oct 21, 2016 at 03:42:50PM -0700, Michael Scott wrote:
> Initial pinctrl driver for QCOM msm8994 platforms.
>
> In order to continue the initial board support for QCOM msm8994/msm8992
> presented in patches from Jeremy McNicoll , let's put
> a proper pinctrl driver in place.
>
>
When running checkpatch.pl on a new pinctrl driver in
drivers/pinctrl/qcom, I noticed a warning about creating
a new maintainer. The drivers/pinctrl/qcom folder doesn't have
anyone assigned in the MAINTAINERS file.
Let's assign it to ARM/QUALCOMM SUPPORT.
Signed-off-by: Michael Scott
When running checkpatch.pl on a new pinctrl driver in
drivers/pinctrl/qcom, I noticed a warning about creating
a new maintainer. The drivers/pinctrl/qcom folder doesn't have
anyone assigned in the MAINTAINERS file.
Let's assign it to ARM/QUALCOMM SUPPORT.
Signed-off-by: Michael Scott
---
On Sat, Oct 22, 2016 at 12:51:32AM +0300, sonofa...@openmailbox.org wrote:
> Thank you for your time! I have chosen reply to list and all recipients, it
> must work now.
Yes, exactly what I had in mind.
> My brother rejected the proposed patch because it does not provide
> equivalent
On Sat, Oct 22, 2016 at 12:51:32AM +0300, sonofa...@openmailbox.org wrote:
> Thank you for your time! I have chosen reply to list and all recipients, it
> must work now.
Yes, exactly what I had in mind.
> My brother rejected the proposed patch because it does not provide
> equivalent
On Fri, Oct 21, 2016 at 01:35:14PM -0700, Shaohua Li wrote:
> In our systems, proc/sysfs inode/dentry cache use more than 1G memory
> even memory pressure is high sometimes. Since proc/sysfs is in-memory
> filesystem, rebuilding the cache is fast. There is no point proc/sysfs
> and disk fs have
On Fri, Oct 21, 2016 at 01:35:14PM -0700, Shaohua Li wrote:
> In our systems, proc/sysfs inode/dentry cache use more than 1G memory
> even memory pressure is high sometimes. Since proc/sysfs is in-memory
> filesystem, rebuilding the cache is fast. There is no point proc/sysfs
> and disk fs have
Salut,
On 11/10/16 15:28, Maxime Ripard wrote:
> Modify the current clocks we have to be able to specify the minimum for
> each clocks we support, just like we support the max.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/clk/sunxi-ng/ccu_mult.c | 7
Salut,
On 11/10/16 15:28, Maxime Ripard wrote:
> Modify the current clocks we have to be able to specify the minimum for
> each clocks we support, just like we support the max.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/clk/sunxi-ng/ccu_mult.c | 7 ++-
>
On 10/21/16 11:41, Andrew Morton wrote:
> On Wed, 5 Oct 2016 21:40:10 +0800 cheng...@emindsoft.com.cn wrote:
>
>> In api itself, kernel does not use it -- it is divided into ac_etime_hi
>> and ac_etime_lo. So kernel side only need generate the correct
>> ac_etime_hi and ac_etime_lo, but need
On 10/21/16 11:41, Andrew Morton wrote:
> On Wed, 5 Oct 2016 21:40:10 +0800 cheng...@emindsoft.com.cn wrote:
>
>> In api itself, kernel does not use it -- it is divided into ac_etime_hi
>> and ac_etime_lo. So kernel side only need generate the correct
>> ac_etime_hi and ac_etime_lo, but need
On Fri, Oct 21, 2016 at 06:00:07PM +0300, Kirill A. Shutemov wrote:
> On Fri, Oct 21, 2016 at 04:01:18PM +1100, Dave Chinner wrote:
> > On Thu, Oct 20, 2016 at 07:01:16PM -0700, Andi Kleen wrote:
> > > > Ugh, no, please don't use mount options for file specific behaviours
> > > > in filesystems
On Fri, Oct 21, 2016 at 06:00:07PM +0300, Kirill A. Shutemov wrote:
> On Fri, Oct 21, 2016 at 04:01:18PM +1100, Dave Chinner wrote:
> > On Thu, Oct 20, 2016 at 07:01:16PM -0700, Andi Kleen wrote:
> > > > Ugh, no, please don't use mount options for file specific behaviours
> > > > in filesystems
On Fri, Oct 21, 2016 at 09:51:03PM +0300, Kirill A. Shutemov wrote:
> + case SHEME_HUGE_ALWAYS:
Oops. Forgot to commit the fixup :-/
>From 79b0a3bf4503225d0e6ba553b8496f0c4d55514e Mon Sep 17 00:00:00 2001
From: "Kirill A. Shutemov"
Date: Mon, 17 Oct
On Fri, Oct 21, 2016 at 09:51:03PM +0300, Kirill A. Shutemov wrote:
> + case SHEME_HUGE_ALWAYS:
Oops. Forgot to commit the fixup :-/
>From 79b0a3bf4503225d0e6ba553b8496f0c4d55514e Mon Sep 17 00:00:00 2001
From: "Kirill A. Shutemov"
Date: Mon, 17 Oct 2016 14:44:47 +0300
Subject:
Initial pinctrl driver for QCOM msm8994 platforms.
In order to continue the initial board support for QCOM msm8994/msm8992
presented in patches from Jeremy McNicoll , let's put
a proper pinctrl driver in place.
Currently, the DT for these platforms uses the msm8x74 pinctrl
Initial pinctrl driver for QCOM msm8994 platforms.
In order to continue the initial board support for QCOM msm8994/msm8992
presented in patches from Jeremy McNicoll , let's put
a proper pinctrl driver in place.
Currently, the DT for these platforms uses the msm8x74 pinctrl driver to enable
basic
On Sun, Sep 18, 2016 at 01:38:30PM +0200, Linus Walleij wrote:
> On Fri, Sep 16, 2016 at 7:41 PM, Srinivas Kandagatla
> wrote:
>
> > This patch adds defines for internal voltage regulators used
> > to switch voltage levels on gpio/mpp pads.
> >
> > Signed-off-by:
On Sun, Sep 18, 2016 at 01:38:30PM +0200, Linus Walleij wrote:
> On Fri, Sep 16, 2016 at 7:41 PM, Srinivas Kandagatla
> wrote:
>
> > This patch adds defines for internal voltage regulators used
> > to switch voltage levels on gpio/mpp pads.
> >
> > Signed-off-by: Srinivas Kandagatla
>
>
Hi Linus,
Please pull some more powerpc fixes for 4.9:
The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
Hi Linus,
Please pull some more powerpc fixes for 4.9:
The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
On Fri, Oct 21, 2016 at 11:19:31AM -0700, Eric Biggers wrote:
>
> I don't think it's reasonable to require require changes to filesystems
> whenever
> someone introduces a new encryption mode --- contents, filenames, or both.
> Filesystems need to be able to handle unsupported encryption modes
On Fri, Oct 21, 2016 at 11:19:31AM -0700, Eric Biggers wrote:
>
> I don't think it's reasonable to require require changes to filesystems
> whenever
> someone introduces a new encryption mode --- contents, filenames, or both.
> Filesystems need to be able to handle unsupported encryption modes
1 - 100 of 1918 matches
Mail list logo