Currently, the governor calculates the next frequency, set the current CPU
frequency (policy->cur). It also assumes the current CPU frequency doesn't
change if the next frequency isn't calculated again and hence caches the
"current frequency".
However, this isn't true when CPU min/max frequency li
On Tue, Jul 11, 2017 at 06:04:54PM +0200, Peter Zijlstra wrote:
>
> Sorry for the much delayed response; aside from the usual backlog I got
> unusually held up by family responsibilities.
>
> My comments in the form of a patch..
Thank you.
I will apply it at the next spin.
Hi Oliver,
Thanx for your comments, and sorry for reply late.
On 07/04/2017 07:38 PM, Oliver Neukum wrote:
Am Freitag, den 23.06.2017, 11:46 +0800 schrieb jeffy:
---
drivers/bluetooth/btusb.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/bluetooth/btusb.c b/dr
Hi Suganath,
[auto build test ERROR on scsi/for-next]
[also build test ERROR on v4.12 next-20170711]
[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/Suganath-Prabu-S/mpt3sas-Add-nvme-device
> -Original Message-
> From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
> Behalf Of Daniel Vetter
> Sent: Tuesday, July 11, 2017 5:13 PM
> To: Gerd Hoffmann
> Cc: Tian, Kevin ; linux-kernel@vger.kernel.org; intel-
> g...@lists.freedesktop.org; alex.william...@r
On 2017/7/12 0:09, Frederic Weisbecker wrote:
> On Tue, Jul 11, 2017 at 11:41:57AM +0200, Peter Zijlstra wrote:
>>
>>> - totally from arch_cpu_idle_enter entry to arch_cpu_idle_exit return costs
>>> 9122ns - 15318ns.
>>> --In this period, rcu_idle_enter costs 1985ns - 2262ns, rcu_idle_exit
>>>
On Wed, Jul 12, 2017 at 3:31 AM, Maxime Ripard
wrote:
> On Mon, Jul 10, 2017 at 11:48:00PM +0800, Chen-Yu Tsai wrote:
>> On Sun, Jun 18, 2017 at 10:05 PM, Rob Herring wrote:
>> > On Wed, Jun 14, 2017 at 02:30:16PM +0800, Chen-Yu Tsai wrote:
>> >> The explanation for the endpoint ID numbering sche
On Wed, Jul 12, 2017 at 3:21 AM, Maxime Ripard
wrote:
> On Mon, Jul 10, 2017 at 04:55:04PM +1000, Jonathan Liu wrote:
>> The drm_driver lastclose callback is called when the last userspace
>> DRM client has closed. Call drm_fbdev_cma_restore_mode to restore
>> the fbdev console otherwise the fbdev
> -Original Message-
> From: Gerd Hoffmann [mailto:kra...@redhat.com]
> Sent: Tuesday, July 11, 2017 2:08 PM
> To: Zhang, Tina ; alex.william...@redhat.com;
> ch...@chris-wilson.co.uk; zhen...@linux.intel.com; Lv, Zhiyuan
> ; Wang, Zhi A ; Tian, Kevin
> ; dan...@ffwll.ch; kwankh...@nvidia
Could you check this patchset considering cpu topology on cpu selection?
On Tue, May 23, 2017 at 11:00:55AM +0900, Byungchul Park wrote:
> When cpudl_find() returns any among free_cpus, the cpu might not be
> closer than others, considering sched domain. For example:
>
>this_cpu: 15
>free
Hi, Xiaolong
Thank you very much for testing. I have got the reason why the ACPI
error happened and will give a fix patch below.
Also cc ACPI maintainers..
At 07/08/2017 11:48 AM, kernel test robot wrote:
FYI, we noticed the following commit:
commit: f61a8e12b5972879f8decfe059e54c813dc4416b (
The LM75 interrupt cannot be masked in the device so an over-temperature
event can cause an interrupt that cannot be cleared.
Add an interrupt handler if an interrupt node exists in the DTS for an
LM75. The handler simply reads a device register to clear the interrupt
and returns.
Signed-off-by:
On 2017/7/12 0:30, Luis Henriques wrote:
> This commit removes an extra inode_unlock() that is being done in function
> f2fs_ioc_setflags error path. While there, get rid of a useless 'out'
> label as well.
>
> Fixes: 0abd675e97e6 ("f2fs: support plain user/group quota")
> Signed-off-by: Luis Hen
From: Eduardo Valentin
Date: Tue, 11 Jul 2017 14:55:12 -0700
> We currently get the following kmemleak report:
> unreferenced object 0x8800039d9820 (size 32):
> comm "softirq", pid 0, jiffies 4295212383 (age 792.416s)
> hex dump (first 32 bytes):
> 00 0c e0 03 00 88 ff ff ff 02 00 00
On Lenovo ThinkPad X1 Carbon - the 5th Generation, enabling an earlier EC
event freezing timing causes acpitz-virtual-0 to report a stucked 48C
temparature. And with EC firmware revisioned as 1.14, without reverting
back to old EC event freezing timing, the fan still blows up after a system
resume
According to the bug report, though the busy polling mode can make noirq
stages executed faster, it causes abnormal fan blowing up after a system
resume (see link #1 for a video demonstration) on Lenovo ThinkPad X1 Carbon
- the 5th Generation. The problem can be fixed by an upgraded EC firmware.
On Tue, 11 Jul 2017 08:44:15 -0700
Ram Pai wrote:
> On Tue, Jul 11, 2017 at 03:59:59PM +1000, Balbir Singh wrote:
> > On Wed, 5 Jul 2017 14:21:39 -0700
> > Ram Pai wrote:
> >
> > > Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6
> > > in the 64K backed HPTE pages. This along with t
> -Original Message-
> From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
> Behalf Of Daniel Vetter
> Sent: Tuesday, July 11, 2017 5:16 PM
> To: Zhang, Tina
> Cc: Tian, Kevin ; linux-kernel@vger.kernel.org; intel-
> g...@lists.freedesktop.org; kwankh...@nvidia.co
From: Meelis Roos
Date: Tue, 11 Jul 2017 14:48:27 +0300 (EEST)
>> I tested yesterdays git with 4.13 sparc merge on a big bunch of my test
>> machines.
>>
>> Good news: the timestamps starting from boot seem to work on all the
>> machines, starting with Ultra 1 and Ultra 2.
>>
>> Bad news: all
On 2017/7/12 2:11, Paul E. McKenney wrote:
> On Tue, Jul 11, 2017 at 06:33:55PM +0200, Frederic Weisbecker wrote:
>> On Tue, Jul 11, 2017 at 05:58:47AM -0700, Paul E. McKenney wrote:
>>> On Mon, Jul 10, 2017 at 09:38:34AM +0800, Aubrey Li wrote:
From: Aubrey Li
The system will enter
On 07/11/2017 06:20 PM, Andrew Jeffery wrote:
On Tue, 2017-07-11 at 06:31 -0700, Guenter Roeck wrote:
On 07/10/2017 06:56 AM, Andrew Jeffery wrote:
Some PMBus chips, such as the MAX31785, use different coefficients for
FAN_COMMAND_[1-4] depending on whether the fan is in PWM (percent duty)
or R
On 07/06/2017 06:01 PM, Heiko Stübner wrote:
Hi Elaine,
Am Donnerstag, 6. Juli 2017, 16:28:34 CEST schrieb Elaine Zhang:
fractional divider must set that denominator is 20 times larger than
numerator to generate precise clock frequency.
Otherwise the CLK jitter is very big, poor quality of th
On 2017.07.11 11:12:36 +0200, Daniel Vetter wrote:
> On Tue, Jul 11, 2017 at 08:14:08AM +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > > > +struct vfio_device_query_gfx_plane {
> > > > + __u32 argsz;
> > > > + __u32 flags;
> > > > + struct vfio_device_gfx_plane_info plane_info;
>
On Wed, 5 Jul 2017 14:21:51 -0700
Ram Pai wrote:
> Initial plumbing to manage all the keys supported by the
> hardware.
>
> Total 32 keys are supported on powerpc. However pkey 0,1
> and 31 are reserved. So effectively we have 29 pkeys.
>
> This patch keeps track of reserved keys, allocated k
From: Sean Wang
The series adds the driver for ethernet controller found on MT7622 SoC.
There are additions against with previous MT7623 SoC such as shared SGMII
given for the dual GMACs and built-in 5-ports 10/100 embedded switch support
(ESW). Thus more clocks consumers and SGMII hardware setup
From: Sean Wang
The patch adds the supplements in the dt-binding document for MediaTek
MT7622 SoC with extra SGMII system controller and relevant clock consumers
listed as the requirements for those SoCs equipped with the SGMII circuit.
Also, add the missing binding information for MT7623 SoC her
From: Sean Wang
Sean and Nelson work for MediaTek on maintaining the MediaTek ethernet
driver for the existing SoCs and adding support for the following SoCs.
In the past, Sean has been active at making most of the qualifications
, stress test and submitting a lot of patches for the driver while
From: Sean Wang
This patch is the preparation patch in order to adapt into various
hardware through adding platform data which holds specific characteristics
among MediaTek SoCs and introducing the unified clock handler for those
distinct clock requirements depending on different features such as
From: Sean Wang
This patch adds the driver for ethernet controller on MT7622 SoC. It has
the similar handling logic as the previously MT7623 does, but there are
additions against with MT7623 SoC, the shared SGMII given for the dual
GMACs and including 5-ports 10/100 embedded switch support (ESW)
On Tue, Jul 11, 2017 at 06:01:38AM +, Nick Terrell wrote:
> On 7/10/17, 9:57 PM, "Nick Terrell" wrote:
> > The problem is caused by a gcc-7 bug [1]. It miscompiles
> > ZSTD_wildcopy(void *dst, void const *src, ptrdiff_t len) when len is 0.
>
> Sorry, my patch still triggered the gcc bug, I use
Similar to other Gigabyte laptops, the touchpad on P57 requires a
keyboard reset to detect Elantech touchpad correctly.
BugLink: https://bugs.launchpad.net/bugs/1594214
Signed-off-by: Kai-Heng Feng
---
drivers/input/serio/i8042-x86ia64io.h | 7 +++
1 file changed, 7 insertions(+)
diff --git
On 07/11/2017 05:39 PM, Andrew Jeffery wrote:
On Tue, 2017-07-11 at 06:40 -0700, Guenter Roeck wrote:
On 07/10/2017 06:56 AM, Andrew Jeffery wrote:
Augment PMBus support to include control of fans via the
FAN_COMMAND_[1-4] registers, both in RPM and PWM modes. The behaviour
of FAN_CONFIG_{1_2,3
On 07/11/2017 05:34 PM, David Miller wrote:
From: Tushar Dave
Date: Tue, 11 Jul 2017 15:38:21 -0700
On 07/11/2017 02:48 PM, Meelis Roos wrote:
I tested yesterdayd 4.12+git on sparc64 to see if the sparc merge
works
fine, and on all of my sun4v machines (T1000, T2000, T5120) it crashed
on
Quoting Stefan Berger (Stefan bergerstef...@linux.vnet.ibm.com):
> +/*
> + * xattr_list_userns_rewrite - Rewrite list of xattr names for user
> namespaces
> + * or determine needed size for attribute list
> + * in case size == 0
> + *
> + * I
Some platforms add the OPPs dynamically from platform specific drivers
instead of getting them statically from DT. The cpufreq-dt driver
already ignores the return value of dev_pm_opp_of_cpumask_add_table() to
not error out for such cases, but we still end up printing error message
from that routin
From:
Date: Wed, 12 Jul 2017 11:37:41 +0800
> From: Sean Wang
>
> The series adds the driver for ethernet controller found on MT7622 SoC.
> There are additions against with previous MT7623 SoC such as shared SGMII
> given for the dual GMACs and built-in 5-ports 10/100 embedded switch support
>
Wir vergeben Kredite mit einem Zinssatz von jährlich 2%.
Die Bearbeitung des Antrags erfolgt rasch, wir verlangen keine Gebühren, was
sie beantragen werden wir annehmen. Wir bewilligen Kredite von bis zu 40
Millionen Euro und von mindestens 15.000 Euro. Sie können einen geschäftlichen
oder pri
> In following commits around this one (some bisect steps before, and the
> last step) the crashes were slightly different from the original crash
> yersterday, like
>
> in:imuxsock[1606]: segfault at fff8 ip f774e154 (rpc
> f774dfe8) sp 0001f7965a68 error 30002 in
> li
The dwc3 could not release resources when the module is built-in
because this module does not have shutdown method. This causes the USB
3.0 hub is not able to detect after warm boot.
Original patch by Brian Kim, updated and submitted upstream by gustavo
panizzo.
Also see https://bugs.debian.org/8
From: Tushar Dave
Date: Tue, 11 Jul 2017 20:43:39 -0700
> Yes, indeed the bug is in Linus's tree. However, 'sparc' tree doesn't
> have DMA API change (e.g. commit b02c2b0bfd7ae) yet that introduced
> the panic.
You can simply make a note of this when you send the bug fix to me.
All PCIe devices are expected to be able to handle 8-bit tags.
'commit 60db3a4d8cc9 ("PCI: Enable PCIe Extended Tags if supported")'
enabled extended tags for all devices based on the spec direction.
The Broadcom HT2100 seems to be having issues with handling
8-bit tags. Mark it as broken.
If a d
1) Fix symbol version generation for assembler on sparc, from
Nagarathnam Muthusamy.
2) Fix compound page handling in gup_huge_pmd(), from Nitin Gupta.
Please pull, thanks a lot!
The following changes since commit 5faab9e0f03c4eef97886b45436015e107f79f5f:
Merge branch 'for-linus' of
git:
Hi all,
Please do not add any v4.14 material to you linux-next included branches
until after v4.13-rc1 has been released.
Changes since 20170711:
The vfs tree lost its build failure.
Non-merge commits (relative to Linus' tree): 1170
1121 files changed, 44069 insertions(+), 16713 dele
On 11-07-17, 16:06, Dietmar Eggemann wrote:
> But in the meantime we're convinced that cpufreq_driver_fast_switch() is
> not the right place to call arch_set_freq_scale() since for (future)
> arm/arm64 fast-switch driver, the return value of
> cpufreq_driver->fast_switch() does not give us the info
From: Al Viro
Date: Wed, 12 Jul 2017 04:59:45 +0100
> Again, my apologies for format of that all - I'm almost completely
> off-net and while typing an ed script is feasible, context diff is
> too far over the top. Usimg mutt in ssh session from android is
> not fun, to put it mildly...
Yes, t
Anyone think this is an OK-ish idea?
It saves us the global symbol but requires the two functions to remained
glued together. :-\
---
diff --git a/arch/x86/entry/entry_64_compat.S b/arch/x86/entry/entry_64_compat.S
index e1721dafbcb1..262519da8661 100644
--- a/arch/x86/entry/entry_64_compat.S
+++
On 2017/7/12 0:34, Peter Zijlstra wrote:
> On Tue, Jul 11, 2017 at 06:09:27PM +0200, Frederic Weisbecker wrote:
>
- tick_nohz_idle_enter costs 7058ns - 10726ns
- tick_nohz_idle_exit costs 8372ns - 20850ns
>>>
>>> Right, those are horrible expensive, but skipping them isn't 'hard', the
>>
On 07/11/2017 08:37 PM, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> This patch is the preparation patch in order to adapt into various
> hardware through adding platform data which holds specific characteristics
> among MediaTek SoCs and introducing the unified clock handler for those
>
On 07/11/2017 09:02 PM, David Miller wrote:
From: Tushar Dave
Date: Tue, 11 Jul 2017 20:43:39 -0700
Yes, indeed the bug is in Linus's tree. However, 'sparc' tree doesn't
have DMA API change (e.g. commit b02c2b0bfd7ae) yet that introduced
the panic.
You can simply make a note of this when y
Hi all,
On Sat, 06 May 2017 11:12:36 -0700 James Bottomley
wrote:
>
> What about resending the conflict reminders at -rc7 ... that way we
> only have a week or two to forget again?
OK, I attempted to do that this time ... I wonder if it made a
difference :-)
> The other issue is that one of th
Declare functions to fix sparse warnings:
ion_carveout_heap.c:115:17: warning: symbol 'ion_carveout_heap_create' \
was not declared. Should it be static?
ion_chunk_heap.c:120:17: warning: symbol 'ion_chunk_heap_create' \
was not declared. Should it be static?
Signed-off-by: Joseph
Split sparse warning fixes into multiple patches.
Joseph Wright (2):
Staging: android/ion: fix sparse warnings
Staging: android/ion: fix sparse warning
drivers/staging/android/ion/ion.h | 4
drivers/staging/android/ion/ion_cma_heap.c | 2 +-
2 files changed, 5 insertions(+), 1
Declare private function static to fix sparse warning:
ion_cma_heap.c:109:5: warning: symbol '__ion_add_cma_heaps' \
was not declared. Should it be static?
Signed-off-by: Joseph Wright
---
Changes in v2:
- Split into multiple patches
drivers/staging/android/ion/ion_cma_heap.c | 2 +-
On 11-07-17, 07:14, Joel Fernandes wrote:
> I think the whole point of IOWAIT boost was to solve the issue with a
> long sequence of repeated I/O requests as described in the commit
> message. So IIUC there isn't a usecase for that (increase freq. on
> first request).
Right. So we can take example
On Wed, Jul 12, 2017 at 11:19:59AM +0800, Li, Aubrey wrote:
> On 2017/7/12 2:11, Paul E. McKenney wrote:
> > On Tue, Jul 11, 2017 at 06:33:55PM +0200, Frederic Weisbecker wrote:
> >> On Tue, Jul 11, 2017 at 05:58:47AM -0700, Paul E. McKenney wrote:
> >>> On Mon, Jul 10, 2017 at 09:38:34AM +0800, Au
On 2017-07-12 03:02, Stephen Boyd wrote:
> This patchset adds support for the TC7USB40MU usb mux found on
> db410c 96boards platforms via the new multiplexer framework and
> hooks that into the chipidea driver. This allows us to properly
> control host or device mode on this board via the sysfs kn
On Jul 11, 2017, at 11:14, Greg Kroah-Hartman
wrote:
>
> On Fri, Jul 07, 2017 at 01:47:04AM +, Craig Inches wrote:
>> This fixes multiple block statements found not to match
>> style as per checkpatch
>>
>> Signed-off-by: Craig Inches
>> ---
>> drivers/staging/lustre/include/linux/lnet/lne
> On Jul 11, 2017, at 11:08, Greg KH wrote:
>
> On Thu, Jul 06, 2017 at 12:43:15PM +0530, Jaya Durga wrote:
>> Replace all instances of (1 << 27) with BIT(27) to fix
>> checkpatch check messages
>>
>> Signed-off-by: Jaya Durga
>> ---
>> drivers/staging/lustre/lustre/include/lustre_compat.h | 2
We should free 'wgds.pointer' here as done a few lines above in another
error handling path.
It was allocated within 'acpi_evaluate_object()'.
Signed-off-by: Christophe JAILLET
---
A comment in '/drivers/acpi/acpica/utalloc.c' states that:
/* [...] Note: The caller should use acpi_os_free to free
Hi,
please consider changing your subject to something like
staging: android/ion: declare two functions
Perhaps you can make it more on-topic. It's more useful than "fix
sparse warning"
On Wed, Jul 12, 2017 at 6:51 AM, Joseph Wright wrote:
> Declare functions to fix sparse warnings:
>
> ion_ca
On 2017/7/12 13:03, Paul E. McKenney wrote:
> On Wed, Jul 12, 2017 at 11:19:59AM +0800, Li, Aubrey wrote:
>> On 2017/7/12 2:11, Paul E. McKenney wrote:
>>> On Tue, Jul 11, 2017 at 06:33:55PM +0200, Frederic Weisbecker wrote:
On Tue, Jul 11, 2017 at 05:58:47AM -0700, Paul E. McKenney wrote:
>
Hi,
Again, your subject is too generic.
On Wed, Jul 12, 2017 at 6:51 AM, Joseph Wright wrote:
> Declare private function static to fix sparse warning:
>
> ion_cma_heap.c:109:5: warning: symbol '__ion_add_cma_heaps' \
> was not declared. Should it be static?
>
> Signed-off-by: Joseph Wri
On 11-07-17, 19:24, Saravana Kannan wrote:
> Currently, the governor calculates the next frequency, set the current CPU
> frequency (policy->cur). It also assumes the current CPU frequency doesn't
> change if the next frequency isn't calculated again and hence caches the
> "current frequency".
>
>
On 06/21, Eugeniy Paltsev wrote:
> AXS10X boards manages it's clocks using various PLLs. These PLL has same
> dividers and corresponding control registers mapped to different addresses.
> So we add one common driver for such PLLs.
>
> Each PLL on AXS10X board consist of three dividers: IDIV, FBDIV
On Wed, 5 Jul 2017 14:21:52 -0700
Ram Pai wrote:
> Implements helper functions to read and write the key related
> registers; AMR, IAMR, UAMOR.
>
> AMR register tracks the read,write permission of a key
> IAMR register tracks the execute permission of a key
> UAMOR register enables and disables
* Sebastian Reichel [170711 15:51]:
> Hi,
>
> On Tue, Jul 11, 2017 at 11:41:52PM +0200, Thomas Gleixner wrote:
> > [...]
> >
> > Here is a revised version of the previous patch with the conditional
> > locking removed and a bunch of comments added.
>
> That one also fixes Droid 4 boot.
>
> Test
On Tue, Jul 11, 2017 at 7:57 PM, Yves Lemée wrote:
> According the coding style guidelines, the ENOSYS error code must be returned
> in case of a non existent system call. This code has been replaced with
> the ENOTTY error code indicating, a missing functionality.
>
> Signed-off-by: Yves Lemée
On Tue, 11 Jul 2017 10:57:44 -0400
Jerome Glisse wrote:
> On Tue, Jul 11, 2017 at 02:12:15PM +1000, Balbir Singh wrote:
> > On Mon, 3 Jul 2017 17:14:12 -0400
> > Jérôme Glisse wrote:
> >
> > > Platform with advance system bus (like CAPI or CCIX) allow device
> > > memory to be accessible fro
On Tue, Jul 11, 2017 at 10:03:01PM +0100, Sudip Mukherjee wrote:
> Hi Greg,
>
> On Fri, Jun 30, 2017 at 09:57:43PM +0100, Sudip Mukherjee wrote:
> > From: Teddy Wang
> >
> > If vesafb is enabled in the config then /dev/fb0 is created by vesa
> > and this sm750 driver gets fb1, fb2. But we need t
Hi,
On 12 July 2017 at 11:52, gustavo panizzo wrote:
> The dwc3 could not release resources when the module is built-in
> because this module does not have shutdown method. This causes the USB
> 3.0 hub is not able to detect after warm boot.
>
> Original patch by Brian Kim, updated and submitted
On Wed, Jul 12, 2017 at 10:23:02AM +0800, Rui Teng wrote:
> On 12/07/2017 1:04 AM, Greg Kroah-Hartman wrote:
> > On Mon, Jul 10, 2017 at 04:57:31PM +0800, Rui Teng wrote:
> > > This patch sets memory to zero directly to avoid unnecessary shift and
> > > bitwise operations on bool type, which can fi
DRM_IOCTL_VERSION is supposed to update the name_len/date_len/desc_len
fields to user.
Fixes: 012c6741c6aa("switch compat_drm_version() to drm_ioctl_kernel()")
Signed-off-by: Jeffy Chen
---
drivers/gpu/drm/drm_ioc32.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/drm_i
RK3399's GPU uses the quad-core Mali-T860, which is the new generation of
high-end graphics processors from ARM.
This patch added "rockchip,rk3399-mali" for dt-bindings, in order to
support IPA of gpu thermal in later.
Signed-off-by: Caesar Wang
---
Documentation/devicetree/bindings/gpu/arm,ma
This patch enables the gpu and adds the mali-supply power for RK3399-GRU
devices.
Signed-off-by: Caesar Wang
---
arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi
b/arch/arm64/boot/dts/rockchip/rk3
As RK3399 had used the Power allocator thermal governor by default,
enabled this to manage thermals by dynamically allocating and limiting
power to devices.
Also, this patch supported the dynamic-power-coefficient/sustainable_power
and GPU's power model for needed parameters with thermal IPA.
Sig
Add Mali GPU device tree node for the RK3399 SoCs, with devfreq
opp table.
RK3399 and RK3399-OP1 SoCs have a different recommendation table with
gpu opp. As the ARM's mali driver found on
https://developer.arm.com/products/software/mali-drivers/midgard-kernel.
Signed-off-by: Caesar Wang
---
ar
This series patches supported the mail in devicetree and used the
thermal IPA by default.
Verified with rk3399 kevin board on my github
https://github.com/Caesar-github/rockchip/commits/gru/next-stable-chromeos
The kernel is based on Linus's master branch and Heiko's
v4.14-armsoc-tmp/dts64 branch.
This patch adds the first constraint type: power-supply.
The constraint is set by setting a voltage range for the respective
regulator device, which will be honored by the regulator core even if
more users turn up. Once the device is probed, the regulator is
released and the constraint is removed.
Some devices are powered ON by the bootloader before the bootloader
handovers control to Linux. It maybe important for those devices to keep
working until the time a Linux device driver probes the device and
reconfigure its resources.
A typical example of that can be the LCD controller, which is u
Hi Greg and others,
I am sending the V2 for this series after waiting for just 2 weeks
because this one presents a clearer picture on how is this going to get
used. V2 has gained updates for adding the constraints for platform and
AMBA devices created from DT.
Problem statement:
Some devices are
This implements the device tree dependent part of the boot constraints.
The supply constraints are added automatically for the platform and AMBA
devices created from DT and will be removed after the driver is
registered for the devices.
It is possible that some of the resources aren't available a
This adds device tree bindings for boot constraints. Only power supply
constraint types are supported currently.
Signed-off-by: Viresh Kumar
---
.../devicetree/bindings/boot-constraints.txt | 68 ++
1 file changed, 68 insertions(+)
create mode 100644 Documentation/devi
This patch adds debugfs support for boot constraints. This is how it
looks for a "vmmc-supply" constraint for the MMC device.
$ ls -R /sys/kernel/debug/boot_constraints/
/sys/kernel/debug/boot_constraints/:
f723d000.dwmmc0
/sys/kernel/debug/boot_constraints/f723d000.dwmmc0:
supply-vmmc
/sys/kern
Users must be given an option to discard any constraints set by
bootloaders. For example, consider that a constraint is set for the LCD
controller's supply and the LCD driver isn't loaded by the kernel. If
the user doesn't need to use the LCD device, then he shouldn't be forced
to honour the constr
On Thu, Jul 06, 2017 at 04:20:42PM +0300, Leonard Crestez wrote:
> On newer imx SOCs accessing OCOTP directly is wrong because the ocotp clock
> needs to be enabled first. Add support for reading those same values through
> the nvmem API instead.
>
> The older path is preserved for compatibility w
On Thu, Jul 06, 2017 at 04:20:43PM +0300, Leonard Crestez wrote:
> On imx6sx accessing OCOTP directly is wrong because the ocotp clock
> needs to be enabled first. Use the nvmem-cells binding instead.
>
> This requirement does not apply to older imx6qdl chips because there the
> ocotp access clock
On Tue, 11 Jul 2017, Linus Torvalds wrote:
> On Tue, Jul 11, 2017 at 3:39 PM, tip-bot for Thomas Gleixner
> wrote:
> > Rightfully-ranted-at-by: Linux Torvalds
>
> Insert .
Google led me to this one:
http://i.imgur.com/qIbRuvb.jpg
Not sure, if that is what you meant.
> I guess with al
On 2017-07-12 03:02, Stephen Boyd wrote:
> On the db410c 96boards platform we have a TC7USB40MU on the board
> to mux the D+/D- lines coming from the controller between a micro
> usb "device" port and a USB hub for "host" roles[1]. During a
> role switch, we need to toggle this mux to forward the D
On Mon, Jun 19, 2017 at 08:00:10AM -0700, Tim Harvey wrote:
> Enables the ADV7180 analog video decoder sensor connected to the
> IMX6 IPU on various Gateworks Ventana boards.
>
> Signed-off-by: Tim Harvey
Applied, thanks.
Hi Dmitry, did you get a chance to merge the sugguested revision, yet?
With gcc 4.1.2:
mm/memory.o: In function `create_huge_pmd':
memory.c:(.text+0x93e): undefined reference to `do_huge_pmd_anonymous_page'
Converting transparent_hugepage_enabled() from a macro to a static
inline function reduced the ability of the compiler to remove unused
code.
Fix this b
701 - 791 of 791 matches
Mail list logo
