On 2018/10/20 2:03, Stephen Boyd wrote:
> Quoting Jianxin Pan (2018-10-19 09:12:53)
>> On 2018/10/19 1:13, Stephen Boyd wrote:
>>> Quoting Jianxin Pan (2018-10-17 22:07:25)
diff --git a/drivers/clk/meson/clk-regmap.c
b/drivers/clk/meson/clk-regmap.c
index 305ee30..f96314d 100644
On 2018/10/20 2:03, Stephen Boyd wrote:
> Quoting Jianxin Pan (2018-10-19 09:12:53)
>> On 2018/10/19 1:13, Stephen Boyd wrote:
>>> Quoting Jianxin Pan (2018-10-17 22:07:25)
diff --git a/drivers/clk/meson/clk-regmap.c
b/drivers/clk/meson/clk-regmap.c
index 305ee30..f96314d 100644
Hi Sebastian,
On 22 October 2018 at 00:52, Sebastian Reichel wrote:
> Hi,
>
> On Fri, Oct 19, 2018 at 06:53:15PM +0800, Baolin Wang wrote:
>> This patch adds the Spreadtrum SC27XX serial PMICs fuel gauge support,
>> which is used to calculate the battery capacity.
>>
>> Original-by: Yuanjiang Yu
Hi Sebastian,
On 22 October 2018 at 00:52, Sebastian Reichel wrote:
> Hi,
>
> On Fri, Oct 19, 2018 at 06:53:15PM +0800, Baolin Wang wrote:
>> This patch adds the Spreadtrum SC27XX serial PMICs fuel gauge support,
>> which is used to calculate the battery capacity.
>>
>> Original-by: Yuanjiang Yu
On 15-10-18, 14:47, Niklas Cassel wrote:
> Extend qcom-opp bindings with properties needed for Core Power Reduction
> (CPR).
>
> CPR is included in a great variety of Qualcomm SoC, e.g. msm8916 and
> msm8996, and was first introduced in msm8974.
>
> Signed-off-by: Niklas Cassel
> ---
> Hello
On 15-10-18, 14:47, Niklas Cassel wrote:
> Extend qcom-opp bindings with properties needed for Core Power Reduction
> (CPR).
>
> CPR is included in a great variety of Qualcomm SoC, e.g. msm8916 and
> msm8996, and was first introduced in msm8974.
>
> Signed-off-by: Niklas Cassel
> ---
> Hello
On 21-10-18, 23:54, Dmitry Osipenko wrote:
> Voltage regulators may be not available on some variations of HW, allow to
> request stub voltage regulators by OPP core in a such case to reduce code
> churning within drivers.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/cpufreq-dt.c
On 21-10-18, 23:54, Dmitry Osipenko wrote:
> Voltage regulators may be not available on some variations of HW, allow to
> request stub voltage regulators by OPP core in a such case to reduce code
> churning within drivers.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/cpufreq-dt.c
Can i trust you with a transaction of usd 8.3m?($8,370.000.00) Reply me if
interested
- Mr Yi Gang
Can i trust you with a transaction of usd 8.3m?($8,370.000.00) Reply me if
interested
- Mr Yi Gang
Commit-ID: 977e4be5eb714c48a67afc26a6c477f24130a1f2
Gitweb: https://git.kernel.org/tip/977e4be5eb714c48a67afc26a6c477f24130a1f2
Author: Christophe Leroy
AuthorDate: Sat, 20 Oct 2018 09:26:49 +0200
Committer: Ingo Molnar
CommitDate: Mon, 22 Oct 2018 04:07:24 +0200
x86/stackprotector:
Commit-ID: 977e4be5eb714c48a67afc26a6c477f24130a1f2
Gitweb: https://git.kernel.org/tip/977e4be5eb714c48a67afc26a6c477f24130a1f2
Author: Christophe Leroy
AuthorDate: Sat, 20 Oct 2018 09:26:49 +0200
Committer: Ingo Molnar
CommitDate: Mon, 22 Oct 2018 04:07:24 +0200
x86/stackprotector:
On 10/21/2018 07:32 PM, Hou Tao wrote:
>
> On 2018/10/19 16:30, Daniel Santos wrote:
>> jffs2_sync_fs makes the assumption that if CONFIG_JFFS2_FS_WRITEBUFFER
>> is defined then a write buffer is available and has been initialized.
>> However, this does is not the case when the mtd device has no
On 10/21/2018 07:32 PM, Hou Tao wrote:
>
> On 2018/10/19 16:30, Daniel Santos wrote:
>> jffs2_sync_fs makes the assumption that if CONFIG_JFFS2_FS_WRITEBUFFER
>> is defined then a write buffer is available and has been initialized.
>> However, this does is not the case when the mtd device has no
Hi Stephen,
On 10/18/2018 1:46 AM, Stephen Boyd wrote:
> Quoting Stephen Boyd (2018-10-17 08:44:12)
>> Quoting Sricharan R (2018-09-20 06:03:31)
>>>
>>>
>>> On 9/20/2018 1:54 AM, Craig wrote:
Yup, this patch seems to have fixed the higher frequencies from the quick
test I did.
>>>
Hi Stephen,
On 10/18/2018 1:46 AM, Stephen Boyd wrote:
> Quoting Stephen Boyd (2018-10-17 08:44:12)
>> Quoting Sricharan R (2018-09-20 06:03:31)
>>>
>>>
>>> On 9/20/2018 1:54 AM, Craig wrote:
Yup, this patch seems to have fixed the higher frequencies from the quick
test I did.
>>>
Can i trust you with a transaction of usd 8.3m?($8,370.000.00) Reply me if
interested
- Mr Yi Gang
Can i trust you with a transaction of usd 8.3m?($8,370.000.00) Reply me if
interested
- Mr Yi Gang
When trying to migrate to a CPU in task_numa_migrate(), we invoke
task_numa_find_cpu() to choose a spot, in which function we skip
the CPU which is not in cpus_allowed, but forgot to concern the
isolated CPUs, and this may cause the task would run on the isolcpus.
This patch fixes this issue by
When trying to migrate to a CPU in task_numa_migrate(), we invoke
task_numa_find_cpu() to choose a spot, in which function we skip
the CPU which is not in cpus_allowed, but forgot to concern the
isolated CPUs, and this may cause the task would run on the isolcpus.
This patch fixes this issue by
On 10/19/2018 01:39 PM, Michal Hocko wrote:
> I planed to get to review this earlier but been busy. Anyway, this patch
> should be applied only after movability one to prevent from
> (theoretical) bisectability issues.
Sure, I can change the order there.
>
> I would probably fold it into the
On 10/19/2018 01:39 PM, Michal Hocko wrote:
> I planed to get to review this earlier but been busy. Anyway, this patch
> should be applied only after movability one to prevent from
> (theoretical) bisectability issues.
Sure, I can change the order there.
>
> I would probably fold it into the
Hi Arnaldo,
On Thu, Oct 18, 2018 at 10:56:10PM +0800, Arnaldo Carvalho de Melo wrote:
> Em Thu, Oct 18, 2018 at 04:36:46PM +0800, Nickhu escreveu:
> > The error message:
> > =
> > util/symbol-elf.c:46:12: error: static
Hi Arnaldo,
On Thu, Oct 18, 2018 at 10:56:10PM +0800, Arnaldo Carvalho de Melo wrote:
> Em Thu, Oct 18, 2018 at 04:36:46PM +0800, Nickhu escreveu:
> > The error message:
> > =
> > util/symbol-elf.c:46:12: error: static
If the PMIC ID is unknown, the current code would call
irq_domain_remove and panic, as pmic->irq_domain is only
initialized by mt6397_irq_init.
Return immediately with an error, if the chip ID is unsupported.
Signed-off-by: Nicolas Boichat
---
drivers/mfd/mt6397-core.c | 3 +--
1 file changed,
If the PMIC ID is unknown, the current code would call
irq_domain_remove and panic, as pmic->irq_domain is only
initialized by mt6397_irq_init.
Return immediately with an error, if the chip ID is unsupported.
Signed-off-by: Nicolas Boichat
---
drivers/mfd/mt6397-core.c | 3 +--
1 file changed,
This PoC generated by syzkaller needs ROOT permission to run.
Steven Rostedt 于2018年10月18日周四 上午10:13写道：
>
> On Sat, 29 Sep 2018 17:22:13 +0800
> 王晓东 wrote:
>
> > Hi there,
> >
> > We would like to report a kernel stack corrupted problem we identified
> > in the perf_trace_rcu_dyntick function of
This PoC generated by syzkaller needs ROOT permission to run.
Steven Rostedt 于2018年10月18日周四 上午10:13写道：
>
> On Sat, 29 Sep 2018 17:22:13 +0800
> 王晓东 wrote:
>
> > Hi there,
> >
> > We would like to report a kernel stack corrupted problem we identified
> > in the perf_trace_rcu_dyntick function of
On 18-10-19 16:20:52, Juergen Gross wrote:
> On 19/10/2018 15:13, Yi Sun wrote:
[...]
> > diff --git a/kernel/locking/qspinlock_paravirt.h
> > b/kernel/locking/qspinlock_paravirt.h
> > index 0130e48..9e88c7e 100644
> > --- a/kernel/locking/qspinlock_paravirt.h
> > +++
On 18-10-19 16:20:52, Juergen Gross wrote:
> On 19/10/2018 15:13, Yi Sun wrote:
[...]
> > diff --git a/kernel/locking/qspinlock_paravirt.h
> > b/kernel/locking/qspinlock_paravirt.h
> > index 0130e48..9e88c7e 100644
> > --- a/kernel/locking/qspinlock_paravirt.h
> > +++
Thx Peter,
Your review has been a great help.
On Sun, Oct 21, 2018 at 10:55:08PM +0200, Peter Zijlstra wrote:
> On Tue, Oct 16, 2018 at 10:58:30AM +0800, Guo Ren wrote:
> > + smp_mb();
> > + lock->tickets.owner++;
>
> WRITE_ONCE(lock->tickets.owner, lock->tickets.owner + 1);
Yes,
Thx Peter,
Your review has been a great help.
On Sun, Oct 21, 2018 at 10:55:08PM +0200, Peter Zijlstra wrote:
> On Tue, Oct 16, 2018 at 10:58:30AM +0800, Guo Ren wrote:
> > + smp_mb();
> > + lock->tickets.owner++;
>
> WRITE_ONCE(lock->tickets.owner, lock->tickets.owner + 1);
Yes,
Ping...
Anson Huang
Best Regards!
> -Original Message-
> From: Anson Huang
> Sent: Thursday, September 13, 2018 5:44 PM
> To: 'Rob Herring'
> Cc: rui.zh...@intel.com; edubez...@gmail.com; robh...@kernel.org;
> mark.rutl...@arm.com; linux...@vger.kernel.org;
>
Ping...
Anson Huang
Best Regards!
> -Original Message-
> From: Anson Huang
> Sent: Friday, October 12, 2018 2:42 PM
> To: 'Daniel Lezcano' ; rui.zh...@intel.com;
> edubez...@gmail.com; linux...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: RE: [PATCH 1/2] thermal: imx:
Ping...
Anson Huang
Best Regards!
> -Original Message-
> From: Anson Huang
> Sent: Thursday, September 13, 2018 5:44 PM
> To: 'Rob Herring'
> Cc: rui.zh...@intel.com; edubez...@gmail.com; robh...@kernel.org;
> mark.rutl...@arm.com; linux...@vger.kernel.org;
>
Ping...
Anson Huang
Best Regards!
> -Original Message-
> From: Anson Huang
> Sent: Friday, October 12, 2018 2:42 PM
> To: 'Daniel Lezcano' ; rui.zh...@intel.com;
> edubez...@gmail.com; linux...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: RE: [PATCH 1/2] thermal: imx:
On Sun, Oct 21, 2018 at 10:30:16AM +0300, Mike Rapoport wrote:
>
>
>On October 19, 2018 11:17:30 AM GMT+03:00, Wei Yang
> wrote:
>>Which tree it applies?
>
>To mmotm of the end of September.
>
I may lost some background of this change.
The file I am looking at is
On Sun, Oct 21, 2018 at 10:30:16AM +0300, Mike Rapoport wrote:
>
>
>On October 19, 2018 11:17:30 AM GMT+03:00, Wei Yang
> wrote:
>>Which tree it applies?
>
>To mmotm of the end of September.
>
I may lost some background of this change.
The file I am looking at is
Commit-ID: 2e62024c265aa69315ed02835623740030435380
Gitweb: https://git.kernel.org/tip/2e62024c265aa69315ed02835623740030435380
Author: Masami Hiramatsu
AuthorDate: Sat, 20 Oct 2018 18:47:53 +0900
Committer: Ingo Molnar
CommitDate: Mon, 22 Oct 2018 03:31:01 +0200
kprobes/x86: Use
Commit-ID: 2e62024c265aa69315ed02835623740030435380
Gitweb: https://git.kernel.org/tip/2e62024c265aa69315ed02835623740030435380
Author: Masami Hiramatsu
AuthorDate: Sat, 20 Oct 2018 18:47:53 +0900
Committer: Ingo Molnar
CommitDate: Mon, 22 Oct 2018 03:31:01 +0200
kprobes/x86: Use
Can i trust you with a transaction of usd 8.3m?($8,370.000.00) Reply me if
interested
- Mr Yi Gang
Can i trust you with a transaction of usd 8.3m?($8,370.000.00) Reply me if
interested
- Mr Yi Gang
On 2018/10/19 16:30, Daniel Santos wrote:
> jffs2_sync_fs makes the assumption that if CONFIG_JFFS2_FS_WRITEBUFFER
> is defined then a write buffer is available and has been initialized.
> However, this does is not the case when the mtd device has no
> out-of-band buffer:
>
> int
On 2018/10/19 16:30, Daniel Santos wrote:
> jffs2_sync_fs makes the assumption that if CONFIG_JFFS2_FS_WRITEBUFFER
> is defined then a write buffer is available and has been initialized.
> However, this does is not the case when the mtd device has no
> out-of-band buffer:
>
> int
On Sun, Oct 21, 2018 at 11:26:08PM +0100, Josh Triplett wrote:
> On Mon, Oct 22, 2018 at 08:20:11AM +1100, NeilBrown wrote:
> > I call on you, Greg:
> > - to abandon this divisive attempt to impose a "Code of Conduct"
> > - to revert 8a104f8b5867c68
> > - to return to your core competence of
On Sun, Oct 21, 2018 at 11:26:08PM +0100, Josh Triplett wrote:
> On Mon, Oct 22, 2018 at 08:20:11AM +1100, NeilBrown wrote:
> > I call on you, Greg:
> > - to abandon this divisive attempt to impose a "Code of Conduct"
> > - to revert 8a104f8b5867c68
> > - to return to your core competence of
Greg Kroah-Hartman :
> This patch series adds this new document to the kernel tree, as well as
> removes a paragraph from the existing Code of Conduct that was
> bothersome to many maintainers.
I think the changes have improved it.
There is still a process issue with how this code was
Greg Kroah-Hartman :
> This patch series adds this new document to the kernel tree, as well as
> removes a paragraph from the existing Code of Conduct that was
> bothersome to many maintainers.
I think the changes have improved it.
There is still a process issue with how this code was
On Sun, 21 Oct 2018, Pavel Machek wrote:
> Imagine JIT running evil code (flash, javascript). JIT will prevent evil
> code from doing ptrace() (or maybe there is syscall filter in effect or
> something like that), but if evil code can poison branch buffers and do
> timings, security problem
On Sun, 21 Oct 2018, Pavel Machek wrote:
> Imagine JIT running evil code (flash, javascript). JIT will prevent evil
> code from doing ptrace() (or maybe there is syscall filter in effect or
> something like that), but if evil code can poison branch buffers and do
> timings, security problem
On 10/21/18 3:33 PM, Joe Perches wrote:
> On Mon, 2018-10-22 at 08:20 +1100, NeilBrown wrote:
>> On Sat, Oct 20 2018, Greg Kroah-Hartman wrote:
>>> As everyone knows by now, we added a new Code of Conduct to the kernel
>>> tree a few weeks ago.
>>
>> I wanted to stay detached from all this, but as
On 10/21/18 3:33 PM, Joe Perches wrote:
> On Mon, 2018-10-22 at 08:20 +1100, NeilBrown wrote:
>> On Sat, Oct 20 2018, Greg Kroah-Hartman wrote:
>>> As everyone knows by now, we added a new Code of Conduct to the kernel
>>> tree a few weeks ago.
>>
>> I wanted to stay detached from all this, but as
On Sun, 2018-10-21 at 05:22 -0700, Metztli Information Technology
wrote:
> Niltze, all-
>
> Ever since I build reiser4 -patched [1] Linux kernel 4.18.xy
> iterations I have had kernel hanging issues --which manifest
> themselves after considerable load and/or multitasking in my local
>
On Sun, 2018-10-21 at 05:22 -0700, Metztli Information Technology
wrote:
> Niltze, all-
>
> Ever since I build reiser4 -patched [1] Linux kernel 4.18.xy
> iterations I have had kernel hanging issues --which manifest
> themselves after considerable load and/or multitasking in my local
>
On Mon, 2018-10-22 at 08:20 +1100, NeilBrown wrote:
> On Sat, Oct 20 2018, Greg Kroah-Hartman wrote:
> > As everyone knows by now, we added a new Code of Conduct to the kernel
> > tree a few weeks ago.
>
> I wanted to stay detached from all this, but as remaining (publicly)
> silent might be seen
On Mon, 2018-10-22 at 08:20 +1100, NeilBrown wrote:
> On Sat, Oct 20 2018, Greg Kroah-Hartman wrote:
> > As everyone knows by now, we added a new Code of Conduct to the kernel
> > tree a few weeks ago.
>
> I wanted to stay detached from all this, but as remaining (publicly)
> silent might be seen
On Mon, Oct 22, 2018 at 08:20:11AM +1100, NeilBrown wrote:
> I call on you, Greg:
> - to abandon this divisive attempt to impose a "Code of Conduct"
> - to revert 8a104f8b5867c68
> - to return to your core competence of building a great team around
>a great kernel
>
> #Isupportreversion
>
On Mon, Oct 22, 2018 at 08:20:11AM +1100, NeilBrown wrote:
> I call on you, Greg:
> - to abandon this divisive attempt to impose a "Code of Conduct"
> - to revert 8a104f8b5867c68
> - to return to your core competence of building a great team around
>a great kernel
>
> #Isupportreversion
>
On Sun, 21 Oct 2018 19:53:03 +0200,
Connor McAdams wrote:
>
> This patch fixes the microphone issue for all cards. The previous fix
> worked on the ZxR, but not on the AE-5 or Z. This patch has been tested
> to work for all cards.
>
> Signed-off-by: Connor McAdams
Thanks, that's a good news.
On Sun, 21 Oct 2018 19:53:03 +0200,
Connor McAdams wrote:
>
> This patch fixes the microphone issue for all cards. The previous fix
> worked on the ZxR, but not on the AE-5 or Z. This patch has been tested
> to work for all cards.
>
> Signed-off-by: Connor McAdams
Thanks, that's a good news.
From: Matthias Brugger
By defaul of-based thermal driver do not enable hwmon.
This patch does this explicitly, so that the temperature can be read
through the common hwmon sysfs.
Signed-off-by: Matthias Brugger
---
drivers/thermal/broadcom/bcm2835_thermal.c | 11 +++
1 file changed,
From: Matthias Brugger
By defaul of-based thermal driver do not enable hwmon.
This patch does this explicitly, so that the temperature can be read
through the common hwmon sysfs.
Signed-off-by: Matthias Brugger
---
drivers/thermal/broadcom/bcm2835_thermal.c | 11 +++
1 file changed,
On 10/21/18 11:54 PM, Dmitry Osipenko wrote:
> This function is used by tegra20-cpufreq driver which can be built as a
> kernel module.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/soc/tegra/fuse/tegra-apbmisc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On 10/21/18 11:54 PM, Dmitry Osipenko wrote:
> This function is used by tegra20-cpufreq driver which can be built as a
> kernel module.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/soc/tegra/fuse/tegra-apbmisc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On Sat, Oct 20 2018, Greg Kroah-Hartman wrote:
> Hi all,
>
> As everyone knows by now, we added a new Code of Conduct to the kernel
> tree a few weeks ago.
I wanted to stay detached from all this, but as remaining (publicly)
silent might be seen (publicly) as acquiescing, I hereby declare that:
On Sat, Oct 20 2018, Greg Kroah-Hartman wrote:
> Hi all,
>
> As everyone knows by now, we added a new Code of Conduct to the kernel
> tree a few weeks ago.
I wanted to stay detached from all this, but as remaining (publicly)
silent might be seen (publicly) as acquiescing, I hereby declare that:
This function is used by tegra20-cpufreq driver which can be built as a
kernel module.
Signed-off-by: Dmitry Osipenko
---
drivers/soc/tegra/fuse/tegra-apbmisc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/soc/tegra/fuse/tegra-apbmisc.c
b/drivers/soc/tegra/fuse/tegra-apbmisc.c
This function is used by tegra20-cpufreq driver which can be built as a
kernel module.
Signed-off-by: Dmitry Osipenko
---
drivers/soc/tegra/fuse/tegra-apbmisc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/soc/tegra/fuse/tegra-apbmisc.c
b/drivers/soc/tegra/fuse/tegra-apbmisc.c
Voltage regulators may be not available on some variations of HW, allow to
request stub voltage regulators by OPP core in a such case to reduce code
churning within drivers.
Signed-off-by: Dmitry Osipenko
---
drivers/cpufreq/cpufreq-dt.c | 2 +-
drivers/cpufreq/ti-cpufreq.c | 3 ++-
Voltage regulators may be not available on some variations of HW, allow to
request stub voltage regulators by OPP core in a such case to reduce code
churning within drivers.
Signed-off-by: Dmitry Osipenko
---
drivers/cpufreq/cpufreq-dt.c | 2 +-
drivers/cpufreq/ti-cpufreq.c | 3 ++-
Tegra20-cpufreq driver require a platform device in order to be loaded,
instantiate a simple platform device for the driver during of the machines
late initialization. Driver now supports Tegra30 SoC's, hence create the
device on Tegra30 machines.
Signed-off-by: Dmitry Osipenko
---
Tegra20-cpufreq driver require a platform device in order to be loaded,
instantiate a simple platform device for the driver during of the machines
late initialization. Driver now supports Tegra30 SoC's, hence create the
device on Tegra30 machines.
Signed-off-by: Dmitry Osipenko
---
Add support for thermal throttling, Operating Performance Points and DVFS.
Driver now relies on OPP's supplied via device tree and therefore will
work only on devices that use the updated device tree. The generalization
of the driver allows to transparently support Tegra30.
Signed-off-by: Dmitry
Add support for thermal throttling, Operating Performance Points and DVFS.
Driver now relies on OPP's supplied via device tree and therefore will
work only on devices that use the updated device tree. The generalization
of the driver allows to transparently support Tegra30.
Signed-off-by: Dmitry
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-colibri.dtsi | 31 ++
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-colibri.dtsi | 31 ++
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-ventana.dts | 31 +++
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git
Add CPU's Operating Performance Points to the device tree, they are used
by the CPUFreq driver and allow to setup thermal throttling for the boards
by linking the cooling device (CPU) with thermal sensors via thermal-zones
description.
Signed-off-by: Dmitry Osipenko
---
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30-colibri.dtsi | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/tegra30-colibri.dtsi
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-seaboard.dts | 27 +++---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30-cardhu.dtsi | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/tegra30-cardhu.dtsi
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-ventana.dts | 31 +++
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git
Add CPU's Operating Performance Points to the device tree, they are used
by the CPUFreq driver and allow to setup thermal throttling for the boards
by linking the cooling device (CPU) with thermal sensors via thermal-zones
description.
Signed-off-by: Dmitry Osipenko
---
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30-colibri.dtsi | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/tegra30-colibri.dtsi
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-seaboard.dts | 27 +++---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30-cardhu.dtsi | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/tegra30-cardhu.dtsi
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-paz00.dts | 31 -
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30-apalis.dtsi | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/tegra30-apalis.dtsi
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-tamonten.dtsi | 31 ++---
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git
Add CPU's Operating Performance Points to the device tree, they are used
by the CPUFreq driver and allow to setup thermal throttling for the boards
by linking the cooling device (CPU) with thermal sensors via thermal-zones
description.
Signed-off-by: Dmitry Osipenko
---
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-paz00.dts | 31 -
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30-apalis.dtsi | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/tegra30-apalis.dtsi
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-tamonten.dtsi | 31 ++---
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git
Add CPU's Operating Performance Points to the device tree, they are used
by the CPUFreq driver and allow to setup thermal throttling for the boards
by linking the cooling device (CPU) with thermal sensors via thermal-zones
description.
Signed-off-by: Dmitry Osipenko
---
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30-beaver.dts | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/tegra30-beaver.dts
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30-beaver.dts | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/tegra30-beaver.dts
Add device-tree binding that describes CPU frequency-scaling hardware
found on NVIDIA Tegra20/30 SoC's.
Signed-off-by: Dmitry Osipenko
---
.../cpufreq/nvidia,tegra20-cpufreq.txt| 96 +++
1 file changed, 96 insertions(+)
create mode 100644
Hello,
This series adds support for CPU frequency/voltage scaling on Tegra20/30,
it adds device tree support that allow to specify clock rate/voltages per
board and to implement thermal throttling. The tegra20-cpufreq driver has
been re-worked to support that all.
Note that this series depends
Set min/max regulators voltage and add CPU node that hooks up CPU with
voltage regulators.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-harmony.dts | 31 +++
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git
Add device-tree binding that describes CPU frequency-scaling hardware
found on NVIDIA Tegra20/30 SoC's.
Signed-off-by: Dmitry Osipenko
---
.../cpufreq/nvidia,tegra20-cpufreq.txt| 96 +++
1 file changed, 96 insertions(+)
create mode 100644
1 - 100 of 306 matches
Mail list logo
