the IS_ENABLED in the code path.
Suggested-by: Rafael J. Wysocki
Signed-off-by: Daniel Lezcano
Acked-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 6 ++
include/linux/cpufreq.h | 6 ++
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/cpufreq/cpufreq.c b
On 27/06/2019 15:21, Zhang Rui wrote:
> On 一, 2019-06-24 at 09:32 +0200, Daniel Lezcano wrote:
>> Any chance this patch gets merged for v5.4?
>>
>> Thanks
>> -- Daniel
>>
>
> have you run compile test for the patch?
> I got the following errors
On 23/06/2019 14:38, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> On some i.MX8M platforms, clock driver uses platform driver
> model and it is NOT ready during timer initialization phase,
> the clock operations will fail and system counter driver will
> fail too. As all the i.MX8M
On 23/06/2019 14:38, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> Systems which use platform driver model for clock driver require the
> clock frequency to be supplied via device tree when system counter
> driver is enabled.
>
> This is necessary as in the platform driver model the of_clk
Hi Anson,
On 27/06/2019 10:11, Anson Huang wrote:
> Hi, Daniel
>
>> On 27/06/2019 02:43, Anson Huang wrote:
>>> Hi, Daniel
>>>
On 26/06/2019 03:42, Anson Huang wrote:
> Hi, Daniel
>
>> On 23/06/2019 14:38, anson.hu...@nxp.com wrote:
>>> From: Anson Huang
>>>
>>>
On 27/06/2019 02:43, Anson Huang wrote:
> Hi, Daniel
>
>> On 26/06/2019 03:42, Anson Huang wrote:
>>> Hi, Daniel
>>>
On 23/06/2019 14:38, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> Systems which use platform driver model for clock driver require the
> clock frequency
On 24/06/2019 09:29, Sekhar Nori wrote:
> On 24/06/19 12:51 PM, Bartosz Golaszewski wrote:
>> pon., 24 cze 2019 o 07:40 Daniel Lezcano
>> napisał(a):
>>>
>>>
>>> Sekhar, Bartosz,
>>>
>>> if the sparse warning is not fixed, the dr
From: Dmitry Osipenko
Rename driver's source file to better reflect that it's not specific to
older SoC generations.
Suggested-by: Daniel Lezcano
Signed-off-by: Dmitry Osipenko
Acked-By: Peter De Schrijver
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/Makefile
s.
Signed-off-by: Dmitry Osipenko
Acked-By: Peter De Schrijver
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra20.c | 43 -
1 file changed, 24 insertions(+), 19 deletions(-)
diff --git a/drivers/clocksource/timer-tegra20.c
b/drivers/clocksource/tim
From: Dmitry Osipenko
Release all requested IRQ's on the request error to properly clean up
allocated resources.
Signed-off-by: Dmitry Osipenko
Acked-By: Peter De Schrijver
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra20.c | 5 +++--
1 file changed, 3 insertions(+), 2
, Tegra210 has the
microseconds counter, hence the timer_us clocksource is now made available
for Tegra210 as well.
Signed-off-by: Dmitry Osipenko
Acked-By: Peter De Schrijver
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra20.c | 111 +++-
1 file changed
From: Dmitry Osipenko
Remove build dependency on ARM for compile-testing to allow non-arch
specific build-bots (like Intel's test robot) to compile the driver and
report about problems.
Signed-off-by: Dmitry Osipenko
Acked-By: Peter De Schrijver
Signed-off-by: Daniel Lezcano
---
drivers
From: Dmitry Osipenko
Arch-timer is more preferable for a range of Tegra SoC generations as
it has higher precision and is not affect by any kind of problems.
Pointed-out-by: Peter De Schrijver
Signed-off-by: Dmitry Osipenko
Acked-By: Peter De Schrijver
Signed-off-by: Daniel Lezcano
by some of the
clocksource drivers internally and hence this is just a minor cleanup
change that doesn't fix anything.
Signed-off-by: Dmitry Osipenko
Acked-by: Jon Hunter
Acked-by: Thierry Reding
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra.c | 5 +++--
1 file changed, 3
uot; value can't ever be 0,
unless it's a bug in clocksource core.
Signed-off-by: Dmitry Osipenko
Acked-by: Jon Hunter
Acked-by: Thierry Reding
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git
the proper address.
Signed-off-by: Dmitry Osipenko
Acked-by: Jon Hunter
Acked-by: Thierry Reding
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clocksource/timer-tegra.c
b/drivers/clocksource/timer-tegra.c
index
From: Dmitry Osipenko
It was left unnoticed by accident, which means that the code could be
cleaned up a tad more.
Acked-by: Jon Hunter
Signed-off-by: Dmitry Osipenko
Acked-by: Thierry Reding
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra.c | 42
-by: Mark Rutland
Acked-by: Will Deacon
Signed-off-by: Daniel Lezcano
---
arch/arm/include/asm/arch_timer.h| 10 ++
arch/arm64/include/asm/arch_timer.h | 13 +
drivers/clocksource/arm_arch_timer.c | 15 ++-
3 files changed, 25 insertions(+), 13 deletions
From: Dmitry Osipenko
There is no need to cast void because kernel allows to do that without
a warning message from a compiler.
Acked-by: Jon Hunter
Signed-off-by: Dmitry Osipenko
Acked-by: Thierry Reding
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra.c | 2 +-
1 file
dle equals to
29 bits + 1.
Signed-off-by: Dmitry Osipenko
Acked-by: Jon Hunter
Acked-by: Thierry Reding
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/drivers/clocksource/timer-tegra.c
. The
clocksource code will be included in a subsequent patch.
Signed-off-by: Bartosz Golaszewski
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/Kconfig | 5 +
drivers/clocksource/Makefile| 1 +
drivers/clocksource/timer-davinci.c | 284
include
From: Dmitry Osipenko
Convert all 1MHz literals to a verbose constant for better readability.
Suggested-by: Daniel Lezcano
Acked-by: Jon Hunter
Signed-off-by: Dmitry Osipenko
Acked-by: Thierry Reding
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra.c | 12 +++-
1
From: Bartosz Golaszewski
Extend the davinci-timer driver to also register a clock source.
Signed-off-by: Bartosz Golaszewski
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-davinci.c | 85 +
1 file changed, 85 insertions(+)
diff --git a/drivers
n all
Tegra's")
Acked-by: Jon Hunter
Tested-by: Jon Hunter
Signed-off-by: Dmitry Osipenko
Acked-by: Thierry Reding
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clocksource/timer-tegra.c
b/drivers/c
supports:
- 56-bit counter width (roll-over time greater than 40 years)
- compare frame(64-bit compare value) contains programmable interrupt
generation when compare value <= counter value.
[dlezcano] Fixed over 80 chars length warning
Signed-off-by: Bai Ping
Signed-off-by: Daniel Lezc
From: Masahiro Yamada
This is in-kernel C code, so there is no reason to use _BITUL().
Replace it with equivalent BIT().
I added #include explicitly although it has been included
by other headers eventually.
Signed-off-by: Masahiro Yamada
Signed-off-by: Daniel Lezcano
---
drivers
From: Dmitry Osipenko
Reset timer's hardware state to ensure that initially it is in a
predictable state.
Signed-off-by: Dmitry Osipenko
Acked-By: Peter De Schrijver
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra20.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
with the relaxed versions
since there is no need for the memory-access syncing.
Signed-off-by: Dmitry Osipenko
Acked-By: Peter De Schrijver
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra20.c | 35 +++--
1 file changed, 18 insertions(+), 17 deletions(-)
diff
very
accurate due to the clock rate jitter caused by CPU frequency scaling.
Signed-off-by: Dmitry Osipenko
Acked-By: Peter De Schrijver
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-tegra20.c | 120 ++--
1 file changed, 43 insertions(+), 77 deletions
Szyprowski
Reviewed-by: Krzysztof Kozlowski
Reviewed-by: Chanwoo Choi
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/exynos_mct.c | 4 ++--
include/linux/cpuhotplug.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/clocksource/exynos_mct.c b/drivers
From: Linus Walleij
This adds delay timer functionality to the IXP4xx
timer driver.
Signed-off-by: Linus Walleij
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-ixp4xx.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/drivers/clocksource
From: Neil Armstrong
Comply with the licensing rules defined in the documentation.
Signed-off-by: Neil Armstrong
Reviewed-by: Martin Blumenstingl
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-meson6.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
for clockevents
clocksource/drivers/davinci: Add support for clocksource
Daniel Lezcano (1):
Merge branch 'timers/drivers/davinci' into timers/drivers/next
Dmitry Osipenko (17):
clocksource/drivers/tegra: Support per-CPU timers on all Tegra's
clocksource/drivers/tegra: Unify timer
On 26/06/2019 13:28, Rafael J. Wysocki wrote:
> On Wed, Jun 26, 2019 at 12:19 PM Daniel Lezcano
> wrote:
>>
>> On 26/06/2019 11:06, Rafael J. Wysocki wrote:
>>> On Wed, Jun 26, 2019 at 8:37 AM Viresh Kumar
>>> wrote:
>>>>
>>>> On 26-0
On 26/06/2019 03:42, Anson Huang wrote:
> Hi, Daniel
>
>> On 23/06/2019 14:38, anson.hu...@nxp.com wrote:
>>> From: Anson Huang
>>>
>>> Systems which use platform driver model for clock driver require the
>>> clock frequency to be supplied via device tree when system counter
>>> driver is
On 26/06/2019 11:06, Rafael J. Wysocki wrote:
> On Wed, Jun 26, 2019 at 8:37 AM Viresh Kumar wrote:
>>
>> On 26-06-19, 08:02, Daniel Lezcano wrote:
>>> On 26/06/2019 04:58, Viresh Kumar wrote:
>>>> On 25-06-19, 13:32, Daniel Lezcano wrote:
>>>>&g
Hi Viresh,
On 26/06/2019 04:58, Viresh Kumar wrote:
> On 25-06-19, 13:32, Daniel Lezcano wrote:
>> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
>> index aee024e42618..f07454249fbc 100644
>> --- a/drivers/cpufreq/cpufreq.c
>> +++ b/drivers/cpuf
On 23/06/2019 14:38, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> Systems which use platform driver model for clock driver require the
> clock frequency to be supplied via device tree when system counter
> driver is enabled.
>
> This is necessary as in the platform driver model the of_clk
the IS_ENABLED in the code path.
Suggested-by: Rafael J. Wysocki
Signed-off-by: Daniel Lezcano
Acked-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 6 ++
include/linux/cpufreq.h | 6 ++
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/cpufreq/cpufreq.c b
incorrect
things with the returned pointers (like using it to unregister the
cooling device).
Replace the returned value an integer instead of a pointer to a
thermal cooling device structure.
Suggested-by: Rafael J. Wysocki
Signed-off-by: Daniel Lezcano
---
drivers/thermal/cpu_cooling.c
is
to unregister the cpu cooling device.
As there is no more need of this pointer, remove it.
Signed-off-by: Daniel Lezcano
Acked-by: Viresh Kumar
---
drivers/cpufreq/arm_big_little.c | 9 +++--
drivers/cpufreq/cpufreq.c | 10 --
drivers/thermal
is
to unregister the cpu cooling device.
As there is no more need of this pointer, remove it.
Signed-off-by: Daniel Lezcano
Acked-by: Viresh Kumar
---
drivers/cpufreq/arm_big_little.c | 9 +++--
drivers/cpufreq/cpufreq.c | 10 --
drivers/thermal
the IS_ENABLED in the code path.
Signed-off-by: Daniel Lezcano
---
drivers/cpufreq/cpufreq.c | 6 ++
include/linux/cpufreq.h | 5 +
2 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 85ff958e01f1..aee024e42618
On 24/06/2019 11:30, Rafael J. Wysocki wrote:
> On Monday, June 24, 2019 11:22:19 AM CEST Daniel Lezcano wrote:
>> On 22/06/2019 11:12, Rafael J. Wysocki wrote:
>>> On Fri, Jun 21, 2019 at 3:23 PM Daniel Lezcano
>>> wrote:
>>>>
>>>>
On 22/06/2019 11:12, Rafael J. Wysocki wrote:
> On Fri, Jun 21, 2019 at 3:23 PM Daniel Lezcano
> wrote:
>>
>> The functions stub already exist for the condition the IS_ENABLED
>> is trying to avoid.
>>
>> Remove the IS_ENABLED macros as they are pointless
Hi Rafael,
On 24/06/2019 11:00, Rafael J. Wysocki wrote:
> On Mon, Jun 24, 2019 at 10:53 AM Daniel Lezcano
> wrote:
>>
>>
>> Hi Viresh,
>>
>> On 21/06/2019 15:22, Daniel Lezcano wrote:
>>> The functions stub already exist for the condition the IS_E
Hi Viresh,
On 21/06/2019 15:22, Daniel Lezcano wrote:
> The functions stub already exist for the condition the IS_ENABLED
> is trying to avoid.
>
> Remove the IS_ENABLED macros as they are pointless.
>
> Signed-off-by: Daniel Lezcano
what about this one?
> ---
> d
On 21/06/2019 12:34, claudiu.bez...@microchip.com wrote:
> Hi Daniel,
>
> On 20.06.2019 11:53, Daniel Lezcano wrote:
>> Hi Claudiu,
>>
>> sorry for the late reply.
>
> No problem, I understand.
>
>>
>>
>> On 13/06/2019 16
On 24/06/2019 09:37, Viresh Kumar wrote:
> On 24-06-19, 09:30, Daniel Lezcano wrote:
>> On 24/06/2019 08:03, Viresh Kumar wrote:
>>> On 21-06-19, 15:22, Daniel Lezcano wrote:
>>>> Currently the function cpufreq_cooling_register() returns a cooling
>>
Any chance this patch gets merged for v5.4?
Thanks
-- Daniel
On 12/06/2019 22:13, Daniel Lezcano wrote:
> Currently the governors are declared in their respective files but they
> export their [un]register functions which in turn call the [un]register
> governors core's
Gentle ping ...
On 04/06/2019 18:57, Daniel Lezcano wrote:
> Currently the common thermal zones definitions for the rk3399 assumes
> multiple thermal zones are supported by the governors. This is not the
> case and each thermal zone has its own governor instance acting
> individu
On 24/06/2019 08:03, Viresh Kumar wrote:
> On 21-06-19, 15:22, Daniel Lezcano wrote:
>> Currently the function cpufreq_cooling_register() returns a cooling
>> device pointer which is used back as a pointer to call the function
>> cpufreq_cooling_unregister(). Even if it is c
Sekhar, Bartosz,
if the sparse warning is not fixed, the driver won't hit this kernel
version. Please fix it before the two next days otherwise it won't make
it for v5.4.
Thanks
-- Daniel
On 14/06/2019 12:39, Sekhar Nori wrote:
> Hi Daniel,
>
> On 05/06/19 2:03 PM, Bartosz Golaszewski
The cpufreq_cooling_unregister() function uses now the policy to
unregister itself. The only purpose of the cooling device pointer is
to unregister the cpu cooling device.
As there is no more need of this pointer, remove it.
Signed-off-by: Daniel Lezcano
---
drivers/cpufreq/arm_big_little.c
The cpufreq_cooling_unregister() function uses now the policy to
unregister itself. The only purpose of the cooling device pointer is
to unregister the cpu cooling device.
As there is no more need of this pointer, remove it.
Signed-off-by: Daniel Lezcano
---
drivers/thermal/imx_thermal.c | 8
The cpufreq_cooling_unregister() function uses now the policy to
unregister itself. The only purpose of the cooling device pointer is
to unregister the cpu cooling device.
As there is no more need of this pointer, remove it.
Signed-off-by: Daniel Lezcano
---
drivers/cpufreq/cpufreq.c | 6
The cpufreq_cooling_unregister() function uses now the policy to
unregister itself. The only purpose of the cooling device pointer is
to unregister the cpu cooling device.
As there is no more need of this pointer, remove it.
Signed-off-by: Daniel Lezcano
---
drivers/thermal/ti-soc-thermal/ti
-encapsulate. Moreover, that forces to add an
extra variable in each driver using this function.
Instead of passing the cooling device to unregister, pass the policy.
Signed-off-by: Daniel Lezcano
---
drivers/cpufreq/arm_big_little.c | 2 +-
drivers/cpufreq/cpufreq.c
The functions stub already exist for the condition the IS_ENABLED
is trying to avoid.
Remove the IS_ENABLED macros as they are pointless.
Signed-off-by: Daniel Lezcano
---
drivers/cpufreq/cpufreq.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/cpufreq
identified workloads on an Android
reference platform.
Signed-off-by: Daniel Lezcano
---
drivers/cpuidle/Kconfig| 11 ++-
drivers/cpuidle/governors/Makefile | 1 +
drivers/cpuidle/governors/mobile.c | 151 +
3 files changed, 162 insertions(+), 1 deletion
Hi Claudiu,
sorry for the late reply.
On 13/06/2019 16:12, claudiu.bez...@microchip.com wrote:
> Hi Daniel,
>
> On 31.05.2019 13:41, Daniel Lezcano wrote:
>>
>> Hi Claudiu,
>>
>>
>> On 30/05/2019 09:46, claudiu.bez...@microchip.com wrote:
>
On 14/06/2019 16:25, Daniel Lezcano wrote:
> On 14/06/2019 12:39, Sekhar Nori wrote:
>> Hi Daniel,
>>
>> On 05/06/19 2:03 PM, Bartosz Golaszewski wrote:
>>> From: Bartosz Golaszewski
>>>
>>> This is another version of the new davinci clocksource
On 17/06/2019 11:36, Andrew Murray wrote:
> The function 'arch_timer_set_evtstrm_feature' has no return statement
> despite its prototype - let's change the function prototype to return
> void. This matches the equivalent arm64 implementation.
>
> fixes: 11e34eca5d0a ("clocksource/arm_arch_timer:
On 16/06/2019 11:31, Krzysztof Kozlowski wrote:
> On Fri, Jun 14, 2019 at 04:30:13PM +0200, Daniel Lezcano wrote:
>> On 14/06/2019 16:02, Robin Murphy wrote:
>>> On 14/06/2019 14:03, Daniel Lezcano wrote:
>>>> On 14/06/2019 11:35, Heiko Stuebner wrote:
>>>&
On 16/06/2019 16:08, Dmitry Osipenko wrote:
> 16.06.2019 16:24, Stephen Rothwell пишет:
>> Hi Daniel,
>>
>> [Sorry for the slow response.]
>>
>> On Thu, 13 Jun 2019 08:52:21 +0200 Daniel Lezcano
>> wrote:
>>>
>>> actually it returns:
&g
On 14/06/2019 16:02, Robin Murphy wrote:
> On 14/06/2019 14:03, Daniel Lezcano wrote:
>> On 14/06/2019 11:35, Heiko Stuebner wrote:
>>> Hi Daniel,
>>>
>>> Am Dienstag, 4. Juni 2019, 18:57:57 CEST schrieb Daniel Lezcano:
>>>> Currently the common
On 14/06/2019 12:39, Sekhar Nori wrote:
> Hi Daniel,
>
> On 05/06/19 2:03 PM, Bartosz Golaszewski wrote:
>> From: Bartosz Golaszewski
>>
>> This is another version of the new davinci clocksource driver. After much
>> discussion this contains many changes to simplify and improve the driver.
>
>
On 14/06/2019 11:35, Heiko Stuebner wrote:
> Hi Daniel,
>
> Am Dienstag, 4. Juni 2019, 18:57:57 CEST schrieb Daniel Lezcano:
>> Currently the common thermal zones definitions for the rk3399 assumes
>> multiple thermal zones are supported by the governors. This is not the
>
Hi Nathan,
On 13/06/2019 23:12, Nathan Huckleberry wrote:
> Clang produces the following warning
>
> vers/thermal/rcar_gen3_thermal.c:147:33: warning: shifting a negative
> signed value is undefined [-Wshift-negative-value] / (ptat[0] - ptat[2])) +
> FIXPT_INT(TJ_3); ^~~
gBuiltLinux/linux/issues/532
> Signed-off-by: Nathan Huckleberry
Reviewed-by: Daniel Lezcano
> ---
> drivers/thermal/armada_thermal.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/thermal/armada_thermal.c
> b/drivers/thermal/a
On 13/06/2019 01:07, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 98793726ab3f ("clocksource/drivers/tegra: Restore timer rate on Tegra210")
>
> Fixes tag
>
> Fixes: 3be2a85a0b61 ("Support per-CPU timers on all Tegra's")
>
> has these problem(s):
>
> - Subject does not match
is patch through the renesas tree.
> It has been outstanding for some time now.
Acked-by: Daniel Lezcano
>> Signed-off-by: Cao Van Dong
>> Reviewed-by: Rob Herring
>> Reviewed-by: Geert Uytterhoeven
>> Signed-off-by: Simon Horman
>> ---
>> Documentation/de
On 13/06/2019 15:03, Marc Zyngier wrote:
> + Daniel
>
> On Thu, 13 Jun 2019 13:51:02 +0100,
> Andrew Murray wrote:
>>
>> Different mechanisms are used to test and set elf_hwcaps between ARM
>> and ARM64, this results in the use of ifdeferry in this file when
>> setting/testing for the EVTSTRM
to declare themselves in a __init section table.
Define the table in the asm generic linker description like the other
tables and provide the specific macros to deal with.
Reviewed-by: Amit Kucheria
Signed-off-by: Daniel Lezcano
---
drivers/thermal/thermal_core.h| 15 +++
include
function which in turn
call the [un]register_thermal_governor. The governors are fully
self-encapsulated.
The cyclic dependency is no longer needed, remove it.
Reviewed-by: Amit Kucheria
Signed-off-by: Daniel Lezcano
---
drivers/thermal/fair_share.c | 12 +--
drivers/thermal
Hi all,
is there any comment on these two patches?
On 04/06/2019 18:57, Daniel Lezcano wrote:
> Currently the common thermal zones definitions for the rk3399 assumes
> multiple thermal zones are supported by the governors. This is not the
> case and each thermal zone has its own
Hi Thomas,
this a couple of fixes for v5.2-rc
Thanks
-- Daniel
The following changes since commit 4dde821e4296e156d133b98ddc4c45861935a4fb:
Merge tag 'xfs-5.2-fixes-1' of
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux (2019-05-23 11:18:18 -0700)
are available in the Git repository at:
Commit-ID: 699785f5d898965408430e841d10cd1cb2c02a77
Gitweb: https://git.kernel.org/tip/699785f5d898965408430e841d10cd1cb2c02a77
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:21 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:05 +0200
genirq/timings: Add
Commit-ID: f52da98d900e18a250cb14ca426d4041ea7002db
Gitweb: https://git.kernel.org/tip/f52da98d900e18a250cb14ca426d4041ea7002db
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:20 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:05 +0200
genirq/timings: Add
Commit-ID: 6aed82de719b424bd5548aa4179e95f34fd779ab
Gitweb: https://git.kernel.org/tip/6aed82de719b424bd5548aa4179e95f34fd779ab
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:19 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:04 +0200
genirq/timings: Add
Commit-ID: 23aa3b9a6b7d5029c1f124426bc5ba4430dcc29c
Gitweb: https://git.kernel.org/tip/23aa3b9a6b7d5029c1f124426bc5ba4430dcc29c
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:18 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:04 +0200
genirq/timings
Commit-ID: df025e47e4e34b779af2cc72c350877be7104ef3
Gitweb: https://git.kernel.org/tip/df025e47e4e34b779af2cc72c350877be7104ef3
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:17 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:04 +0200
genirq/timings
Commit-ID: 3c2e79f4cef7938125b356e7f5c8fd038212619a
Gitweb: https://git.kernel.org/tip/3c2e79f4cef7938125b356e7f5c8fd038212619a
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:16 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:03 +0200
genirq/timings
Commit-ID: 2840eef0513c518faeb8a0ab8d07268c6285cdd0
Gitweb: https://git.kernel.org/tip/2840eef0513c518faeb8a0ab8d07268c6285cdd0
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:15 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:03 +0200
genirq/timings: Fix
Commit-ID: 619c1baa91b2820eae9ff5d89eb525df81ea7a5a
Gitweb: https://git.kernel.org/tip/619c1baa91b2820eae9ff5d89eb525df81ea7a5a
Author: Daniel Lezcano
AuthorDate: Mon, 27 May 2019 22:55:14 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 12 Jun 2019 10:47:03 +0200
genirq/timings: Fix
On 12/06/2019 11:13, Quentin Perret wrote:
> Hi,
>
> On Thursday 30 May 2019 at 10:20:35 (+0100), Quentin Perret wrote:
>> Changes in v5:
>> **
>> - Changed patch 02 to guard IPA-specific code in cpu_cooling.c with
>>appropriate ifdefery (Daniel)
>> - Rebased on 5.2-rc2
>
> Is
Hi Dmitry,
On 09/06/2019 21:27, Dmitry Osipenko wrote:
> It was left unnoticed by accident, which means that the code could be
> cleaned up a tad more.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/clocksource/timer-tegra.c | 40 +++
> 1 file changed, 25
On 09/06/2019 14:12, Pavel Machek wrote:
> Hi!
>
>>> When I start flightgear, I get framerates around 20 fps and cpu at
>>> 3GHz:
>>>
>>> pavel@duo:~/bt$ cat /proc/cpuinfo | grep MHz
>>> cpu MHz : 3027.471
>>> cpu MHz : 2981.863
>>> cpu MHz :
On 08/06/2019 00:18, Linus Walleij wrote:
> On Tue, Jun 4, 2019 at 6:58 PM Daniel Lezcano
> wrote:
>
>> The intelligent power allocator PID coefficient to be set in sysfs
>> are:
>>
>> k_d: 0
>> k_po: 79
>> k_i: 10
>> k_pu: 50
when it reaches 75°C
- restrict the cooling device to the big CPUs as the little CPUs
contribution to the heating effect can be considered negligible
The intelligent power allocator PID coefficient to be set in sysfs
are:
k_d: 0
k_po: 79
k_i: 10
k_pu: 50
Signed-off-by: Daniel
.
Signed-off-by: Daniel Lezcano
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
index 196ac9b78076..e1357e0f60f7 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399
Hi,
is it possible to consider this series for merging?
Thanks in advance
-- Daniel
On 27/05/2019 22:55, Daniel Lezcano wrote:
> This series provides a couple of fixes, an optimization and the code
> to do the selftests.
>
> While writing the selftests, a couple of issues
On 04/06/2019 07:56, Andy Tang wrote:
> Hi Edubezval, Rui,
>
> Any further comments?
>From my POV, this patch makes sense. We may be interested to show up the
thermal zones in sysfs and optionally mitigate them via an userspace
governor.
Acked-by: Daniel Lezcano
>> ---
Hi Stephen,
I dropped the patch from my tree.
Thanks
-- Daniel
On 03/06/2019 04:13, Stephen Rothwell wrote:
> Hi Daniel,
>
> After merging the clockevents tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/clocksource/timer-atmel-tcb.c: In function
Hi Anders,
thanks for your patch. As mentioned by Mark I already applied this fix
from Julien Thierry.
-- Daniel
On 03/06/2019 11:23, Marc Zyngier wrote:
> Hi Anders,
>
>
> On 03/06/2019 10:12, Anders Roxell wrote:
>> When CONFIG_FUNCTION_GRAPH_TRACER is enabled we end up in this circular
is unsorted, since that is
> fairly uncommon in general, and there are currently no users of
> cpu_cooling for this use-case.
>
> Acked-by: Viresh Kumar
> Signed-off-by: Quentin Perret
Acked-by: Daniel Lezcano
> ---
> drivers/thermal/Kconfig | 1 +
> drivers/thermal/cpu_c
On 31/05/2019 14:33, Dmitry Osipenko wrote:
> 31.05.2019 11:26, Peter De Schrijver пишет:
>> On Fri, May 24, 2019 at 06:32:45PM +0300, Dmitry Osipenko wrote:
>>> Hello,
>>>
>>> This series primarily unifies the driver code across all Tegra SoC
>>> generations. In a result the clocksources are
ER_ALLOCATOR to not waste space
> unnecessarily.
>
> Suggested-by: Daniel Lezcano
> Signed-off-by: Quentin Perret
Acked-by: Daniel Lezcano
Thanks!
-- Daniel
> ---
> drivers/thermal/cpu_cooling.c | 214 +-
> 1 file changed, 104 insertions(+),
On 30/05/2019 12:50, Marek Szyprowski wrote:
> Exynos SoCs based on CA7/CA15 have 2 timer interfaces: custom Exynos MCT
> (Multi Core Timer) and standard ARM Architected Timers.
>
> There are use cases, where both timer interfaces are used simultanously.
> One of such examples is using Exynos MCT
On 30/05/2019 12:50, Marek Szyprowski wrote:
> Exynos SoCs based on CA7/CA15 have 2 timer interfaces: custom Exynos MCT
> (Multi Core Timer) and standard ARM Architected Timers.
>
> There are use cases, where both timer interfaces are used simultanously.
> One of such examples is using Exynos MCT
801 - 900 of 8072 matches
Mail list logo
