On 2016/5/25 6:35, David Daney wrote:
From: David Daney
As noted by Dennis Chen, we don't want to print "No NUMA configuration
found" if NUMA was forced off from the command line.
Change the type of numa_off to bool, and clean up printing code.
Print "NUMA disabled" if forced off on command li
On (05/31/16 21:20), Sergey Senozhatsky wrote:
> This has started as a 'add zlib support' work, but after some
> thinking I saw no blockers for a bigger change -- a switch to
> crypto API.
>
> We don't have an idle zstreams list anymore and our write path
> now works absolutely differently, pr
On 05/31/2016 02:07 PM, Vlastimil Babka wrote:
On 05/31/2016 08:37 AM, Joonsoo Kim wrote:
@@ -3695,22 +3695,22 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int
order,
else
no_progress_loops++;
- if (should_reclaim_retry(gfp_mask, order, ac, alloc_flags,
-
Space prohibited before close parenthesis ')'.
Signed-off-by: Sandhya Bankar
---
drivers/usb/class/cdc-acm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
index 94a14f5..def5a54 100644
--- a/drivers/usb/class/cdc-acm
On 31 May 2016 at 14:03, Peter Zijlstra wrote:
> On Tue, May 31, 2016 at 01:55:49PM +0200, Vincent Guittot wrote:
>> Hi Yuyang,
>>
>> On 31 May 2016 at 00:32, Yuyang Du wrote:
>> > Vincent reported that the first task to a new task group's cfs_rq will
>> > be attached in attach_task_cfs_rq() and
On Tue, May 31, 2016 at 08:43:14AM +0100, David Drysdale wrote:
> > index cac6d17..555263e 100644
> > --- a/arch/x86/entry/syscalls/syscall_64.tbl
> > +++ b/arch/x86/entry/syscalls/syscall_64.tbl
> > @@ -374,3 +374,5 @@
> > 543x32 io_setupcompat_sys_io_setup
> > 544x32
On Tue, May 31, 2016 at 12:53:12PM +0200, Gerd Hoffmann wrote:
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/drm_crtc.c | 2 ++
> include/drm/drm_crtc.h | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
> index d2a6d9
On Tue, May 31, 2016 at 02:33:45PM +0200, Vincent Guittot wrote:
> The sched_avg of a task is not used anymore in copy_process with
> yuyang's patchset. To be fully correct, we still have a
> p->se.avg.last_update_time = 0 in cpu_cgroup_fork but this is just the
> side effect of factoring cpu_grou
On Tue, May 31, 2016 at 04:34:36PM +0800, Huang, Ying wrote:
> Hi, Ingo,
>
> Part of the regression has been recovered in v4.7-rc1 from -32.9% to
> -9.8%. But there is still some regression. Is it possible for fully
> restore it?
after much searching on how you guys run hackbench... I figured
s
On Tue, May 31, 2016 at 03:09:01PM +0300, Heikki Krogerus wrote:
> On Tue, May 31, 2016 at 10:48:29AM +0200, Oliver Neukum wrote:
> > On Tue, 2016-05-31 at 11:31 +0300, Heikki Krogerus wrote:
> > > Hi Oliver,
> > >
> > > On Mon, May 30, 2016 at 03:59:27PM +0200, Oliver Neukum wrote:
> > > > On Mon
This patch fixes an issue that the driver is possible to cause
unexpected repeat interrupts if a board condition is wrong
(e.g. even if the ID pin is as function, a board supplies the VBUS.)
The reason why unexpected repeat interrupts happen is:
1) The driver changed the mode to function if it de
On Sun 29-05-16 23:25:40, Oleg Nesterov wrote:
> sorry for delay,
>
> On 05/25, Michal Hocko wrote:
[...]
> > This is a bit surprising but my testing shows that the result shouldn't
> > make much difference. I can see some discrepancies between lru_vec size
> > and zone_reclaimable_pages but they
Arriving at read_kmem() with an offset representing a bogus kernel
address (e.g. 0 from a simple "cat /dev/kmem") leads to copy_to_user
faulting on the kernel-space read.
x86_64 happens to get away with this since the optimised implementation
uses "rep movs*", thus the user write (which is allowed
Pick up the correct source rectangle from framebuffer.
Without this multihead setups are not working correctly.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_plane.c | 31 ++-
1 file changed, 18 insertions(+), 13 deletions(-)
diff --git a/drivers/gp
Use the firmware provided identifier for the domain name.
Signed-off-by: Punit Agrawal
---
kernel/irq/irqdomain.c | 4
1 file changed, 4 insertions(+)
diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
index 1fe2fea..3af09e1 100644
--- a/kernel/irq/irqdomain.c
+++ b/kernel/irq/ir
Commit 1bf4ddc46c5d ("irqdomain: Introduce irq_domain_create_{linear,
tree}") introduced the use of fwnode_handle to identify the interrupt
controller when calling __irq_domain_add but missed updating the kernel
doc parameters for the function.
Update this comment. While we are touching this code,
Space required after that ','.
Signed-off-by: Sandhya Bankar
---
drivers/usb/phy/phy-omap-otg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/phy/phy-omap-otg.c b/drivers/usb/phy/phy-omap-otg.c
index c4bf2de..6f6d2a7 100644
--- a/drivers/usb/phy/phy-omap-otg.c
+
Hi All,
On Tue, May 31, 2016 at 3:58 PM, Kirtika Ruchandani
wrote:
> This patch fixes the checkpatch.pl check "Please don't use multiple
> blank lines" for all files in net/wireless, except nl80211.c which
> is covered in a separated patch.
>
> Signed-off-by: Kirtika Ruchandani
Looks right to m
2016-05-31 03:53-0400, Paolo Bonzini:
> > 2016-05-27 17:22+0200, Radim Krčmář:
> > > (I wonder why MacOS X doesn't read IA32_PERF_STATUS, though.)
> >
> > Oh, it maybe does ... we already emulate status and return 0x1000 in its
> > bottom 16 bits. I have no idea what is that supposed to mean, but
On 2016/5/25 6:35, David Daney wrote:
From: David Daney
Follow-on arm64 ACPI/NUMA patches need to map MADT entries very early
(before kmalloc is usable).
Add acpi_map_madt_entry() which, indirectly, uses
early_memremap()/early_memunmap() to access the table and parse out
the mpidr. The existi
If zalloc fail, setting evlist->mmap[i].fd is unsafe.
perf_evlist__alloc_mmap() should fail right after zalloc() fail.
Signed-off-by: Wang Nan
Cc: Arnaldo Carvalho de Melo
Cc: He Kuang
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Namhyung Kim
Cc: Zefan Li
Cc: pi3or...@163.com
---
tools/perf/util
This is mostly a followup to Michal's oom detection rework, which highlighted
the need for direct compaction to provide better feedback in reclaim/compaction
loop, so that it can reliably recognize when compaction cannot make further
progress, and allocation should invoke OOM killer or fail. We've
The __compaction_suitable() function checks the low watermark plus a
compact_gap() gap to decide if there's enough free memory to perform
compaction. This check uses direct compactor's alloc_flags, but that's wrong,
since these flags are not applicable for freepage isolation.
For example, alloc_fl
Compaction uses a watermark gap of (2UL << order) pages at various places and
it's not immediately obvious why. Abstract it through a compact_gap() wrapper
to create a single place with a thorough explanation.
Signed-off-by: Vlastimil Babka
---
include/linux/compaction.h | 16
m
The compaction_ready() is used during direct reclaim for costly order
allocations to skip reclaim for zones where compaction should be attempted
instead. It's combining the standard compaction_suitable() check with its own
watermark check based on high watermark with extra gap, and the result is
co
On Di, 2016-05-31 at 15:36 +0300, Ville Syrjälä wrote:
> Why store it in the fb and not eg. the plane state?
Well, drm_plane_state is allocated by drm_atomic_helper_update_plane.
When sticking the hotspot into the the plane state we have to add hot_x
and hot_y parameters to drm_plane_funcs->upda
During reclaim/compaction loop, it's desirable to get a final answer from
unsuccessful compaction so we can either fail the allocation or invoke the OOM
killer. However, heuristics such as deferred compaction or pageblock skip bits
can cause compaction to skip parts or whole zones and lead to prema
In __alloc_pages_slowpath(), alloc_flags doesn't change after it's initialized,
so move the initialization above the retry: label. Also make the comment above
the initialization more descriptive.
The only exception in the alloc_flags being constant is ALLOC_NO_WATERMARKS,
which may change due to T
The __compact_finished() function uses low watermark in a check that has to
pass if the direct compaction is to finish and allocation should succeed. This
is too pessimistic, as the allocation will typically use min watermark. It may
happen that during compaction, we drop below the low watermark (d
The __compaction_suitable() function checks the low watermark plus a
compact_gap() gap to decide if there's enough free memory to perform
compaction. Then __isolate_free_page uses low watermark check to decide if
particular free page can be isolated. In the latter case, using low watermark
is needl
During reclaim/compaction loop, compaction priority can be increased by the
should_compact_retry() function, but the current code is not optimal. Priority
is only increased when compaction_failed() is true, which means that compaction
has scanned the whole zone. This may not happen even after multi
The should_continue_reclaim() function decides during direct reclaim/compaction
whether shrink_zone() should continue reclaming, or whether compaction is ready
to proceed in that zone. This relies mainly on the compaction_suitable() check,
but by passing a zero classzone_idx, there can be false pos
A recent patch has added whole_zone flag that compaction sets when scanning
starts from the zone boundary, in order to report that zone has been fully
scanned in one attempt. For allocations that want to try really hard or cannot
fail, we will want to introduce a mode where scanning whole zone is g
In the context of direct compaction, for some types of allocations we would
like the compaction to either succeed or definitely fail while trying as hard
as possible. Current async/sync_light migration mode is insufficient, as there
are heuristics such as caching scanner positions, marking pagebloc
Async compaction detects contention either due to failing trylock on zone->lock
or lru_lock, or by need_resched(). Since 1f9efdef4f3f ("mm, compaction:
khugepaged should not give up due to need_resched()") the code got quite
complicated to distinguish these two up to the __alloc_pages_slowpath() le
On Tue, May 31, 2016 at 01:52:45PM +0100, Robin Murphy wrote:
> Arriving at read_kmem() with an offset representing a bogus kernel
> address (e.g. 0 from a simple "cat /dev/kmem") leads to copy_to_user
> faulting on the kernel-space read.
>
> x86_64 happens to get away with this since the optimise
Hi Robin
During some of the stress tests we also came across a different warning from
the arm64 page management code
It looks like a race is detected between HW and SW marking a bit in the PTE
Not sure it's really related but I thought it might give a clue on the issue
http://pastebin.com/ASv1
Since THP allocations during page faults can be costly, extra decisions are
employed for them to avoid excessive reclaim and compaction, if the initial
compaction doesn't look promising. The detection has never been perfect as
there is no gfp flag specific to THP allocations. At this moment it chec
After __alloc_pages_slowpath() sets up new alloc_flags and wakes up kswapd, it
first tries get_page_from_freelist() with the new alloc_flags, as it may
succeed e.g. due to using min watermark instead of low watermark. This attempt
does not have to be retried on each loop, since direct reclaim, dire
Since kswapd compaction moved to kcompactd, compact_pgdat() is not called
anymore, so we remove it. The only caller of __compact_pgdat() is
compact_node(), so we merge them and remove code that was only reachable from
kswapd.
Signed-off-by: Vlastimil Babka
---
include/linux/compaction.h | 5 ---
After the previous patch, we can distinguish costly allocations that should be
really lightweight, such as THP page faults, with __GFP_NORETRY. This means we
don't need to recognize khugepaged allocations via PF_KTHREAD anymore. We can
also change THP page faults in areas where madvise(MADV_HUGEPAG
The retry loop in __alloc_pages_slowpath is supposed to keep trying reclaim
and compaction (and OOM), until either the allocation succeeds, or returns
with failure. Success here is more probable when reclaim precedes compaction,
as certain watermarks have to be met for compaction to even try, and m
From: Hugh Dickins
At present MIGRATE_SYNC_LIGHT is allowing __isolate_lru_page() to
isolate a PageWriteback page, which __unmap_and_move() then rejects
with -EBUSY: of course the writeback might complete in between, but
that's not what we usually expect, so probably better not to isolate it.
Wh
On Tue, May 31, 2016 at 01:10:44PM +, Yehuda Yitschak wrote:
> During some of the stress tests we also came across a different warning
> from the arm64 page management code
> It looks like a race is detected between HW and SW marking a bit in the PTE
A72 (which I believe is the CPU in that So
2016-05-31 13:06+0300, km...@yandex-team.ru:
> 31.05.2016, 11:21, "Paolo Bonzini" :
> >> 2016-05-27 17:22+0200, Radim Krčmář:
> >> > (I wonder why MacOS X doesn't read IA32_PERF_STATUS, though.)
> >>
> >> Oh, it maybe does ... we already emulate status and return 0x1000 in its
> >> bottom 16 bi
Implement gpio_get_direction() callback for MAX77620 GPIO.
This is useful for debugfs and the userspace ABI.
Signed-off-by: Laxman Dewangan
---
Changes from V1:
Earlier it was part of series to implement get_directiona dn set_single_mode.
Other patches are alreadya pplied and hence making this as
On Tuesday, May 31, 2016 8:25:40 AM CEST Valentin Rothberg wrote:
> Hi Arnd,
>
> your commit fabb13db448e ("fou: add Kconfig options for IPv6 support")
> has shown up in today's linux-next. ./scripts/checkkconfigsymbols.py
> warned because of the following statement in net/ipv6/Makefile:
>
> +obj
On 05/29/2016 07:06 PM, Jonathan Cameron wrote:
> On 25/05/16 11:34, Daniel Baluta wrote:
>> On Tue, May 24, 2016 at 10:16 PM, Alison Schofield
>> wrote:
>>> Driver was checking for direct mode and trying to lock it, but
>>> left a gap where mode could change before the desired operation.
>>> Use
On 31 May 2016 at 14:39, Peter Zijlstra wrote:
> On Tue, May 31, 2016 at 02:33:45PM +0200, Vincent Guittot wrote:
>
>> The sched_avg of a task is not used anymore in copy_process with
>> yuyang's patchset. To be fully correct, we still have a
>> p->se.avg.last_update_time = 0 in cpu_cgroup_fork bu
On 05/29/2016 08:33 PM, Jonathan Cameron wrote:
> On 25/05/16 11:36, Daniel Baluta wrote:
>> On Tue, May 24, 2016 at 10:17 PM, Alison Schofield
>> wrote:
>>> Driver was checking for direct mode and trying to lock it, but
>>> left a gap where mode could change before the desired operation.
>>> Use
On Tue, May 31, 2016 at 12:44:54PM +0200, Michal Suchanek wrote:
> On 30 May 2016 at 17:50, Mark Brown wrote:
> > On Mon, May 30, 2016 at 05:28:10PM +0200, Michal Suchanek wrote:
> >> It's what the driver did to start with and it was requested to fall
> >> back to non-DMA in the case DMA is not a
On Tue, 31 May 2016 13:06:15 +
Wang Nan wrote:
> If zalloc fail, setting evlist->mmap[i].fd is unsafe.
> perf_evlist__alloc_mmap() should fail right after zalloc() fail.
Good catch!!
Reviewed-by: Masami Hiramatsu
Thanks!
>
> Signed-off-by: Wang Nan
> Cc: Arnaldo Carvalho de Melo
> Cc:
Remove endianness conversion functions that are declared but never used.
Signed-off-by: Luis de Bethencourt
---
Hi,
Continuing to learn the BeFS code. Noticed some cleanup.
Thanks for the review :)
Luis
fs/befs/endian.h | 44
1 file changed, 44 d
On Tue, 2016-05-31 at 10:51 +0300, Jani Nikula wrote:
> On Mon, 30 May 2016, James Bottomley <
> james.bottom...@hansenpartnership.com> wrote:
> > I've tested a pristine 4.6.0 system, so it's definitely something
> > that
> > went in during the merge window. The flicker isn't continuous,
> > it's
On Tue, May 31, 2016 at 2:35 AM, Chanwoo Choi wrote:
> Hi Rob,
>
> On 2016년 05월 31일 15:44, Chanwoo Choi wrote:
>> On 2016년 05월 28일 00:29, Rob Herring wrote:
>>> On Thu, May 26, 2016 at 05:17:45PM +0530, Venkat Reddy Talla wrote:
Add the support for Device tree bindings of extcon-gpio driver.
Add integrated MDIO multiplexer driver node which contains
two mux PCIe bus and one ethernet bus along with phys
lying on these bus.
Signed-off-by: Pramod Kumar
---
arch/arm64/boot/dts/broadcom/ns2-svk.dts | 12
arch/arm64/boot/dts/broadcom/ns2.dtsi| 32 +
Add DT binding doc for Broadcom MDIO bus mutiplexer driver.
Signed-off-by: Pramod Kumar
---
.../bindings/net/brcm,mdio-mux-iproc.txt | 60 ++
1 file changed, 60 insertions(+)
create mode 100644
Documentation/devicetree/bindings/net/brcm,mdio-mux-iproc.txt
diff --
iProc based SoCs supports the integrated mdio multiplexer which
has the bus selection as well as mdio transaction generation logic
inside.
This mutiplexer has child buses for PCIe, SATA, USB and ETH. These
buses could be internal or external to SOC where PHYs are attached.
These buses could use C-
Add PCI Phy support for Broadcom Northstar2 SoCs. This driver uses the
interface from the iproc mdio mux driver to enable the devices
respective phys.
Signed-off-by: Jon Mason
Signed-off-by: Pramod Kumar
---
drivers/phy/Kconfig| 8 +++
drivers/phy/Makefile | 1 +
driv
An integrated multiplexer uses same address space for
"muxed bus selection" and "generation of mdio transaction"
hence its good to register parent bus from mux driver.
Hence added a mechanism where mux driver could register a
parent bus and pass it down to framework via mdio_mux_init api.
Below c
Broadcom iProc based SoCs use a MDIO bus multiplexer where child buses
could be internal as well external to SoCs. These buses could supports
MDIO transaction compatible to C-22/C-45.
Broadcom MDIO bus mulitplexer is an integrated multiplexer where child bus
selection and mdio transaction logic li
This property is used by integrated MDIO multiplexer
which has bus selection and mdio transaction generation logic,
integrated inside.
Signed-off-by: Pramod Kumar
---
Documentation/devicetree/bindings/net/mdio-mux.txt | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/Do
On Tue, May 31, 2016 at 04:15:15PM +0800, kernel test robot wrote:
>
>
> FYI, we noticed reaim.jobs_per_min -49.1% regression due to commit:
>
> commit 4e82901cd6d1af21ae232ae835c36d8230c809e8
> ("dcache_{readdir,dir_lseek}() users: switch to ->iterate_shared")
> https://git.kernel.org/pub/scm/
Binding doc for NS2 PCIe PHYs.
Signed-off-by: Jon Mason
Signed-off-by: Pramod Kumar
---
.../bindings/phy/brcm,mdio-mux-bus-pci.txt | 27 ++
1 file changed, 27 insertions(+)
create mode 100644
Documentation/devicetree/bindings/phy/brcm,mdio-mux-bus-pci.txt
diff --g
EDP PSR function is interesting in vblank enable or disable event,
so it would be great introduce a way to notify encoder about this
event.
Signed-off-by: Yakir Yang
---
drivers/gpu/drm/rockchip/Makefile | 2 +-
drivers/gpu/drm/rockchip/rockchip_drm_notify.c | 66 ++
The full name of PSR is Panel Self Refresh, panel device could refresh
itself with the hardware framebuffer in panel, this would make a lots
of sense to save the power consumption.
For example, when desktop haven't change the context for a long time,
then we could refresh the data to the hardware
Em Tue, May 31, 2016 at 05:00:16PM +0900, Masami Hiramatsu escreveu:
> On Mon, 30 May 2016 13:30:53 -0300
> Arnaldo Carvalho de Melo wrote:
>
> > Em Mon, May 30, 2016 at 01:22:52PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Sun, May 29, 2016 at 12:15:01AM +0900, Masami Hiramatsu escreveu:
The full name of PSR is Panel Self Refresh, panel device could refresh
itself with the hardware framebuffer in panel, this would make a lots
of sense to save the power consumption.
For example, when desktop haven't change the context for a long time,
then we could refresh the data to the hardware
Em Tue, May 31, 2016 at 06:01:28PM +0900, Masami Hiramatsu escreveu:
> On Mon, 30 May 2016 13:10:20 -0300
> Arnaldo Carvalho de Melo wrote:
> > Em Mon, May 30, 2016 at 12:54:58PM +0900, Namhyung Kim escreveu:
> > > On Sun, May 29, 2016 at 12:15:01AM +0900, Masami Hiramatsu wrote:
> > > > Here is t
On 31/05/16 14:08, Russell King - ARM Linux wrote:
On Tue, May 31, 2016 at 01:52:45PM +0100, Robin Murphy wrote:
Arriving at read_kmem() with an offset representing a bogus kernel
address (e.g. 0 from a simple "cat /dev/kmem") leads to copy_to_user
faulting on the kernel-space read.
x86_64 happ
Hello,
My laptop will, after a short while, wake right up after issuing the command
pm-suspend.
The computer does not need to be connected to the internet.
I Get no errors and pm-suspend returns 0.
This tells me that the kernel must have some sort of wakeup event set.
The output on syslog is as fo
Em Tue, May 31, 2016 at 10:13:43AM +0900, Taeung Song escreveu:
> 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 u
On Tue, May 31, 2016 at 01:52:45PM +0100, Robin Murphy wrote:
> Arriving at read_kmem() with an offset representing a bogus kernel
> address (e.g. 0 from a simple "cat /dev/kmem") leads to copy_to_user
> faulting on the kernel-space read.
>
> x86_64 happens to get away with this since the optimise
Hi Daniel,
On 05/30/2016 07:56 PM, Daniel Lezcano wrote:
> On 05/24/2016 03:15 PM, Shreyas B. Prabhu wrote:
>> POWER ISA v3 defines a new idle processor core mechanism. In summary,
>> a) new instruction named stop is added.
>> b) new per thread SPR named PSSCR is added which controls the behav
Hello Loh Tien
On 5/31/2016 11:10 AM, Loh Tien Hock wrote:
Hi Peppe,
Sorry for the late reply.
no pbl at all.
I believe my patch's title is a little confusing. The patch is to
enable Altera TSE PCS SGMII support, not to add SGMII support to
stmmac (well that in a way tests SGMII for stmmac
On Mon, May 30, 2016 at 11:40:28PM +0100, Russell King - ARM Linux wrote:
> On Mon, May 30, 2016 at 10:35:29PM +0100, Russell King - ARM Linux wrote:
> > With that, on a single CPU, it seems to work correctly every time, but
> > if I bring up a secondary CPU I start seeing the same problems you've
Hi Daniel:
On 2016年05月31日 07:16, Daniel Lezcano wrote:
> On 05/25/2016 11:50 AM, Caesar Wang wrote:
>> From: Huang Tao
>>
>> The rockchip timer is broadcast timer. Add CLOCK_EVT_FEAT_DYNIRQ
>> flag and set cpumask to all cpu to save power by avoid unnecessary
>> wakeups and IPIs.
>>
>> Signed-off-
Hi Daniel:
On 2016年05月31日 07:28, Daniel Lezcano wrote:
> On 05/25/2016 11:50 AM, Caesar Wang wrote:
>> From: Huang Tao
>>
>> The CONTROL register offset is different from old SoCs.
>> For Linux driver, there are not functional changes at all.
>> Let's call it v2.
>>
>> Signed-off-by: Huang Tao
>>
On Tue, May 31, 2016 at 03:09:13PM +0200, Gerd Hoffmann wrote:
> On Di, 2016-05-31 at 15:36 +0300, Ville Syrjälä wrote:
>
> > Why store it in the fb and not eg. the plane state?
>
> Well, drm_plane_state is allocated by drm_atomic_helper_update_plane.
>
> When sticking the hotspot into the the p
Hi Rob,
On Tuesday 31 May 2016 07:05 PM, Rob Herring wrote:
On Tue, May 31, 2016 at 2:35 AM, Chanwoo Choi wrote:
The extcon-gpio.c driver can separate the kind of external connector
by using the 'extcon-id' property.
This use of DT is just broken. Come up with another way.
Can we have th
When the clk_get() of "uart" clock returns EPROBE_DEFER, the next re-probe
finishes with success but uses invalid (ERR_PTR) values. This leads to
dereferencing of ERR_PTR stored under ourport->clk:
12c3.serial: Controller clock not found
(...)
12c3.serial: ttySAC3
From: Thomas Graziadei
The user notices the problem in a raw and real time drift, calling
clock_gettime with CLOCK_REALTIME / CLOCK_MONOTONIC_RAW on a system
with no ntp correction taking place (no ntpd or ptp stuff running).
The problem is, that old_vsyscall_fixup adds an extra 1ns even though
On non-DeviceTree platforms, the index of serial device is a static
variable incremented on each probe. It is incremented even if deferred
probe happens when getting the clock in s3c24xx_serial_init_port().
This index is used for referencing elements of statically allocated
s3c24xx_serial_ports a
On 05/30/2016 02:49 PM, Crestez Dan Leonard wrote:
> On 05/29/2016 10:48 PM, Jonathan Cameron wrote:
>> On 23/05/16 19:40, Crestez Dan Leonard wrote:
>>> The trigger name is documented as unique but drivers are currently
>>> allowed to register triggers with duplicate names. This should be
>>> cons
On 05/31/2016 03:46 PM, Huang, Tao wrote:
Hi Daniel:
On 2016年05月31日 07:28, Daniel Lezcano wrote:
On 05/25/2016 11:50 AM, Caesar Wang wrote:
From: Huang Tao
The CONTROL register offset is different from old SoCs.
For Linux driver, there are not functional changes at all.
Let's call it v2.
Sig
On 05/23/2016 08:39 PM, Crestez Dan Leonard wrote:
> This allows controlling the current trigger by numeric ID rather than
> name.
This is most certainly the far better interface, but so far we've tried to
have only one way to do a certain task with the IIO userspace ABI and try to
live with our m
On Tue, May 31, 2016 at 02:52:52PM +0100, Will Deacon wrote:
> The only thing I'm uncertain of is whether or not PTRACE_SEIZE/PTRACE_LISTEN
> allow switching to the child (but even then, how is the parent doing
> to issue such a request?).
I can't see how that would be possible - the parent needs
Remove __init annotation from all of console->setup implementations
because:
1. The pointer to it is stored in a struct console which is not
marked with __initdata.
2. It is referenced by register_console() from kernel which is not
marked with __init.
Signed-off-by: Krzysztof Kozlowski
---
On Tue, May 31, 2016 at 04:19:31PM +0200, Krzysztof Kozlowski wrote:
> Remove __init annotation from all of console->setup implementations
> because:
> 1. The pointer to it is stored in a struct console which is not
>marked with __initdata.
> 2. It is referenced by register_console() from kerne
Definition of function should start from new line.
Signed-off-by: Krzysztof Kozlowski
---
drivers/tty/serial/pnx8xxx_uart.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/tty/serial/pnx8xxx_uart.c
b/drivers/tty/serial/pnx8xxx_uart.c
index 84c4efdde8dc..9eaedd6a049
On 31 May 2016 at 15:27, Mark Brown wrote:
> On Tue, May 31, 2016 at 12:44:54PM +0200, Michal Suchanek wrote:
>> On 30 May 2016 at 17:50, Mark Brown wrote:
>> > On Mon, May 30, 2016 at 05:28:10PM +0200, Michal Suchanek wrote:
>
>> >> It's what the driver did to start with and it was requested to
From: Gustavo Padovan
Add Gustavo as maintainer for the Sync File Framework. Sumit is
co-maintainer as he maintains drivers/dma-buf/. It also uses Sumit's
tree as base.
Signed-off-by: Gustavo Padovan
Acked-by: Sumit Semwal
Acked-by: Maarten Lankhorst
---
MAINTAINERS | 11 +++
1 file
From: Gustavo Padovan
We've got a complaint saying that the description was quite obtuse and
indeed it was. This patch tries to improve it.
Cc: Dave Jones
Signed-off-by: Gustavo Padovan
---
drivers/dma-buf/Kconfig | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --
Hi Rob,
On Tue, May 31, 2016 at 10:35 PM, Rob Herring wrote:
> On Tue, May 31, 2016 at 2:35 AM, Chanwoo Choi wrote:
>> Hi Rob,
>>
>> On 2016년 05월 31일 15:44, Chanwoo Choi wrote:
>>> On 2016년 05월 28일 00:29, Rob Herring wrote:
On Thu, May 26, 2016 at 05:17:45PM +0530, Venkat Reddy Talla wrote:
On 05/31/2016 04:21 PM, Russell King - ARM Linux wrote:
> On Tue, May 31, 2016 at 04:19:31PM +0200, Krzysztof Kozlowski wrote:
>> Remove __init annotation from all of console->setup implementations
>> because:
>> 1. The pointer to it is stored in a struct console which is not
>>marked with __in
On Tue, May 31, 2016 at 09:39:19PM +0800, Yakir Yang wrote:
> EDP PSR function is interesting in vblank enable or disable event,
> so it would be great introduce a way to notify encoder about this
> event.
>
> Signed-off-by: Yakir Yang
notifiers considered evil, especially if you add a global no
Hi Lv...
I was dead in the water before this patch, qemu-kvm would crash
right away, now everything seems to work great again, thanks! From
my perspective this fixes the c3bc26d problem.
Acked-by: Mike Marshall
-Mike
On Tue, May 31, 2016 at 3:13 AM, Zheng, Lv wrote:
> Hi, Boris and Mike
>
> P
The value assigned to ret will be overwritten before it could be read in a
future iteration of the loop. Removing the unnecessary assignment.
Signed-off-by: Luis de Bethencourt
---
drivers/staging/gdm724x/gdm_usb.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drive
On Tue, May 31, 2016 at 09:37:36PM +0800, Yakir Yang wrote:
> The full name of PSR is Panel Self Refresh, panel device could refresh
> itself with the hardware framebuffer in panel, this would make a lots
> of sense to save the power consumption.
>
> For example, when desktop haven't change the co
Hi Lv,
On Tue, May 31, 2016 at 4:55 AM, Zheng, Lv wrote:
> Hi,
>
>> From: Benjamin Tissoires [mailto:benjamin.tissoi...@gmail.com]
>> Subject: Re: [PATCH v2 3/3] ACPI / button: Send "open" state after
>> boot/resume
>>
>> On Fri, May 27, 2016 at 9:16 AM, Lv Zheng wrote:
[snipped
]>> As Valdis re
601 - 700 of 1013 matches
Mail list logo
