On Mon, 15 Apr 2019, Enric Balletbo i Serra wrote:
> On 12/4/19 9:18, Pi-Hsun Shih wrote:
> > System Companion Processor (SCP) is Cortex M4 co-processor on some
> > MediaTek platform that can run EC-style firmware. Since a SCP and EC
> > would both exist on a system, and use the cros_ec_dev driver,
On 4/24/19 5:28 PM, Fabien Dessenne wrote:
> During probe, return the "get_irq" error value instead of -ENOENT. This
> allows the driver to be deferred probed if needed.
>
> Signed-off-by: Fabien Dessenne
Acked-by: Olivier Moysan
> ---
> sound/soc/stm/stm32_i2s.c | 5 +++--
> 1 file chang
On Thu, Apr 25, 2019 at 09:33:48AM +0200, Peter Zijlstra wrote:
> > Let me explain the bug more specific:
> >
> > the bug ONLY matters in following situation:
> >
> > #. more than one cpu (assume cpu A and B) doing ll/sc on same shared
> > var V
> >
> > #. speculative memory access from A cause
On Mon, Apr 22, 2019 at 12:45:39PM +0800, Kai-Heng Feng wrote:
> Commit a939bb57cd47 ("pinctrl: intel: implement gpio_irq_enable") was
> added because clearing interrupt status bit is required to avoid
> unexpected behavior.
>
> Turns out the unmask callback also needs the fix, which can solve wei
On Thu, 11 Apr 2019, Heiko Stuebner wrote:
> Hi Lee,
>
> Am Dienstag, 2. April 2019, 08:33:05 CEST schrieb Lee Jones:
> > On Wed, 02 Jan 2019, Tony Xie wrote:
> >
> > > The RK809 and RK817 are a Power Management IC (PMIC) for multimedia
> > > and handheld devices. They contains the following com
On Thu, Apr 25, 2019 at 09:33:48AM +0200, Peter Zijlstra wrote:
> > Let me explain the bug more specific:
> >
> > the bug ONLY matters in following situation:
> >
> > #. more than one cpu (assume cpu A and B) doing ll/sc on same shared
> > var V
> >
> > #. speculative memory access from A cause
* Ingo Molnar wrote:
> Third, beyond readability there's another advantage of my suggested
> approach as well: for example that way we could verify the passed in
> length with the patchlet length. Right now it's completely unverified:
>
> case PARAVIRT_PATCH(ops.m):
Use #hwlock-cells value to define whether the locks can be shared
by several users.
Signed-off-by: Fabien Dessenne
Reviewed-by: Rob Herring
---
.../devicetree/bindings/hwlock/hwlock.txt | 27 --
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git a/Document
>-Original Message-
>From: owner-linux...@kvack.org [mailto:owner-linux...@kvack.org] On
>Behalf Of Michal Hocko
>Sent: Thursday, April 25, 2019 4:43 PM
>To: Du, Fan
>Cc: a...@linux-foundation.org; Wu, Fengguang ;
>Williams, Dan J ; Hansen, Dave
>; xishi.qiuxi...@alibaba-inc.com; Huang,
On Thu 2019-04-25 15:43:21, Sergey Senozhatsky wrote:
> On (04/25/19 12:52), Sergey Senozhatsky wrote:
> > > Could we remove it in this patch? It touches it indirectly anyway.
> >
> > Sure we can.
> >
> > We also can take extra care of pr_info("%sconsole [%s%d] enabled\n".
> > Right now we do
> >
* Peter Zijlstra wrote:
> > I think these open-coded hexa versions are somewhat fragile as well, how
> > about putting these into a .S file and controlling the sections in an LTO
> > safe manner there?
> >
> > That will also allow us to write proper asm, and global labels can be
> > used to
On Thu, Apr 25, 2019 at 11:17:17AM +0200, Ingo Molnar wrote:
> It basically means that we silently won't do any patching and the kernel
> will crash later on in mysterious ways, because paravirt patching is
> usually relied on.
That's OK. The compiler emits an indirect CALL/JMP to the pv_ops
str
hi Ulf
On 4/23/19 3:39 PM, Ulf Hansson wrote:
On Tue, 5 Mar 2019 at 17:10, Ludovic Barre wrote:
From: Ludovic Barre
The busy status bit could occurred even if no busy response is
expected (example cmd11). On sdmmc variant, the busy_detect_flag
reflects inverted value of d0 state, it's sampl
On Tue, 2019-04-23 at 22:32 +0800, Muchun Song wrote:
> There is a race condition between removing glue directory and adding a new
> device under the glue directory. It can be reproduced in following test:
>
.../...
> In order to avoid this happening, we we should not call kobject_del() on
> pa
On Wed, Apr 24, 2019 at 12:00:05PM -0700, Nathan Chancellor wrote:
> On Wed, Apr 24, 2019 at 11:49:37AM -0700, Nick Desaulniers wrote:
> > On Wed, Apr 24, 2019 at 11:34 AM Nathan Chancellor
> > wrote:
> > >
> > > Clang warns:
> > >
> > > drivers/thunderbolt/tunnel.c:504:17: warning: implicit trunc
Hello,
Some time ago, after upgrading the Kernel on our i.MX6Q-based boards to
mainline 4.18, and now to LTS 4.19 line, during stress tests we started
noticing strange warnings coming from 'read' syscall, when page_copy_sane()
check failed. Typical reproducibility is up to ~4 events per 24h. Wa
On Tue, Apr 16, 2019 at 09:34:51PM -0400, Sasha Levin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>
> Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>
> are available in the Git repository at:
>
> git
Le jeu. 25 avr. 2019 à 10:45, Benjamin Tissoires
a écrit :
>
> On Thu, Apr 25, 2019 at 10:25 AM Clément VUCHENER
> wrote:
> >
> > Le jeu. 25 avr. 2019 à 09:40, Benjamin Tissoires
> > a écrit :
> > >
> > > Hi Clément,
> > >
> > > On Wed, Apr 24, 2019 at 5:34 PM Clément VUCHENER
> > > wrote:
> >
On Wed, Apr 17, 2019 at 06:27:58PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the updated pull request for 5.1 -rc.
>
> I've removed the lengthy ti-pipe3 PHY driver changes to follow the TRM
> sequence. This will be included in 5.2 -rc1 pull request.
>
> I've also added an a
I have a business of $11.5million U.S.Dollar I want to discuss with you
On Thu, Apr 25, 2019 at 11:29 AM Clément VUCHENER
wrote:
>
> Le jeu. 25 avr. 2019 à 10:45, Benjamin Tissoires
> a écrit :
> >
> > On Thu, Apr 25, 2019 at 10:25 AM Clément VUCHENER
> > wrote:
> > >
> > > Le jeu. 25 avr. 2019 à 09:40, Benjamin Tissoires
> > > a écrit :
> > > >
> > > > Hi Clément,
Hi,
Here is another attempt to get some benefit out of the sched-idle
policy. The previous version [1] focused on getting better power numbers
and this version tries to get better performance or lower response time
for the tasks.
The first patch is unchanged from v1 and accumulates
information ab
On (04/25/19 16:56), Sergey Senozhatsky wrote:
> > Great idea!
> >
> > It would deserve a separate patch that moves the pr_info()
> > and removes the invalid comment.
> >
> > Actually, the pr_info() would deserve a comment explaining
> > why it should be called before console_unlock().
>
> Good.
Start tracking how many tasks with SCHED_IDLE policy are present in each
cfs_rq. This will be used by later commits.
Signed-off-by: Viresh Kumar
---
kernel/sched/fair.c | 14 --
kernel/sched/sched.h | 2 ++
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/kernel/sche
"Gustavo A. R. Silva" writes:
> Hi all,
>
> Friendly ping:
>
> Who can take this?
It's in my queue.
--
Kalle Valo
We target for an idle CPU in select_idle_sibling() to run the next task,
but in case we don't find idle CPUs it is better to pick a CPU which
will run the task the soonest, for performance reason. A CPU which isn't
idle but has only SCHED_IDLE activity queued on it should be a good
target based on
On Thu, Apr 25, 2019 at 10:19 AM Life is hard, and then you die
wrote:
>
>
> Hi Benjamin,
>
> Thank you for looking at this.
>
> On Wed, Apr 24, 2019 at 04:18:23PM +0200, Benjamin Tissoires wrote:
> > On Mon, Apr 22, 2019 at 5:13 AM Ronald Tschalär
> > wrote:
> > >
> > > The iBridge device pro
Good morning kernel hackers,
we are a small company in Switzerland running some IPv6 only
networks. The systems in the IPv6 only networks do not need any IPv4
support anymore and thus for switches/routers we turned the support off.
Today we tried to turn off IPv4 in the Linux kernel at compile
On 25-04-19, 11:04, Ulf Hansson wrote:
> When genpd fails to attach a device to one of its multiple PM domains, we
> end up calling driver_deferred_probe_check_state() for the recently
> allocated virtual device. This is wrong, as it's the base device that is
> being probed. Fix this, by passing al
On 25-04-19, 11:04, Ulf Hansson wrote:
> Both genpd_alloc_dev_data() and genpd_add_device(), whom are internal genpd
> functions, allows a struct gpd_timing_data *td to be passed as an
> in-parameter. However, as NULL is always passed, let's just drop the
> in-parameter altogether.
>
> Signed-off-
On Wed, Apr 24, 2019 at 02:47:59PM -0700, Atish Patra wrote:
> nosmp command line option sets max_cpus to zero. No secondary harts
> will boot if this is enabled. But present cpu mask will still point to
> all possible masks.
>
> Fix present cpu mask for nosmp usecase.
>
> Signed-off-by: Atish Patr
Hi,
On Fri, Mar 8, 2019 at 6:11 AM Kai-Heng Feng
wrote:
>
> Commit 71f6fa90a353 ("HID: increase maximum global item tag report size
> to 256") increases the max report size from 128 to 256.
>
> We also need to update the report size in hid_field_extract() otherwise
> it complains and truncates n
On 25-04-19, 11:04, Ulf Hansson wrote:
> While attaching/detaching a device to a PM domain (genpd) that has the
> GENPD_FLAG_CPU_DOMAIN set, genpd iterates the cpu_possible_mask to check
> whether the device corresponds to a CPU. This iteration is done while
> holding the genpd's lock, which is unn
On 25-04-19, 11:04, Ulf Hansson wrote:
> Attaching a device via genpd_dev_pm_attach_by_id|name() makes genpd to
> allocate a virtual device that it attaches instead. This leads to a problem
> in case the base device belongs to a CPU. More precisely, it means
> genpd_get_cpu() compares against the v
From: Yogesh Gaur
Increase size of cmux_to_group array, to accomdate entry of
-1 termination.
Added -1, terminated, entry for 4080_cmux_grpX.
Signed-off-by: Yogesh Gaur
Signed-off-by: Vabhav Sharma
Acked-by: Scott Wood
Acked-by: Stephen Boyd
---
Changes for v2:
- Incorporated review comment
From: Yogesh Gaur
Add clockgen support for lx2160a.
Added entry for compat 'fsl,lx2160a-clockgen'.
Signed-off-by: Tang Yuantian
Signed-off-by: Yogesh Gaur
Signed-off-by: Vabhav Sharma
Acked-by: Scott Wood
Acked-by: Stephen Boyd
Acked-by: Viresh Kumar
---
Changes for v2:
- Subject line upda
Alexander Shishkin writes:
> Hi Greg,
Hi Greg,
This seems to have fallen through the cracks. Unless you picked it up
already, should I resend these as a part of my pull request for v5.2
instead? Both fixes are not v5.1 specific and will have to go to stable
either way.
Regards,
--
Alex
Alexander Shishkin writes:
> Alexander Shishkin writes:
>
>> Hi Greg,
>
> Hi Greg,
>
> This seems to have fallen through the cracks. Unless you picked it up
> already, should I resend these as a part of my pull request for v5.2
> instead? Both fixes are not v5.1 specific and will have to go to s
* Peter Zijlstra wrote:
> On Thu, Apr 25, 2019 at 11:17:17AM +0200, Ingo Molnar wrote:
> > It basically means that we silently won't do any patching and the kernel
> > will crash later on in mysterious ways, because paravirt patching is
> > usually relied on.
>
> That's OK. The compiler emit
On Wed, Apr 24, 2019 at 4:23 PM Christoph Hellwig wrote:
>
> On Wed, Apr 24, 2019 at 12:45:56PM +, Gary Guo wrote:
> > The RISC-V privileged spec is explicitly designed to allow the
> > techniques described above (this is the sole purpose of MSTATUS.TVM). It
> > might be as high performance as
* Aubrey Li wrote:
> On Wed, Apr 24, 2019 at 10:00 PM Julien Desfossez
> wrote:
> >
> > On 24-Apr-2019 09:13:10 PM, Aubrey Li wrote:
> > > On Wed, Apr 24, 2019 at 12:18 AM Vineeth Remanan Pillai
> > > wrote:
> > > >
> > > > Second iteration of the core-scheduling feature.
> > > >
> > > > This
On Thu, Apr 25, 2019 at 11:04 AM Ulf Hansson wrote:
>
> Recently genpd was extended to cope with devices belonging to CPUs. However,
> attaching CPU devices via genpd_dev_pm_attach_by_id|name() doesn't work,
> because of the virtual device that genpd allocates in this path.
>
> In this series, thi
On Thu, Apr 25, 2019 at 12:48:11PM +0300, Alexander Shishkin wrote:
> Alexander Shishkin writes:
>
> > Hi Greg,
>
> Hi Greg,
>
> This seems to have fallen through the cracks. Unless you picked it up
> already, should I resend these as a part of my pull request for v5.2
> instead? Both fixes are
On Wed, Apr 24, 2019 at 02:48:00PM -0700, Atish Patra wrote:
> If nr_cpus command line option is set, maximum possible cpu should be
> set to that value.
>
> Signed-off-by: Atish Patra
> Reviewed-by: Christoph Hellwig
FWIW,
Reviewed-by: Sudeep Holla
--
Regards,
Sudeep
Replace the indirection through struct stack_trace with an invocation of
the storage array based interface.
Signed-off-by: Thomas Gleixner
---
kernel/latencytop.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
--- a/kernel/latencytop.c
+++ b/kernel/latencytop.c
@@ -1
On Fri 19-04-19 13:46:01, Chengguang Xu wrote:
> We need to check return code only when calling ->read_dqblk(),
> so fix it properly.
>
> Signed-off-by: Chengguang Xu
Thanks. Added to my tree.
Honza
> ---
> fs/quota/dquot.c | 7 +
From: Kirill Smelkov
> Sent: 24 April 2019 19:30
>
> On Wed, Apr 24, 2019 at 10:26:55AM -0700, Linus Torvalds wrote:
> > On Wed, Apr 24, 2019 at 10:19 AM Sasha Levin wrote:
> > >
> > > Hm, I might be confusing something here but I see a bunch of patches
> > > that convert existing callers mention
On Thu, Apr 25, 2019 at 11:48 AM Vabhav Sharma wrote:
>
> From: Yogesh Gaur
>
> Add clockgen support for lx2160a.
> Added entry for compat 'fsl,lx2160a-clockgen'.
Well, if I'm expected to apply this, the above is a bit terse.
It looks like the patch makes the qoriq-cpufreq driver handle some ne
The indirection through struct stack_trace is not necessary at all. Use the
storage array based interface.
Signed-off-by: Thomas Gleixner
Tested-by: Tom Zanussi
Reviewed-by: Tom Zanussi
Acked-by: Steven Rostedt (VMware)
---
kernel/trace/trace_events_hist.c | 12 +++-
1 file changed,
Hi Lee,
On 25/4/19 11:06, Lee Jones wrote:
> On Mon, 15 Apr 2019, Enric Balletbo i Serra wrote:
>> On 12/4/19 9:18, Pi-Hsun Shih wrote:
>>> System Companion Processor (SCP) is Cortex M4 co-processor on some
>>> MediaTek platform that can run EC-style firmware. Since a SCP and EC
>>> would both exi
Hi Jacob,
On 4/24/19 1:31 AM, Jacob Pan wrote:
> Make use of generic IOASID code to manage PASID allocation,
> free, and lookup.
>
> Signed-off-by: Jacob Pan
> ---
> drivers/iommu/Kconfig | 1 +
> drivers/iommu/intel-iommu.c | 9 -
> drivers/iommu/intel-pasid.c | 36
On Wed, 24 Apr 2019 at 22:48, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.179 release.
> There are 168 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
On Thu, 25 Apr 2019 at 11:22, Ludovic BARRE wrote:
>
> hi Ulf
>
> On 4/23/19 3:39 PM, Ulf Hansson wrote:
> > On Tue, 5 Mar 2019 at 17:10, Ludovic Barre wrote:
> >>
> >> From: Ludovic Barre
> >>
> >> The busy status bit could occurred even if no busy response is
> >> expected (example cmd11). On
On Thu, 25 Apr 2019 at 11:56, Rafael J. Wysocki wrote:
>
> On Thu, Apr 25, 2019 at 11:04 AM Ulf Hansson wrote:
> >
> > Recently genpd was extended to cope with devices belonging to CPUs. However,
> > attaching CPU devices via genpd_dev_pm_attach_by_id|name() doesn't work,
> > because of the virtu
Change in V3:
[PATCH v3 1/4]: Correct description
[PATCH v3 2/4]: Use an SPDX tag instead.
[PATCH v3 3/4]: Use an SPDX tag instead,
parent_rate might overflow and fix it.
fix up the checkpatch warning.
add more CMPOSITE_xxx_HALFdiv.
Change in V2:
[PA
PX30 SOC has two Temperature Sensors for CPU and GPU.
Signed-off-by: Elaine Zhang
---
drivers/thermal/rockchip_thermal.c | 38 ++
1 file changed, 38 insertions(+)
diff --git a/drivers/thermal/rockchip_thermal.c
b/drivers/thermal/rockchip_thermal.c
index 03ff
Add a new compatible for thermal founding on PX30 SoCs.
Signed-off-by: Elaine Zhang
Acked-by: Daniel Lezcano
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/thermal/rockchip-thermal.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/thermal
Explicitly use the pinctrl to set/unset the right mode
instead of relying on the pinctrl init mode.
And it requires setting the tshut polarity before select pinctrl.
When the temperature sensor mode is set to 0, it will automatically
reset the board via the Clock-Reset-Unit (CRU) if the over tempe
1. add pinctrl control.
2. support PX30 soc
change in V2:
PATCH V2 1/3: keep tshut_mode TSHUT_MODE_GPIO;
In case of pinctrl get or lookup error, just bail out;
No need to use the thermal_pinctrl_select_otp/gpio wrappers,
just replace them with:
PATCH V2 2/
On 25.04.19 03:50, Li, Aubrey wrote:
>>> +>>> +config PROC_PID_ARCH_STATUS>>> + bool "Enable
/proc//arch_status file" Why is this switchable? x86 selects it
if PROC_FS is enabled and all other>> architectures are absolutely not
interested in this.> > Above and this, I was trying to avoid
On Thu, Apr 25, 2019 at 11:24:55AM +0530, Yash Shah wrote:
> Add device tree bindings for SiFive FU540 L2 cache controller driver
>
> Signed-off-by: Yash Shah
> ---
> .../devicetree/bindings/riscv/sifive-l2-cache.txt | 53
> ++
> 1 file changed, 53 insertions(+)
> create m
On Thu, Apr 25, 2019 at 12:11 PM Ulf Hansson wrote:
>
> On Thu, 25 Apr 2019 at 11:56, Rafael J. Wysocki wrote:
> >
> > On Thu, Apr 25, 2019 at 11:04 AM Ulf Hansson wrote:
> > >
> > > Recently genpd was extended to cope with devices belonging to CPUs.
> > > However,
> > > attaching CPU devices v
It does not make sense to only get value from pll->base and assign
to a local variable when recalc_rate.
Signed-off-by: Peng Fan
---
drivers/clk/imx/clk-pll14xx.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/clk/imx/clk-pll14xx.c b/drivers/clk/imx/clk-pll14xx
On Thu, 25 Apr 2019 at 11:45, Viresh Kumar wrote:
>
> On 25-04-19, 11:04, Ulf Hansson wrote:
> > While attaching/detaching a device to a PM domain (genpd) that has the
> > GENPD_FLAG_CPU_DOMAIN set, genpd iterates the cpu_possible_mask to check
> > whether the device corresponds to a CPU. This ite
> -Original Message-
> From: Rafael J. Wysocki
> Sent: 2019年4月25日 18:04
> To: Vabhav Sharma
> Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
> linux...@vger.kernel.org; sb...@kernel.org; mturque...@baylibre.com;
> r...@rjwysocki.net; viresh.ku...@linaro.org; Yogesh Narayan
On 25-04-19, 11:04, Ulf Hansson wrote:
> While attaching/detaching a device to a PM domain (genpd) that has the
> GENPD_FLAG_CPU_DOMAIN set, genpd iterates the cpu_possible_mask to check
> whether the device corresponds to a CPU. This iteration is done while
> holding the genpd's lock, which is unn
On Thu, 25 Apr 2019 at 12:14, Rafael J. Wysocki wrote:
>
> On Thu, Apr 25, 2019 at 12:11 PM Ulf Hansson wrote:
> >
> > On Thu, 25 Apr 2019 at 11:56, Rafael J. Wysocki wrote:
> > >
> > > On Thu, Apr 25, 2019 at 11:04 AM Ulf Hansson
> > > wrote:
> > > >
> > > > Recently genpd was extended to cop
On Thu, Apr 25, 2019 at 11:24:56AM +0530, Yash Shah wrote:
> The driver currently supports only SiFive FU540-C000 platform.
>
> The initial version of L2 cache controller driver includes:
> - Initial configuration reporting at boot up.
> - Support for ECC related functionality.
>
> Signed-off-by:
On 2019年04月25日 15:07, Ingo Molnar wrote:
Thanks for the review.
* Zhao Yakui wrote:
When ACRN hypervisor is detected, the hypercall is needed so that the
ACRN guest can query/config some settings. For example: it can be used
to query the resources in hypervisor and manage the CPU/memory/d
On Wed, Apr 24, 2019 at 09:55:37AM -0700, Kees Cook wrote:
> Clang's integrated assembler does not allow assembly macros defined
> in one inline asm block using the .macro directive to be used across
> separate asm blocks. LLVM developers consider this a feature and not a
> bug, recommending code r
On Thu, Apr 25, 2019 at 11:50:39AM +0200, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
> > On Thu, Apr 25, 2019 at 11:17:17AM +0200, Ingo Molnar wrote:
> > > It basically means that we silently won't do any patching and the kernel
> > > will crash later on in mysterious ways, because paravi
On 04/24, Paul E. McKenney wrote:
>
> * Must be invoked within some flavor of RCU read-side critical section.
>
> Does that work for you?
Thanks!
Oleg.
On Thu, Apr 25, 2019 at 12:15 PM Andy Tang wrote:
>
>
> > -Original Message-
> > From: Rafael J. Wysocki
> > Sent: 2019年4月25日 18:04
> > To: Vabhav Sharma
> > Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
> > linux...@vger.kernel.org; sb...@kernel.org; mturque...@baylibre.c
On Thu, Apr 25, 2019 at 11:32:38AM +0200, Nico Schottelius wrote:
> running some IPv6 only
> networks. The systems in the IPv6 only networks do not need any IPv4
> support anymore and thus for switches/routers we turned the support off.
> Today we tried to turn off IPv4 in the Linux kernel at comp
On Thu, Apr 25, 2019 at 12:17 PM Ulf Hansson wrote:
>
> On Thu, 25 Apr 2019 at 12:14, Rafael J. Wysocki wrote:
> >
> > On Thu, Apr 25, 2019 at 12:11 PM Ulf Hansson wrote:
> > >
> > > On Thu, 25 Apr 2019 at 11:56, Rafael J. Wysocki wrote:
> > > >
> > > > On Thu, Apr 25, 2019 at 11:04 AM Ulf Hans
The help describing the memory model selection is outdated. It still says
that SPARSEMEM is experimental and DISCONTIGMEM is a preferred over
SPARSEMEM.
Update the help text for the relevant options:
* add a generic help for the "Memory Model" prompt
* add description for FLATMEM
* reduce the desc
On 25/04/2019 10:41, Long Cheng wrote:
> Add SW and HW follow control function.
Can you please explain a bit more what you are doing in this patch.
You change the setting of the registers for different baud rates. Please
elaborate what is happening there.
>
> Signed-off-by: Long Cheng
> ---
On 24.04.19 23:18, Thomas Gleixner wrote:
Hi,
>> +config PROC_PID_ARCH_STATUS
>> +bool "Enable /proc//arch_status file"
>
> Why is this switchable? x86 selects it if PROC_FS is enabled and all other
> architectures are absolutely not interested in this.
IMHO, it's good to have a switch, but
On 2019/4/25 18:11, Enrico Weigelt, metux IT consult wrote:
> On 25.04.19 03:50, Li, Aubrey wrote:
>
+>>> +config PROC_PID_ARCH_STATUS>>> + bool "Enable
> /proc//arch_status file" Why is this switchable? x86 selects it
> if PROC_FS is enabled and all other>> architectures are absolute
On Tuesday 23 Apr 2019 at 18:38:46 (-0400), Thara Gopinath wrote:
> I think there is one major difference between user-defined frequency
> constraints and frequency constraints due to thermal events in terms of
> the time period the system spends in the the constraint state.
> Typically, a user con
Sensitive workloads like DPDK polling do not like any interrupts.
This patch adds flag 'freq' for boot option 'isolcpu': isolcpu=freq,.
Users like show_cpuinfo() fallback to frequency from generic cpufreq
policy if arch-specific requesting method returns 0.
Signed-off-by: Konstantin Khlebnikov
On 25.04.19 12:42, Li, Aubrey wrote:
>
> Yep, I'll make it disabled by default and not switchable and let arch select
> it.
>
That's not quite what I've suggested. Instead:
#1: make the switch depend on the arch's that support it
#2: still leave it selectable to the user, so somebody who doesn
On Wed, Mar 06, 2019 at 03:59:12PM -0800, Matthew Garrett wrote:
> From: David Howells
>
> static int open_proxy_open(struct inode *inode, struct file *filp)
> {
> struct dentry *dentry = F_DENTRY(filp);
> @@ -147,6 +166,11 @@ static int open_proxy_open(struct inode *inode, struct
> file
On Thu, 25 Apr 2019, Enrico Weigelt, metux IT consult wrote:
> On 25.04.19 12:42, Li, Aubrey wrote:
> >
> > Yep, I'll make it disabled by default and not switchable and let arch
> > select it.
> >
>
> That's not quite what I've suggested. Instead:
>
> #1: make the switch depend on the arch's
On Tuesday 16 Apr 2019 at 15:38:39 (-0400), Thara Gopinath wrote:
> +/* Per cpu structure to keep track of Thermal Pressure */
> +struct thermal_pressure {
> + unsigned long scale; /* scale reflecting average cpu max capacity*/
> + unsigned long acc_scale; /* Accumulated scale for this time
* Peter Zijlstra wrote:
> On Thu, Apr 25, 2019 at 11:50:39AM +0200, Ingo Molnar wrote:
> >
> > * Peter Zijlstra wrote:
> >
> > > On Thu, Apr 25, 2019 at 11:17:17AM +0200, Ingo Molnar wrote:
> > > > It basically means that we silently won't do any patching and the
> > > > kernel
> > > > wil
On Thu, Apr 25, 2019 at 06:16:02PM +0800, Zhao, Yakui wrote:
> The parameter register for the VMCALL is predefined in ACRN hypervisor. Now
> the R8 is used to pass the hcall_id.
> It seems that there is no special constraint for R8~R15.
> So the explicit register variable is used so that the R8 can
Andrew Zaborowski wrote:
> > extern key_ref_t keyring_search(key_ref_t keyring,
> > struct key_type *type,
> > - const char *description);
> > + const char *description,
> > +
On Wed 2019-04-24 16:51:12, Feng Tang wrote:
> Currently on panic, kernel will lower the loglevel and print out
> pending printk msg only with console_flush_on_panic().
>
> Add an option for users to configure the "panic_print" to replay
> all dmesg in buffer, some of which they may have never see
On Sat, Mar 16, 2019 at 05:12:43PM +0100, Remi Pommarel wrote:
> The PCI_EXP_LNKSTA_LT flag in the emulated root device's PCI_EXP_LNKSTA
> config register does not reflect the actual link training state and is
> always cleared. The Link Training and Status State Machine (LTSSM) flag
> in LMI config
Hi,
On Tue, Apr 23, 2019 at 11:04:42AM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Add the DT binding document for the battery charger module of max77650.
>
> Signed-off-by: Bartosz Golaszewski
> ---
Reviewed-by: Sebastian Reichel
-- Sebastian
> .../power/supply/max7
From: Thomas Gleixne]
> Sent: 25 April 2019 11:59
> On Thu, 25 Apr 2019, David Laight wrote:
>
> > From: Fenghua Yu
> > > Sent: 24 April 2019 20:33
> > > A split locked access locks bus and degrades overall memory access
> > > performance. When split lock detection feature is enumerated, enable
>
Split the bd718x7.h to ROHM common and bd718x7 specific parts
so that we do not need to add same things in every new ROHM
PMIC header. Please note that this change requires changes also
in bd718x7 sub-device drivers for regulators and clk.
Signed-off-by: Matti Vaittinen
Acked-by: Mark Brown
Acke
Patch series introducing support for ROHM BD70528 PMIC
Resending the series as I forgot Lee from the recipient list of
the original mail.
ROHM BD70528 is a programmable Power Management IC for battery
powered 'ultra low power' systems like the pre-announced NXP
i.MX7 ULP. This patch series introd
ROHM BD70528MWV is an ultra-low quiescent current general
purpose single-chip power management IC for battery-powered
portable devices.
Add MFD core which enables chip access for following subdevices:
- regulators/LED drivers
- battery-charger
- gpios
- 32.768kHz cl
ROHM BD70528 is an ultra low power PMIC with similar 32K clk as
bd718x7. Only difference (from clk perspective) is register address.
Add support for controlling BD70528 clk using bd718x7 driver.
Signed-off-by: Matti Vaittinen
Acked-by: Stephen Boyd
---
Changelog v13:
- No changes
Changelog v12:
ROHM BD70528 PMIC has 4 GPIO pins. Allow them to be
controlled by GPIO framework.
IRQs are handled by regmap-irq and GPIO driver is not
aware of the irq usage.
Signed-off-by: Matti Vaittinen
Reviewed-by: Linus Walleij
---
Changelog v13:
- No changes
Changelog v12:
- No functional changes
- Sty
Document bindings for regulators (3 bucks, 3 LDOs and 2 LED
drivers) and 4 GPIO pins which can be configured for I/O or
as interrupt sources withe configurable trigger levels.
Signed-off-by: Matti Vaittinen
Reviewed-by: Rob Herring
Acked-by: Linus Walleij
---
Changelog v13:
- No changes
Change
Support RTC block in ROHM bd70528 power management IC. Support
getting and setting the time and date as well as arming an alarm
which can also be used to wake the PMIC from standby state.
HW supports wake interrupt only for the next 24 hours (sec, minute
and hour information only) so we limit also
ROHM BD70528 PMIC includes battery charger block. Support charger
staus queries and doing few basic settings like input current limit
and charging current.
Signed-off-by: Matti Vaittinen
---
Changelog v13:
- no changes
Changelog v12:
- Styling fixes only
drivers/power/supply/Kconfig
101 - 200 of 901 matches
Mail list logo
