On Wed, Dec 12, 2018 at 05:41:29PM +1100, NeilBrown wrote:
>
> So you would substantially slow down the rhashtable_walk_start() step.
This whole thing is meant for uses such as /proc and netlink
enumeration. Speed is definitely not a prerogative of these
iterators.
For that matter, if speed was
Hi Mark,
Thank you for the review.
> SPDX headers need to be C++ comments - please make the entire comment
> block a C++ one so it looks more intentional.
I sent a new patch (v4) with the modified comment.
>> +#ifdef CONFIG_SUSPEND
>> +static int mcp16502_suspend(struct device *dev)
>> +{
>> +
Hello,
On Thu, Dec 06, 2018 at 01:41:31PM +, Vokáč Michal wrote:
> Normally the PWM output is held LOW when PWM is disabled. This can cause
> problems when inverted PWM signal polarity is needed. With this behavior
> the connected circuit is fed by 100% duty cycle instead of being shut-off.
>
On 12/12/18 at 12:12pm, Chao Fan wrote:
> On Wed, Dec 12, 2018 at 11:10:48AM +0800, Chao Fan wrote:
> >Introduce kstrtoull() from lib/kstrtox.c to boot directory so that code
> >in boot/ can use kstrtoull() and the old simple_strtoull() can be
> >replaced.
> >
>
> Hi all,
>
> Thanks for Boris,
scatterlist elements longer than 4GB sound odd. Please submit it
in a series with your actual user so that we can help figuring out
if it really makes sense or if there is a better way to solve your
problem.
As is this patch will massively increase the memory usage for all users
of struct
On Tue, Dec 11, 2018 at 01:59:03PM +, Andrew Murray wrote:
> On Tue, Dec 11, 2018 at 10:06:53PM +1100, Michael Ellerman wrote:
> > [ Reviving old thread. ]
> >
> > Andrew Murray writes:
> > > On Tue, Nov 20, 2018 at 10:31:36PM +1100, Michael Ellerman wrote:
> > >> Andrew Murray writes:
> >
On (12/12/18 01:48), Sasha Levin wrote:
> > > > I guess we still don't have a really clear understanding of what exactly
> > > is going in your system
> > >
> > > I would also like to get to the bottom of it. Unfortunately I haven't
> > > got the expertise in this area nor the time to do it yet.
On Wed, Dec 12, 2018 at 03:46:15PM +0800, Baoquan He wrote:
>On 12/12/18 at 11:10am, Chao Fan wrote:
>> Introduce kstrtoull() from lib/kstrtox.c to boot directory so that code
>
>It's not introducing kstrtoull(), just copying kstrtoull() from
>lib/kstrtox.c to boot.
Oops, maybe I misunderstand
> -Original Message-
> From: Andrey Smirnov [mailto:andrew.smir...@gmail.com]
> Sent: 2018年12月8日 7:57
> To: niklas.cas...@linaro.org
> Cc: Lucas Stach ; linux-...@vger.kernel.org; Bjorn
> Helgaas ; Chris Healy ;
> Leonard Crestez ; Aisheng Dong
> ; Richard Zhu ;
> dl-linux-imx ;
Hi Naga,
Naga Sureshkumar Relli wrote on Wed, 12 Dec 2018
05:27:03 +:
> Hi Boris & Miquel,
>
> An update to my comments on thread https://lkml.org/lkml/2018/11/15/656.
> In this I said, will take a default error count value as 16 and during page
> read, will check the error count
>
> -Original Message-
> From: devicetree-ow...@vger.kernel.org [mailto:devicetree-
> ow...@vger.kernel.org] On Behalf Of Yogesh Narayan Gaur
> Sent: Friday, November 16, 2018 4:44 PM
> To: linux-...@lists.infradead.org; boris.brezil...@bootlin.com;
> marek.va...@gmail.com;
On 2018/12/11 0:37, WANG Chao wrote:
Since commit 4cd24de3a098 ("x86/retpoline: Make CONFIG_RETPOLINE depend
on compiler support"), RETPOLINE has been replaced by CONFIG_RETPOLINE.
Fixes: 4cd24de3a098 ("x86/retpoline: Make CONFIG_RETPOLINE depend on compiler
support")
Signed-off-by: WANG
I encounter a case where crashkernel=384M, and kaslr is enabled. During the
test, sometimes, the system may fail to reserve region for crash kernel,
although there is much free space above 896MB. It is caused by the
truncation of the candidate region by kaslr kernel. It raises confusion to
the end
On 12/11/18 11:16 PM, Rob Herring wrote:
> On Tue, Nov 27, 2018 at 05:48:15PM +0100, Fabrice Gasnier wrote:
>> Some system control registers need to be clocked, so the registers can
>> be accessed. Add an optional clock.
>>
>> Signed-off-by: Fabrice Gasnier
>> ---
>>
On Tue, Dec 11, 2018 at 05:54:54PM -0700, Jeremy Fertic wrote:
> ADT7316_DA_EN_VIA_DAC_LDCA is set when the dac and ldac registers are being
> used to update the dacs instead of the ldac pin. ADT7516_SEL_AIN3 is an adc
> input that shares the ldac pin. Only set these bits if an ldac pin is not
>
Hi Jacob,
On 9/21/18 12:06 AM, Jacob Pan wrote:
> On Tue, 18 Sep 2018 16:24:51 +0200
> Eric Auger wrote:
>
>> From: Jacob Pan
>>
>> Device faults detected by IOMMU can be reported outside IOMMU
>> subsystem for further processing. This patch intends to provide
>> a generic device fault data
Hi Jisheng,
śr., 12 gru 2018 o 03:48 Jisheng Zhang napisał(a):
>
> Hi,
>
> On Tue, 11 Dec 2018 13:56:49 +0100 Marcin Wojtas wrote:
>
> > Recent changes in the mvneta driver reworked allocation
> > and handling of the ingress buffers to use entire pages.
> > Apart from that in SW BM scenario the
On Tue, Dec 11, 2018 at 05:54:56PM -0700, Jeremy Fertic wrote:
> @@ -651,10 +649,12 @@ static ssize_t adt7316_store_da_high_resolution(struct
> device *dev,
> u8 config3;
> int ret;
>
> + if (chip->id == ID_ADT7318 || chip->id == ID_ADT7519)
> + return -EPERM;
Reference to commit 58eb5b670747 ("pstore: fix crypto dependencies"),
which fixed crypto dependencies of deflate, lzo, lz4 and lz4hc
compression, but omitted 842 and newer compression zstd from
commit 1021bcf44d0e ("pstore: add zstd compression support")
Signed-off-by: liaoweixiong
---
On Wed, Dec 12, 2018 at 10:38:36AM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the pull request for 4.21 merge window below.
>
> The major changes are, the set_mode ops now takes 2 arguments (mode and
> submode) instead of just 'mode'. The value in 'submode' will be specific
On 11. 12. 18 12:01, Masahiro Yamada wrote:
> I guess this is a constant value instead of a symbol.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> I will apply this to my Kbuild tree
> because it is necessary for Kconfig clean-ups.
>
>
> arch/microblaze/Kconfig.platform | 2 +-
> 1 file
On Wed, Dec 12, 2018 at 12:02:52PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> MAINTAINERS
>
> between commit:
>
> cb4f131e1f2c ("MAINTAINERS: Patch monkey for the Hyper-V code")
>
> from the char-misc.current tree and
On Mon, Dec 10, 2018 at 8:37 PM Michal Hocko wrote:
>
[...]
>
> In other words. Does the following work? I am sorry to wildguess this
> way but I am not able to recreate your setups to play with this myself.
>
> diff --git a/arch/x86/mm/numa.c b/arch/x86/mm/numa.c
> index
On Tue, Dec 11, 2018 at 05:55:02PM -0700, Jeremy Fertic wrote:
> Based on the output of adt7316_show_all_DAC_update_modes() and
> adt7316_show_DAC_update_mode(), adt7316_store_DAC_update_mode() should
> expect the user to enter an integer input from 0 to 3. The user input is
> currently expected
Without this patch, if we have multi PCIe devices, and one of them has
AER error, aer_recover_work_func() -> kfifo_get() will traverse the whole
kfifo which has wrong element number(16).
If one null element's uninitialized memory matches another
PCIe device(:01:00.0), we may get the below call
An LSM doesn't get path information related to an access request to open
an inode. This new (internal) MAY_EXECMOUNT flag enables an LSM to
check if the underlying mount point of an inode is marked as executable.
This is useful to implement a security policy taking advantage of the
noexec mount
'commit ecae65e133f2 ("PCI/AER: Use kfifo_in_spinlocked() to
insert locked elements")' replace kfifo_put() with kfifo_in_spinlocked().
But as "kfifo_in(fifo, buf, n)" describes:
" * @n: number of elements to be added".
We want to insert only one element into kfifo, not "sizeof(entry) = 16".
Signed-off-by: Mickaël Salaün
Reviewed-by: Philippe Trébuchet
Reviewed-by: Thibaut Sautereau
Cc: Jonathan Corbet
Cc: Kees Cook
Cc: Mickaël Salaün
---
Documentation/admin-guide/LSM/Yama.rst | 41 ++
1 file changed, 41 insertions(+)
diff --git
On Tue, Dec 11, 2018 at 5:44 PM Michal Hocko wrote:
>
> On Tue 11-12-18 16:05:58, Pingfan Liu wrote:
> > On Mon, Dec 10, 2018 at 8:37 PM Michal Hocko wrote:
> > >
> > > On Fri 07-12-18 16:56:27, Michal Hocko wrote:
> > > > On Fri 07-12-18 22:27:13, Pingfan Liu wrote:
> > > > [...]
> > > > > diff
Hello,
I am Mr. Dorso Sandwidi from Burkina Faso in West African region. I
work with the bank of Africa here in the nation. I am writing you from
my office that which will be of an immense benefit to both of us. In
my department, being the account manager I discovered an abandoned sum
of $18
Hi,
The goal of this patch series is to control script interpretation. A
new O_MAYEXEC flag used by sys_open() is added to enable userland script
interpreter to delegate to the kernel (and thus the system security
policy) the permission to interpret scripts or other files containing
what can be
When the O_MAYEXEC flag is passed, sys_open() may be subject to
additional restrictions depending on a security policy implemented by an
LSM through the inode_permission hook.
The underlying idea is to be able to restrict scripts interpretation
according to a policy defined by the system
Enable to either propagate the mount options from the underlying VFS
mount to prevent execution, or to propagate the file execute permission.
This may allow a script interpreter to check execution permissions
before reading commands from a file.
The main goal is to be able to protect the kernel
Peter Chen writes:
>> >> >> +irqreturn_t ret = IRQ_NONE;
>> >> >> +unsigned long flags;
>> >> >> +u32 reg;
>> >> >> +
>> >> >> +priv_dev = cdns->gadget_dev;
>> >> >> +spin_lock_irqsave(_dev->lock, flags);
>> >> >
>> >> >you're already running in hardirq context. Why do you
Test propagation of noexec mount points or file executability through
files open with or without O_MAYEXEC.
Signed-off-by: Mickaël Salaün
Cc: Kees Cook
Cc: Mickaël Salaün
Cc: Shuah Khan
---
MAINTAINERS | 1 +
tools/testing/selftests/Makefile |
Hi Michael,
On Tue, Dec 11, 2018 at 02:53:24PM +0100, Michael Nazzareno Trimarchi wrote:
> Hi Jacopo
>
> On Tue, Dec 11, 2018 at 12:39 PM jacopo mondi wrote:
> >
> > Hi Michael,
> >
> > On Mon, Dec 10, 2018 at 10:45:02PM +0100, Michael Nazzareno Trimarchi wrote:
> > > Hi Jacopo
> > >
> > > Let's
On Tue, 11 Dec 2018 at 18:23, Rob Herring wrote:
>
> On Mon, Dec 10, 2018 at 3:30 AM Krzysztof Kozlowski wrote:
> >
> > Document new linux,trigger-pattern property for initialization of LED
> > pattern trigger.
> >
> > Signed-off-by: Krzysztof Kozlowski
> > ---
> >
Hi
On Wed, Dec 12, 2018 at 9:39 AM jacopo mondi wrote:
>
> Hi Michael,
>
> On Tue, Dec 11, 2018 at 02:53:24PM +0100, Michael Nazzareno Trimarchi wrote:
> > Hi Jacopo
> >
> > On Tue, Dec 11, 2018 at 12:39 PM jacopo mondi wrote:
> > >
> > > Hi Michael,
> > >
> > > On Mon, Dec 10, 2018 at
STM32 syscfg registers are accessed using syscon. It needs syscfg clock
to be enabled while accessing registers.
This adds support for optional clock on syscon, and the relevant clock
in stm32mp157 device tree.
Changes in v2:
- move clocks to specific bindings using syscon as per Rob's comment
STM32 syscfg needs a clock to access registers.
Signed-off-by: Fabrice Gasnier
---
arch/arm/boot/dts/stm32mp157c.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi
b/arch/arm/boot/dts/stm32mp157c.dtsi
index 8bf1c17..61b2a70 100644
---
Some system control registers need to be clocked, so the registers can
be accessed. Add an optional clock and attach it to regmap.
Signed-off-by: Fabrice Gasnier
---
drivers/mfd/syscon.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/mfd/syscon.c
On Wed, Dec 12 2018, Herbert Xu wrote:
> On Wed, Dec 12, 2018 at 05:41:29PM +1100, NeilBrown wrote:
>>
>> So you would substantially slow down the rhashtable_walk_start() step.
>
> This whole thing is meant for uses such as /proc and netlink
> enumeration. Speed is definitely not a prerogative
STM32 system configuration controller registers needs to be clocked.
Document clock support on stm32-syscon.
Signed-off-by: Fabrice Gasnier
---
Changes in v2:
- move clocks to specific bindings using syscon as per Rob's comment
---
Documentation/devicetree/bindings/arm/stm32/stm32-syscon.txt |
On Tue, Dec 11, 2018 at 11:12 PM Geert Uytterhoeven
wrote:
> CC Jacopo, who has an Ecovec24
Thanks Geert, Ecovec24 has the biggest boardfile (setup.c) of all the
Super-H boards, so I suppose it is simply the best supported board,
meaning if stuff works on Ecovec24 it is more likely to work with
>>> On 12.12.18 at 08:06, wrote:
> On Wed, Dec 05, 2018 at 09:01:33AM -0500, Boris Ostrovsky wrote:
>>On 12/5/18 4:32 AM, Roger Pau Monné wrote:
>>> On Wed, Dec 05, 2018 at 10:19:17AM +0800, Chao Gao wrote:
I find some pass-thru devices don't work any more across guest reboot.
Assigning
On Wed, Dec 12, 2018 at 09:43:23AM +0100, Michael Nazzareno Trimarchi wrote:
> Hi
>
> On Wed, Dec 12, 2018 at 9:39 AM jacopo mondi wrote:
> >
> > Hi Michael,
> >
> > On Tue, Dec 11, 2018 at 02:53:24PM +0100, Michael Nazzareno Trimarchi wrote:
> > > Hi Jacopo
> > >
> > > On Tue, Dec 11, 2018 at
On Mon, Dec 10, 2018 at 04:30:25PM +0300, Dmitry V. Levin wrote:
> On Mon, Dec 10, 2018 at 02:06:28PM +0100, Geert Uytterhoeven wrote:
> > On Mon, Dec 10, 2018 at 1:41 PM Dmitry V. Levin wrote:
> > > On Mon, Dec 10, 2018 at 09:45:42AM +0100, Geert Uytterhoeven wrote:
> > > > On Mon, Dec 10, 2018
Hi Felipe & Mathias,
It seems that my below reply mail failed to be shown on lkml.org.
So I have to resend it. Like to have your comment/suggestion before I begin
the
solution implement work. Thanks
Ran Wang wrote:
>
> Hello Felipe,
>
> Felipe Balbi wrote:
> >
> > Hi Ran,
> >
> > Ran
Hi Christoph,
On Sat, Dec 8, 2018 at 12:25 AM Christoph Hellwig wrote:
>
> Folks, can you take a look at this tree and see if this is useful
> for USB:
>
> http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-noncoherent-allocator
>
> The idea is that you use dma_alloc_attrs with
Hi Pingfan,
Thanks for fixing this.
On 12/12/18 at 04:19pm, Pingfan Liu wrote:
> I encounter a case where crashkernel=384M, and kaslr is enabled. During the
> test, sometimes, the system may fail to reserve region for crash kernel,
> although there is much free space above 896MB. It is caused by
Hi Dmitry,
On Wed, Dec 12, 2018 at 9:55 AM Dmitry V. Levin wrote:
> On Mon, Dec 10, 2018 at 04:30:25PM +0300, Dmitry V. Levin wrote:
> > On Mon, Dec 10, 2018 at 02:06:28PM +0100, Geert Uytterhoeven wrote:
> > > On Mon, Dec 10, 2018 at 1:41 PM Dmitry V. Levin wrote:
> > > > On Mon, Dec 10, 2018
Hi Miquel,
> -Original Message-
> From: Miquel Raynal [mailto:miquel.ray...@bootlin.com]
> Sent: Wednesday, December 12, 2018 1:42 PM
> To: Naga Sureshkumar Relli
> Cc: Boris Brezillon ; r...@kernel.org;
> rich...@nod.at; linux-
> ker...@vger.kernel.org; marek.va...@gmail.com;
On Mon, Dec 10, 2018 at 06:43:51PM +0100, Thomas Gleixner wrote:
> On Mon, 10 Dec 2018, Peter Zijlstra wrote:
> > On Mon, Dec 10, 2018 at 04:23:06PM +0100, Thomas Gleixner wrote:
> > There is another callers of futex_lock_pi_atomic(),
> > futex_proxy_trylock_atomic(), which is part of
On Wed, Dec 12, 2018 at 3:38 AM Thorsten Glaser wrote:
>
> Andy Lutomirski dixit:
>
> >That’s the thing, though: the whole generic kernel compat
> >infrastructure assumes there are at most two ABIs: native and, if
> >enabled and relevant, compat. x32 breaks this entirely.
>
> MIPS had o32, n32,
On Wed, Dec 12, 2018 at 12:42:52PM +0900, Sergey Senozhatsky wrote:
> Something like this (not tested):
>
> ---
>
> drivers/tty/serial/serial_core.c | 14 --
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/tty/serial/serial_core.c
>
On Tue, Dec 11, 2018 at 06:25:06PM -0800, Derek Basehore wrote:
> The function __lock_acquire checks that the nest lock is held passed
> in as an argument. The issue with this is that __lock_acquire is used
> for internal bookkeeping on lock_release. This produces a false
> positive lockdep
On Wed, Dec 12, 2018 at 05:57:02PM +0900, Tomasz Figa wrote:
> How about dma_sync_sg_*()? I'd expect some drivers to export/import
> such memory via sg, since that's the typical way of describing memory
> in DMA-buf.
The way it is implemented dma_sync_sg_* would just work, however there
really
Hi Naga,
Naga Sureshkumar Relli wrote on Wed, 12 Dec 2018
09:04:16 +:
> Hi Miquel,
>
> > -Original Message-
> > From: Miquel Raynal [mailto:miquel.ray...@bootlin.com]
> > Sent: Wednesday, December 12, 2018 1:42 PM
> > To: Naga Sureshkumar Relli
> > Cc: Boris Brezillon ;
Hi
On Wed, Dec 12, 2018 at 9:55 AM jacopo mondi wrote:
>
> On Wed, Dec 12, 2018 at 09:43:23AM +0100, Michael Nazzareno Trimarchi wrote:
> > Hi
> >
> > On Wed, Dec 12, 2018 at 9:39 AM jacopo mondi wrote:
> > >
> > > Hi Michael,
> > >
> > > On Tue, Dec 11, 2018 at 02:53:24PM +0100, Michael
On Wed, Nov 28, 2018 at 10:56:41AM -0300, Arnaldo Carvalho de Melo wrote:
SNIP
> LD /tmp/build/perf/libtraceevent-in.o
> MKDIR/tmp/build/perf/util/
> LINK /tmp/build/perf/libtraceevent.a
> CC /tmp/build/perf/util/block-range.o
> MKDIR/tmp/build/perf/arch/
>
On 12.12.2018 00:13, Rob Herring wrote:
> On Tue, Nov 27, 2018 at 11:57:25AM +, claudiu.bez...@microchip.com wrote:
>> From: Claudiu Beznea
>>
>> Add documentation for regulator modes and suspend states.
>>
>> Signed-off-by: Claudiu Beznea
>> ---
>>
As this apparently got merged despite no proper reviews from VFS
level persons:
NAK - the ioctl format that expects the verifycation hash in the file
data data with padding after the real data is simply not acceptable,
we can't just transform the data in the file itself based on a magic
calls
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
First off I'd like to request: Please don't break my userspace!
I have a number of systems running with x32-abi as native. They work
well, I've no want or desire to upgrade their memory or CPUs to make
keep them working as well as they do now.
On Wed, Dec 12, 2018 at 11:47:42AM +0530, Naresh Kamboju wrote:
> On Tue, 11 Dec 2018 at 21:25, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 4.19.9 release.
> > There are 118 patches in this series, all will be posted as a response
> > to this one. If
On Tue, 11 Dec 2018 at 15:20, Faiz Abbas wrote:
>
> The driver fetches a thermal zone using the string "cpu_thermal" for
> tuning operation. Add a note for the same.
>
> Signed-off-by: Faiz Abbas
Applied for next, thanks!
Kind regards
Uffe
> ---
>
+ Thermal maintainers
On Tue, 11 Dec 2018 at 15:20, Faiz Abbas wrote:
>
> Errata i929 in certain OMAP5/DRA7XX/AM57XX silicon revisions
> (SPRZ426D - November 2014 - Revised February 2018 [1]) mentions
> unexpected tuning pattern errors. A small failure band may be present
> in the tuning range
Fix a static code checker warning:
drivers/net/can/flexcan.c:1435 flexcan_setup_stop_mode() warn: passing zero to
'PTR_ERR'
Fixes: de3578c198c6 ("can: flexcan: add self wakeup support")
Signed-off-by: YueHaibing
---
drivers/net/can/flexcan.c | 2 +-
1 file changed, 1 insertion(+), 1
> >
> > Interrupt handler (hardirq context) at CPU0, and process at CPU1, eg
> > role switch, unload module, etc.
>
> the process at CPU1 would need to disable interrupts (spin_lock_irq() or
> spin_lock_irqsave()), not the hardirq on CPU0 as that already runs with
> interrrupts
> disabled.
>
The Power domains for corners just pass the performance state set by the
consumers to the RPM (Remote Power manager) which then takes care
of setting the appropriate voltage on the corresponding rails to
meet the performance needs.
We add all power domain data needed on msm8996 here. This driver
Add support for the .set_performace_state() and .opp_to_performance_state()
callbacks in the rpmpd driver.
Signed-off-by: Rajendra Nayak
Signed-off-by: Viresh Kumar
Reviewed-by: Ulf Hansson
---
drivers/soc/qcom/rpmpd.c | 44
1 file changed, 44
Hi Firoz,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.20-rc6]
[cannot apply to next-20181211]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Marcin,
On Wed, 12 Dec 2018 09:22:57 +0100 Marcin Wojtas wrote:
> Hi Jisheng,
>
> śr., 12 gru 2018 o 03:48 Jisheng Zhang
> napisał(a):
> >
> > Hi,
> >
> > On Tue, 11 Dec 2018 13:56:49 +0100 Marcin Wojtas wrote:
> >
> > > Recent changes in the mvneta driver reworked allocation
> > > and
Add DT bindings to describe the rpm/rpmh power domains found on Qualcomm
Technologies, Inc. SoCs. These power domains communicate a performance
state to RPM/RPMh, which then translates it into corresponding voltage on a
PMIC rail.
Signed-off-by: Rajendra Nayak
Signed-off-by: Viresh Kumar
On Qualcomm Technologies, Inc. platforms, an OPP node needs
to describe an additional level/corner value that is then communicated
to a remote microprocessor by the CPU, which then takes some
actions (like adjusting voltage values across various rails)
based on the value passed.
Describe these
Add rpmpd device node and its OPP table
Signed-off-by: Rajendra Nayak
Signed-off-by: Viresh Kumar
Reviewed-by: Ulf Hansson
Reviewed-by: Stephen Boyd
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 34 +++
1 file changed, 34 insertions(+)
diff --git
The RPMh power domain driver aggregates the corner votes from various
consumers for the ARC resources and communicates it to RPMh.
With RPMh we use 2 different numbering space for corners, one used
by the clients to express their performance needs, and another used
to communicate to RPMh
Specify the active + sleep and active-only MX power domains as
the parents of the corresponding CX power domains. This will ensure that
performance state requests on CX automatically generate equivalent requests
on MX power domains.
This is used to enforce a requirement that exists for various
Now that we have atleast 2 genpd providers, both using a simple
routine to read a performance state value from device tree and
return it, in order to implement the .opp_to_performance_state
callback, add a simple_opp_to_performance_state() helper to do
it, so it can be resued across all such genpd
Add the DT node for the rpmhpd powercontroller.
Signed-off-by: Rajendra Nayak
Acked-by: Viresh Kumar
Reviewed-by: Stephen Boyd
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 51
1 file changed, 51 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
On Wed, Dec 12, 2018 at 6:29 AM Sinan Kaya wrote:
>
> Now that we allow CONFIG_PCI to be unset, remove useless code from ACPICA
> too.
>
> Signed-off-by: Sinan Kaya
> ---
> drivers/acpi/acpica/Makefile | 2 +-
> drivers/acpi/osl.c | 9 +
> 2 files changed, 10 insertions(+), 1
Get rid of the duplicate code across rpmpd and rpmhpd to read the
performance state value from Device tree and use the
simple_opp_to_performance_state() helper instead.
Suggested-by: Stephen Boyd
Signed-off-by: Rajendra Nayak
Reviewed-by: Stephen Boyd
---
drivers/soc/qcom/rpmhpd.c | 11
Changes in v7:
* Rebased on Andy's for-next, and used the updated cmd_db_read_aux_data()
* Other minor fixes, all in 'PATCH 06/10' as suggested by Stephen
Changes in v6:
* OPP binding updates for qcom,level reviewed by Rob
* DT bindings for rpmpd and rpmhpd updated to specify the
OPP tables as
On Wed, Dec 12, 2018 at 10:01:29AM +0100, Geert Uytterhoeven wrote:
> Hi Dmitry,
>
> On Wed, Dec 12, 2018 at 9:55 AM Dmitry V. Levin wrote:
> > On Mon, Dec 10, 2018 at 04:30:25PM +0300, Dmitry V. Levin wrote:
> > > On Mon, Dec 10, 2018 at 02:06:28PM +0100, Geert Uytterhoeven wrote:
> > > > On
Hi Elvira,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.20-rc6]
[cannot apply to next-20181211]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Russell, Baruch,
On Tue, Dec 11, 2018 at 06:51:56PM +, Russell King - ARM Linux wrote:
> On Tue, Dec 11, 2018 at 07:53:42PM +0200, Baruch Siach wrote:
> > That is, something like this, right?
> >
> > diff --git a/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
> >
On Wed, Dec 12, 2018 at 6:29 AM Sinan Kaya wrote:
>
> Getting ready to allow PCI to be disabled with ACPI enabled. Stub out
> acpi_os_read_pci_configuration function that depend on PCI.
>
> Signed-off-by: Sinan Kaya
> ---
> drivers/acpi/osl.c | 4
> 1 file changed, 4 insertions(+)
>
> diff
Hi Stefan,
On Tue, Dec 11, 2018 at 09:11:31PM +, Stefan Chulski wrote:
>
> >
> > Are these modes supported on anything except port 0? If not, you should be
> > rejecting these, rather than just treating them as RGMII.
>
> In CP115(which has PPv2) PHY_INTERFACE_MODE_10GKR supported on
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git
tags/fuse-fixes-4.20-rc7
There's one patch fixing a minor but long lived bug, the others are fixing
regressions introduced in this cycle.
Thanks,
Miklos
Changes in v6:
modifications according to comments from Rob/Andrew/Sean:
1. use delay_ps instead of delay stage.
2. add comments in driver to avoid confusion.
2. rewrite set_delay function.
3. modify binding document for properties: tx-delay-ps/rx-delay-ps/pericfg etc.
Biao Huang (2):
Add Ethernet support for MediaTek SoCs from the mt2712 family
Signed-off-by: Biao Huang
---
drivers/net/ethernet/stmicro/stmmac/Kconfig|8 +
drivers/net/ethernet/stmicro/stmmac/Makefile |1 +
.../net/ethernet/stmicro/stmmac/dwmac-mediatek.c | 408
3
The commit adds the device tree binding documentation for the MediaTek DWMAC
found on MediaTek MT2712.
Signed-off-by: Biao Huang
---
.../devicetree/bindings/net/mediatek-dwmac.txt | 87
1 file changed, 87 insertions(+)
create mode 100644
If a server side socket is bound to an address, but not in the listening
state yet, incoming connection requests should receive a reset control
packet in response. However, the function used to send the reset
silently drops the reset packet if the sending socket isn't bound
to a remote address (as
On Wed, Dec 12, 2018 at 6:09 PM Christoph Hellwig wrote:
>
> On Wed, Dec 12, 2018 at 05:57:02PM +0900, Tomasz Figa wrote:
> > How about dma_sync_sg_*()? I'd expect some drivers to export/import
> > such memory via sg, since that's the typical way of describing memory
> > in DMA-buf.
>
> The way
On Tue, Dec 11, 2018 at 02:26:45PM +0100, Michal Hocko wrote:
> From: Michal Hocko
>
> Liu Bo has experienced a deadlock between memcg (legacy) reclaim and the
> ext4 writeback
> task1:
> [] wait_on_page_bit+0x82/0xa0
> [] shrink_page_list+0x907/0x960
> [] shrink_inactive_list+0x2c7/0x680
> []
Hi Dmitry,
On Wed, Dec 12, 2018 at 10:27 AM Dmitry V. Levin wrote:
> On Wed, Dec 12, 2018 at 10:01:29AM +0100, Geert Uytterhoeven wrote:
> > On Wed, Dec 12, 2018 at 9:55 AM Dmitry V. Levin wrote:
> > > On Mon, Dec 10, 2018 at 04:30:25PM +0300, Dmitry V. Levin wrote:
> > > > On Mon, Dec 10, 2018
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git
tags/ovl-fixes-4.20-rc7
Needed to revert a patch, because it possibly introduces a security hole.
Since the patch is basically a conceptual cleanup, not a bug fix, it's safe
to revert. I'm not giving
Hello,
syzbot found the following crash on:
HEAD commit:14cf8c1d5b90 Add linux-next specific files for 20181210
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=133296db40
kernel config: https://syzkaller.appspot.com/x/.config?x=c9133d0a4284c012
On Tue, Dec 11, 2018 at 10:51:48AM +0100, Rafael J. Wysocki wrote:
> On Mon, Dec 10, 2018 at 11:51 PM Peter Zijlstra wrote:
> > Dunno; it could be cold cachelines, at which point it can be fairly
> > expensive. Also, being stuck with API is fairly horrible if you want to
> > 'fix' it.
>
> All
Hi Will,
On Fri, Oct 12, 2018 at 11:37 AM Vivek Gautam
wrote:
>
>
>
> On 10/12/2018 3:46 AM, Rob Herring wrote:
> > On Thu, 11 Oct 2018 15:19:29 +0530, Vivek Gautam wrote:
> >> Qcom's implementation of arm,mmu-500 works well with current
> >> arm-smmu driver implementation. Adding a soc specific
On 11/12/2018 17:58, Rob Herring wrote:
> On Mon, Dec 10, 2018 at 7:22 AM Neil Armstrong
> wrote:
>>
>> The Amlogic ARM Mali Midgard requires reset controls to power on and
>> software reset the GPU, adds these as optional in the bindings.
>>
>> Signed-off-by: Neil Armstrong
>> ---
>>
1 - 100 of 1315 matches
Mail list logo
