On 06/01/2016 10:34 AM, Daniel Lezcano wrote:
> The init functions do not return any error. They behave as the following:
>
> - panic, thus leading to a kernel crash while another timer may work and
>make the system boot up correctly
>
> or
>
> - print an error and let the caller unaware
On 24/05/16 10:55, Vincent Guittot wrote:
[...]
> +/* Take into account the change of the utilization of a child task group */
> +static void update_tg_cfs_util(struct sched_entity *se, int blocked)
> +{
> + int delta;
> + struct cfs_rq *cfs_rq;
> + long update_util_avg;
> + long
Instead of perf_config(), This function initialize config set
collecting all configs from config files (i.e. user config
~/.perfconfig and system config $(sysconfdir)/perfconfig).
If there are the same config variable both user and system
config file, user config has higher priority than system co
Hello, :)
This patchset is to reimplement perf_config() for efficient config management.
Everytime perf_config() is called, perf_config() always read config files.
(i.e. user config '~/.perfconfig' and system config '$(sysconfdir)/perfconfig')
But we need to use 'struct perf_config_set config_se
If a config file has wrong key-value pairs, perf process
will be forcibly terminated by die() at perf_parse_file()
called by perf_config() so terminal setting can be crushed
because of unusual termination.
For example,
If user config file has a wrong value 'red;default'
instead of a normal value
perf_config_set__delete() delete allocated the config set
but the global variable 'config_set' is used all around.
So purge and zfree by an address of the global variable
, i.e. 'struct perf_config_set **' type
instead of using local variable 'set' of which type
is 'struct perf_config_set *'.
Cc:
Everytime perf_config() is called, perf_config() always read config files.
(i.e. user config '~/.perfconfig' and system config '$(sysconfdir)/perfconfig')
But we need to use the config set that already contains all config
key-value pairs to avoid this repetitive work reading the config files
in pe
When first calling perf_config(), the config set is
initialized collecting both user and system config files
(i.e. user config ~/.perfconfig and system config
$(sysconfdir)/perfconfig) so config set contains
not only user config but also system config key-value pairs.
(User config has higher priori
Old show_config() directly use config set so
there are many duplicated code with perf_config_set__iter().
So reimplement show_config() using perf_config() that use
perf_config_set__iter() with config set that already
contains all configs.
Cc: Namhyung Kim
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc:
collect_config() collect all config key-value pairs
from config files and put each config info in config set.
But if config set (i.e. 'set' variable at collect_config())
is NULL, this is wrong so handle it.
Cc: Namhyung Kim
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Alexander Shishkin
Signed-off-b
The config set is prepared by collecting
all configs from config files (i.e. user config
~/.perfconfig and system config $(sysconfdir)/perfconfig)
so the config set contains all config key-value pairs.
We need to use it as global variable to share it.
And in near future, the variable will be handl
Because of die() at perf_parse_file() a config set was freed
in collect_config(), if failed.
But it is natural to free a config set after collect_config() is done
when some problems happened.
So, in case of failure, lastly free a config set at perf_config_set__new()
instead of freeing the config s
With required ARC PGU updates that allow it to be used on simulation
platforms we may finally utilize ARC PGU in nSIM OSCI virtual platforms
with modern Linux kernels.
Signed-off-by: Alexey Brodkin
---
arch/arc/boot/dts/nsimosci.dts | 14 +++---
arch/arc/boot/dts/nsimosci_hs.
Initially ARC PGU required real encoder/trnasmitter to exist.
That was fine for real HW such as ARC SDP boards.
But on some simulaiton platroms like ARC VDK or nSIM OSCI we have model
of the same ARC PGU and ability to output video data in a virtual LCD.
To make ARC PGU driver usable in those vir
With required ARC PGU updates that allow it to be used on simulation
platforms we may finally utilize ARC PGU in HS38 VDK with modern
Linux kernels.
Signed-off-by: Alexey Brodkin
---
arch/arc/boot/dts/vdk_axs10x_mb.dtsi| 13 +
arch/arc/boot/dts/vdk_hs38_smp.dts | 2 +-
arch
From: Ruud Derwig
Initially ARC PGU required real encoder/trnasmitter to exist.
That was fine for real HW such as ARC SDP boards.
But on some simulaiton platroms like ARC VDK or nSIM OSCI we have model
of the same ARC PGU and ability to output video data in a virtual LCD.
To make ARC PGU driver
This patch Replace all occurences of (1<
---
drivers/staging/comedi/drivers/das16.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/staging/comedi/drivers/das16.c
b/drivers/staging/comedi/drivers/das16.c
index fd8e0b7..69133e3 100644
This is a patch to the me_daq.c file that fixes up a
WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
found by the checkpatch.pl tool.
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
drivers/staging/comedi/drivers/me_daq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
This patch Replace all occurences of (1<
---
drivers/staging/comedi/drivers/das16.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/staging/comedi/drivers/das16.c
b/drivers/staging/comedi/drivers/das16.c
index fd8e0b7..69133e3 100644
This is a patch to the pcmuio.c file that fixes up a
WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
found by the checkpatch.pl tool.
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
drivers/staging/comedi/drivers/pcmuio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
This patch Replace all occurences of (1<
---
drivers/staging/comedi/drivers/das6402.c | 74
1 file changed, 38 insertions(+), 36 deletions(-)
diff --git a/drivers/staging/comedi/drivers/das6402.c
b/drivers/staging/comedi/drivers/das6402.c
index 1701294..0fdf5e0 1
This is a patch to the comedi_bond.c file that fixes up a
WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
found by the checkpatch.pl tool.
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
drivers/staging/comedi/drivers/comedi_bond.c | 10 +-
1 file changed, 5 insertions(+)
This is a patch to the das16m1.c file that fixes up a
WARNING: 'Block comments use a trailing */ on a separate line'
found by the checkpatch.pl tool.
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
drivers/staging/comedi/drivers/das16m1.c | 168 ---
1 file chan
On Mon, Jun 6, 2016 at 11:17 AM, Ricard Wanderlof
wrote:
>
> On Thu, 2 Jun 2016, Boris Brezillon wrote:
>
>> Hi Ricard,
>>
>> I was not in Cc of this series, so you're either developing an old
>> kernel version, or you didn't check the MAINTAINERS file (or didn't run
>> get_maintainer.pl on your s
This is a patch to the jr3_pci.c file that fixes up a
WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
found by the checkpatch.pl tool.
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
drivers/staging/comedi/drivers/jr3_pci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-
This is a patch to the jr3_pci.c file that fixes up a
WARNING: 'Block comments use a trailing */ on a separate line'
found by the checkpatch.pl tool.
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
drivers/staging/comedi/drivers/jr3_pci.c | 32
1 file chan
On 06/01/2016 11:45 AM, Krzysztof Kozlowski wrote:
> Add clock hierarchy for Security SubSystem clock and watchdog.
>
> Signed-off-by: Krzysztof Kozlowski
A applied patches:
[PATCH 1/3] dt-bindings: clock: Add watchdog and SSS clock IDs to Exynos5410
[PATCH 2/3] clk: samsung: exynos5410: Add W
This is a patch to the mpc624.c file that fixes up a
WARNING: 'Statements should start on a tabstop' found by
the checkpatch.pl tool.
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
drivers/staging/comedi/drivers/mpc624.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --g
This is a patch to the ni_65xx.c file that fixes up a
WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
found by the checkpatch.pl tool
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
drivers/staging/comedi/drivers/ni_65xx.c | 18 +-
1 file changed, 9 insertions(+),
Hi, Arnaldo :)
Did you have a nice weekend?
I sent this mail for nothing else but to tell the reason of v6 to you.
On 06/01/2016 01:52 AM, Taeung Song wrote:
On 05/31/2016 10:43 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, May 31, 2016 at 10:13:43AM +0900, Taeung Song escreveu:
Instead of pe
This got rejected by mailing-list[due to HTML content] so resending it again.
On Sat, Jun 4, 2016 at 10:25 AM, Pranay Srivastava wrote:
>
>
> On Thursday, June 2, 2016, Pranay Kr. Srivastava wrote:
>> This patch series fixes the following
>>
>> 1) fix might_sleep warning on socket shutdown:
>>
On 06/06/2016 01:02 PM, Sylwester Nawrocki wrote:
> On 06/01/2016 11:45 AM, Krzysztof Kozlowski wrote:
>> Add clock hierarchy for Security SubSystem clock and watchdog.
>>
>> Signed-off-by: Krzysztof Kozlowski
>
> A applied patches:
>
> [PATCH 1/3] dt-bindings: clock: Add watchdog and SSS clock
On Fri, 2016-03-06 at 03:49:48 UTC, Boqun Feng wrote:
> diff --git a/arch/powerpc/include/asm/spinlock.h
> b/arch/powerpc/include/asm/spinlock.h
> index 523673d7583c..2ed893662866 100644
> --- a/arch/powerpc/include/asm/spinlock.h
> +++ b/arch/powerpc/include/asm/spinlock.h
> @@ -64,6 +64,25 @@ st
Bartosz,
the only thing you achieve by resending large series a week(!) after it
had been originally posted is to create annoyance. You should know by
now that I use patchwork which doesn't forget things...
I appreciate the work you did; yet I alone can't compensate for the lack
of reviewing on t
On 06/06/2016 12:51 PM, Krzysztof Kozlowski wrote:
On 06/01/2016 10:34 AM, Daniel Lezcano wrote:
The init functions do not return any error. They behave as the following:
- panic, thus leading to a kernel crash while another timer may work and
make the system boot up correctly
or
-
This patch series cleanup usage of alps_model_data table.
Pali Rohár (5):
Input: alps - move ALPS_PROTO_V6 out of alps_model_data table
Input: alps - move ALPS_PROTO_V4 out of alps_model_data table
Input: alps - move ALPS_PROTO_V1 out of alps_model_data table
Input: alps - warn about unsup
Like for other protocols create alps_v1_protocol_data and use it in
alps_identify() function.
Signed-off-by: Pali Rohár
---
drivers/input/mouse/alps.c |9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
index 087
Like for other protocols create alps_v6_protocol_data and use it in
alps_identify() function.
Signed-off-by: Pali Rohár
---
drivers/input/mouse/alps.c |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
index 936f07
Table alps_model_data is now used only for ALPS_PROTO_V2, so add "v2"
indentifier to all relevant functions/variables/structures. Sort all
devices by signature and remove command_mode_resp which is not used
anymore.
Signed-off-by: Pali Rohár
---
drivers/input/mouse/alps.c | 66
Support for devices with ALPS_PROTO_V9 is not implemented yet but we can
detect these alps touchpads and warn users about it.
Signed-off-by: Pali Rohár
---
drivers/input/mouse/alps.c |9 +
drivers/input/mouse/alps.h |1 +
2 files changed, 10 insertions(+)
diff --git a/drivers/in
Like for other protocols create alps_v4_protocol_data and use it in
alps_identify() function.
Signed-off-by: Pali Rohár
---
drivers/input/mouse/alps.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
index eb
Hi Christoph,
I tried enabling kmemleak on 4.7-rc2 on an x86 host (macbook pro running
Debian sid) and I get some kmemleak reports every few minutes coming
from the block layer. Reverting commit 9082e87bfbf8 ("block: remove
struct bio_batch") makes them go away:
unreferenced object 0x88007785
On Mon, Jun 06, 2016 at 05:20:03PM +0800, Frank Wang wrote:
> Signed-off-by: Frank Wang
> ---
>
> Changes in v3:
> - Added 'clocks' and 'clock-names' optional properties.
> - Specified 'otg-port' and 'host-port' as the sub-node name.
>
> Changes in v2:
> - Changed vbus_host optional property
On 06/06/2016 01:23 PM, Daniel Lezcano wrote:
> On 06/06/2016 12:51 PM, Krzysztof Kozlowski wrote:
>> On 06/01/2016 10:34 AM, Daniel Lezcano wrote:
>>> The init functions do not return any error. They behave as the
>>> following:
>>>
>>> - panic, thus leading to a kernel crash while another timer
From: Jocelyn Mayer
Make cdc_ether able to use Samsung Galaxy Grand Prime VE (aka SM-G531F)
smartphone as an USB Wifi / 4G network gateway.
This patch has only been succesfully tested with Galaxy Grand Prime VE
but according to libmtp headers, it should also work with most (or all)
Samsung Andro
Hi,
On 06-06-16 13:23, Pali Rohár wrote:
This patch series cleanup usage of alps_model_data table.
Pali Rohár (5):
Input: alps - move ALPS_PROTO_V6 out of alps_model_data table
Input: alps - move ALPS_PROTO_V4 out of alps_model_data table
Input: alps - move ALPS_PROTO_V1 out of alps_model
Hi,
this is a follow up for __GFP_REPEAT clean up merged into mmotm just
recently [1]. The main motivation for the change is that the current
implementation of __GFP_REPEAT is not very much useful.
The documentation says:
* __GFP_REPEAT: Try hard to allocate the memory, but the allocation attempt
From: Michal Hocko
__GFP_REPEAT was designed to allow retry-but-eventually-fail semantic to
the page allocator. This has been true but only for allocations requests
larger than PAGE_ALLOC_COSTLY_ORDER. It has been always ignored for
smaller sizes. This is a bit unfortunate because there is no way
From: Michal Hocko
KM_MAYFAIL didn't have any suitable GFP_FOO counterpart until recently
so it relied on the default page allocator behavior for the given set
of flags. This means that small allocations actually never failed.
Now that we have __GFP_RETRY_HARD flags which works independently on
On Sun, Jun 05, 2016 at 01:27:11PM +0200, Michal Suchanek wrote:
> On 2 June 2016 at 16:26, Mark Brown wrote:
> > On Thu, Jun 02, 2016 at 02:14:26PM +0200, Michal Suchanek wrote:
> >> And the code added in that patch will never run unless you
> >> 1) use long spi transfers
> >> 2) compile in/loa
From: Boqun Feng
There is an ordering issue with spin_unlock_wait() on powerpc, because
the spin_lock primitive is an ACQUIRE and an ACQUIRE is only ordering
the load part of the operation with memory operations following it.
Therefore the following event sequence can happen:
CPU 1
On Mon, Jun 06, 2016 at 11:09:07AM +0200, Arnd Bergmann wrote:
> On Monday, June 6, 2016 9:56:27 AM CEST Mark Rutland wrote:
> > [adding devicetree]
> >
> > On Sun, Jun 05, 2016 at 11:20:29PM -0400, Bill Mills wrote:
> > > Keystone2 can do DMA coherency but only if:
> > > 1) DDR3A DMA buffers are
On Mon, Jun 06, 2016 at 09:56:27AM +0100, Mark Rutland wrote:
> I very much do not like this. As I previously mentioned [1],
> dma-coherent has de-facto semantics today. This series deliberately
> changes that, and inverts the relationship between DT and kernel (as the
> describption in the DT woul
Whenever the current temperature is updated, the trip points immediately
below and above the current temperature are found. A sensor driver
callback `set_trips' is then called with the temperatures.
Lastly, The sensor will trigger the hardware high temperature interrupts
to increase the sampleing r
From: Sascha Hauer
This patch implements .set_trips for device tree thermal zones.
As the hardware-tracked trip points is supported by thermal core patch[0].
patch[0]
"thermal: Add support for hardware-tracked trip points".
Signed-off-by: Sascha Hauer
Signed-off-by: Caesar Wang
Cc: Zhang Rui
From: Sascha Hauer
The .get_trend callback in struct thermal_zone_device_ops has
the prototype:
int (*get_trend) (struct thermal_zone_device *, int,
enum thermal_trend *);
whereas the .get_trend callback in struct thermal_zone_of_device_ops
has:
int (*get
From: Sascha Hauer
With interrupt driven thermal zones we pass the lower and upper
temperature on which shall be acted, so in the governor we have to act on
the exact lower temperature to be consistent. Otherwise an interrupt maybe
generated on the exact lower temperature, but the bang bang gover
-next-20160606-02546-g534926d (wxt@nb)
---
There are five pathes in this series.
thermal: Add support for hardware-tracked trip point
thermal: of: implement .set_trips for device tree thermal zones
thermal: streamline get_trend callbacks
thermal: bang-bang governor: act on lower trip boundary
th
From: Sascha Hauer
This adds support for hardware-tracked trip points to the device tree
thermal sensor framework.
The framework supports an arbitrary number of trip points. Whenever
the current temperature is updated, the trip points immediately
below and above the current temperature are found
Some IRQ chips, such as GPIO controllers or secondary level interrupt
controllers, may require require additional runtime power management
control to ensure they are accessible. For such IRQ chips, it makes sense
to enable the IRQ chip when interrupts are requested and disabled them
again once all
Some IRQ chips may be located in a power domain outside of the CPU
subsystem and hence will require device specific runtime power
management. In order to support such IRQ chips, add a pointer for a
device structure to the irq_chip structure, and if this pointer is
populated by the IRQ chip driver a
To re-use the code that initialises the GIC (found in
__gic_init_bases()), from within a platform driver, it is necessary to
move the code from the __init section so that it is always present and
not removed. Unfortunately, it is not possible to simply drop the __init
from the function declaration
The Tegra210 has a 2nd level interrupt controller located in a separate
power domain to the main GIC interrupt controller and hence requires
runtime-pm support.
Add a platform driver for the GICs that require runtime-pm and make the
necessary changes to the genirq and irqdomain core to support IRQ
To support GICs that require runtime power management, it is necessary
to add a platform driver, so that the probing of the chip can be
deferred if resources, such as a power-domain, is not yet available.
To prepare for adding a platform driver:
1. Drop the __init section from the gic_dist_config
When mapping an IRQ, it is possible that a mapping for the IRQ already
exists. If mapping does exist then there are the following issues with
regard to the handling of the IRQ type settings ...
1. If the domain is part of a hierarchy, then:
a. We do not check that the type settings for the exist
The Tegra AGIC interrupt controller is compatible with the ARM GIC-400
interrupt controller. Add the compatible string and clock information
for the AGIC to the GIC device-tree binding documentation.
Signed-off-by: Jon Hunter
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/interrupt
For GICs that require runtime power-management it is necessary to
populate the 'parent_device' member of the irqchip structure. In
preparation for supporting such GICs, move the code that initialises
the irqchip structure for a GIC into its own function called
gic_init_chip() where the parent devic
Add a platform driver to support non-root GICs that require runtime
power-management. Currently, only non-root GICs are supported because
the functions, smp_cross_call() and set_handle_irq(), that need to
be called for a root controller are located in the __init section and
so cannot be called by t
For some devices the IRQ trigger type for a device is read from
firmware, such as device-tree. The IRQ trigger type is typically read
when the mapping for IRQ is created, which is before the IRQ is
requested. Hence, the IRQ trigger type is programmed when mapping the
IRQ and not when requesting the
On Mon, Jun 06, 2016 at 09:42:20PM +1000, Michael Ellerman wrote:
> +static inline void arch_spin_unlock_wait(arch_spinlock_t *lock)
> +{
> + arch_spinlock_t lock_val;
> +
> + smp_mb();
> +
> + /*
> + * Atomically load and store back the lock value (unchanged). This
> + * ensu
Maxim Semiconductor Max77620 supports alarm interrupts when
its die temperature crosses 120C and 140C. These threshold
temperatures are not configurable.
Add thermal driver to register PMIC die temperature as thermal
zone sensor and capture the die temperature warning interrupts
to notifying the c
Maxim Semiconductor MAX77620 supports alarm interrupts when
its die temperature crosses 120C and 140C. These threshold
temperatures are not configurable.
Add DT binding document to details out the DT property related
to MAX77620 thermal functionality.
Signed-off-by: Laxman Dewangan
---
.../bind
On Mon, Jun 06, 2016 at 12:43:21PM +0100, Russell King - ARM Linux wrote:
> On Mon, Jun 06, 2016 at 09:56:27AM +0100, Mark Rutland wrote:
> > I very much do not like this. As I previously mentioned [1],
> > dma-coherent has de-facto semantics today. This series deliberately
> > changes that, and in
Hi,
On 06/06/16 13:44, Lothar Waßmann wrote:
> 'brightness' is usually an index into a table of duty_cycle values,
> where the value at index 0 may well be non-zero
> (tegra30-apalis-eval.dts and tegra30-colibri-eval-v3.dts are real-life
> examples).
> Thus brightness == 0 does not necessarily mea
On Sun, 5 Jun 2016 08:16:58 -0700
Alison Chaiken wrote:
> Steven Rostedt suggests in reference to "[PATCH][RT] netpoll: Always
> take poll_lock when doing polling"
> >> [ Alison, can you try this patch ]
>
> Sebastian follows up:
> >Alison, did you try it?
>
> Sorry for not responding soone
Signed-off-by: Pali Rohár
---
MAINTAINERS |4
1 file changed, 4 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ed1229e..057c626 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -595,6 +595,10 @@ S: Odd Fixes
L: linux-al...@vger.kernel.org
F: arch/alpha/
+ALPS PS/2 T
Maxim PMIC MAX77620 is Power management IC which have multiple
sub blocks like regulators (DCDC/LDOs), GPIO, RTC, Clock, Watchdog
timer etc.
Add the driver for watchdog timer under watchdog framework.
The driver implements the watchdog callbacks to start, stop,
ping and set timeout for watchodg fr
In current system, when we set core_pattern to a pipe, both pipe program
and program's output are in host's filesystem.
But when we set core_pattern to a file, the container will write dump
into container's filesystem.
For example, when we set following core_pattern:
# echo "|/my_dump_pipe %s %c
In current system, when we set core_pattern to a pipe, both pipe program
and program's output are in host's filesystem.
But when we set core_pattern to a file, the container will write dump
into container's filesystem.
For example, when we set following core_pattern:
# echo "|/my_dump_pipe %s %c
To make the dump_pipe thread run in container's filesystem, we need to
make it possible to select its fs_root from fork.
Then the dump_pipe thread will exec user_defined pipe program in
container's fs_root, and the problem will also write dumpdata into
the same fs_root.
Signed-off-by: Zhao Lei
-
On Monday, June 06, 2016 09:22:31 AM Viresh Kumar wrote:
> On 03-06-16, 16:48, Steve Muckle wrote:
> > On Fri, Jun 03, 2016 at 07:05:14PM +0530, Viresh Kumar wrote:
> > ...
> > > @@ -468,20 +469,15 @@ unsigned int acpi_cpufreq_fast_switch(struct
> > > cpufreq_policy *policy,
> > > struct acpi_cp
In current system, when we set core_pattern to a pipe, both pipe program
and program's output are in host's filesystem.
But when we set core_pattern to a file, the container will write dump
into container's filesystem.
Reason of above different is:
In pipe_mode dump_pattern setting, the process wh
On 6 May 2016 at 15:16, Pramod Gurav wrote:
> uart_change_pm is used to turn on the UART controller resources and
> change UART's PM status. On failure to allocate pages the controller
> be left in ON state. This will change the state to OFF on failure.
>
> Signed-off-by: Pramod Gurav
> ---
> dr
Hi Dietmar,
On 1 June 2016 at 21:39, Dietmar Eggemann wrote:
> Since task utilization is accrued only on the root cfs_rq, there are a
> couple of places where the se has to be synced with the root cfs_rq:
>
> (1) The root cfs_rq has to be updated in attach_entity_load_avg() for
> an se repres
On Mon, 2016-06-06 at 13:56 +0200, Peter Zijlstra wrote:
> On Mon, Jun 06, 2016 at 09:42:20PM +1000, Michael Ellerman wrote:
> > +static inline void arch_spin_unlock_wait(arch_spinlock_t *lock)
> > +{
> > + arch_spinlock_t lock_val;
> > +
> > + smp_mb();
> > +
> > + /*
> > +* Atomically l
On Sun, Jun 05, 2016 at 11:20:26PM -0400, Bill Mills wrote:
> Allow early-init to specify modifications to be made to the boot time page
> table. Any modifications specified will be done with MMU off at the same
> time that any Phy<->Virt fixup is done.
I think this is rather over-engineered - do
On Mon, Jun 06, 2016 at 09:34:54AM +0300, Leon Romanovsky wrote:
> On Sun, Jun 05, 2016 at 09:13:56PM +0100, Sudip Mukherjee wrote:
> > If the allocation of hsag fails we were just returning but stats was
> > not released.
> >
> > Signed-off-by: Sudip Mukherjee
>
> Thanks,
> Reviewed-by: Leon Ro
On 06/06/2016 07:59 AM, Mark Rutland wrote:
> On Mon, Jun 06, 2016 at 12:43:21PM +0100, Russell King - ARM Linux wrote:
>> On Mon, Jun 06, 2016 at 09:56:27AM +0100, Mark Rutland wrote:
>>> I very much do not like this. As I previously mentioned [1],
>>> dma-coherent has de-facto semantics today.
> Hi Andrew,
>
> it is waiting for the watchdog to trigger :-) TBH the 1s seems to be too
> short to for the dma ring length to be flushed and i had to pick some
> value and 5 is used most places.
>
> it really depends on the amount of packets in the queue, their length
> and the mac setting. the
On 06/03/16 16:56, Srinivas Kandagatla wrote:
> This patch adds support to generic audio codec via
> ASoC hdmi-codec infrastucture which is merged recently.
>
I know nothing about msm HW, but from the hdmi-codec point of view this
looks like a correct usage. However, the hdmi-codec could probably
Dear all,
This time I am sending a very early pull request because:
1. I already have a lot of stuff.
2. There are some conflicts, including annoying re-indent one (see below).
3. I am going for holidays soon. After this weekend, my availability
will be reduced.
There is no specific order o
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
tags/samsung-soc-4.8
for you to fetch changes up to da81593a5a0d93fcc
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
tags/samsung-soc64-4.8
for you to fetch changes up to 3b3428e384b7aff
Hi,
This topic branch pulls external clk dependency (provided by Sylwester
Nawrocki).
Expected annoying conflict with DT changes here (please see the email 0/8).
Best regards,
Krzysztof
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 0
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
tags/samsung-defconfig-4.8
for you to fetch changes up to 4b388071a22
Hi,
A topic branch for MultiFormat Codec driver. This pulls in
an external dependency from media tree (Sylwester Nawrocki).
Below you will find two pull-request-changelogs
Best regards,
Krzysztof
Samsung tree only changes:
#
vmbus_teardown_gpadl() can result in infinite wait when it is called
on 5 second timeout in vmbus_open(). The issue is caused by the fact
that gpadl teardown operation won't ever succeed for an opened channel
and the timeout isn't always enough. As a guest, we can always trust
the host to respond t
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
tags/samsung-drivers-4.8
for you to fetch changes up to 9479f7cc91879
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
tags/samsung-dt-4.8
for you to fetch changes up to cb0df00040d593e3f5
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
tags/samsung-dt64-4.8
for you to fetch changes up to 8b77005c40376816
701 - 800 of 1112 matches
Mail list logo
