> >> Adding to Ezequiel's point, shouldn't we take more granular lock
> >> (devfreq->lock) first and then call devfreq_list_lock at the time of
> >> adding to the list?
> >>
> >
> > Not sure why we should do that. devfreq->lock should be used to
> > protect the struct devfreq state, while the dev
On 2018-07-03 14:04, Lukas Wunner wrote:
On Mon, Jul 02, 2018 at 06:52:47PM -0400, Sinan Kaya wrote:
If a bridge supports hotplug and observes a PCIe fatal error, the
following
events happen:
1. AER driver removes the devices from PCI tree on fatal error
2. AER driver brings down the link by i
> and today when I tried it on next-20180620 I saw 8 errors at TX.
> >
> >> I couldn't reproduce in my local machine using 4.17-rc6.
> >> How do I checkin the "next-20180613" source code?
> >
> > You can find the source code here [1], and I would look i
On Mon, Jul 02, 2018 at 04:44:33PM -0700, Kevin Hilman wrote:
> Hi Sudeep,
>
> On Wed, May 9, 2018 at 9:02 AM Sudeep Holla wrote:
> >
> > Checking the equality of cpumask for both new and old tick device doesn't
> > ensure that it's CPU local device. This will cause issue if a low rating
> > cloc
>@@ -988,12 +1030,13 @@ static ssize_t governor_store(struct device *dev,
>struct device_attribute *attr,
> if (ret != 1)
> return -EINVAL;
>
>- mutex_lock(&devfreq_list_lock);
>- governor = find_devfreq_governor(str_governor);
>+ governor = try_then_request_gov
Hi Michal
cpuset_print_current_mems_allowed is also invoked by
warn_alloc(page_alloc.c). So, can I remove the current->comm output in
the pr_info ?
diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
index d8b12e0d39cd..09b8ef6186c6 100644
--- a/kernel/cgroup/cpuset.c
+++ b/kernel/cgroup/
在 2018年07月03日 10:17, lijiang 写道:
> 在 2018年07月02日 18:14, Borislav Petkov 写道:
>> On Mon, Jul 02, 2018 at 03:26:35PM +0800, Lianbo Jiang wrote:
>>> @@ -131,7 +132,8 @@ static void __ioremap_check_mem(resource_size_t addr,
>>> unsigned long size,
>>> * caller shouldn't need to know that small detail
On Tue, Jul 03, 2018 at 01:03:48PM +0300, Alexander Shishkin wrote:
> On Mon, Jul 02, 2018 at 04:33:29PM -0600, Mathieu Poirier wrote:
> > +/*
> > + * PMU driver configuration works the same way as filter management above,
> > + * but without the need to deal with memory mapping. Driver configurat
On Tue, Jul 03, 2018 at 10:59:48AM +0200, Thomas Gleixner wrote:
> On Tue, 3 Jul 2018, Kirill A. Shutemov wrote:
>
> > On Mon, Jul 02, 2018 at 07:01:28PM +, Benjamin Gilbert wrote:
> > > On Mon, Jul 02, 2018 at 12:34:50PM +0300, Kirill A. Shutemov wrote:
> > > > Could you check if you can trig
On Tue, 2018-07-03 at 18:17 +0800, Yixun Lan wrote:
> I'm seeing you already applied this patch, so would you like to
> fix/amend the patch for me, or want me send another patch version?
>
> thanks
It means that I amended your patch before applying it.
On Tue 03-07-18 18:57:14, 禹舟键 wrote:
> Hi Michal
> cpuset_print_current_mems_allowed is also invoked by
> warn_alloc(page_alloc.c). So, can I remove the current->comm output in
> the pr_info ?
>
> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
> index d8b12e0d39cd..09b8ef6186c6 10064
Hi Anson,
On Tue, Jul 3, 2018 at 4:44 AM, Anson Huang wrote:
> It is NOT easy to identify which switch is critical or NOT, and different
> platforms
> have different board design, it will introduce many platform specified code,
> so I think
> just revert the pfuze100 switch enable/disable patc
Commit-ID: dbd0fbc76c77daac08ddd245afdcbade0d506e19
Gitweb: https://git.kernel.org/tip/dbd0fbc76c77daac08ddd245afdcbade0d506e19
Author: Andy Shevchenko
AuthorDate: Fri, 29 Jun 2018 22:31:10 +0300
Committer: Thomas Gleixner
CommitDate: Tue, 3 Jul 2018 13:08:19 +0200
x86/tsc: Add missing
Commit-ID: e2ce67b2b34b6e9d77da2f375dba5b525508f7df
Gitweb: https://git.kernel.org/tip/e2ce67b2b34b6e9d77da2f375dba5b525508f7df
Author: Andy Shevchenko
AuthorDate: Fri, 29 Jun 2018 22:31:08 +0300
Committer: Thomas Gleixner
CommitDate: Tue, 3 Jul 2018 13:08:20 +0200
x86/cpu: Introduce I
Commit-ID: 397d3ad18dc431456baf8bce96606fa1d18b30b0
Gitweb: https://git.kernel.org/tip/397d3ad18dc431456baf8bce96606fa1d18b30b0
Author: Andy Shevchenko
AuthorDate: Fri, 29 Jun 2018 22:31:09 +0300
Committer: Thomas Gleixner
CommitDate: Tue, 3 Jul 2018 13:08:20 +0200
x86/tsc: Convert to
Commit-ID: 5067b087cf5b2fa4de00443cdc6a66acb28a4953
Gitweb: https://git.kernel.org/tip/5067b087cf5b2fa4de00443cdc6a66acb28a4953
Author: Andy Shevchenko
AuthorDate: Fri, 29 Jun 2018 22:31:11 +0300
Committer: Thomas Gleixner
CommitDate: Tue, 3 Jul 2018 13:08:20 +0200
x86/tsc: Use SPDX id
-邮件原件-
发件人: Theodore Y. Ts'o [mailto:ty...@mit.edu]
发送时间: 2018年7月3日 18:36
收件人: Gaoming (ming, consumer BG)
抄送: linux-e...@vger.kernel.org; linux-kernel@vger.kernel.org; Liqingchao
(sorp); Shenchen (harry); miaoxie (A); yangfei (D); Renlipeng (OS driver)
主题: Re: 答复: 答复: 答复: 答复: 答复: 答复: [
Hi Uffe,
On 02.07.2018 17:37, Ulf Hansson wrote:
> On 28 June 2018 at 10:45, Laurentiu Tudor wrote:
>> SDHCI controller in ls1043a and ls1046a generate 40-bit wide addresses
>> when doing DMA. Make sure that the corresponding dma mask is correctly
>> configured.
>>
>> Signed-off-by: Laurentiu Tud
Commit-ID: d99e5da91b36db5c35ddaf3653b280ee060971da
Gitweb: https://git.kernel.org/tip/d99e5da91b36db5c35ddaf3653b280ee060971da
Author: Andy Shevchenko
AuthorDate: Fri, 29 Jun 2018 22:31:12 +0300
Committer: Thomas Gleixner
CommitDate: Tue, 3 Jul 2018 13:08:21 +0200
x86/platform/intel-m
Commit-ID: 41afb1dfad4d6af0c716746f6a15f3230482955c
Gitweb: https://git.kernel.org/tip/41afb1dfad4d6af0c716746f6a15f3230482955c
Author: Andy Shevchenko
AuthorDate: Fri, 29 Jun 2018 22:31:13 +0300
Committer: Thomas Gleixner
CommitDate: Tue, 3 Jul 2018 13:08:21 +0200
x86/platform/intel-m
On Mon, Jun 25, 2018 at 11:27:37PM +0530, Souptick Joarder wrote:
> Use new return type vm_fault_t for both fault handler
> vdso_fault() and vvar_fault(). Previously vm_insert_pfn()
> returns err which has to mapped into VM_FAULT_* type.
> The new function vmf_insert_pfn() will replace this
> ineff
Remove the unused is_ima_appraise_enabled() function.
Signed-off-by: Stefan Berger
---
include/linux/ima.h | 6 --
security/integrity/ima/ima_appraise.c | 10 --
2 files changed, 16 deletions(-)
diff --git a/include/linux/ima.h b/include/linux/ima.h
index 0e4647e0
2018-07-01 23:32 GMT+02:00 Benjamin Gilbert :
> On Sun, Jul 01, 2018 at 05:15:59PM -0400, Benjamin Gilbert wrote:
>> 4.17 kernels built with the CoreOS Container Linux toolchain and kconfig,
>> up to and including 4.17.3, fail to boot on AMD64 running in (at least)
>> QEMU/KVM. No messages are sho
在 2018年07月03日 17:39, Borislav Petkov 写道:
> On Tue, Jul 03, 2018 at 10:17:19AM +0800, lijiang wrote:
>> for example, the elfcorehdr. In fact, the elfcorehdr and notes
>
> You mean this?
>
> ssize_t __weak elfcorehdr_read_notes(char *buf, size_t count, u64 *ppos)
> {
> - return read_from_ol
On Thu, Jun 07, 2018 at 12:31:47AM +0300, Tomas Winkler wrote:
> From: Alexander Usyskin
>
> MEI_IAMTHIF_STALL_TIMER is unused now and can be safely removed.
>
> Signed-off-by: Alexander Usyskin
> Signed-off-by: Tomas Winkler
> ---
> drivers/misc/mei/hw.h | 2 --
> 1 file changed, 2 deletions
I'm announcing the release of the 3.18.114 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be browsed at the normal kernel.org git web browser
diff --git a/Makefile b/Makefile
index ce40d7cd062e..2288ed3b8674 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 18
-SUBLEVEL = 113
+SUBLEVEL = 114
EXTRAVERSION =
NAME = Diseased Newt
@@ -214,7 +214,6 @@ VPATH := $(srctree)$(if
$(KBUILD_EXTMOD),:$
diff --git a/Documentation/printk-formats.txt b/Documentation/printk-formats.txt
index b784c270105f..ed6f6abaad57 100644
--- a/Documentation/printk-formats.txt
+++ b/Documentation/printk-formats.txt
@@ -273,11 +273,10 @@ struct clk:
%pC pll1
%pCnpll1
- %pCr156000
I'm announcing the release of the 4.4.139 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
>
> On Thu, Jun 07, 2018 at 12:31:47AM +0300, Tomas Winkler wrote:
> > From: Alexander Usyskin
> >
> > MEI_IAMTHIF_STALL_TIMER is unused now and can be safely removed.
> >
> > Signed-off-by: Alexander Usyskin
> > Signed-off-by: Tomas Winkler
> > ---
> > drivers/misc/mei/hw.h | 2 --
> > 1 fi
On 2018-07-03 04:34, Lukas Wunner wrote:
On Mon, Jul 02, 2018 at 06:52:47PM -0400, Sinan Kaya wrote:
If a bridge supports hotplug and observes a PCIe fatal error, the
following
events happen:
1. AER driver removes the devices from PCI tree on fatal error
2. AER driver brings down the link by i
I'm announcing the release of the 4.9.111 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/printk-formats.txt b/Documentation/printk-formats.txt
index 5962949944fd..d2fbeeb29582 100644
--- a/Documentation/printk-formats.txt
+++ b/Documentation/printk-formats.txt
@@ -279,11 +279,10 @@ struct clk:
%pC pll1
%pCnpll1
- %pCr156000
From: Peter De Schrijver
Move this to a separate file so it can be used to calculate the sdmmc
clock dividers.
Signed-off-by: Peter De-Schrijver
Signed-off-by: Aapo Vienamo
---
drivers/clk/tegra/Makefile | 1 +
drivers/clk/tegra/clk-divider.c | 30
drivers/clk/t
From: Peter De-Schrijver
These clock have low jitter paths to certain parents. To model these
correctly, use the sdmmc mux divider clock type.
Signed-off-by: Peter De-Schrijver
Signed-off-by: Aapo Vienamo
---
drivers/clk/tegra/clk-id.h | 2 --
drivers/clk/tegra/clk-tegra-periph.c |
From: Peter De-Schrijver
Add a clock type to model the sdmmc switch divider clocks which have paths
to source clocks bypassing the divider (Low Jitter paths). These
are handled by selecting the lj path when the divider is 1 (ie the
rate is the parent rate), otherwise the normal path with divider
On 06/18/2018 10:13 AM, Greg Kroah-Hartman wrote:
> 4.16-stable review patch. If anyone has any objections, please let me know.
So I was wondering, why backport such a considerable number of
*selftests* to stable, given the stable policy? Surely selftests don't
affect the kernel itself breaking f
On Tue, Jul 03, 2018 at 11:28:12AM +, Winkler, Tomas wrote:
>
> >
> > On Thu, Jun 07, 2018 at 12:31:47AM +0300, Tomas Winkler wrote:
> > > From: Alexander Usyskin
> > >
> > > MEI_IAMTHIF_STALL_TIMER is unused now and can be safely removed.
> > >
> > > Signed-off-by: Alexander Usyskin
> > >
I'm announcing the release of the 4.14.53 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser:
On Tue, Jul 03, 2018 at 12:33:20PM +0200, Andrea Parri wrote:
> Hi Mark,
>
> a typo below:
>
>
> > /**
> > - * refcount_inc - increment a refcount
> > + * refcount_inc_checked - increment a refcount
> > * @r: the refcount to increment
> > *
> > * Similar to atomic_inc(), but will saturate
I'm announcing the release of the 4.17.4 kernel.
All users of the 4.17 kernel series must upgrade.
The updated 4.17.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.17.y
and can be browsed at the normal kernel.org git web browser:
On Tue, Jul 03, 2018 at 01:36:43PM +0200, Vlastimil Babka wrote:
> On 06/18/2018 10:13 AM, Greg Kroah-Hartman wrote:
> > 4.16-stable review patch. If anyone has any objections, please let me know.
>
> So I was wondering, why backport such a considerable number of
> *selftests* to stable, given th
On Tue, Jul 03, 2018 at 01:23:30PM +0300, Vladimir Zapolskiy wrote:
> Hi Johan,
>
> On 07/03/2018 01:05 PM, Johan Hovold wrote:
> > Make sure to enable the clock before registering regions and exporting
> > partitions to user space at which point we must be prepared for I/O.
> >
> > Fixes: ee895c
On Tue, Jul 3, 2018 at 4:47 PM, Matthew Wilcox wrote:
> On Mon, Jun 25, 2018 at 11:27:37PM +0530, Souptick Joarder wrote:
>> Use new return type vm_fault_t for both fault handler
>> vdso_fault() and vvar_fault(). Previously vm_insert_pfn()
>> returns err which has to mapped into VM_FAULT_* type.
>
On Tue, 3 Jul 2018 11:22:10 +0200
Halil Pasic wrote:
> On 07/03/2018 09:46 AM, Harald Freudenberger wrote:
> > On 02.07.2018 18:28, Halil Pasic wrote:
> >>
> >>
> >> On 06/29/2018 11:11 PM, Tony Krowiak wrote:
> >>> This patch provides documentation describing the AP architecture and
> >>> de
From: Joerg Roedel
PTI init code clones some parts of the kernel mappings to the user-space
page-table. For the kernel and user-space page-table to be consistent,
the cloning should happen when the relevant parts of the kernel
page-table are finished, which is right after mark_readonly() returns.
Hi,
here is a small patch-set to move the call to pti_init()
after mark_readonly() has run. The purpose of pti_inti() is to
initialize the kernel-mappings in the user-space page-table
by mapping kernel-text, entry-text, espfix and vsyscall
mappings into the user-space page-table.
These mappings o
From: Joerg Roedel
This removes the __init annotations from pti_init() and everything it
calls on x86. The pti_init() function sets up the kernel-mappings
visible in the user-space page-table when PTI is enabled, which only
makes sense after the relevant kernel mappings have been finished.
The k
From: Joerg Roedel
The pti_init() function is now called late enough for
pti_clone_kernel_text(), so call it directly from there.
Signed-off-by: Joerg Roedel
---
arch/x86/include/asm/pti.h | 2 --
arch/x86/mm/init_64.c | 6 --
arch/x86/mm/pti.c | 3 ++-
3 files changed, 2 ins
On 07/03/2018 10:46 AM, David Laight wrote:
From: Jan Beulich
Sent: 03 July 2018 09:36
...
As said there, omitting suffixes from instructions in AT&T mode is bad
practice when operand size cannot be determined by the assembler from
register operands, and is likely going to be warned about by u
The gnss_allocate_device() function returns a mix of NULL and error
pointers on error. It should only return one or the other. Since the
callers both check for NULL, I've modified it to return NULL on error.
Fixes: 10f146639fee ("gnss: add receiver type support")
Signed-off-by: Dan Carpenter
d
On 03/07/18 08:28, Stefan Mavrodiev wrote:
> When mmc host controller enters suspend state, the clocks are
> disabled, but irqs are not. For some reason the irqchip emmits
Not so much the irqchip, but the device itself.
> false interrupts, which causes system lock loop.
I'm not sure the interrup
On 2018-07-03 06:52, p...@codeaurora.org wrote:
On 2018-07-03 14:04, Lukas Wunner wrote:
On Mon, Jul 02, 2018 at 06:52:47PM -0400, Sinan Kaya wrote:
If a bridge supports hotplug and observes a PCIe fatal error, the
following
events happen:
1. AER driver removes the devices from PCI tree on fa
When perf data is recorded with the dwarf call-graph option, the
callchain shown by perf script still shows the binary offsets of
the userspace symbols instead of their virtual addresses. Since
the symbol offset calculation is based on using virtual address
as the ip, we see incorrect offsets as we
NAND parts can have bitflips in an erased page due to the
process technology used. In this case, QCOM NAND controller
is not able to identify that page as an erased page.
Currently the driver calls nand_check_erased_ecc_chunk() for
identifying the erased pages but this won’t work always since the
c
On Tue, Jul 03, 2018 at 05:18:30PM +0530, Souptick Joarder wrote:
> On Tue, Jul 3, 2018 at 4:47 PM, Matthew Wilcox wrote:
> > On Mon, Jun 25, 2018 at 11:27:37PM +0530, Souptick Joarder wrote:
> >> Use new return type vm_fault_t for both fault handler
> >> vdso_fault() and vvar_fault(). Previously
On Tue, Jul 03, 2018 at 02:59:22PM +0300, Dan Carpenter wrote:
> The gnss_allocate_device() function returns a mix of NULL and error
> pointers on error. It should only return one or the other. Since the
> callers both check for NULL, I've modified it to return NULL on error.
>
> Fixes: 10f14663
On Mon, Jul 02, 2018 at 11:48:05AM -0700, Laura Abbott wrote:
> On 07/02/2018 06:02 AM, Alexander Popov wrote:
> > On 29.06.2018 22:05, Laura Abbott wrote:
> > > Implementation of stackleak based heavily on the x86 version
> > >
> > > Signed-off-by: Laura Abbott
> > > ---
> > > Changes since last
On 07/03/2018 01:52 PM, Cornelia Huck wrote:
On Tue, 3 Jul 2018 11:22:10 +0200
Halil Pasic wrote:
[..]
Let me try to invoke the DASD analogy. If one for some reason wants to detach
a DASD the procedure to follow seems to be (see
https://www.ibm.com/support/knowledgecenter/en/linuxonibm/co
On Tue, Jul 03, 2018 at 02:11:43PM +0200, Johan Hovold wrote:
> On Tue, Jul 03, 2018 at 02:59:22PM +0300, Dan Carpenter wrote:
> > The gnss_allocate_device() function returns a mix of NULL and error
> > pointers on error. It should only return one or the other. Since the
> > callers both check fo
From: Denys Vlasenko
> Sent: 03 July 2018 12:59
>
> On 07/03/2018 10:46 AM, David Laight wrote:
> > From: Jan Beulich
> >> Sent: 03 July 2018 09:36
> > ...
> >> As said there, omitting suffixes from instructions in AT&T mode is bad
> >> practice when operand size cannot be determined by the assemb
The gnss_allocate_device() function returns a mix of NULL and error
pointers on error. It should only return one or the other. Since the
callers both check for NULL, I've modified it to return NULL on error.
Fixes: 2b6a44035143 ("gnss: add GNSS receiver subsystem")
Signed-off-by: Dan Carpenter
On 07/03/2018 02:47 PM, Johan Hovold wrote:
> On Tue, Jul 03, 2018 at 01:23:30PM +0300, Vladimir Zapolskiy wrote:
>> Hi Johan,
>>
>> On 07/03/2018 01:05 PM, Johan Hovold wrote:
>>> Make sure to enable the clock before registering regions and exporting
>>> partitions to user space at which point we
The driver now requires two memory resources to be supplied, the first
one for the channel-specific registers, the second one for the
controller-specific registers.
Signed-off-by: Paul Cercueil
---
arch/mips/boot/dts/ingenic/jz4780.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
di
Add the two devicetree nodes for the two DMA cores of the JZ4770 SoC,
disabled by default, as currently there are no clients for the DMA
driver (until the MMC driver and/or others get a devicetree node).
Signed-off-by: Paul Cercueil
---
arch/mips/boot/dts/ingenic/jz4770.dtsi | 30 +++
From: Daniel Silsby
Normally, we wouldn't set the channel transfer count register directly
when using descriptor-driven transfers. However, there is no harm in
doing so, and it allows jz4780_dma_desc_residue() to report the correct
residue of an ongoing transfer, no matter when it is called.
Sig
From: Daniel Silsby
Func jz4780_dma_desc_residue() expects the index to the next hw
descriptor as its last parameter. Caller func jz4780_dma_tx_status(),
however, applied modulus before passing it. When the current hw
descriptor was last in the list, the index passed became zero.
The resulting e
From: Daniel Silsby
The 'dtc' word in jz DMA descriptors contains two fields: The
lowest 24 bits are the transfer count, and upper 8 bits are the DOA
offset to next descriptor. The upper 8 bits are now correctly masked
off when computing residue in jz4780_dma_desc_residue(). Note that
reads of th
From: Daniel Silsby
This is the standard method provided by dmaengine header.
Signed-off-by: Daniel Silsby
---
drivers/dma/dma-jz4780.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/dma/dma-jz4780.c b/drivers/dma/dma-jz4780.c
index 690b853977b2..084b7a46a
From: Daniel Silsby
Simple cleanup, no changes to actual logic here.
Signed-off-by: Daniel Silsby
---
drivers/dma/dma-jz4780.c | 15 +--
1 file changed, 5 insertions(+), 10 deletions(-)
diff --git a/drivers/dma/dma-jz4780.c b/drivers/dma/dma-jz4780.c
index 7b2e305e28fb..adada2a3a0
The JZ4725B has one DMA core starring six DMA channels.
As for the JZ4770, each DMA channel's clock can be enabled with
a register write, the difference here being that once started, it
is not possible to turn it off.
Signed-off-by: Paul Cercueil
---
Documentation/devicetree/bindings/dma/jz4780-
The only information we use in the 8-word version of the hardware DMA
descriptor that is not present in the 4-word version is the transfer
type, aka. the ID of the source or recipient device.
Since the transfer type will never change for a DMA channel in use,
we can just set it once for all in the
The JZ4740 SoC has a single DMA core starring six DMA channels.
Signed-off-by: Paul Cercueil
---
Documentation/devicetree/bindings/dma/jz4780-dma.txt | 1 +
drivers/dma/Kconfig | 2 +-
drivers/dma/dma-jz4780.c | 4
3 files changed
With the fast DMA bit set, the DMA will transfer twice as much data
per clock period to the AIC, so there is little point not to set it.
Signed-off-by: Paul Cercueil
---
drivers/dma/dma-jz4780.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/dma-jz4780.c b/d
The JZ4770 SoC has two DMA cores, each one featuring six DMA channels.
The major change is that each channel's clock can be enabled or disabled
through register writes.
Signed-off-by: Paul Cercueil
---
.../devicetree/bindings/dma/jz4780-dma.txt| 4 +-
drivers/dma/Kconfig
As part of the work to support various other Ingenic JZ47xx SoC versions,
which don't feature the same number of DMA channels per core, we now
deduce the number of DMA channels available from the devicetree
compatible string.
Signed-off-by: Paul Cercueil
---
drivers/dma/dma-jz4780.c | 53 +++
On Fri, May 25, 2018 at 04:02:01PM +0530, Viresh Kumar wrote:
> The OPP properties, like "operating-points", should either be present
> for all the CPUs of a cluster or none. If these are present only for a
> subset of CPUs of a cluster then things will start falling apart as soon
> as the CPUs are
Hi,
This set of patches by myself and Daniel extends the dma-jz4780 driver
to support other SoCs (JZ4770, JZ4740, JZ4725B).
Some fixes are also included, for proper residue reporting, which fixes
errors with ALSA.
Finally, the last two patches update the devicetree bindings for the
JZ4780 SoC an
The register area of the JZ4780 DMA core can be split into different
sections for different purposes:
* one set of registers is used to perform actions at the DMA core level,
that will generally affect all channels;
* one set of registers per DMA channel, to perform actions at the DMA
channel lev
Like vm_insert_pfn_prot(), but returns a vm_fault_t instead of an errno.
Also unexport vm_insert_pfn_prot as it has no modular users.
Signed-off-by: Matthew Wilcox
---
include/linux/mm.h | 2 ++
mm/memory.c| 47 ++
2 files changed, 33 insertio
Return vm_fault_t codes directly from the appropriate mm routines instead
of converting from errnos ourselves. Fixes a minor bug where we'd return
SIGBUS instead of the correct OOM code if we ran out of memory allocating
page tables.
Signed-off-by: Matthew Wilcox
---
arch/x86/entry/vdso/vma.c |
Now this is no longer used outside mm/memory.c, make it static.
Signed-off-by: Matthew Wilcox
---
include/linux/mm.h | 2 --
mm/memory.c| 50 +++---
2 files changed, 25 insertions(+), 27 deletions(-)
diff --git a/include/linux/mm.h b/include/linu
On Tue, Jul 03, 2018 at 01:24:49PM +0200, Gabriel C wrote:
> 2018-07-01 23:32 GMT+02:00 Benjamin Gilbert :
> > On Sun, Jul 01, 2018 at 05:15:59PM -0400, Benjamin Gilbert wrote:
> >> 4.17 kernels built with the CoreOS Container Linux toolchain and kconfig,
> >> up to and including 4.17.3, fail to bo
On Mon, Jul 02, 2018 at 10:59:45PM +0100, Suzuki K Poulose wrote:
> The armpmu uses get_event_idx callback to allocate an event
> counter for a given event, which marks the selected counter
> as "used". Now, when we delete the counter, the arm_pmu goes
> ahead and clears the "used" bit and then inv
This patch adds an additional property in the device tree for adjusting the
delay between a rising edge on PD_SCK until data is ready on DOUT.
This is necessary because of parasitic capacities on different systems.
In the last patch there is a fix of dtc warning if someone is using the
given exam
add avia,data-ready-delay-ns property for hx711 ADC
this is the delay after rising PD_SCK until DOUT is read and assumed to be
ready
Signed-off-by: Andreas Klinger
---
Documentation/devicetree/bindings/iio/adc/avia-hx711.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentatio
On a system with parasitic capacities it turned out that DOUT is not ready
after 100 ns after PD_SCK has raised. A measurement showed almost 1000 ns
until DOUT has reached its correct value.
With this patch its now possible to wait until data is ready.
The wait time should not be higher than the
device tree compiler (dtc) gives a warning if a device node has "@" with a
following number as it's name but no reg property.
fix the example in the documentation of avia,hx711 to conform to dtc
behavior
Signed-off-by: Andreas Klinger
---
Documentation/devicetree/bindings/iio/adc/avia-hx711.txt
Hi,
On 27/06/2018 15:16:04+0200, Piotr Bugalski wrote:
> Just minor typo fix. Fixed in preparation of new driver.
>
> Signed-off: Piotr Bugalski
This SoB line must match the author. It doesn't matter which one you
change. note that you can still submit your patch from an address
different from
Hello Peter,
Thanks for your comments. Will send v3 with comments fixed.
On 06/30/2018 11:51 AM, Peter Meerwald-Stadler wrote:
Add support for VCNL4035, which is capable of Ambient light
sensing (ALS) and proximity function. This patch adds support
only for ALS function
comments below
a lo
On Mon, Jul 02, 2018 at 10:59:48PM +0100, Suzuki K Poulose wrote:
> Add support for 64bit event by using chained event counters
> and 64bit cycle counters.
>
> PMUv3 allows chaining a pair of adjacent 32-bit counters, effectively
> forming a 64-bit counter. The low/even counter is programmed to co
Hi Miquel,
> -Original Message-
> From: Miquel Raynal [mailto:miquel.ray...@bootlin.com]
> Sent: Thursday, June 28, 2018 12:45 PM
> To: Naga Sureshkumar Relli
> Cc: boris.brezil...@bootlin.com; rich...@nod.at; dw...@infradead.org;
> computersforpe...@gmail.com; marek.va...@gmail.com; f.fa
On Tue, 2018-07-03 at 10:22 +0800, Jisheng Zhang wrote:
> Hi,
>
> On Mon, 2 Jul 2018 14:51:03 +0300 Andy Shevchenko wrote:
>
> > On Mon, 2018-07-02 at 13:18 +0300, Andy Shevchenko wrote:
> > > On Mon, 2018-07-02 at 18:04 +0800, Jisheng Zhang wrote:
> > > > For Synopsys DesignWare 8250 uart whic
On Tue, 2018-07-03 at 10:48 +0800, Jisheng Zhang wrote:
> On Tue, 3 Jul 2018 10:22:57 +0800 Jisheng Zhang wrote:
> patching struct uart_port seems a bit overhead. After reading the code
> again, I propose another solution, similar as what dl_write() is used
> in
> 8250 core:
>
> 1.introduce the h
On Tue, Jul 03, 2018 at 02:52:40PM +0530, Srinath Mannam wrote:
> This patch provides a function, to get of_device_id after
> matching with ACPI device _DSD object compatible property
> in the case driver does not contain acpi_device_id list
> and driver probe called for ACPI device ID PRP0001 with
On Tue, Jul 03, 2018 at 03:30:09PM +0300, Vladimir Zapolskiy wrote:
> On 07/03/2018 02:47 PM, Johan Hovold wrote:
> > On Tue, Jul 03, 2018 at 01:23:30PM +0300, Vladimir Zapolskiy wrote:
> >> Hi Johan,
> >>
> >> On 07/03/2018 01:05 PM, Johan Hovold wrote:
> >>> Make sure to enable the clock before r
On 2018-07-03 17:00, ok...@codeaurora.org wrote:
On 2018-07-03 04:34, Lukas Wunner wrote:
On Mon, Jul 02, 2018 at 06:52:47PM -0400, Sinan Kaya wrote:
If a bridge supports hotplug and observes a PCIe fatal error, the
following
events happen:
1. AER driver removes the devices from PCI tree on f
This script performs build testing, by building several configurations
several times. The script is introduced to improve the consistency of
testing changes in the kernel configuration.
This version build randconfig 10 times, as well as allyesconfig,
allnoconfig and allmodconfig. Depending on the
On 03/07/18 14:00, Mark Rutland wrote:
On Mon, Jul 02, 2018 at 10:59:48PM +0100, Suzuki K Poulose wrote:
Add support for 64bit event by using chained event counters
and 64bit cycle counters.
PMUv3 allows chaining a pair of adjacent 32-bit counters, effectively
forming a 64-bit counter. The low/
On 03/07/18 13:49, Mark Rutland wrote:
On Mon, Jul 02, 2018 at 10:59:45PM +0100, Suzuki K Poulose wrote:
The armpmu uses get_event_idx callback to allocate an event
counter for a given event, which marks the selected counter
as "used". Now, when we delete the counter, the arm_pmu goes
ahead and
201 - 300 of 888 matches
Mail list logo
