Commit-ID: 867fe800b4c423bce46e66ccb2ce91bebbd5afc6
Gitweb: http://git.kernel.org/tip/867fe800b4c423bce46e66ccb2ce91bebbd5afc6
Author: Luis R. Rodriguez
AuthorDate: Wed, 13 Apr 2016 17:04:44 -0700
Committer: Ingo Molnar
CommitDate: Fri, 22 Apr 2016 10:29:07 +0200
x86/paravirt: Remove
Commit-ID: f6935b7bfbf8345bea05f73dc48ce81b70f016e0
Gitweb: http://git.kernel.org/tip/f6935b7bfbf8345bea05f73dc48ce81b70f016e0
Author: Luis R. Rodriguez
AuthorDate: Wed, 13 Apr 2016 17:04:45 -0700
Committer: Ingo Molnar
CommitDate: Fri, 22 Apr 2016 10:29:08 +0200
x86/init: Disable
Linus,
please pull sound fixes for v4.6-rc5 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.6-rc5
The topmost commit is 3194ed497939c6448005542e3ca4fa2386968fa0
sound fixes for 4.6-rc5
Again
Commit-ID: a50b22a7a1e60c48ca26cada362076b54823c501
Gitweb: http://git.kernel.org/tip/a50b22a7a1e60c48ca26cada362076b54823c501
Author: Luis R. Rodriguez
AuthorDate: Wed, 13 Apr 2016 17:04:46 -0700
Committer: Ingo Molnar
CommitDate: Fri, 22 Apr 2016 10:29:09 +0200
x86/init: Disable
Hi Linus,
The following changes since commit bf16200689118d19de1b8d2a3c314fc21f5dc7bb:
Linux 4.6-rc3 (2016-04-10 17:58:30 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
tags/iommu-fixes-v4.6-rc4
for you to fetch changes up to
We should only expand the atomic64 relaxed bits once we've included
all relevant headers. So move it down until after we potentially
include asm-generic/atomic64.h.
In practise this will not have made a difference so far, since the
generic bits will not define _relaxed versions.
Signed-off-by:
Implement FETCH-OP atomic primitives, these are very similar to the
existing OP-RETURN primitives we already have, except they return the
value of the atomic variable _before_ modification.
This is especially useful for irreversible operations -- such as
bitops (because it becomes impossible to
Implement FETCH-OP atomic primitives, these are very similar to the
existing OP-RETURN primitives we already have, except they return the
value of the atomic variable _before_ modification.
This is especially useful for irreversible operations -- such as
bitops (because it becomes impossible to
All the atomic operations have their arguments the wrong way around;
make atomic_fetch_or() consistent and flip them.
Signed-off-by: Peter Zijlstra (Intel)
---
include/linux/atomic.h |4 ++--
kernel/time/tick-sched.c |4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
---
Now that all the architectures have implemented support for these new
atomic primitives add on the generic infrastructure to expose and use
it.
Signed-off-by: Peter Zijlstra (Intel)
---
include/asm-generic/atomic-long.h | 36 +++-
include/asm-generic/atomic.h | 49 +
These functions have been deprecated for a while and there is only the
one user left, convert and kill.
Signed-off-by: Peter Zijlstra (Intel)
---
include/linux/atomic.h | 10 --
kernel/locking/qspinlock_paravirt.h |4 ++--
2 files changed, 2 insertions(+), 12
On 20/04/16 12:03, Jon Hunter wrote:
> Add a driver for the Tegra-AGIC interrupt controller which is compatible
> with the ARM GIC-400 interrupt controller.
>
> The Tegra AGIC (Audio GIC) is part of the Audio Processing Engine (APE) on
> Tegra210 and can route interrupts to either the GIC for the
Implement FETCH-OP atomic primitives, these are very similar to the
existing OP-RETURN primitives we already have, except they return the
value of the atomic variable _before_ modification.
This is especially useful for irreversible operations -- such as
bitops (because it becomes impossible to
Implement FETCH-OP atomic primitives, these are very similar to the
existing OP-RETURN primitives we already have, except they return the
value of the atomic variable _before_ modification.
This is especially useful for irreversible operations -- such as
bitops (because it becomes impossible to
Implement FETCH-OP atomic primitives, these are very similar to the
existing OP-RETURN primitives we already have, except they return the
value of the atomic variable _before_ modification.
This is especially useful for irreversible operations -- such as
bitops (because it becomes impossible to
Implement FETCH-OP atomic primitives, these are very similar to the
existing OP-RETURN primitives we already have, except they return the
value of the atomic variable _before_ modification.
This is especially useful for irreversible operations -- such as
bitops (because it becomes impossible to
Implement FETCH-OP atomic primitives, these are very similar to the
existing OP-RETURN primitives we already have, except they return the
value of the atomic variable _before_ modification.
This is especially useful for irreversible operations -- such as
bitops (because it becomes impossible to
As there have been a few requests for atomic_fetch_$op primitives and recently
by Linus, I figured I'd go and implement the lot.
The atomic_fetch_$op differs from the existing atomic_$op_return we already
have by returning the old value instead of the new value. This is especially
useful when the
Implement FETCH-OP atomic primitives, these are very similar to the
existing OP-RETURN primitives we already have, except they return the
value of the atomic variable _before_ modification.
This is especially useful for irreversible operations -- such as
bitops (because it becomes impossible to
On Wed, Apr 20, 2016 at 12:03:56PM +0100, Jon Hunter wrote:
> The Tegra AGIC interrupt controller is compatible with the ARM GIC-400
> interrupt controller.
The cover letter says it _is_ a GIC-400, just used in a slightly unusual
manner (i.e. not directly connected to CPUs).
> The Tegra AGIC
There are two issues here:
1) We need to decrement "i" otherwise we unregister something that was
not successfully registered.
2) The original code did not unregister the first element in the array
where i is zero.
Fixes: d293b640ebd5 ('crypto: mxc-scc - add basic driver for the MXC SCC')
From: "jeffrey.lin"
Raydium I2C touch driver.
Signed-off-by: jeffrey.lin
---
drivers/input/touchscreen/Kconfig | 12 +
drivers/input/touchscreen/Makefile |1 +
drivers/input/touchscreen/raydium_i2c_ts.c | 1172
3 files changed, 1185
The only reason for the current code is to make GCC emit only the
"LOCK XADD" instruction on x86 (and not do a pointless extra ADD on
the result), do so nicer.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/locking/qrwlock.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
Implement FETCH-OP atomic primitives, these are very similar to the
existing OP-RETURN primitives we already have, except they return the
value of the atomic variable _before_ modification.
This is especially useful for irreversible operations -- such as
bitops (because it becomes impossible to
This patch fixes the incorrect conversion table.
The Code to Temperature mapping is updated based on sillcon results.
Fixes commit b0d70338bca22cb14
("thermal: rockchip: Support the RK3399 SoCs in thermal driver").
Signed-off-by: Caesar Wang
Cc: Zhang Rui
Cc: Eduardo Valentin
Cc: Heiko
To update the notes for keeping in mind that quickly in case
someone re-read this driver in the future.
Signed-off-by: Caesar Wang
Cc: Zhang Rui
Cc: Eduardo Valentin
Cc: Heiko Stuebner
---
drivers/thermal/rockchip_thermal.c | 74 +++---
1 file changed, 53
We should judge the table.id[mid].code insearch algorithm on matter the
adc value increment or decrement.
Or otherwise, the temperature return the incorrect value in some cases.
[1.438589] adc_val=402,temp=-4
[1.438903] adc_val=403,temp=-39375
[1.439217] adc_val=404,temp=-38750
We print an uninitialized "actlen" variable on the error path.
Signed-off-by: Dan Carpenter
diff --git a/drivers/media/usb/cx231xx/cx231xx-core.c
b/drivers/media/usb/cx231xx/cx231xx-core.c
index f497888..6741fd0 100644
--- a/drivers/media/usb/cx231xx/cx231xx-core.c
+++
Implement FETCH-OP atomic primitives, these are very similar to the
existing OP-RETURN primitives we already have, except they return the
value of the atomic variable _before_ modification.
This is especially useful for irreversible operations -- such as
bitops (because it becomes impossible to
dts: rockchip: move the rk3368 thermal data into rk3368.dtsi
Verified on url =
https://github.com/Caesar-github/rockchip/tree/wip/fixes-rockchip-thermal
Based on linux-next kernel for 20160422
Verified on rk3288/rk3366/rk3399 SoCs with rockchip inside kernel(develop4.4).
The rk3399 dtsi has benn s
In order to be standard to manage for rockchip SoCs, move the thermal
data into rk3288 dtsi, we needn't to add a new file for thermal.
Signed-off-by: Caesar Wang
Cc: Zhang Rui
Cc: Eduardo Valentin
Cc: Heiko Stuebner
---
arch/arm/boot/dts/rk3288-thermal.dtsi | 118
From: Elaine Zhang
The RK3366 SoCs have two Temperature Sensors, channel 0 is for CPU
channel 1 is for GPU.
Signed-off-by: Elaine Zhang
Signed-off-by: Caesar Wang
---
drivers/thermal/rockchip_thermal.c | 28
1 file changed, 28 insertions(+)
diff --git
In order to be standard to manage for rockchip SoCs, move the thermal
data into rk3368 dtsi, we needn't to add a new file for thermal.
Fixes commit f990238f859e
("arm64: dts: rockchip: Add main thermal info to rk3368.dtsi")
Signed-off-by: Caesar Wang
Cc: Zhang Rui
Cc: Eduardo Valentin
Cc:
It causes a static checker warning if we use "buf" on the failure path
so move that inside the if statement.
Signed-off-by: Dan Carpenter
diff --git a/drivers/iio/light/apds9960.c b/drivers/iio/light/apds9960.c
index a6af56a..fbdd172 100644
--- a/drivers/iio/light/apds9960.c
+++
This adds the grf property to handle the tsadc power sequence on
rockchip some SoCs.
Verified on rk3399 can work with this patch on now.
while true; do grep "" /sys/class/thermal/thermal_zone[0-1]/temp
sleep .5; done
/sys/class/thermal/thermal_zone0/temp:40555
Hola,
am Dr. Eric CHARLES, legítimo y confiable prestamista préstamo de Skye de
Servicios Financieros. Ofrecemos préstamos en una forma clara y comprensible y
condiciones en la tasa de interés del 3%. De $ 5,000.00 a $ 450,000,000.00USD y
Euros Solo. Nos ofrecen préstamos de negocios,
On 04/22/2016 03:25 PM, Dan Carpenter wrote:
> We read one element beyond the end of the array when we access
> "rdesc[i + 1]" so it causes a static checker warning. It's harmless
> because we write over it again on the next line. But let's just silence
> the warning.
>
> Signed-off-by: Dan
We could print an uninitialized value in the error message.
Signed-off-by: Dan Carpenter
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index 47ca4b3..641c2d1 100644
--- a/drivers/bluetooth/ath3k.c
+++ b/drivers/bluetooth/ath3k.c
@@ -206,7 +206,8 @@ static int
Set free_count to zero before walking through ai->erase list
in wl_init().
Found in U-Boot as U-Boot has no workqueue/threads, it immediately
calls erase_worker(), which increase for each erased block
free_count. Without this patch, free_count gets after
this initialized to zero in wl_init(), so
From: Shawn Lin
Disable thermal->clk when enabling pclk fails in
resume routine.
Signed-off-by: Shawn Lin
Reviewed-by: Heiko Stuebner
Reviewed-by: Caesar Wang
Signed-off-by: Caesar Wang
---
drivers/thermal/rockchip_thermal.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff
On 04/21/2016 04:56 PM, Peter Rosin wrote:
> Crestez Dan Leonard wrote:
>> On 04/20/2016 11:31 PM, Peter Rosin wrote:
>>> Crestez Dan Leonard wrote:
Changes since that version:
* Nest the adapter in inv_mpu6050_state instead of making it static
* Explicitly forward of_node
On Fri, 2016-04-22 at 17:23 +0900, Greg Kroah-Hartman wrote:
> On Fri, Apr 22, 2016 at 10:10:59AM +0200, Sebastian M. Bobrecki wrote:
> > W dniu 22.04.2016 o 09:55, Greg Kroah-Hartman pisze:
> > > On Fri, Apr 22, 2016 at 09:47:04AM +0200, Sebastian M. Bobrecki wrote:
> > > > Hi,
> > > >
> > > > I
Hi Sascha,
These are still the newest patches. I won't have any resources in the
near future for continuing the work on them, so feel free to pick them
up. There hasn't been much discussion around these patches which was the
reason I abandoned them.
Okay.
I start to pick them up and do some
In the original code the clock rate was only obtained during
initialisation; however, the rate may change between then and
its use. This patch ensures the correct rate is acquired just
before use.
Signed-off-by: Lee Jones
---
drivers/pwm/pwm-sti.c | 16
1 file changed, 8
Once a PWM Capture has been initiated, the capture call
enables a rising edge detection IRQ, then waits. Once each
of the 3 phase changes have been recorded the thread then
wakes. The remaining part of the call carries out the
relevant calculations and passes back a formatted string to
the
Each PWM Capture device is allocated a structure to hold its own
state. During a capture the device may be partaking in one of 3
phases. Initial (rising) phase change, a subsequent (falling)
phase change indicating end of the duty-cycle phase and finally
a final (rising) phase change indicating
This includes fixing some Coding Style issues and re-ordering/
simplifying a little code.
Signed-off-by: Lee Jones
---
drivers/pwm/pwm-sti.c | 40 ++--
1 file changed, 22 insertions(+), 18 deletions(-)
diff --git a/drivers/pwm/pwm-sti.c
Here we're requesting the PWM Capture IRQ and supplying the
handler which will be called in the event of an IRQ fire to
handle it.
Signed-off-by: Lee Jones
---
drivers/pwm/pwm-sti.c | 92 ++-
1 file changed, 91 insertions(+), 1 deletion(-)
diff
This is to bring the terminology used in the STi PWM driver more
into line with the PWM subsystem.
Signed-off-by: Lee Jones
---
drivers/pwm/pwm-sti.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/pwm/pwm-sti.c
ST's PWM IP is supplied by 2 different clocks. One for PWM
Output and the other for Capture. This patch provides clock
handling for the latter.
Signed-off-by: Lee Jones
---
drivers/pwm/pwm-sti.c | 25 +
1 file changed, 25 insertions(+)
diff --git
Allow a user to read PWM Capture results from /sysfs.
To start a capture and read the result, simply read the file:
$ cat $PWMCHIP/capture
The output format is ":".
Signed-off-by: Lee Jones
---
drivers/pwm/sysfs.c | 17 +
1 file changed, 17 insertions(+)
diff --git
Signed-off-by: Lee Jones
---
drivers/pwm/pwm-sti.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/pwm/pwm-sti.c b/drivers/pwm/pwm-sti.c
index c4a34af..2f61e1e 100644
--- a/drivers/pwm/pwm-sti.c
+++ b/drivers/pwm/pwm-sti.c
@@ -22,26 +22,48 @@
#include
Exciting functionality is on the way to this device. But
before we can add it, we need to do some basic housekeeping
so the additions can be added cleanly.
Signed-off-by: Lee Jones
---
drivers/pwm/pwm-sti.c | 76 +++
1 file changed, 41
The first part of this set extends the current PWM API to allow external
code to request a PWM Capture. Subsequent patches then make use of the
new API by providing a userspace offering via /sysfs. The final part of
the set supplies PWM Capture functionality into the already existing STi
PWM
The data member of the of_device_id is the constant type
and hence all static structure which is used for this
initialisation as static.
Signed-off-by: Laxman Dewangan
Suggested-by: Thierry Reding
Reviewed-by: Stephen Warren
---
Changes from V2:
-This is new in series based on discussion on
Supply a PWM Capture call-back Op in order to pass back
information obtained by running analysis on PWM a signal.
This would normally (at least during testing) be called from
the Sysfs routines with a view to printing out PWM Capture
data which has been encoded into a string.
Signed-off-by: Lee
NVIDIA's Tegra210 support the HW debounce in the GPIO controller
for all its GPIO pins.
Add support for setting debounce timing by implementing the
set_debounce callback of gpiochip.
Signed-off-by: Laxman Dewangan
---
Changes from V1:
- Write debounce count before enable.
- Make sure the
Move the file scoped multiple global variable from Tegra GPIO
driver to the structure and make this as gpiochip data which
can be referred from GPIO chip callbacks.
Signed-off-by: Laxman Dewangan
Reviewed-by: Stephen Warren
---
This patch is reworked on top of earlier patch
gpio: tegra: Remove
On 22/04/16 10:57, Marc Zyngier wrote:
> On 20/04/16 12:03, Jon Hunter wrote:
>> Add a driver for the Tegra-AGIC interrupt controller which is compatible
>> with the ARM GIC-400 interrupt controller.
>>
>> The Tegra AGIC (Audio GIC) is part of the Audio Processing Engine (APE) on
>> Tegra210 and
Hi,
We can use the config files (i.e user wide ~/.perfconfig
and system wide $(sysconfdir)/perfconfig)
to configure perf tools. perf-config help user
manage the config files, not manually look into or edit them.
Introduce new infrastructure code for config
management features of perf-config
On Fri, 22 Apr 2016 11:25:38 +0200
Greg Kurz wrote:
> On Thu, 21 Apr 2016 19:36:11 +0200
> Radim Krčmář wrote:
> > > For other architectures, it is simply KVM_MAX_VCPUS.
> >
> > (Other architectures would not implement the capability.)
> >
>
> So this would be KVM_CAP_PPC_MAX_VCPU_ID ?
>
To avoid duplicated config variables and
use perf_config_set classifying between standard
perf config variables and unknown or new config
variables other than them, initialize perf_config_set
with all default configs.
And this will be needed when showing all configs with
default value or checking
Use of_device_get_match_data() for getting matched data
instead of implementing this locally.
Signed-off-by: Laxman Dewangan
Reviewed-by: Stephen Warren
Reviewed-by: Alexandre Courbot
Acked-by: Thierry Reding
---
Collected reviewed/ack by from Stephen, Alexandre and Thieery.
To precisely manage configs,
prepare all default perf's configs that contain
default section name, variable name, value
and correct type, not string type.
In the near future, this will be used when
checking type of config variable or showing
all configs with default values, etc.
Cc: Namhyung Kim
On Wed, Apr 20, 2016 at 06:59:47PM +, Wang Nan wrote:
> v5 -> v6: Improve trigger class: rename (Suggested by Namhyung Kim)
> toggle -> hit; don't generate functions for each trigger,
> use generic functions instead.
>
> Patch cleanup: switch auxtrace_snapshot to
The DVCO present in the DFLL IP block has a separate reset line,
exposed via the CAR IP block. This reset line is asserted upon SoC
reset. Unless something (such as the DFLL driver) deasserts this
line, the DVCO will not oscillate, although reads and writes to the
DFLL IP block will complete.
This patch series implements the DFLL/CL-DVFS clock source on Tegra210
based on Tegra124 DFLL driver, Tegra210 support on Tegra124 cpufreq
driver, and exposes DFLL HW as a PWM controller and provides DFLL_PWM
driver to generate PWM signals to control an OpenVReg (PWM regulator)
for CPU rail.
This
When generating opp table, the voltage is round down based on the
alignment in cvb table. This alignment should be also applied on all
voltage comparison. By the way, the alignment voltage values should
depend on regulator device specification, so these values should not
be hard code in cvb table.
On Wed, Apr 20, 2016 at 10:34:41AM +0100, Stefano Stabellini wrote:
> Hello Mark,
>
> do you think that this patch addresses your previous comments
> (http://marc.info/?l=devicetree=145926913008544=2) appropriately?
>
> Thanks,
>
> Stefano
>
> On Thu, 7 Apr 2016, Shannon Zhao wrote:
> > From:
The CPU rail on Jetson TX1 is supplied by a Open Voltage Regulator
(OVR) which is controlled by PWM signals, and the PWM signals are
generated by DFLL PWM controller. So this patch adds DFLL_PWM
device-tree node and a PWM regulator node for the OVR.
Signed-off-by: Penny Chiu
---
Add clocks, clock-names, and clock-latency into cpu0 node.
These properties will be used by cpufreq driver.
Signed-off-by: Penny Chiu
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
Add tegra210 support in tegra124 cpufreq driver.
Signed-off-by: Penny Chiu
---
drivers/cpufreq/tegra124-cpufreq.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/cpufreq/tegra124-cpufreq.c
b/drivers/cpufreq/tegra124-cpufreq.c
index 20bcceb..c891e6e 100644
---
Enable CPUFreq-DT, PWM regulator for CPU rail, and related PWM
controller driver.
Signed-off-by: Penny Chiu
---
arch/arm64/configs/defconfig | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 5091d35..865daca 100644
---
Tegra DFLL IP block controls off-chip PMIC via I2C bus or PWM
signals. This driver exposes DFLL as a PWM controller to generate
PWM signals to PWM regulator.
Tegra DFLL HW changes regulator voltage by adjusting PWM signals
duty cycle automatically based on required DVCO frequency, so PWM
Add DFLL clock device-tree node for Tegra210 DFLL IP block.
Signed-off-by: Penny Chiu
---
arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi | 16
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 15 +++
2 files changed, 31 insertions(+)
diff --git
The DFLL module can autonomously change the supply voltage by
communicating with an off-chip PMIC via either I2C or PWM signals.
Original driver only supports I2C interface, this patch adds PWM
interface support.
Signed-off-by: Penny Chiu
---
.../bindings/clock/nvidia,tegra124-dfll.txt
Add Tegra210 support and related CVB table in tegra124 DFLL driver,
and also update the binding document.
Signed-off-by: Penny Chiu
---
.../bindings/clock/nvidia,tegra124-dfll.txt| 4 +-
drivers/clk/tegra/Makefile | 4 +-
Move all SoC specific fcpu data into of_device_id structure, and
move SoC fcpu data assignments from init function to probe
function.
Signed-off-by: Penny Chiu
---
drivers/clk/tegra/clk-tegra124-dfll-fcpu.c | 51 ++
1 file changed, 37 insertions(+), 14 deletions(-)
We used generic hooks in remap_pfn_range to help archs to
track pfnmap regions. The code is something like:
int remap_pfn_range()
{
...
track_pfn_remap(vma, , pfn, addr, PAGE_ALIGN(size));
...
pfn -= addr >> PAGE_SHIFT;
...
untrack_pfn(vma, pfn,
Hi Linus,
Please pull a few powerpc fixes for 4.6:
The following changes since commit 71528d8bd7a8aa920cd69d4223c6c87d5849257d:
powerpc: Correct used_vsr comment (2016-03-29 12:08:08 +1100)
are available in the git repository at:
Under virtualisation it is possible to get unexpected latency during a
clockevent device's set_next_event() callback which can make it return
-ETIME even for a delta based on min_delta_ns.
The clockevents_program_min_delta() implementation for
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=n doesn't
For compound atomics performing both a load and a store operation, make
it clear that _acquire and _release variants refer only to the load and
store portions of compound atomic. For example, xchg_acquire is an xchg
operation where the load takes on ACQUIRE semantics.
Cc: Paul E. McKenney
Cc:
Hi Dan,
> We could print an uninitialized value in the error message.
>
> Signed-off-by: Dan Carpenter
patch has been applied to bluetooth-next tree.
Regards
Marcel
Android N adds os_desc_compat in v2_descriptor by init_functionfs()
(system/core/adb/usb_linux_client.cpp) to support automatic install
of MTP driver on Windows for USB device mode.
Current __ffs_data_do_os_desc() of f_fs.c will check reserved1 field
and return -EINVAL.
This results in a second
On Thu, Apr 21, 2016 at 05:12:00PM +0100, Jon Hunter wrote:
> A regulator that is in bypass will fail to be registered because we will
> attempt to get the voltage of the regulator (ie. it's bypass voltage)
> before the supply for the regulator has been resolved. Therefore, when
> getting the
The patch
regulator: core: Clear the supply pointer if enabling fails
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
regulator: helpers: Ensure bypass register field matches ON value
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
The patch
regulator: core: Don't terminate supply resolution early
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
regulator: core: Add debugfs to show constraint flags
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
regulator: core: Move registration of regulator device
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
On Thu, Apr 07, 2016 at 08:03:28PM +0800, Shannon Zhao wrote:
> --- a/arch/arm64/kernel/setup.c
> +++ b/arch/arm64/kernel/setup.c
> @@ -320,6 +320,7 @@ void __init setup_arch(char **cmdline_p)
>*/
> cpu_uninstall_idmap();
>
> + xen_early_init();
> efi_init();
>
On Friday 22 April 2016 03:13 PM, Peter Zijlstra wrote:
> Implement FETCH-OP atomic primitives, these are very similar to the
> existing OP-RETURN primitives we already have, except they return the
> value of the atomic variable _before_ modification.
>
> This is especially useful for irreversible
On Thu, Apr 07, 2016 at 08:03:29PM +0800, Shannon Zhao wrote:
> From: Shannon Zhao
>
> When it's a Xen domain0 booting with ACPI, it will supply a /chosen and
> a /hypervisor node in DT. So check if it needs to enable ACPI.
>
> Signed-off-by: Shannon Zhao
> Reviewed-by: Stefano Stabellini
>
On Thu, Apr 07, 2016 at 08:03:32PM +0800, Shannon Zhao wrote:
> From: Shannon Zhao
>
> When running on Xen hypervisor, runtime services are supported through
> hypercall. Add a Xen specific function to initialize runtime services.
>
> Signed-off-by: Shannon Zhao
> Reviewed-by: Stefano
On Fri, Apr 22, 2016 at 11:04:14AM +0200, Peter Zijlstra wrote:
> All the atomic operations have their arguments the wrong way around;
> make atomic_fetch_or() consistent and flip them.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
> include/linux/atomic.h |4 ++--
>
Hi Andy,
On Fri, Apr 22, 2016 at 01:45:38AM +0300, Andy Shevchenko wrote:
> On Thu, Apr 14, 2016 at 8:25 PM, Lorenzo Pieralisi
> wrote:
> > On DT based systems, the of_dma_configure() API implements DMA configuration
> > for a given device. On ACPI systems an API equivalent to of_dma_configure()
On 22-04-16, 18:31, Penny Chiu wrote:
> Add tegra210 support in tegra124 cpufreq driver.
>
> Signed-off-by: Penny Chiu
> ---
> drivers/cpufreq/tegra124-cpufreq.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Acked-by: Viresh Kumar
--
viresh
Hi Eric,
On 19/04/16 18:13, Eric Auger wrote:
Let's introduce a new msi_domain_info flag value, MSI_FLAG_IRQ_REMAPPING
meant to tell the domain supports IRQ REMAPPING, also known as Interrupt
Translation Service. On Intel HW this IRQ remapping capability is
abstracted on IOMMU side while on ARM
On 4/21/2016 4:25 PM, Christian Lamparter wrote:
On Thursday, April 21, 2016 09:15:21 PM Andy Shevchenko wrote:
The last approach in the commit 8b3444852a2b ("sata_dwc_460ex: move to generic
DMA driver") to switch to generic DMA engine API wasn't tested on bare metal.
Besides that we expecting
On 21/04/16 15:56, Suzuki K Poulose wrote:
Add scope parameter to the arm64_cpu_capabilities::matches(), so that
this can be reused for checking the capability on a given CPU vs the
system wide. The system uses the default scope associated with the
capability for initialising the CPU_HWCAPs and
1101 - 1200 of 1826 matches
Mail list logo
