From: Todd Poynor
Change-Id: Ia4966e949a6c24c34fdbd4a6e522cd7c37e4108e
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
drivers/cpufreq/cpufreq_interactive.c | 13 -
1 file changed, 4 insertions(+),
From: Todd Poynor
Helps avoid waking up other CPUs to react to activity on the local CPU.
Change-Id: Ife272aaa7916894a437705d44521b1a1693fbe8e
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
From: Todd Poynor
Not useful to have a separate, non-realtime workqueue for speed down
events, avoid priority inversion for speed up events.
Change-Id: Iddcd05545245c847aa1bbe0b8790092914c813d2
Signed-off-by: Todd Poynor
Signed-off-by: Bálint
On Tue, 27 Oct 2015, Joe Perches wrote:
> On Tue, 2015-10-27 at 08:21 +, Lee Jones wrote:
> > On Mon, 26 Oct 2015, j...@perches.com wrote:
> > > On 2015-10-26 19:47, Theodore Ts'o wrote:
> > > >What if we have a git_fallback "auto" mode which only falls back to
> > > >using git if there is no
On 25/10/15 08:06, Siddhesh Poyarekar wrote:
On Tuesday 13 October 2015 10:52 PM, Suzuki K. Poulose wrote:
Apart from the selected feature registers, we expose MIDR_EL1 (Main
ID Register). The user should be aware that, reading MIDR_EL1 can be
tricky on a heterogeneous system (just like
On 10/27/2015 01:46 PM, Denys Vlasenko wrote:
> This function compiles to 58 bytes of machine code.
Reviewed-by: Peter Hurley
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
On 10/27/2015 01:46 PM, Denys Vlasenko wrote:
> This function compiles to 172 bytes of machine code.
>
> Signed-off-by: Denys Vlasenko
> CC: Greg Kroah-Hartman
> CC: Peter Hurley
> CC: Jiri Slaby
> CC:
On Tue, 2015-10-27 at 18:15 +, Lee Jones wrote:
> On Tue, 27 Oct 2015, Sebastian Reichel wrote:
> > On Tue, Oct 27, 2015 at 03:42:37PM +, Lee Jones wrote:
> > > Since eafbaac ("MAINTAINERS: Add "R:" designated-reviewers tag") we
> > > have been able to tag specific people as Reviewers.
On Thursday, October 22, 2015 02:53:13 PM Richard Guy Briggs wrote:
> This set of patches cleans up a number of corner cases in the management
> of the audit queue.
>
> Richard Guy Briggs (7):
> audit: don't needlessly reset valid wait time
> audit: include auditd's threads in
+ Stefano
On 27.10.2015 17:38, Tomasz Nowicki wrote:
From: Hanjun Guo
In drivers/xen/pci.c, there are arch x86 dependent codes when
CONFIG_PCI_MMCONFIG is enabled, since CONFIG_PCI_MMCONFIG
depends on ACPI, so this will prevent XEN PCI running on other
architectures
The H3 bus resets have some holes between the registers, so we add
an of_xlate() function to skip them according to the datasheet.
Signed-off-by: Jens Kuske
---
.../bindings/reset/allwinner,sunxi-clock-reset.txt | 1 +
drivers/reset/reset-sunxi.c|
The H3 clock control unit is similar to the those of other sun8i family
members like the A23.
It adds a new bus gates clock similar to the simple gates, but with a
different parent clock for each single gate.
Some of the gates use the new AHB2 clock as parent, whose clock source
is muxable
Hi everyone,
This is v4 of my patch series introducing basic kernel support for Allwinner's
H3 SoC. It mainly adds basic clocks, resets and pinctrl. It also adds
interrupts, timers, watchdog, RTC, dmaengine, MMC and UARTs, which are mostly
compatible to those in earlier SoCs like A23 and A31, and
There are two ways we can get ECAM (aka MCFG) regions using ACPI,
from MCFG static table and from _CBA method. We cannot remove static
regions, however regions coming from _CBA should be removed while removing
bridge device.
In the light of above we need flag to mark hot added ECAM entries
so
First function acpi_mcfg_check_entry() does not apply any quirks by default.
Last two functions are required by ACPI subsystem to make PCI config
space accessible. Generic code assume to do nothing for early init call but
late init call does as follow:
- parse MCFG table and add regions to ECAM
On Tue, Oct 27, 2015 at 05:42:23PM +0100, Linus Walleij wrote:
> On Tue, Oct 27, 2015 at 3:23 PM, Mika Westerberg
> wrote:
> > On Tue, Oct 27, 2015 at 11:06:58AM +0100, Linus Walleij wrote:
> >> > +menu "ISA GPIO drivers"
> >> > +
> >> > +config GPIO_104_IDIO_16
>
This patch is to the host_interface.c that fixes up following
warning by checkpatch:
-prefer eth_broadcast_addr() over memset()
Signed-off-by: Punit Vara
---
drivers/staging/wilc1000/host_interface.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 10/27/2015 12:47 PM, Tomasz Nowicki wrote:
+ Stefano
On 27.10.2015 17:38, Tomasz Nowicki wrote:
From: Hanjun Guo
In drivers/xen/pci.c, there are arch x86 dependent codes when
CONFIG_PCI_MMCONFIG is enabled, since CONFIG_PCI_MMCONFIG
depends on ACPI, so this will
From: Todd Poynor
If multiple governors are in use then avoid processing frequency transition
notifications for CPUs on which the interactive governor is not enabled.
Change-Id: Ibd75255b921d887501a64774a8c4f62302f2d4e4
Reported-by: Francisco Franco
From: Lianwei Wang
Avoid wakeups only to handle the governor timer when the system is otherwise
idle.
For platforms where the power cost of remaining in idle at higher CPU
speed may outweigh the cost of a governor wakeup from idle to lower the speed,
set parameter
From: Todd Poynor
Sysfs attribute boostpulse_duration specifies the duration of boosting CPU
speed in response to bootpulse events. Duration is specified in usecs,
default 80ms.
Change-Id: Ifd41625574891a44f1787a4e85d1e7b4f2afb52b
Signed-off-by: Todd Poynor
From: Todd Poynor
Now handled in userspace Power HAL instead.
Change-Id: I78a4a2fd471308bfcd785bbefcc65fede27314cf
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
drivers/cpufreq/cpufreq_interactive.c | 146
From: Todd Poynor
Accept a string of target loads and speeds at which to apply the
target loads, per the documentation update in this patch. For example,
"85 100:90 170:99" targets CPU load 85% below speed 1GHz, 90%
at or above 1GHz, until 1.7GHz and above, at
From: Todd Poynor
Add a target_load attribute that specifies how aggressively the governor is
to adjust speed to meet the observed load. New target speed is calculated
as the current actual speed (may be higher than target speed on SMP) times
the CPU load (as a fraction)
From: Sam Leffler
Register an idle notifier only when the governor is active. Also
short-circuit work of idle end if the governor is not enabled.
Signed-off-by: Sam Leffler
Change-Id: I4cae36dd2e7389540d337d74745ffbaa0131870f
Signed-off-by: Bálint
From: Todd Poynor
When load is below go_hispeed_load, apply the percentage of CPU load to
a max frequency of hispeed_freq instead of the max speed. This avoids
jumping too quickly to hispeed_freq when it is a relatively low
percentage of max speed. This also allows
From: Ruchi Kandoi
Change-Id: I36fe217fa047d68ea90e78b12c7db4537ea8010b
Signed-off-by: Ruchi Kandoi
Signed-off-by: Bálint Czobor
---
drivers/cpufreq/cpufreq_interactive.c |1 +
1 file changed, 1 insertion(+)
diff
From: Marc Titinger
re-instate a two step init, first register the CPU-power domains, then
attach the CPUs, because CPU ordering does not match cluster/PD boundaries.
Signed-off-by: Marc Titinger
---
drivers/base/power/cpu-pd.c | 29
This function compiles to 172 bytes of machine code.
Signed-off-by: Denys Vlasenko
CC: Greg Kroah-Hartman
CC: Peter Hurley
CC: Jiri Slaby
CC: linux-ser...@vger.kernel.org
---
This function compiles to 198 bytes of machine code.
Signed-off-by: Denys Vlasenko
CC: Greg Kroah-Hartman
CC: Peter Hurley
CC: Jiri Slaby
CC: linux-ser...@vger.kernel.org
---
drivers/tty/n_tty.c | 2
This function compiles to 141 bytes of machine code.
Signed-off-by: Denys Vlasenko
CC: Greg Kroah-Hartman
CC: Peter Hurley
CC: Jiri Slaby
CC: linux-ser...@vger.kernel.org
---
On Tue, 2015-10-27 at 08:21 +, Lee Jones wrote:
> On Mon, 26 Oct 2015, j...@perches.com wrote:
> > On 2015-10-26 19:47, Theodore Ts'o wrote:
> > >What if we have a git_fallback "auto" mode which only falls back to
> > >using git if there is no entry in the MAINTAINERS file? That might
> >
From: Todd Poynor
The longer-term load since last speed change isn't terribly useful,
may delay recognition of dropping load, and would need forthcoming
changes to adjust load for changing CPU speeds. Drop it.
Change-Id: Ic3cbb0542cc3484617031787e03ed9bdd632dec1
From: Todd Poynor
Add notifier for speed transitions. Keep a count of CPU active
microseconds times current frequency, converted to a percentage relative
to the current frequency when load is evaluated.
Change-Id: I5c27adb11081c50490219784ca57cc46e97fc28c
Signed-off-by:
From: Todd Poynor
Always use deferrable timer for load sampling.
Set a non-deferrable timer to an additional slack time to allow prior to
waking up from idle to drop speed when not at minimum speed. Slack value
-1 avoids wakeups to drop speed. Default is 80ms.
Remove
From: Todd Poynor
For systems that set a common speed for all CPUs, checking current
speed here could bypass the intermediate hispeed bump decision for
this CPU when another CPU was already at hispeed. This could
result in an overly high setting (for all CPUs) in
From: Todd Poynor
Change-Id: I4d6ac40b23a3790d48e30c37408284e9f955e8fa
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
drivers/cpufreq/cpufreq_interactive.c | 41 +
1 file
From: Todd Poynor
Allow speed drop after min_sample_time elapses from last time
the current speed was last re-validated as appropriate for
current load / input boost.
Allow speed bump after min_sample_time (or above_hispeed_delay)
elapses from the time the current speed
From: Todd Poynor
Apply min_sample_time to the last time the current target speed
was originally requested or re-validated as appropriate for the
current load, not to the time since the current speed was
originally set. Avoids periodic dips in speed during bursty
loads.
From: Todd Poynor
Evaluate spikes in load (below go_hispeed_load) against the maximum
speed supported by the device, not the current speed (which tends to
make it too difficult to raise speed to intermediate levels until
very busy).
Change-Id:
Gotcha, tested it and took a look at the changes, looks good to me.
On Mon, 2015-10-26 at 16:26 -0700, Dmitry Torokhov wrote:
> Hi,
>
> On Mon, Oct 26, 2015 at 09:51:57AM -0400, Lyude wrote:
> > Hi! So, I'm guessing you want me to merge this with the patch I've got
> > right now and post the new
On 10/27/2015 01:46 PM, Denys Vlasenko wrote:
> This function compiles to 181 bytes of machine code.
Reviewed-by: Peter Hurley
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
> -Original Message-
> From: dan.street...@canonical.com
> [mailto:dan.street...@canonical.com]
> Sent: Monday, October 26, 2015 5:16 PM
> To: Kirsher, Jeffrey T
> Cc: Brandeburg, Jesse; Nelson, Shannon; Wyborny, Carolyn; Skidmore,
> Donald C; Vick, Matthew; Ronciak, John; Williams,
Hi Ulf,
>
> Hi Axel,
>
> Apologize for the delay in providing feedback.
>
Thanks for the review!
>> ---
>> arch/arm/mach-exynos/pm_domains.c | 2 +-
>> arch/arm/mach-imx/gpc.c | 2 +-
>> arch/arm/mach-s3c64xx/pm.c| 4 ++--
>> arch/arm/mach-shmobile/pm-rmobile.c
Use the preferred style for multi-line comments.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/comedi_test.c | 94 ++--
1 file changed, 47 insertions(+), 47 deletions(-)
diff --git a/drivers/staging/comedi/drivers/comedi_test.c
The fake waveform generator functions, `fake_sawtooth()` and
`fake_squarewave()`, called from `fake_waveform()`, have a
`current_time` parameter which is the time since the start of a waveform
period. The parameter value may be greater than the waveform period so
they do a modulo operation to
Use `unsigned int` instead of `unsigned long` to hold the period of the
fake waveform generator and the current time within each waveform. The
waveform period will be no more than `INT_MAX` and the current time
within the waveform (prior to the modulo operation to bring it actually
within the
From: Chih-Wei Huang
The gcc warns like:
cpufreq_interactive.c:745:6: warning: operation on 'ret' may be undefined
[-Wsequence-point]
It was introduced by commit cf0fad49d17cb8273ce555dd5b7afab67d7923bf.
Since sprintf(...) just return 1 (one character) in this case,
From: Viresh Kumar
If we have a multi-package system, where we have multiple instances of struct
policy (per package), currently we can't have multiple instances of same
governor. i.e. We can't have multiple instances of Interactive governor for
multiple packages.
This
From: Lianwei Wang
When the policy max freq is raised, and before the timer is
rescheduled in idle callback, the cpu freq may stuck at a
lower freq.
The target_freq shall be updated too, else on a high load
situation, the new_freq is always equal to target_freq and
which
On 10/28/2015 12:05 AM, Albino B Neto wrote:
2015-10-27 13:13 GMT-02:00 Ivan Safonov :
ARRAY_SIZE shorter and more difficult to create bugs.
Signed-off-by: Ivan Safonov
You tested ?
Albino
Not tested. Is this transformation can to break the
From: Minsung Kim
sysfs ops for target_loads and above_hispeed_delay can be called before
initializing tunables at CPUFREQ_GOV_POLICY_INIT. Create sysfs entries after
initialization.
Change-Id: I50356198d7629731c0d32a3066d61fe8354e0001
Signed-off-by: Minsung Kim
From: Todd Poynor
Allow speed to drop to flooor frequency but not below, don't pin
to speed at last boost.
Change-Id: I0147c2b7a2e61ba16820605af6baaf09570be787
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
From: Shridhar Rasal
Make sure that timers cpu_timer and cpu_slack_timer
deactivated before addition of new.
Change-Id: If31c4049606871df6f00efdc24b1d713c86a6f69
Signed-off-by: Shridhar Rasal
Signed-off-by: Bharat Nihalani
From: Todd Poynor
From: Cylen Yao
common_tunables should be static.
Change-Id: I502ee3062bece5082fea7861eff2f6237e25cede
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
From: Badhri Jagan Sridharan
The cpufreq_interactive_timer gets cancelled and rescheduled
whenever the cpufreq_policy is changed. When the cpufreq policy is
changed at a rate faster than the sampling_rate of the interactive
governor, then the governor misses to change the
From: Todd Poynor
35a84de cpufreq: interactive: apply above_hispeed_delay to each step above
hispeed
caused the speed choice logic to osciallate between boosting and not boosting.
Add back code to ensure speed does not drop below boost frequency while
boosting.
On Thu, Oct 22, 2015 at 07:05:58AM -0700, Drew Richardson wrote:
> On Fri, Oct 09, 2015 at 03:13:38AM -0700, Will Deacon wrote:
> > Also, would you be able to do something similar for AArch64 too, please?
> > (take a look at our for-next/core branch for the latest perf changes).
>
> Here are some
On Tue, Oct 27, 2015 at 1:03 PM, Skidmore, Donald C
wrote:
>
>
>> -Original Message-
>> From: dan.street...@canonical.com
>> [mailto:dan.street...@canonical.com]
>> Sent: Monday, October 26, 2015 5:16 PM
>> To: Kirsher, Jeffrey T
>> Cc: Brandeburg, Jesse;
Hi Michal,
On Tue, Oct 27, 2015 at 05:20:47PM +0100, Michal Hocko wrote:
> Yes this is a mess. But I think it is worth cleaning up.
> dump_stack_print_info (arch independent) has a log level parameter.
> show_stack_log_lvl (x86) has a loglevel parameter which is unused.
>
> I haven't checked
From: Todd Poynor
Starting the governor, or restarting on a hotplugged-in CPU, can race
with the timer start in idle, triggering a BUG on timer already pending.
Start the timer before setting the enable flag, and use enable_sem to
protect the sequence (and ensure correct
From: Todd Poynor
Change-Id: Icf1e86d2065cc8f0816ba9c6b065eb056d4e8249
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
Documentation/cpu-freq/governors.txt |9 ++--
From: Todd Poynor
The explicit hint on/off version.
Change-Id: Ibf62b6d45bf6fb8c9c055b9bdaf074ce9374c04f
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
Documentation/cpu-freq/governors.txt |3 ++
Add support for Cortex A57 and A53 EDAC driver.
Signed-off-by: Brijesh Singh
CC: robh...@kernel.org
CC: pawel.m...@arm.com
CC: mark.rutl...@arm.com
CC: ijc+devicet...@hellion.org.uk
CC: ga...@codeaurora.org
CC: dougthomp...@xmission.com
CC: b...@alien8.de
CC:
From: Sam Leffler
Fix a problem where the hung task mechanism was deeming the interactive
clock boost thread as hung. This was because the thread is created at
module init but never run/woken up until needed. If the governor is not
being used this can be forever. To
From: Todd Poynor
Change-Id: I2e5b91d45e8806b0ab94ca2301ed671c9af9ab13
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
drivers/cpufreq/cpufreq_interactive.c |9 -
1 file changed, 8 insertions(+), 1
On Tue, Oct 27, 2015 at 09:17:40PM +0530, Saurabh Sengar wrote:
> replace GFP_KERNEL with GFP_ATOMIC, as code while holding a spinlock
> should be atomic
> GFP_KERNEL may sleep and can cause deadlock, where as GFP_ATOMIC may
> fail but certainly avoids deadlock
Great catch. Thanks!
However,
On Tue, Oct 27, 2015 at 02:12:36PM -0400, ira.weiny wrote:
> On Tue, Oct 27, 2015 at 09:17:40PM +0530, Saurabh Sengar wrote:
> > replace GFP_KERNEL with GFP_ATOMIC, as code while holding a spinlock
> > should be atomic
> > GFP_KERNEL may sleep and can cause deadlock, where as GFP_ATOMIC may
> >
On 10/27/2015 01:46 PM, Denys Vlasenko wrote:
> This function compiles to 141 bytes of machine code.
Fails to apply to tty-next
Regards,
Peter Hurley
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
On 10/27/2015 01:46 PM, Denys Vlasenko wrote:
> This function compiles to 141 bytes of machine code.
Reviewed-by: Peter Hurley
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
Hi Bjorn,
[auto build test WARNING on ljones-mfd/for-mfd-next -- if it's inappropriate
base, please suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Bjorn-Andersson/devicetree-mfd-Add-binding-for-the-TI-LM3533/20151028-003248
config:
-Original Message-
From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
Behalf Of Nicholas Krause
Sent: Friday, October 9, 2015 8:53 AM
To: Kirsher, Jeffrey T
Cc: linux-kernel@vger.kernel.org; intel-wired-...@lists.osuosl.org;
Hi,
On Tue, Oct 27, 2015 at 03:42:37PM +, Lee Jones wrote:
> Since eafbaac ("MAINTAINERS: Add "R:" designated-reviewers tag") we
> have been able to tag specific people as Reviewers. These are key
> individuals who are tasked with or volunteer to review code submitted
> to a subsystem or
On Tue, Oct 27, 2015 at 1:14 PM, Skidmore, Donald C
wrote:
>
>
>> -Original Message-
>> From: dan.street...@canonical.com
>> [mailto:dan.street...@canonical.com]
>> Sent: Monday, October 26, 2015 5:20 PM
>> To: Kirsher, Jeffrey T
>> Cc: Brandeburg, Jesse;
The Intel Volume Management Device (VMD) is an integrated endpoint on the
platform's PCIe root complex that acts as a host bridge to a secondary
PCIe domain. BIOS can reassign one or more root ports to appear within
a VMD domain instead of the primary domain. The immediate benefit is
that
> -Original Message-
> From: Jiang Liu [mailto:jiang@linux.intel.com]
> Sent: Tuesday, October 27, 2015 12:10 AM
> To: Jake Oshins ; gre...@linuxfoundation.org; KY
> Srinivasan ; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org;
PCI-e segments will continue to use the lower 16 bits as required by
ACPI. Special domains may use the full 32-bits.
Signed-off-by: Keith Busch
---
lib/filter.c |2 +-
lib/pci.h|2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/filter.c
From: Marc Titinger
This patch allows cluster-level idle-states to being soaked in as generic
domain power states, in order for the domain governor to chose the most
efficient power state compatible with the device constraints. Similarly,
devices can register power-states
Hi Lina,
this is the rebased version of my patches to handle cluster sleep with genpd.
I rebased over your current patches in the linaro git, and Axels v10, and
finally linux-next.
The arm64/Juno stuff is mainly for testing, it may not be 100% up-to-date with
the CPU-pd discussion outcomes, and
From: Jon Medhurst
Signed-off-by: Jon Medhurst
---
arch/arm64/boot/dts/arm/juno.dts | 29 +
1 file changed, 29 insertions(+)
diff --git a/arch/arm64/boot/dts/arm/juno.dts b/arch/arm64/boot/dts/arm/juno.dts
index 53442b5..b3fcee8
From: Viresh Kumar
Cpufreq no longer calls governor callback for offlined cpus. i.e. All
policy->cpus are guaranteed to be online. Hence we don't need explicit check to
see if cpu is online or not.
Change-Id: I9ad85ea4addd5b4a40952e59ed730dd15e328690
Signed-off-by:
From: Todd Poynor
Need to use irqsave/restore spinlock calls to avoid a deadlock in calls
from the timer.
Change-Id: I15b6b590045ba1447e34ca7b5ff342723e53a605
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
From: Minsung Kim
Accept a string of delays and speeds at which to apply the delay before
raising each step above hispeed. For example, "8 130:20
150:4" means that the delay at or above 1GHz, until 1.3GHz is 80 msecs,
the delay until 1.5GHz is 200 msecs
From: Todd Poynor
When stopping the governor, del_timer_sync() can race against an
invocation of the idle notifier callback, which has the potential
to reactivate the timer.
To fix this issue, a read-write semaphore is used. Multiple readers are
allowed as long as
From: Todd Poynor
Time to wait should be based on the intended target speed, not the
actual speed (which may be held high by another CPU).
Change-Id: Ifc5bb55d06adddb9a02af90af05398a78f282272
Reported-by: Arve Hjønnevåg
Signed-off-by: Todd Poynor
Regards,
Igal Liberman
> -Original Message-
> From: Wood Scott-B07421
> Sent: Saturday, September 26, 2015 2:02 AM
> To: Liberman Igal-B31950
> Cc: net...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> ker...@vger.kernel.org; Bucur
On Tue, 27 Oct 2015 17:50:20 +0100
Jens Kuske wrote:
> Changes since v3:
> - add a clock driver specific to the bus gates instead of listing parents in
> the DTSI
> - skip the holes in the reset controller with of_xlate()
Hi, Maxime, there we are :(. The H3 description is
From: Todd Poynor
Change-Id: I37c5085b91318242612440dfd775ad762996612f
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
drivers/cpufreq/cpufreq_interactive.c |7 +--
1 file changed, 1 insertion(+), 6
From: Todd Poynor
Change-Id: If59c668d514a29febe5c35404fd9d01df8548eb1
Signed-off-by: Todd Poynor
Signed-off-by: Bálint Czobor
---
Documentation/cpu-freq/governors.txt | 16 +---
From: Todd Poynor
If load is above go_hispeed_load, always go to at least hispeed_freq,
even when reducing speed from a higher speed, not just when jumping
up from minimum speed. Avoids running at a lower than intended
speed after a burst of even higher load.
Change-Id:
Hi Denys,
On 10/27/2015 01:46 PM, Denys Vlasenko wrote:
> For Peter's review.
> (Pater, I removed a few patches which looked most problematic)
I'd take 'Deinline finish_erasing, save 112 bytes' as well.
Regards,
Peter Hurley
> Denys Vlasenko (15):
> cyclades: Deinline cyz_is_loaded, save 240
The driver currently waits 1us after issuing a RST, but the spec
requires it to wait 1ms. This adds a msleep(1) before polling the
reset bit.
Signed-off-by: Dan Streetman
Signed-off-by: Dan Streetman
---
changes since v1:
use msleep(1) instead
mmconfig_64.c version is going to be default implementation for low-level
operation on mmconfig regions. However, now it initializes raw_pci_ext_ops
pointer which is specific for
x86 only. Moreover, mmconfig_32.c is doing the same thing at the same time.
So lets move it to mmconfig_shared.c so it
ECAM standard and MCFG table are architecture independent and it makes
sense to share common code across all architectures. Both are going to
corresponding files - ecam.c and mcfg.c
While we are here, rename pci_parse_mcfg to acpi_parse_mcfg.
We already have acpi_parse_mcfg prototype which is
This patch is the first step for MMCONFIG refactoring process.
Code that uses pci_mmcfg_lock will be moved to common file and become
accessible for all architectures. pci_mmconfig_insert() cannot be moved
so easily since it is mixing generic mmconfig code with x86 specific logic
inside of mutual
On 10/26/2015 8:09 PM, Borislav Petkov wrote:
you called it "AMD
extended features 2" - then those should really go into into the
x86_capability array, i.e., like you've done it in your initial version.
So please fix the SOB chain of your initial patch and send that one out.
Forgot to ask
> -Original Message-
> From: dan.street...@canonical.com
> [mailto:dan.street...@canonical.com]
> Sent: Monday, October 26, 2015 5:20 PM
> To: Kirsher, Jeffrey T
> Cc: Brandeburg, Jesse; Nelson, Shannon; Wyborny, Carolyn; Skidmore,
> Donald C; Vick, Matthew; Ronciak, John; Williams,
Hi Neil,
[auto build test ERROR on net/master -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Neil-Armstrong/net-dsa-cleanup-dsa-driver/20151028-003842
config: x86_64-allmodconfig (attached as .config)
-Original Message-
From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
Behalf Of Nicholas Krause
Sent: Tuesday, October 20, 2015 2:05 PM
To: Kirsher, Jeffrey T
Cc: linux-kernel@vger.kernel.org; intel-wired-...@lists.osuosl.org;
Here's version 3 for the VMD device driver, and overview of what changed
from v2:
>From review discussions, we discovered potential clashes in domain
numbering (thanks, Bjorn). This new version avoids that clash by using
domain numbers outside the ACPI defined _SEG range. Domains are purely
a
501 - 600 of 2552 matches
Mail list logo