The 100c08 scratch page is mapped using dma_map_page() before the TTM
layer has had a chance to set the DMA mask. This means we are still
running with the default of 32 when this code executes, and this causes
problems for platforms with no memory below 4 GB (such as AMD Seattle)
So move the dma_m
On 06/20/2016 02:30 PM, Ricardo Ribalda Delgado wrote:
According to the doc, V4L2_BUF_FLAG_DONE is cleared after DQBUF:
V4L2_BUF_FLAG_DONE 0x0004 ... After calling the VIDIOC_QBUF or
VIDIOC_DQBUF it is always cleared ...
Unfortunately, it seems that videobuf2 keeps it set after DQBUF. This
On 06/20/2016 10:28 AM, Andy Yan wrote:
> Hi Krzysztof:
>
> On 2016年06月20日 16:09, Krzysztof Kozlowski wrote:
>> On 06/20/2016 08:38 AM, Andy Yan wrote:
>>> This driver parses the reboot commands like "reboot bootloader"
>>> and "reboot recovery" to get a boot mode described in the
>>> device tree
Hi,
this is the v5 version of the patchse. Previous version was posted
http://lkml.kernel.org/r/1465473137-22531-1-git-send-email-mho...@kernel.org
There was one issue fixed in patch 7. Other than that we have discussed
nommu situation after patch 7 which might reintroduce a theoretical
race condit
After all the code refactoring, vb2_internal_dqbuf is only called by
vb2_dqbuf.
Since the function it is very simple, there is no need to have two
functions.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/videobuf2-v4l2.c | 27 +++
1 file changed, 11
From: Michal Hocko
Currently oom_kill_process skips both the oom reaper and SIG_KILL if a
process sharing the same mm is unkillable via OOM_ADJUST_MIN. After "mm,
oom_adj: make sure processes sharing mm have same view of oom_score_adj"
all such processes are sharing the same value so we shouldn't
The comment was referencing the wrong function.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/videobuf2-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/v4l2-core/videobuf2-core.c
b/drivers/media/v4l2-core/videobuf2-core.c
index 633fc
After all the code refactoring, vb2_internal_dqbuf is only called by
vb2_dqbuf.
Since the function it is very simple, there is no need to have
two functions.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/videobuf2-v4l2.c | 14 +-
1 file changed, 5 insertions(+),
From: Michal Hocko
Oleg has pointed out that can simplify both oom_adj_{read,write}
and oom_score_adj_{read,write} even further and drop the sighand
lock. The main purpose of the lock was to protect p->signal from
going away but this will not happen since ea6d290ca34c ("signals:
make task_struct-
From: Michal Hocko
The only case where the oom_reaper is not triggered for the oom victim
is when it shares the memory with a kernel thread (aka use_mm) or with
the global init. After "mm, oom: skip vforked tasks from being selected"
the victim cannot be a vforked task of the global init so we ar
From: Michal Hocko
oom_score_adj is shared for the thread groups (via struct signal) but
this is not sufficient to cover processes sharing mm (CLONE_VM without
CLONE_SIGHAND) and so we can easily end up in a situation when some
processes update their oom_score_adj and confuse the oom killer. In t
From: Michal Hocko
vforked tasks are not really sitting on any memory. They are sharing
the mm with parent until they exec into a new code. Until then it is
just pinning the address space. OOM killer will kill the vforked task
along with its parent but we still can end up selecting vforked task
w
From: Michal Hocko
oom_reaper relies on the mmap_sem for read to do its job. Many places
which might block readers have been converted to use down_write_killable
and that has reduced chances of the contention a lot. Some paths where
the mmap_sem is held for write can take other locks and they mig
From: Michal Hocko
0-day robot has encountered the following:
[ 82.694232] Out of memory: Kill process 3914 (trinity-c0) score 167 or
sacrifice child
[ 82.695110] Killed process 3914 (trinity-c0) total-vm:55864kB,
anon-rss:1512kB, file-rss:1088kB, shmem-rss:25616kB
[ 82.706724] oom_reaper
From: Michal Hocko
task_will_free_mem is rather weak. It doesn't really tell whether
the task has chance to drop its mm. 98748bd72200 ("oom: consider
multi-threaded tasks in task_will_free_mem") made a first step
into making it more robust for multi-threaded applications so now we
know that the w
From: Michal Hocko
both oom_adj_write and oom_score_adj_write are using task_lock,
check for task->mm and fail if it is NULL. This is not needed because
the oom_score_adj is per signal struct so we do not need mm at all.
The code has been introduced by 3d5992d2ac7d ("oom: add per-mm oom
disable c
From: Michal Hocko
Currently we have two proc interfaces to set oom_score_adj. The legacy
/proc//oom_adj and /proc//oom_score_adj which both have their
specific handlers. Big part of the logic is duplicated so extract the
common code into __set_oom_adj helper. Legacy knob still expects some
detai
On 2016-06-18 22:02, Wolfram Sang wrote:
We run the command i2cdetect for address 0x3 to 0x77. The QUP
generates
write error for address 0x3 to 0x7 apart from other bus errors since
these are reserved addresses. I was getting the crash in non DMA mode
and BAM hang in DMA mode before putting the
Hi,
Roger Quadros writes:
> diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
> index 8689dcb..ed596ec 100644
> --- a/drivers/usb/Kconfig
> +++ b/drivers/usb/Kconfig
> @@ -32,6 +32,23 @@ if USB_SUPPORT
> config USB_COMMON
> tristate
>
> +config USB_O
On Mon, Jun 20, 2016 at 02:18:38PM +0200, Richard Cochran wrote:
> Documentation/sound/alsa/timestamping.txt says:
Examples of typestamping with HDaudio:
1. DMA timestamp, no compensation for DMA+analog delay
$ ./audio_time -p --ts_type=1
Where is this "audio_time" program of which you
On Sat, Jun 18, 2016 at 02:54:23AM +0300, Yury Norov wrote:
> From: Andrew Pinski
>
> Add a separate syscall-table for ILP32, which dispatches either to native
> LP64 system call implementation or to compat-syscalls, as appropriate.
>
> Signed-off-by: Andrew Pinski
> Signed-off-by: Yury Norov
According to the doc, V4L2_BUF_FLAG_DONE is cleared after DQBUF:
V4L2_BUF_FLAG_DONE 0x0004 ... After calling the VIDIOC_QBUF or
VIDIOC_DQBUF it is always cleared ...
Unfortunately, it seems that videobuf2 keeps it set after DQBUF. This
can be tested with vivid and dev_debug:
[257604.338082]
On Sun, Jun 19, 2016 at 7:40 PM, Sasha Levin wrote:
> On 06/19/2016 03:24 AM, Alexander Potapenko wrote:
>> Hi Sasha,
>>
>> This commit delays the reuse of memory after it has been freed, so
>> it's intended to help people find more use-after-free errors.
>
> Is there a way to tell if the use-afte
Hi Philipp,
On Mon, 20 Jun 2016 14:05:54 +0200
Philipp Zabel wrote:
> Am Sonntag, den 19.06.2016, 14:06 +0200 schrieb Boris Brezillon:
> > +Philipp
> >
> > On Sun, 19 Jun 2016 19:37:39 +0800
> > Icenowy Zheng wrote:
> >
> > > The NAND controller on some sun8i chips needs its reset line to b
After all the code refactoring, vb2_internal_dqbuf is only called by
vb2_dqbuf.
Since the function it is very simple, there is no need to have
two functions.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/videobuf2-v4l2.c | 14 +-
1 file changed, 5 insertions(+),
On Fri 17-06-16 13:00:41, Andy Lutomirski wrote:
> We should account for stacks regardless of stack size. Move it into
> account_kernel_stack.
>
> Fixes: 12580e4b54ba8 ("mm: memcontrol: report kernel stack usage in cgroup2
> memory.stat")
> Cc: Vladimir Davydov
> Cc: Johannes Weiner
> Cc: Mich
On Mon, Jun 6, 2016 at 4:51 PM, Vlastimil Babka wrote:
> On 05/26/2016 04:37 AM, js1...@gmail.com wrote:
>>
>> From: Joonsoo Kim
>>
>> Currently, we store each page's allocation stacktrace on corresponding
>> page_ext structure and it requires a lot of memory. This causes the
>> problem
>> that m
According to the doc, V4L2_BUF_FLAG_DONE is cleared after DQBUF:
V4L2_BUF_FLAG_DONE 0x0004 ... After calling the VIDIOC_QBUF or
VIDIOC_DQBUF it is always cleared ...
Unfortunately, it seems that videobuf2 keeps it set after DQBUF. This
can be tested with vivid and dev_debug:
[257604.338082]
A couple more changes to "plx9080.h" for easier extraction of fields
from register values, and macro naming consistency.
1) staging: comedi: plx9080.h: define PLX__TO_(r) macros
2) staging: comedi: plx9080.h: rename some macros for consistency
drivers/staging/comedi/drivers/cb_pcidas64.c | 4 +-
On Tuesday 14 June 2016 04:34 AM, Douglas Anderson wrote:
> Previous PHY code waited a fixed amount of time for the DLL to lock at
> power on time. Unfortunately, the time for the DLL to lock is actually
> a bit more dynamic and can be longer if the card clock is slower.
>
> Instead of waiting
On Mon, Jun 20, 2016 at 05:48:15PM +0800, Wei Hu (Xavier) wrote:
>
>
> On 2016/6/20 17:27, Leon Romanovsky wrote:
> >On Mon, Jun 20, 2016 at 03:49:24PM +0800, Wei Hu (Xavier) wrote:
> >>
> >>On 2016/6/20 14:06, Leon Romanovsky wrote:
> >>>On Mon, Jun 20, 2016 at 12:37:40PM +0800, Wei Hu (Xavier)
After all the code refactoring, vb2_internal_dqbuf is only called by
vb2_dqbuf.
Since the function it is very simple, there is no need to have two
functions.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/videobuf2-v4l2.c | 39 ++--
1 file changed
The comment was referencing the wrong function.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/videobuf2-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/v4l2-core/videobuf2-core.c
b/drivers/media/v4l2-core/videobuf2-core.c
index 633fc
On Tuesday 14 June 2016 04:34 AM, Douglas Anderson wrote:
> As of an earlier change in this series ("Documentation: mmc:
> sdhci-of-arasan: Add ability to export card clock") the SDHCI driver
> used on Rockchip SoCs can now expose its clock. Let's now specify that
> the PHY can use it.
>
> Lett
Various macros in "plx9080.h" take the form `PLX__(x)`,
where `` is a register name, `` is a field within the
register, and `x` is a value for the field specified by the caller. The
macros construct a partial register register with the specified field
value placed in the appropriate bits of the re
On Tuesday 14 June 2016 04:34 AM, Douglas Anderson wrote:
> The "phyctrl_frqsel" is described in the Arasan datasheet [1] as "the
> frequency range of DLL operation". Although the Rockchip variant of
> this PHY has different ranges than the reference Arasan PHY it appears
> as if the functionali
On Thu, Jun 16, 2016 at 09:53:29AM -0400, Yendapally Reddy Dhananjaya Reddy
wrote:
> Renames the dt bindings document of Broadcom STB ahci driver to
> common Broadcom ahci driver bindings document
>
> Signed-off-by: Yendapally Reddy Dhananjaya Reddy
>
> ---
> .../bindings/ata/{brcm,sata-brcmst
On Thu, Jun 16, 2016 at 08:40:58PM +0800, Xing Zheng wrote:
> Because we need to support the multiple codecs (MAX98357A/RT5514/DA7219)
> on the RK3399 GRU boards, this patch can help us to support these codecs.
>
> Signed-off-by: Xing Zheng
> ---
>
> Changes in v6:
> - remove enable/disable dapm
Most of the macros in "plx9080.h" that define register values are
single-bits flags of the form `PLX__`, or are constant,
multi-bit values of the form `PLX___`, or are
non-constant, function-like macros of the form `PLX__(x)`.
Some of the macros for constant, multi-bit values do not currently
fit t
On Friday 13 May 2016 04:13 AM, Brian Norris wrote:
> From: Shawn Lin
>
> Signal integrity analysis has suggested we set these values. Do this in
> power_on(), so that they get reconfigured after suspend/resume.
>
> Signed-off-by: Shawn Lin
> Signed-off-by: Brian Norris
Acked-by: Kishon Vij
On Friday 13 May 2016 04:13 AM, Brian Norris wrote:
> From: Shawn Lin
>
> According to the databook, 10.2us is the max time for dll to be ready to
> work. However in testing, some chips need 20us for dll to be ready. This
> patch adds some extra margin for dllrdy to be ready, fixing our
> -ETIM
On Friday 13 May 2016 04:13 AM, Brian Norris wrote:
> Some of the spacing was wrong (spaces instead of tabs), and due to
> longer entries added later, the columns weren't aligned. Let's get
> everything consistent.
>
> Signed-off-by: Brian Norris
Acked-by: Kishon Vijay Abraham I
> ---
> driv
On Friday 13 May 2016 04:13 AM, Brian Norris wrote:
> The output tap delay controls helps maintain the hold requirements for
> eMMC. The exact value is dependent on the SoC and other factors, though
> it isn't really an exact science. But the default of 0 is not very good,
> as it doesn't give th
On Mon, Jun 20, 2016 at 03:39:43PM +0900, Joonsoo Kim wrote:
> CCing Paul to ask some question.
>
> On Wed, Jun 15, 2016 at 10:39:47AM +0200, Geert Uytterhoeven wrote:
> > Hi Joonsoo,
> >
> > On Wed, Jun 15, 2016 at 4:23 AM, Joonsoo Kim wrote:
> > > On Tue, Jun 14, 2016 at 12:45:14PM +0200, Geer
On Tuesday 14 June 2016 04:34 AM, Douglas Anderson wrote:
> There's no reason to store the return value of rockchip_emmc_phy_power()
> in a variable nor to check it. Just return it.
>
> Signed-off-by: Douglas Anderson
Acked-by: Kishon Vijay Abraham I
> ---
> Changes in v2:
> - Move code clea
On Fri 17-06-16 13:00:40, Andy Lutomirski wrote:
> Currently, NR_KERNEL_STACK tracks the number of kernel stacks in a
> zone. This only makes sense if each kernel stack exists entirely in
> one zone, and allowing vmapped stacks could break this assumption.
>
> Since frv has THREAD_SIZE < PAGE_SIZ
On Thu, Jun 16, 2016 at 09:53:31AM -0400, Yendapally Reddy Dhananjaya Reddy
wrote:
> Add documentation for SATA PHY available in Broadcom's
> NSP SoC.
>
> Signed-off-by: Yendapally Reddy Dhananjaya Reddy
>
> ---
> Documentation/devicetree/bindings/phy/brcm-sata-phy.txt | 4 +++-
> 1 file chang
Hi Amit,
On Mon, Jun 20, 2016 at 05:46:36PM +0530, Amit Kucheria wrote:
> The Hisilicon clock stub driver is needed to allow the thermal drivers to
> actually scale the frequency. Make it an automatic dependency.
>
> Signed-off-by: Amit Kucheria
> ---
> drivers/thermal/Kconfig | 1 +
> 1 file c
On Thu, Jun 16, 2016 at 04:40:32PM -0700, Hoan Tran wrote:
> Add fractional scale clock DTS binding.
We've generally decided against putting this level of clock details into
DT.
>
> Signed-off-by: Hoan Tran
> Signed-off-by: Loc Ho
> ---
> .../bindings/clock/fractional-scale-clock.txt |
On Fri, Jun 17, 2016 at 03:00:20PM +1000, Chris Lapa wrote:
> From: Chris Lapa
>
> Signed-off-by: Chris Lapa
> ---
> .../devicetree/bindings/power/max8903-charger.txt | 25
> ++
> 1 file changed, 25 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/p
Commit-ID: 8974189222159154c55f24ddad33e3613960521a
Gitweb: http://git.kernel.org/tip/8974189222159154c55f24ddad33e3613960521a
Author: Peter Zijlstra
AuthorDate: Thu, 16 Jun 2016 10:50:40 +0200
Committer: Ingo Molnar
CommitDate: Mon, 20 Jun 2016 11:29:09 +0200
sched/fair: Fix cfs_rq av
On 2016-05-23 17:18, Julia Lawall wrote:
>
>
> On Mon, 23 May 2016, Yann Droneaud wrote:
>
>> Since commit 3ef0e5ba4673 ('slab: introduce kzfree()'),
>> kfree() is no more the only function to be considered:
>> kzfree() should be recognized too.
>>
>> In particular, kzfree() must not be called o
From: David Hildenbrand
Let's introduce that helper.
Signed-off-by: David Hildenbrand
Signed-off-by: Christian Borntraeger
---
include/linux/page_ref.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/include/linux/page_ref.h b/include/linux/page_ref.h
index 8b5e0a9..610e132 10064
It looks like this patch was totally forgotten?
I don't see it in neither vfs nor nfs trees and yet it fixes a very easy to
cause
crash in nfs code. And I think it's unrelated to the other parallel case too.
On Jun 3, 2016, at 1:56 AM, Al Viro wrote:
> On Fri, Jun 03, 2016 at 12:58:10AM -0400, O
On 06/20/2016 02:12 AM, Pali Rohár wrote:
On Sunday 19 June 2016 00:39:47 Pali Rohár wrote:
On Saturday 18 June 2016 18:54:58 Guenter Roeck wrote:
On 06/18/2016 08:26 AM, Pali Rohár wrote:
On Saturday 18 June 2016 17:13:59 Guenter Roeck wrote:
On 06/17/2016 03:54 PM, Pali Rohár wrote:
I'm se
On Fri, Jun 17, 2016 at 04:57:14PM +0800, Songjun Wu wrote:
> DT binding documentation for ISC driver.
>
> Signed-off-by: Songjun Wu
> ---
>
> Changes in v5:
> - Add clock names.
>
> Changes in v4:
> - Remove the isc clock nodes.
>
> Changes in v3:
> - Remove the 'atmel,sensor-preferred'.
> -
A trivial cosmetic change: interrupt.h header is redundant since
'commit 6b898c07cb1d ("console: use might_sleep in console_lock")'.
Signed-off-by: Sergey Senozhatsky
---
kernel/printk/printk.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
ind
On Thu, Jun 16, 2016 at 09:53:30AM -0400, Yendapally Reddy Dhananjaya Reddy
wrote:
> Add support for Broadcom NSP SoC ahci
>
> Signed-off-by: Yendapally Reddy Dhananjaya Reddy
>
> ---
> Documentation/devicetree/bindings/ata/brcm,sata-brcm.txt | 1 +
> 1 file changed, 1 insertion(+)
Acked-by:
Hi,
On Fri 17-06-16 12:04:05, Tejun Heo wrote:
> 43d1c0eb7e11 ("block: detach bdev inode from its wb in
> __blkdev_put()") detached bdev inode from its wb as the bdev inode may
> outlive the underlying bdi and thus the wb. This is accomplished by
> invoking inode_detach_wb() from __blkdev_put();
On Thu, Jun 16, 2016 at 10:35:14PM +0800, Lijun Ou wrote:
> This patch added the operation for cmd, and added some functions
> for initializing eq table and selecting cmd mode.
>
> Signed-off-by: Wei Hu
> Signed-off-by: Nenglong Zhao
> Signed-off-by: Lijun Ou
> ---
> PATCH v9/v8/v7/v6:
> - No c
On 06/17/2016 06:34 PM, Dan Williams wrote:
diff --git a/arch/um/drivers/ubd_kern.c b/arch/um/drivers/ubd_kern.c
index ef6b4d960bad..4e7cb5df8e43 100644
--- a/arch/um/drivers/ubd_kern.c
+++ b/arch/um/drivers/ubd_kern.c
@@ -823,12 +823,11 @@ static int ubd_disk_register(int major, u64 size, int
u
On Fri 17-06-16 13:00:42, Andy Lutomirski wrote:
> If CONFIG_VMAP_STACK is selected, kernel stacks are allocated with
> vmalloc_node.
I like this! It also reduces demand for higher order (order-2) pages
considerably which is a great plus on its own. I would be little bit
worried about the performa
Hi Tomasz,
On Saturday, June 18, 2016 11:40:05 PM Tomasz Figa wrote:
> Hi Bartlomiej,
>
> 2016-05-24 22:19 GMT+09:00 Bartlomiej Zolnierkiewicz
> :
> > Open-code samsung_cmu_register_one() calls for CMU_APOLLO and
> > CMU_ATLAS setup code as a preparation for adding CPU clocks
> > support for Ex
The Wandboard Quad comes with a SATA port. Enable the IMX SATA driver by
default to make it easy to have the root filesystem on it.
Signed-off-by: Tuomas Tynkkynen
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/a
On 06/17/2016 06:34 PM, Dan Williams wrote:
In preparation for removing the ->driverfs_dev member of a gendisk, add
an api that takes the parent device as a parameter to add_disk(). For
now this maintains the status quo of WARN()ing on failure, but not
return a error code.
Reviewed-by: Bart Va
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/next
head: b4aa201e0c7c73a9f4fee7d82d4ff46b85feeea9
commit: b4aa201e0c7c73a9f4fee7d82d4ff46b85feeea9 [16/16] torture: Convert
torture_shutdown() to hrtimer
config: arm-allyesconfig (attached as .config)
compiler:
On 06/20/2016 02:22 PM, Christoph Hellwig wrote:
On Thu, Jun 16, 2016 at 05:39:07PM +0200, Bart Van Assche wrote:
On 06/16/2016 05:20 PM, Christoph Hellwig wrote:
On Wed, Jun 15, 2016 at 09:36:54PM +0200, Bart Van Assche wrote:
My concern
is that I doubt that there is an interrupt assignment s
On Mon, Jun 20, 2016 at 3:31 PM, Jan Kara wrote:
> Hi,
>
> On Fri 17-06-16 12:04:05, Tejun Heo wrote:
>> 43d1c0eb7e11 ("block: detach bdev inode from its wb in
>> __blkdev_put()") detached bdev inode from its wb as the bdev inode may
>> outlive the underlying bdi and thus the wb. This is accompli
On Mon, 20 Jun 2016 09:46:02 +0900
Namhyung Kim wrote:
> Hi Steve,
>
> On Sun, May 22, 2016 at 04:28:49PM -0400, Steven Rostedt wrote:
> > From: Steven Rostedt
> >
> > Matt Fleming reported seeing crashes when enabling and disabling
> > function profiling which uses function graph tracer. Late
When clock providers are added to the device tree after of_clk_init is called
they are not added to the clock provider list. This makes that drivers such
as i2c-xiic.c fail to init, as they may depend on the unadded clock provider.
We first introduce a new function clk.c that will check if a devic
of_clk_is_provider() checks if a device_node has already been added to
the clk provider list. This can be used to avoid adding the same clock
provider twice.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/clk/clk.c| 20
include/linux/clk-provider.h | 5 +
Adds support for fixed-factor clock providers which have not been
enabled via of_clk_init().
This is required by Device trees overlays that introduce clocks
providers.
Signed-off-by: Ricardo Ribalda Delgado
---
v2: Changes proposed by: Stephen Boyd
-Add error check
-CodeStyle on of_device_ide
-
Adds support for fixed-rate clock providers which have not been
enabled via of_clk_init().
This is required by Device trees overlays that introduce clocks
providers.
Signed-off-by: Ricardo Ribalda Delgado
---
v2: Changes proposed by: Stephen Boyd
-Add error check
-CodeStyle on of_device_ide
-Us
Hello Guenter, Brian
On 06/18/2016 01:09 PM, Guenter Roeck wrote:
> On 06/17/2016 06:08 PM, Brian Norris wrote:
>> On Fri, Jun 17, 2016 at 02:41:51PM -0700, Guenter Roeck wrote:
>>> On Fri, Jun 17, 2016 at 12:58:12PM -0700, Brian Norris wrote:
+int cros_ec_cmd_xfer_status(struct cros_ec_devic
Implement two common pairing scheme (found on many MLC devices), and name
them in reference to the paired pages distance (3 or 6 pages).
Signed-off-by: Boris Brezillon
Signed-off-by: Richard Weinberger
---
drivers/mtd/nand/nand_base.c | 97
include/l
Add a new field to attach a pairing scheme to a NAND chip definition
and assign it to mtd->pairing when a full-id match is detected.
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/nand_base.c | 1 +
include/linux/mtd/nand.h | 2 ++
2 files changed, 3 insertions(+)
diff --git a/drivers/
MLC and TLC NAND devices are using NAND cells exposing more than one bit,
but instead of attaching all the bits in a given cell to a single NAND
page, each bit is usually attached to a different page. This concept is
called 'page pairing', and has significant impacts on the flash storage
usage.
The
Hi,
This series is the first step towards reliable MLC/TLC NAND support.
Those patches allows the NAND layer to expose page pairing information
to MTD users.
The plan is to teach UBI about those constraints and let UBI code take
the appropriate precautions when dealing with those multi-level cells
commit 0139aa7b7fa1 ("mm: rename _count, field of the struct page,
to _refcount") changed all accesses to page->_count to use wrappers.
There is already a page_ref_dec_return and we need for kvm/s390
code the function "page_ref_inc_return" as well.
FWIW, the code is under
https://git.kernel.org/cg
For interrupt controllers successfully initialised early via device-tree,
mark these interrupt controllers as populated so we don't unnecessarily
create a device and populate any platform data later on in the boot
sequence when we populate all the various platform devices.
Signed-off-by: Jon Hunte
On Fri, May 13, 2016 at 8:43 PM, Crestez Dan Leonard
wrote:
> As far as I can tell DRDY for ST sensors behaves as a level rather than
> edge interrupt. Registering for IRQF_TRIGGER_RISING instead of
> IRQF_TRIGGER_HIGH mostly works except when the sampling frequency is
> high enough that new samp
On Sat, Jun 18, 2016 at 04:56:17PM -0400, Brian Gerst wrote:
> Instead of setting up a fake pt_regs context, put the kernel thread
> function pointer and arg into the unused callee-restored registers
> of struct fork_frame.
>
> Signed-off-by: Brian Gerst
> ---
> arch/x86/entry/entry_32.S| 3
The Wandboard Quad can make use of the cpufreq support provided by the
driver. Enable it and its dependency, REGULATOR_ANATOP, by default.
Signed-off-by: Tuomas Tynkkynen
---
arch/arm/configs/multi_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/multi_v7_defco
On 06/17/2016 05:47 PM, Arnd Bergmann wrote:
- jiffies_to_timespec(jiffies, &v0);
- jiffies_to_timespec(lport->boot_time, &v1);
- fc_stats->seconds_since_last_reset = (v0.tv_sec - v1.tv_sec);
+ fc_stats->seconds_since_last_reset = (lport->boot_time - jiffies) / HZ;
Does
From: "Steven Rostedt (Red Hat)"
If a task uses a non constant string for the format parameter in
trace_printk(), then the trace_printk_fmt variable is set to NULL. This
variable is then saved in the __trace_printk_fmt section.
The function hold_module_trace_bprintk_format() checks to see if dup
From: "Steven Rostedt (Red Hat)"
When histograms are not configured in the kernel, the ftracetest histogram
selftests should return "unsupported" and not "Failed". To detect this, the
test scripts have:
FEATURE=`grep hist events/sched/sched_process_fork/trigger`
if [ -z "$FEATURE" ]; then
Linus,
Two fixes for the tracing system.
o When trace_printk() is used with a non constant format descriptor,
it adds a NULL pointer into the trace format section, and the code
isn't prepared to deal with it. This bug appeared by a change that
was added in v3.5.
o The ftracetest (sel
On Sat, 18 Jun 2016 08:23:23 +1000
Benjamin Herrenschmidt wrote:
> On Fri, 2016-06-17 at 17:59 -0400, Steven Rostedt wrote:
> > Sorry for the late reply, this patch got pushed down in my INBOX.
> >
> > Could I get someone from PPC to review this patch, just to be safe?
>
> The patch makes sen
On Fri, 17 Jun 2016, Eric Dumazet wrote:
> To avoid increasing probability of such events we would need to have
> at least 4 ms difference between the RTO timer and delack timer.
>
> Meaning we have to increase both of them and increase P99 latencies of
> RPC workloads.
>
> Maybe a switch to hrti
Hi Stephen
When the device tree is populated or when an overlay is added, all its
nodes have the flag OF_POPULATED set. The flag is enabled recursively
in
of_platform_bus_create->of_platform_device_create_pdata()
So we cannot use that flag to mark what is enabled and what is not.
The other issue
On 20 June 2016 at 20:07, Philipp Zabel wrote:
> Am Montag, den 20.06.2016, 11:50 +0800 schrieb Xinliang Liu:
>>
>> Required properties:
>> -- compatible: may be "hisilicon,hi6220-sysctrl"
>> +- compatible: should be one of the following:
>> + - "hisilicon,hi6220-sysctrl", "syscon" : For periphe
On Monday 20 June 2016 03:10 PM, Jiri Olsa wrote:
> On Mon, Jun 20, 2016 at 05:27:25PM +0800, Wangnan (F) wrote:
>>
>> On 2016/6/20 17:18, Jiri Olsa wrote:
>>> On Mon, Jun 20, 2016 at 02:14:01PM +0530, Madhavan Srinivasan wrote:
When decoding the perf_regs mask in regs_dump__printf(),
w
On Saturday, June 18, 2016 11:53:36 PM Tomasz Figa wrote:
> Hi Bart,
Hi Tomek,
> 2016-05-24 22:19 GMT+09:00 Bartlomiej Zolnierkiewicz
> :
> > Exynos5433 uses different register layout for CPU clock registers
> > than earlier SoCs so add new code for handling this layout. Also
> > add new CLK_C
Ping. Any comment is appreciate.
Thanks
Minfei
On 06/13/16 at 12:33P, Minfei Huang wrote:
> The variable nr_pages is always more than 1, because the size of
> structure aio_ring is bigger than 0. So remove unnecessary test for
> nr_page.
>
> Signed-off-by: Minfei Huang
> ---
> fs/aio.c | 2 --
On Mon, Jun 20, 2016 at 09:25:12AM -0400, Oleg Drokin wrote:
> It looks like this patch was totally forgotten?
> I don't see it in neither vfs nor nfs trees and yet it fixes a very easy to
> cause
> crash in nfs code. And I think it's unrelated to the other parallel case too.
I assumed it would g
On Saturday, June 18, 2016 11:57:30 PM Tomasz Figa wrote:
> Hi Bart,
Hi Tomek,
> 2016-05-24 22:19 GMT+09:00 Bartlomiej Zolnierkiewicz
> :
> > Add the CPU clocks configuration data and instantiate the CPU clocks
> > type for Exynos5433.
> >
> > Cc: Kukjin Kim
> > CC: Krzysztof Kozlowski
> > Sig
On some boards, like omap5-uevm the MCLK is gated by default and in order
to be able to use the High performance modes of twl6040 it need to be
enabled by SW.
Add support for handling the MCLK source clock via CCF.
At the same time lower the print priority of the notification that the 32K
clock is
Hi Dave,
This pull request contains 2 patches adding support for the sii902x
bridge.
Regards,
Boris
The following changes since commit a0877f52035280370707bdefeddc6faa6478b892:
Merge tag 'topic/drm-misc-2016-06-15' of
git://anongit.freedesktop.org/drm-intel into drm-next (2016-06-16 05:49:3
Hi Shawn,
[…]
>>> +
>>> +static int mmc_stop_auto_bkops(struct mmc_card *card)
>>> +{
>>> + int err = 0;
>>> +
>>> + if (!card->ext_csd.auto_bkops_en)
>>> + return 0;
>>> +
>>
>> Shouldn’t the BKOPS_STATUS be checked prior to disabling the BKOPS activity
>> of the device?
>>
>
>Hrm
This patchset contains the pwm support for the Broadcom's iProc SoC's.
The first patch provides the documentation details and the
second patch contains the controller support details. The third patch
contains the enable method for Northstar Plus SoC.
This patch series has been tested on NSP bcm95
301 - 400 of 1165 matches
Mail list logo
