Hi,
On Tue, Jul 17, 2018 at 2:08 PM, Matthias Kaehlcke wrote:
> When the temperature reaches stage 2 the PMIC performs by default a
> 'partial shutdown', unless software override is enabled. It is not well
> defined which peripherals are affected by a 'partial shutdown'. Drivers
> might be
Hi,
On Tue, Jul 17, 2018 at 2:08 PM, Matthias Kaehlcke wrote:
> When the temperature reaches stage 2 the PMIC performs by default a
> 'partial shutdown', unless software override is enabled. It is not well
> defined which peripherals are affected by a 'partial shutdown'. Drivers
> might be
Hi Udit,
I love your patch! Yet something to improve:
[auto build test ERROR on security/next]
[also build test ERROR on v4.18-rc5 next-20180720]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits
Does anyone have any suggestion about those patches ?
On 07/09/2018 02:16 PM, Michal Hocko wrote:
[CC hugetlb guys - http://lkml.kernel.org/r/20180705110716.3919-1-a...@ghiti.fr]
On Thu 05-07-18 11:07:05, Alexandre Ghiti wrote:
In order to reduce copy/paste of functions across architectures
Hi Udit,
I love your patch! Yet something to improve:
[auto build test ERROR on security/next]
[also build test ERROR on v4.18-rc5 next-20180720]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits
Does anyone have any suggestion about those patches ?
On 07/09/2018 02:16 PM, Michal Hocko wrote:
[CC hugetlb guys - http://lkml.kernel.org/r/20180705110716.3919-1-a...@ghiti.fr]
On Thu 05-07-18 11:07:05, Alexandre Ghiti wrote:
In order to reduce copy/paste of functions across architectures
On Thursday, July 19, 2018 8:47:49 AM CEST Boris Brezillon wrote:
> On Thu, 19 Jul 2018 01:57:10 +0200
> Janusz Krzysztofik wrote:
>
> > Don't readw()/writew() data directly from/to GPIO port which is under
> > control of gpio-omap driver, use GPIO chip callbacks instead.
> >
> > Thanks to
On Thursday, July 19, 2018 8:47:49 AM CEST Boris Brezillon wrote:
> On Thu, 19 Jul 2018 01:57:10 +0200
> Janusz Krzysztofik wrote:
>
> > Don't readw()/writew() data directly from/to GPIO port which is under
> > control of gpio-omap driver, use GPIO chip callbacks instead.
> >
> > Thanks to
From: Colin Ian King
Pointer 'nic' is being assigned but is never used hence it is
redundant and can be removed.
Cleans up clang warning:
warning: variable 'nic' set but not used [-Wunused-but-set-variable]
Signed-off-by: Colin Ian King
---
drivers/staging/rtl8712/rtl8712_led.c | 3 ---
1
From: Colin Ian King
Pointer 'nic' is being assigned but is never used hence it is
redundant and can be removed.
Cleans up clang warning:
warning: variable 'nic' set but not used [-Wunused-but-set-variable]
Signed-off-by: Colin Ian King
---
drivers/staging/rtl8712/rtl8712_led.c | 3 ---
1
On Wed, 18 Jul 2018, Manfred Spraul wrote:
Hello Davidlohr,
On 07/17/2018 07:26 AM, Davidlohr Bueso wrote:
In order for load/store tearing to work, _all_ accesses to
the variable in question need to be done around READ and
WRITE_ONCE() macros. Ensure everyone does so for q->status
variable
On Wed, 18 Jul 2018, Manfred Spraul wrote:
Hello Davidlohr,
On 07/17/2018 07:26 AM, Davidlohr Bueso wrote:
In order for load/store tearing to work, _all_ accesses to
the variable in question need to be done around READ and
WRITE_ONCE() macros. Ensure everyone does so for q->status
variable
By digging into the original review, it looks use_zero_page sysfs knob
was added to help ease-of-testing and give user a way to mitigate
refcounting overhead.
It has been a few years since the knob was added at the first place, I
think we are confident that it is stable enough. And, since commit
On Thursday, July 19, 2018 8:25:38 AM CEST Boris Brezillon wrote:
> On Thu, 19 Jul 2018 01:57:06 +0200
> Janusz Krzysztofik wrote:
>
> > Further optimize processing speed of read/write callback functions by
> > resolving private structure pointer only once per callback and passing
> > it to all
By digging into the original review, it looks use_zero_page sysfs knob
was added to help ease-of-testing and give user a way to mitigate
refcounting overhead.
It has been a few years since the knob was added at the first place, I
think we are confident that it is stable enough. And, since commit
On Thursday, July 19, 2018 8:25:38 AM CEST Boris Brezillon wrote:
> On Thu, 19 Jul 2018 01:57:06 +0200
> Janusz Krzysztofik wrote:
>
> > Further optimize processing speed of read/write callback functions by
> > resolving private structure pointer only once per callback and passing
> > it to all
On Thursday, July 19, 2018 8:23:18 AM CEST Boris Brezillon wrote:
> On Thu, 19 Jul 2018 01:57:05 +0200
> Janusz Krzysztofik wrote:
>
> > In its current shape, the driver sets data port direction before each
> > byte read/write operation, even during multi-byte transfers. Optimize
> > that by
On Thursday, July 19, 2018 8:23:18 AM CEST Boris Brezillon wrote:
> On Thu, 19 Jul 2018 01:57:05 +0200
> Janusz Krzysztofik wrote:
>
> > In its current shape, the driver sets data port direction before each
> > byte read/write operation, even during multi-byte transfers. Optimize
> > that by
Hi Pavel,
On 07/19/2018 10:20 PM, Pavel Machek wrote:
Hi!
Please keep in mind that this is ABI documentation for the pattern file
to be exposed by LED core, and not by the pattern trigger, that, as we
agreed, will be implemented later. In this case, I'd go for
Gosh, I got completely
Hi Pavel,
On 07/19/2018 10:20 PM, Pavel Machek wrote:
Hi!
Please keep in mind that this is ABI documentation for the pattern file
to be exposed by LED core, and not by the pattern trigger, that, as we
agreed, will be implemented later. In this case, I'd go for
Gosh, I got completely
When the commit adding ntb_default_port_number() and
ntb_default_peer_port_number() entered the kernel there was no
users of it so it was impossible to tell what the API needed.
When a user finally landed a year later (ntb_pingpong) there were
more NTB topologies were created and no
When the commit adding ntb_default_port_number() and
ntb_default_peer_port_number() entered the kernel there was no
users of it so it was impossible to tell what the API needed.
When a user finally landed a year later (ntb_pingpong) there were
more NTB topologies were created and no
When running ntb_test this warning is issued:
./ntb_test.sh: line 200: warning: command substitution: ignored null
byte in input
This is caused by the kernel returning one more byte than is necessary
when reading the link file.
Reduce the number of bytes read back to 2 as it was before the
On Thursday, July 19, 2018 8:22:00 AM CEST Boris Brezillon wrote:
> On Thu, 19 Jul 2018 01:57:04 +0200
> Janusz Krzysztofik wrote:
>
> > Initialize NWP GPIO pin low to protect the device from hazard during
> > probe. Release write protection as soon as the device is under
> > control.
> >
> >
When running ntb_test this warning is issued:
./ntb_test.sh: line 200: warning: command substitution: ignored null
byte in input
This is caused by the kernel returning one more byte than is necessary
when reading the link file.
Reduce the number of bytes read back to 2 as it was before the
On Thursday, July 19, 2018 8:22:00 AM CEST Boris Brezillon wrote:
> On Thu, 19 Jul 2018 01:57:04 +0200
> Janusz Krzysztofik wrote:
>
> > Initialize NWP GPIO pin low to protect the device from hazard during
> > probe. Release write protection as soon as the device is under
> > control.
> >
> >
ntb_perf should not require more than one memory window per peer. This
was probably an off-by-one error.
Fixes: 5648e56d03fa ("NTB: ntb_perf: Add full multi-port NTB API support")
Signed-off-by: Logan Gunthorpe
---
drivers/ntb/test/ntb_perf.c | 2 +-
1 file changed, 1 insertion(+), 1
ntb_perf should not require more than one memory window per peer. This
was probably an off-by-one error.
Fixes: 5648e56d03fa ("NTB: ntb_perf: Add full multi-port NTB API support")
Signed-off-by: Logan Gunthorpe
---
drivers/ntb/test/ntb_perf.c | 2 +-
1 file changed, 1 insertion(+), 1
Hey,
This is mostly a resend.
To reiterate the main points on the feedback: the switchtec driver,
in the cross link mode, will not be able to implement the port number
function callbacks and will have to always return 0. It's a physical
impossibility due to the symmetry. Therefore, in order fix
Hey,
This is mostly a resend.
To reiterate the main points on the feedback: the switchtec driver,
in the cross link mode, will not be able to implement the port number
function callbacks and will have to always return 0. It's a physical
impossibility due to the symmetry. Therefore, in order fix
When remote files are counted in get_files_count, without using SSH,
the code returns 0 because there is a colon prepended to $LOC. $VPATH
should have been used instead of $LOC.
Fixes: 06bd0407d06c ("NTB: ntb_test: Update ntb_tool Scratchpad tests")
Signed-off-by: Logan Gunthorpe
---
When remote files are counted in get_files_count, without using SSH,
the code returns 0 because there is a colon prepended to $LOC. $VPATH
should have been used instead of $LOC.
Fixes: 06bd0407d06c ("NTB: ntb_test: Update ntb_tool Scratchpad tests")
Signed-off-by: Logan Gunthorpe
---
This commit fixes pingpong support for existing drivers that do not
implement ntb_default_port_number() and ntb_default_peer_port_number().
This is required for hardware (like the crosslink topology of
switchtec) which cannot assign reasonable port numbers to each port due
to its perfect symmetry.
Legacy drivers do not have port numbers (but is reliably only two ports)
and was broken by the recent commit that added mult-port support to
ntb_perf. This is especially important to support the cross link
topology which is perfectly symmetric and cannot assign unique port
numbers easily.
Legacy drivers do not have port numbers (but is reliably only two ports)
and was broken by the recent commit that added mult-port support to
ntb_perf. This is especially important to support the cross link
topology which is perfectly symmetric and cannot assign unique port
numbers easily.
This commit fixes pingpong support for existing drivers that do not
implement ntb_default_port_number() and ntb_default_peer_port_number().
This is required for hardware (like the crosslink topology of
switchtec) which cannot assign reasonable port numbers to each port due
to its perfect symmetry.
Commit 417cf39cfea9 ("NTB: Set dma mask and dma coherent mask to NTB
devices") added code to set the DMA mask for the NTB device
to each driver individually. However, it neglected to set it for the
Switchtec driver. So when the monolithic commit 7f46c8b3a552 ("NTB:
ntb_tool: Add full multi-port
Commit 417cf39cfea9 ("NTB: Set dma mask and dma coherent mask to NTB
devices") added code to set the DMA mask for the NTB device
to each driver individually. However, it neglected to set it for the
Switchtec driver. So when the monolithic commit 7f46c8b3a552 ("NTB:
ntb_tool: Add full multi-port
When running ntb_test, the script tries to run the ntb_perf test
immediately after probing the modules. Since adding multi-port support,
this fails seeing the new initialization procedure in ntb_perf
can not complete instantly.
To fix this we add a completion which is waited on when a test is
When running ntb_test, the script tries to run the ntb_perf test
immediately after probing the modules. Since adding multi-port support,
this fails seeing the new initialization procedure in ntb_perf
can not complete instantly.
To fix this we add a completion which is waited on when a test is
On Tue, Jul 17, 2018 at 01:48:35PM +0200, Alexandre Belloni wrote:
> The Microsemi Ocelot I2C controller is a designware IP. It also has a
> second set of registers to allow tweaking SDA hold time and spike
> filtering.
>
> Cc: Rob Herring
> Signed-off-by: Alexandre Belloni
> ---
>
On Tue, Jul 17, 2018 at 01:48:35PM +0200, Alexandre Belloni wrote:
> The Microsemi Ocelot I2C controller is a designware IP. It also has a
> second set of registers to allow tweaking SDA hold time and spike
> filtering.
>
> Cc: Rob Herring
> Signed-off-by: Alexandre Belloni
> ---
>
On Thursday, July 19, 2018 8:17:28 AM CEST Boris Brezillon wrote:
> On Thu, 19 Jul 2018 01:57:03 +0200
> Janusz Krzysztofik wrote:
>
> > Introduce a driver private structure and allocate it on device probe.
> > Use it for storing nand_chip structure, GPIO descriptors prevoiusly
> > stored in
On Thursday, July 19, 2018 8:17:28 AM CEST Boris Brezillon wrote:
> On Thu, 19 Jul 2018 01:57:03 +0200
> Janusz Krzysztofik wrote:
>
> > Introduce a driver private structure and allocate it on device probe.
> > Use it for storing nand_chip structure, GPIO descriptors prevoiusly
> > stored in
Hi Boris,
On Thursday, July 19, 2018 8:15:08 AM CEST Boris Brezillon wrote:
> Hi Janusz,
>
> On Thu, 19 Jul 2018 01:57:02 +0200
> Janusz Krzysztofik wrote:
>
> > Implement the idea suggested by Artem Bityutskiy and Tony Lindgren
> > described in commit b027274d2e3a ("mtd: ams-delta: fix
> >
Hi Boris,
On Thursday, July 19, 2018 8:15:08 AM CEST Boris Brezillon wrote:
> Hi Janusz,
>
> On Thu, 19 Jul 2018 01:57:02 +0200
> Janusz Krzysztofik wrote:
>
> > Implement the idea suggested by Artem Bityutskiy and Tony Lindgren
> > described in commit b027274d2e3a ("mtd: ams-delta: fix
> >
Hi,
On Fri, Jul 20, 2018 at 10:26 AM, Rob Herring wrote:
> On Fri, Jul 20, 2018 at 9:13 AM Doug Anderson wrote:
>>
>> Rob,
>>
>> On Fri, Jul 20, 2018 at 7:10 AM, Rob Herring wrote:
>> > On Fri, Jul 06, 2018 at 04:31:42PM -0700, Douglas Anderson wrote:
>> >> A few patches have landed for the
Hi,
On Fri, Jul 20, 2018 at 10:26 AM, Rob Herring wrote:
> On Fri, Jul 20, 2018 at 9:13 AM Doug Anderson wrote:
>>
>> Rob,
>>
>> On Fri, Jul 20, 2018 at 7:10 AM, Rob Herring wrote:
>> > On Fri, Jul 06, 2018 at 04:31:42PM -0700, Douglas Anderson wrote:
>> >> A few patches have landed for the
On Fri, Jul 20, 2018 at 10:06:54AM -0700, Andy Lutomirski wrote:
> > On Jul 20, 2018, at 6:22 AM, Joerg Roedel wrote:
> >
> > From: Joerg Roedel
> >
> > The ring-buffer is accessed in the NMI handler, so we better
> > avoid faulting on it. Sync the vmalloc range with all
> > page-tables in
On Fri, Jul 20, 2018 at 10:06:54AM -0700, Andy Lutomirski wrote:
> > On Jul 20, 2018, at 6:22 AM, Joerg Roedel wrote:
> >
> > From: Joerg Roedel
> >
> > The ring-buffer is accessed in the NMI handler, so we better
> > avoid faulting on it. Sync the vmalloc range with all
> > page-tables in
On Tue, Jul 17, 2018 at 04:52:25PM +0800, Mars Cheng wrote:
> This adds scpsys support for MT6765
>
> Signed-off-by: Mars Cheng
> Signed-off-by: Owen Chen
> ---
> drivers/soc/mediatek/mtk-scpsys.c| 88
> ++
> include/dt-bindings/power/mt6765-power.h |
On Tue, Jul 17, 2018 at 04:52:25PM +0800, Mars Cheng wrote:
> This adds scpsys support for MT6765
>
> Signed-off-by: Mars Cheng
> Signed-off-by: Owen Chen
> ---
> drivers/soc/mediatek/mtk-scpsys.c| 88
> ++
> include/dt-bindings/power/mt6765-power.h |
On Tue, Jul 17, 2018 at 04:52:24PM +0800, Mars Cheng wrote:
> This adds power dt-bindings for MT6765
>
> Signed-off-by: Mars Cheng
> Signed-off-by: Owen Chen
> ---
> .../devicetree/bindings/soc/mediatek/scpsys.txt|6 ++
> 1 file changed, 6 insertions(+)
Reviewed-by: Rob Herring
On Tue, Jul 17, 2018 at 04:52:24PM +0800, Mars Cheng wrote:
> This adds power dt-bindings for MT6765
>
> Signed-off-by: Mars Cheng
> Signed-off-by: Owen Chen
> ---
> .../devicetree/bindings/soc/mediatek/scpsys.txt|6 ++
> 1 file changed, 6 insertions(+)
Reviewed-by: Rob Herring
Quoting Rajendra Nayak (2018-07-18 23:59:20)
>
>
> On 7/19/2018 11:12 AM, Bjorn Andersson wrote:
> > On Wed 18 Jul 22:18 PDT 2018, Rajendra Nayak wrote:
> >
> >> commit '8c1b7dc9b: firmware: qcom: scm: Expose download-mode control'
> >> added support for download-mode control using the scm
Quoting Rajendra Nayak (2018-07-18 23:59:20)
>
>
> On 7/19/2018 11:12 AM, Bjorn Andersson wrote:
> > On Wed 18 Jul 22:18 PDT 2018, Rajendra Nayak wrote:
> >
> >> commit '8c1b7dc9b: firmware: qcom: scm: Expose download-mode control'
> >> added support for download-mode control using the scm
On Tue, Jul 17, 2018 at 04:52:23PM +0800, Mars Cheng wrote:
> This patch adds MT6765 smi binding document
>
> Signed-off-by: Mars Cheng
> Signed-off-by: Owen Chen
> ---
> .../memory-controllers/mediatek,smi-common.txt |1 +
> 1 file changed, 1 insertion(+)
Acked-by: Rob Herring
On Tue, Jul 17, 2018 at 04:52:23PM +0800, Mars Cheng wrote:
> This patch adds MT6765 smi binding document
>
> Signed-off-by: Mars Cheng
> Signed-off-by: Owen Chen
> ---
> .../memory-controllers/mediatek,smi-common.txt |1 +
> 1 file changed, 1 insertion(+)
Acked-by: Rob Herring
On Tue, Jul 17, 2018 at 04:52:22PM +0800, Mars Cheng wrote:
> This patch adds the binding documentation for apmixedsys, audsys, camsys,
> imgsys, infracfg, mipi0a, topckgen, vcodecsys
>
> Signed-off-by: Mars Cheng
> Signed-off-by: Owen Chen
> ---
>
On Tue, Jul 17, 2018 at 04:52:22PM +0800, Mars Cheng wrote:
> This patch adds the binding documentation for apmixedsys, audsys, camsys,
> imgsys, infracfg, mipi0a, topckgen, vcodecsys
>
> Signed-off-by: Mars Cheng
> Signed-off-by: Owen Chen
> ---
>
On Tue, Jul 17, 2018 at 04:41:56AM -0400, Brian Masney wrote:
> This patch adds support for the regulator framework to the tsl2772
> driver. Driver was tested using a LG Nexus 5 (hammerhead) phone with
> the two regulators and on a Raspberry Pi 2 without any regulators
> controlling the power to
On Tue, Jul 17, 2018 at 04:41:56AM -0400, Brian Masney wrote:
> This patch adds support for the regulator framework to the tsl2772
> driver. Driver was tested using a LG Nexus 5 (hammerhead) phone with
> the two regulators and on a Raspberry Pi 2 without any regulators
> controlling the power to
On Tue, Jul 17, 2018 at 04:41:54AM -0400, Brian Masney wrote:
> This patch adds support for optionally reading the prox_diode and
> prox_power settings from device tree. This was tested using a LG
> Nexus 5 (hammerhead) which requires a different diode than the driver
> default for the IR LED.
>
On Tue, Jul 17, 2018 at 04:41:54AM -0400, Brian Masney wrote:
> This patch adds support for optionally reading the prox_diode and
> prox_power settings from device tree. This was tested using a LG
> Nexus 5 (hammerhead) which requires a different diode than the driver
> default for the IR LED.
>
Both functions are similar to the context of ep_modify(), called via
epoll_ctl(2). Just like ep_modify(), saving and restoring interrupts
is an overkill in these calls as it will never be called with irqs
disabled. While ep_remove() can be called directly from EPOLL_CTL_DEL,
it can also be called
Both functions are similar to the context of ep_modify(), called via
epoll_ctl(2). Just like ep_modify(), saving and restoring interrupts
is an overkill in these calls as it will never be called with irqs
disabled. While ep_remove() can be called directly from EPOLL_CTL_DEL,
it can also be called
Saving and restoring interrupts in ep_scan_ready_list() is an
overkill as it is never called with interrupts disabled. Loosen
this to simply disabling local irqs such that archs where managing
irqs is expensive or virtual environments. This patch yields
some throughput improvements on a workload
Hi,
Both patches replace saving+restoring interrupts when taking the
ep->lock (now the waitqueue lock), with just disabling local irqs.
This shows immediate performance benefits in patch 1 for an epoll
workload running on Xen. The main concern we need to have with this
sort of changes in epoll is
Hi,
Both patches replace saving+restoring interrupts when taking the
ep->lock (now the waitqueue lock), with just disabling local irqs.
This shows immediate performance benefits in patch 1 for an epoll
workload running on Xen. The main concern we need to have with this
sort of changes in epoll is
Saving and restoring interrupts in ep_scan_ready_list() is an
overkill as it is never called with interrupts disabled. Loosen
this to simply disabling local irqs such that archs where managing
irqs is expensive or virtual environments. This patch yields
some throughput improvements on a workload
On Fri, Jul 20, 2018 at 9:13 AM Doug Anderson wrote:
>
> Rob,
>
> On Fri, Jul 20, 2018 at 7:10 AM, Rob Herring wrote:
> > On Fri, Jul 06, 2018 at 04:31:42PM -0700, Douglas Anderson wrote:
> >> A few patches have landed for the qcom-qmp PHY that affect how you
> >> would write a device tree node.
On Fri, Jul 20, 2018 at 9:13 AM Doug Anderson wrote:
>
> Rob,
>
> On Fri, Jul 20, 2018 at 7:10 AM, Rob Herring wrote:
> > On Fri, Jul 06, 2018 at 04:31:42PM -0700, Douglas Anderson wrote:
> >> A few patches have landed for the qcom-qmp PHY that affect how you
> >> would write a device tree node.
On Thu, 19 Jul 2018, Yury Norov wrote:
> While here. I just wonder, on my system IRQs are sent to nohz_full CPUs
> at every incoming ssh connection. The trace is like this:
> [ 206.835533] Call trace:
> [ 206.848411] [] dump_stack+0x84/0xa8
> [ 206.853455] [] _task_isolation_remote+0x130/0x140
On Thu, 19 Jul 2018, Yury Norov wrote:
> While here. I just wonder, on my system IRQs are sent to nohz_full CPUs
> at every incoming ssh connection. The trace is like this:
> [ 206.835533] Call trace:
> [ 206.848411] [] dump_stack+0x84/0xa8
> [ 206.853455] [] _task_isolation_remote+0x130/0x140
On Fri, Jul 20, 2018 at 03:16:42PM +0530, Kamalesh Babulal wrote:
> livepatch module author can pass module name/old function name with more
> than the defined character limit. With obj->name length greater than
> MODULE_NAME_LEN, the livepatch module gets loaded but waits forever on
> the module
On Fri, Jul 20, 2018 at 03:16:42PM +0530, Kamalesh Babulal wrote:
> livepatch module author can pass module name/old function name with more
> than the defined character limit. With obj->name length greater than
> MODULE_NAME_LEN, the livepatch module gets loaded but waits forever on
> the module
On Fri, Jul 20, 2018 at 9:22 AM, Joerg Roedel wrote:
> From: Joerg Roedel
>
> The code that switches from entry- to task-stack when we
> enter from kernel-mode copies the full entry-stack contents
> to the task-stack.
>
> That is because we don't trust that the entry-stack
> contents. But
On Fri, Jul 20, 2018 at 9:22 AM, Joerg Roedel wrote:
> From: Joerg Roedel
>
> The code that switches from entry- to task-stack when we
> enter from kernel-mode copies the full entry-stack contents
> to the task-stack.
>
> That is because we don't trust that the entry-stack
> contents. But
> On Jul 20, 2018, at 6:22 AM, Joerg Roedel wrote:
>
> From: Joerg Roedel
>
> The ring-buffer is accessed in the NMI handler, so we better
> avoid faulting on it. Sync the vmalloc range with all
> page-tables in system to make sure everyone has it mapped.
>
> This fixes a WARN_ON_ONCE() that can
> On Jul 20, 2018, at 6:22 AM, Joerg Roedel wrote:
>
> From: Joerg Roedel
>
> The ring-buffer is accessed in the NMI handler, so we better
> avoid faulting on it. Sync the vmalloc range with all
> page-tables in system to make sure everyone has it mapped.
>
> This fixes a WARN_ON_ONCE() that can
On Tue, Jul 17, 2018 at 04:41:52AM -0400, Brian Masney wrote:
> This patch adds support for the regulator framework to the mpu6050
> driver.
>
> Signed-off-by: Brian Masney
> Signed-off-by: Jonathan Marek
> ---
> Changes since v1:
> - Use devm_regulator_get() instead of
On Tue, Jul 17, 2018 at 04:41:52AM -0400, Brian Masney wrote:
> This patch adds support for the regulator framework to the mpu6050
> driver.
>
> Signed-off-by: Brian Masney
> Signed-off-by: Jonathan Marek
> ---
> Changes since v1:
> - Use devm_regulator_get() instead of
On Tue, Jul 17, 2018 at 03:58:54PM +0800, c...@rock-chips.com wrote:
> From: Liang Chen
>
> This patch add px30-evb.dts for PX30 evaluation board.
> Tested on PX30 evb.
>
> Signed-off-by: Liang Chen
> ---
> Documentation/devicetree/bindings/arm/rockchip.txt | 4 +
>
On Tue, Jul 17, 2018 at 03:58:54PM +0800, c...@rock-chips.com wrote:
> From: Liang Chen
>
> This patch add px30-evb.dts for PX30 evaluation board.
> Tested on PX30 evb.
>
> Signed-off-by: Liang Chen
> ---
> Documentation/devicetree/bindings/arm/rockchip.txt | 4 +
>
Hi Marek,
> -Original Message-
> From: Jolly Shah
> Sent: Friday, May 18, 2018 2:19 PM
> To: 'Marek Szyprowski'
> Cc: Matthias Brugger ; Andy Gross
> ; Shawn Guo ; Geert
> Uytterhoeven ; Björn Andersson
> ; sean.w...@mediatek.com; Michal Simek
> ; Mark Rutland ; Rajan
> Vaja ; open
Hi Marek,
> -Original Message-
> From: Jolly Shah
> Sent: Friday, May 18, 2018 2:19 PM
> To: 'Marek Szyprowski'
> Cc: Matthias Brugger ; Andy Gross
> ; Shawn Guo ; Geert
> Uytterhoeven ; Björn Andersson
> ; sean.w...@mediatek.com; Michal Simek
> ; Mark Rutland ; Rajan
> Vaja ; open
On Tue, Jul 17, 2018 at 03:56:01PM +0800, c...@rock-chips.com wrote:
> From: Liang Chen
>
> This patch adds the compatible of GRF and PMUGRF for PX30 SoCs.
>
> Signed-off-by: Liang Chen
> ---
> Documentation/devicetree/bindings/soc/rockchip/grf.txt | 2 ++
> 1 file changed, 2 insertions(+)
On Tue, Jul 17, 2018 at 03:56:01PM +0800, c...@rock-chips.com wrote:
> From: Liang Chen
>
> This patch adds the compatible of GRF and PMUGRF for PX30 SoCs.
>
> Signed-off-by: Liang Chen
> ---
> Documentation/devicetree/bindings/soc/rockchip/grf.txt | 2 ++
> 1 file changed, 2 insertions(+)
On Tue, Jul 17, 2018 at 03:49:04PM +0800, c...@rock-chips.com wrote:
> From: Liang Chen
>
> Add "rockchip,px30-i2s", "rockchip,rk3066-i2s" for i2s on px30 platform.
>
> Signed-off-by: Liang Chen
> ---
> Documentation/devicetree/bindings/sound/rockchip-i2s.txt | 1 +
> 1 file changed, 1
On Tue, Jul 17, 2018 at 03:49:04PM +0800, c...@rock-chips.com wrote:
> From: Liang Chen
>
> Add "rockchip,px30-i2s", "rockchip,rk3066-i2s" for i2s on px30 platform.
>
> Signed-off-by: Liang Chen
> ---
> Documentation/devicetree/bindings/sound/rockchip-i2s.txt | 1 +
> 1 file changed, 1
On Tue, Jul 17, 2018 at 03:49:03PM +0800, c...@rock-chips.com wrote:
> From: Liang Chen
>
> Add "rockchip,px30-spi", "rockchip,rk3066-spi" for spi on px30 platform.
>
> Signed-off-by: Liang Chen
> ---
> Documentation/devicetree/bindings/spi/spi-rockchip.txt | 1 +
> 1 file changed, 1
On Tue, Jul 17, 2018 at 03:49:02PM +0800, c...@rock-chips.com wrote:
> From: Liang Chen
>
> Add "rockchip,px30-dw-mshc", "rockchip,rk3288-dw-mshc" for
> dwmmc on px30 platform.
>
> Signed-off-by: Liang Chen
> ---
> Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt | 1 +
> 1 file
On Tue, Jul 17, 2018 at 03:49:03PM +0800, c...@rock-chips.com wrote:
> From: Liang Chen
>
> Add "rockchip,px30-spi", "rockchip,rk3066-spi" for spi on px30 platform.
>
> Signed-off-by: Liang Chen
> ---
> Documentation/devicetree/bindings/spi/spi-rockchip.txt | 1 +
> 1 file changed, 1
On Tue, Jul 17, 2018 at 03:49:02PM +0800, c...@rock-chips.com wrote:
> From: Liang Chen
>
> Add "rockchip,px30-dw-mshc", "rockchip,rk3288-dw-mshc" for
> dwmmc on px30 platform.
>
> Signed-off-by: Liang Chen
> ---
> Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt | 1 +
> 1 file
The patch
ASoC: meson: add axg tdm interface DT bindings documentation
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: meson: add axg tdm interface DT bindings documentation
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
regulator: qcom_spmi: Indent with tabs instead of spaces
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
regulator: qcom_spmi: Fix warning Bad of_node_put()
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
regulator: qcom_spmi: Do not initialise static to NULL
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
regulator: qcom_spmi: Use correct regmap when checking for error
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
301 - 400 of 1786 matches
Mail list logo
