On Mon, Oct 26, 2020 at 09:48:11PM +0100, Alexandre Belloni wrote:
> On 26/10/2020 07:23:26+, Qiang Zhao wrote:
> > Any update for this patchset?
> >
>
> The whole point would be to get the DT and the watchdog maintainers
> agree on the property name. Once done, the driver implementation is
>
On Mon, Oct 26, 2020 at 01:33:48PM -0700, Linus Torvalds wrote:
> On Mon, Oct 26, 2020 at 12:41 PM Guenter Roeck wrote:
> >
> > make ARCH=um SUBARCH=x86_64 defconfig:
> >
> > Building um:defconfig ... failed
> > --
> > Error log:
> > arch/um/kernel/skas/clone.c:24:16: error: expected d
On 6/26/20 8:34 AM, Borislav Petkov wrote:
>> +if (!(atomic_read(&encl->flags) & SGX_ENCL_CREATED))
>> +return -EINVAL;
>> +
>> +if (copy_from_user(&addp, arg, sizeof(addp)))
>> +return -EFAULT;
>> +
>> +if (!IS_ALIGNED(addp.offset, PAGE_SIZE) ||
>> +!IS_
On Mon, Oct 26, 2020 at 9:08 PM Eric Biggers wrote:
> Commit 3f69cc60768b ("crypto: af_alg - Allow arbitrarily long algorithm
> names") made the kernel start accepting arbitrarily long algorithm names
> in sockaddr_alg.
That's not true; it's still limited by the size of struct
sockaddr_storage (1
From: Arnd Bergmann
clang points out a useless check that was recently added:
drivers/net/wireless/realtek/rtw88/fw.c:1485:21: warning: address of array
'rtwdev->chip->fw_fifo_addr' will always evaluate to 'true'
[-Wpointer-bool-conversion]
if (!rtwdev->chip->fw_fifo_addr) {
On Mon, Oct 26, 2020 at 08:29:53PM +0100, Wilken Gottwalt wrote:
> On Mon, 26 Oct 2020 11:41:51 -0700
> Guenter Roeck wrote:
> > I have to admit that it is quite new for me as well, but I find it
> > convenient.
> > And it is kind of odd tht it needs three dots (and it may need spaces before
> >
On Mon, Oct 26 2020 at 17:28, Guilherme Piccoli wrote:
> On Mon, Oct 26, 2020 at 4:59 PM Thomas Gleixner wrote:
>> It gets flooded right at the point where the crash kernel enables
>> interrupts in start_kernel(). At that point there is no device driver
>> and no interupt requested. All you can se
On 10/26/2020 9:06 PM, Iuliana Prodan wrote:
> Use the new crypto_engine_alloc_init_and_set() function to
> initialize crypto-engine and enable retry mechanism.
>
> Set the maximum size for crypto-engine software queue based on
> Job Ring size (JOBR_DEPTH) and a threshold (reserved for the
> non-c
From: Arnd Bergmann
gcc points out a suspicious mixing of enum types in a function that
converts from MTHCA_OPCODE_* values to IB_WC_* values:
drivers/infiniband/hw/mthca/mthca_cq.c: In function 'mthca_poll_one':
drivers/infiniband/hw/mthca/mthca_cq.c:607:21: warning: implicit conversion
from '
Hi,
On Mon, Oct 26, 2020 at 01:07:15PM -0700, Eric Biggers wrote:
> From: Eric Biggers
>
> Commit 3f69cc60768b ("crypto: af_alg - Allow arbitrarily long algorithm
> names") made the kernel start accepting arbitrarily long algorithm names
> in sockaddr_alg. However, the actual length of the salg
On Mon 26 Oct 10:13 CDT 2020, Wolfram Sang wrote:
>
> > Wolfram, would you like to pick this patch or would you prefer that it
> > goes together with the other two through the soc tree?
>
> Actually, I prefer the soc tree because of the functional dependency. I
> am not aware of any pending qcom
On 10/26/2020 1:11 PM, Thomas Gleixner wrote:
> On Mon, Oct 26 2020 at 12:21, Jacob Keller wrote:
>> On 10/26/2020 12:00 PM, Thomas Gleixner wrote:
>>> How does userspace know about the driver internals? Number of management
>>> interrupts, optimal number of interrupts per queue?
>>
>> I guess t
On Fri 02 Oct 21:05 CDT 2020, Siddharth Gupta wrote:
> This change adds a new kind of core dump mechanism which instead of dumping
> entire program segments of the firmware, dumps sections of the remoteproc
> memory which are sufficient to allow debugging the firmware. This function
> thus uses se
From: Arnd Bergmann
gcc -Wextra points out that a field may get overridden in some
configurations such as x86 allmodconfig, when the next index after the one
that has been assigned last already had a value, in this case for index
BPF_PROG_TYPE_SK_LOOKUP, which comes after BPF_PROG_TYPE_LSM in the
From: Arnd Bergmann
Building with -Wextra shows lots of warnings in the bpf
code such as
kernel/bpf/verifier.c: In function ‘jit_subprogs’:
include/linux/filter.h:345:4: warning: cast between incompatible function types
from ‘unsigned int (*)(const void *, const struct bpf_insn *)’ to ‘u64 (*)(
On 26.10.2020 19:15, Krzysztof Kozlowski wrote:
> The Devicetree specification expects device node names to have a generic
> name, representing the class of a device. Also the convention for node
> names is to use hyphens, not underscores.
>
> No functional changes.
>
> Signed-off-by: Krzysztof
Hi Jean-Philippe,
Thanks a lot for the review. Comments inline.
On Tue, 20 Oct 2020 15:58:09 +0200, Jean-Philippe Brucker
wrote:
> On Mon, Sep 28, 2020 at 02:38:28PM -0700, Jacob Pan wrote:
> > IOASID is used to identify address spaces that can be targeted by device
> > DMA. It is a system-wide
On Mon, Oct 26, 2020 at 04:53:48PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> Nesting macros that use the same local variable names causes
> warnings when building with "make W=2":
>
> include/asm-generic/percpu.h:117:14: warning: declaration of '__ret' shadows
> a previous local [-W
From: Arnd Bergmann
Building with 'make W=1' produces countless warnings like
amdgpu/../include/vega10_ip_offset.h:276:51: warning: initialized field
overwritten [-Woverride-init]
Shut these up by disabling the particular warning in the
amdgpu driver.
Signed-off-by: Arnd Bergmann
---
driver
With this change, when the knob is set to 0, it allows unprivileged
users to call userfaultfd, like when it is set to 1, but with the
restriction that page faults from only user-mode can be handled.
In this mode, an unprivileged user (without SYS_CAP_PTRACE capability)
must pass UFFD_USER_MODE_ONLY
userfaultfd handles page faults from both user and kernel code.
Add a new UFFD_USER_MODE_ONLY flag for userfaultfd(2) that makes
the resulting userfaultfd object refuse to handle faults from kernel
mode, treating these faults as if SIGBUS were always raised, causing
the kernel code to fail with EFA
From: Arnd Bergmann
A conversion from 'bool' to 'enum odm_combine_mode' was incomplete,
and gcc warns about this with many instances of
display/dc/dml/dcn20/display_mode_vba_20.c:3899:44: warning: implicit
conversion from 'enum ' to 'enum
odm_combine_mode' [-Wenum-conversion]
3899 | locals
This patch series is split from [1]. The other series enables SELinux
support for userfaultfd file descriptors so that its creation and
movement can be controlled.
It has been demonstrated on various occasions that suspending kernel
code execution for an arbitrary amount of time at any access to
u
From: Arnd Bergmann
gcc -Wextra warns about a function taking an enum argument
being called with a bool:
drivers/gpu/drm/amd/amdgpu/../display/modules/color/color_gamma.c: In function
'apply_degamma_for_user_regamma':
drivers/gpu/drm/amd/amdgpu/../display/modules/color/color_gamma.c:1617:29:
w
From: Arnd Bergmann
gcc -Wextra warns about an incorrect prototype causing multiple
mismatched enums:
display/dc/gpio/gpio_service.c: In function 'dal_gpio_service_create':
display/dc/gpio/gpio_service.c:70:50: warning: implicit conversion from 'enum
dce_environment' to 'enum dce_version' [-Wen
From: Arnd Bergmann
core_link_write_dpcd() returns enum dc_status, not ddc_result:
display/dc/core/dc_link_dp.c: In function 'dp_set_panel_mode':
display/dc/core/dc_link_dp.c:4237:11: warning: implicit conversion from 'enum
dc_status' to 'enum ddc_result'
[-Wenum-conversion]
Avoid the warning
This probe function is too complicated and should be refactored. For now
let's just set this variable to NULL and keep the static analysis tools
happy.
Fixes: 52e013d0bffa ("phy: qcom-qmp: Add support for DP in USB3+DP combo phy")
Reported-by: kernel test robot
Reported-by: Dan Carpenter
Signed-
Helge,
> The mptscsih_remove() function triggers a kernel oops if the
> Scsi_Host pointer (ioc->sh) is NULL, as can be seen in this syslog:
Applied to 5.10/scsi-fixes, thanks!
--
Martin K. Petersen Oracle Linux Engineering
Quoting Arnd Bergmann (2020-10-26 12:41:03)
> From: Arnd Bergmann
>
> There is one harmless duplicate initialization that causes a warning
> with 'make W=1':
>
> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c:122:19: warning: initialized
> field overwritten [-Woverride-init]
> 122 | .max_lin
Hi all,
This patch, building on top of the recently introduced SCMI System Power
Protocol support, adds a new SCMI driver which, registering for SCMI System
Power notifications, acts accordingly to satisfy such SCMI plaform
system-wide transition requests (which can be of forceful or graceful kind
Add an SCMI System Power control driver to handle platform's requests
carried by SYSTEM_POWER_STATE_NOTIFIER notifications: such platform
requested system power state transitions are handled accordingly,
gracefully or forcefully, depending on the notifications' message flags.
Graceful requests are
The user level OpenCL code shouldn't have to align start and end
addresses to a page boundary. That is better handled in the nouveau
driver. The npages field is also redundant since it can be computed
from the start and end addresses.
Signed-off-by: Ralph Campbell
---
I thought I sent this out e
On 10/26/20 6:28 AM, Matthew Wilcox wrote:
On Sun, Oct 25, 2020 at 09:44:07PM -0700, John Hubbard wrote:
On 10/25/20 9:21 PM, Matthew Wilcox wrote:
I don't think the page pinning approach is ever valid. For file
Could you qualify that? Surely you don't mean that the entire pin_user_pages
sto
On 2020-10-26 12:41, Arnd Bergmann wrote:
From: Arnd Bergmann
There is one harmless duplicate initialization that causes a warning
with 'make W=1':
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c:122:19: warning:
initialized field overwritten [-Woverride-init]
122 | .max_linewidth = 4096,
On Mon, Oct 26, 2020 at 03:58:11PM -0400, Mathieu Desnoyers wrote:
> - On Oct 22, 2020, at 6:30 PM, paulmck paul...@kernel.org wrote:
>
> > The current code can lose RCU callbacks at shutdown time, which can
> > result in hangs. This lossage can happen as follows:
> >
> > o A thread in
On 2020-08-31 18:19, Bao D. Nguyen wrote:
UFS version 3.0 and later devices require Vcc and Vccq power supplies
with Vccq2 being optional. While earlier UFS version 2.0 and 2.1
devices, the Vcc and Vccq2 are required with Vccq being optional.
Check the required power supplies used by the device
a
On 26/10/2020 07:23:26+, Qiang Zhao wrote:
> Any update for this patchset?
>
The whole point would be to get the DT and the watchdog maintainers
agree on the property name. Once done, the driver implementation is
trivial and will get applied.
> Best Regards
> Qiang Zhao
>
> > -Original
On Mon, Oct 26, 2020 at 08:28:45PM +0100, Arnd Bergmann wrote:
> On Mon, Oct 26, 2020 at 6:27 PM Will Deacon wrote:
> > On Mon, Oct 26, 2020 at 05:13:30PM +, Peter Maydell wrote:
> > > On Mon, 26 Oct 2020 at 16:23, Mark Rutland wrote:
> > > > On Mon, Oct 26, 2020 at 05:03:31PM +0100, Arnd Ber
On Sun, Oct 25, 2020 at 5:45 AM wrote:
>
> On Thu, Oct 22, 2020 at 08:35:26AM +0200, SeongJae Park wrote:
> > On Wed, 21 Oct 2020 14:32:52 -0700 Brendan Higgins
> > wrote:
> >
> > > On Mon, Oct 12, 2020 at 3:27 AM SeongJae Park wrote:
> > > >
> > > > From: SeongJae Park
> > > >
> > > > 'kunit_
The default value of inotify.max_user_watches sysctl parameter was set
to 8192 since the introduction of the inotify feature in 2005 by
commit 0eeca28300df ("[PATCH] inotify"). Today this value is just too
small for many modern usage. As a result, users have to explicitly set
it to a larger value t
On Mon, 26 Oct 2020 10:28:07 -0400 (EDT)
Mathieu Desnoyers wrote:
> I agree with Peter. Removing the trace_.*_rcuidle weirdness from the
> tracepoint
> API and fixing all callers to ensure they trace from a context where RCU is
> watching would simplify instrumentation of the Linux kernel, thus
On 19/10/2020 12:36:53-0700, t...@redhat.com wrote:
> From: Tom Rix
>
> A break is not needed if it is preceded by a return
>
> Signed-off-by: Tom Rix
Reviewed-by: Alexandre Belloni
> ---
> drivers/crypto/atmel-sha.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/crypto/atm
Applied, thanks
On 15/10/2020 13:24, Lukasz Luba wrote:
> Hi all,
>
> This patch set makes thermal governor Intelligent Power Allocation (IPA)
> aware of cooling device limits for upper and lower bounds and respects them
> in the internal power budget calculation.
>
> This v2 contains for comp
On Fri, 23 Oct 2020, Jeff Vander Stoep wrote:
> During __vsock_create() CAP_NET_ADMIN is used to determine if the
> vsock_sock->trusted should be set to true. This value is used later
> for determing if a remote connection should be allowed to connect
> to a restricted VM. Unfortunately, if the ca
On Mon, Oct 26, 2020 at 01:55:24PM +0100, Peter Zijlstra wrote:
> On Mon, Oct 26, 2020 at 11:56:03AM +, Filipe Manana wrote:
> > > That smells like the same issue reported here:
> > >
> > >
> > > https://lkml.kernel.org/r/20201022111700.gz2...@hirez.programming.kicks-ass.net
> > >
> > > Ma
On Mon, Oct 26, 2020 at 07:38:14PM +0100, Fabien Parent wrote:
> On Mon, Oct 26, 2020 at 6:24 PM Mark Brown wrote:
> > > .name = "mt6392-regulator",
> > > .of_compatible = "mediatek,mt6392-regulator"
> > This is still unneeded, it's just a reflection of Linux implementation
> > d
Applied. Thanks!
Alex
On Mon, Oct 26, 2020 at 4:22 PM Kazlauskas, Nicholas
wrote:
>
> Reviewed-by: Nicholas Kazlauskas
>
> Looks fine to me. Feel free to apply.
>
> Regards,
> Nicholas Kazlauskas
>
> On 2020-10-26 3:34 p.m., Alex Deucher wrote:
> > Yes, looks good to me as well. Series is:
>
On Mon, Oct 26, 2020 at 12:41 PM Guenter Roeck wrote:
>
> make ARCH=um SUBARCH=x86_64 defconfig:
>
> Building um:defconfig ... failed
> --
> Error log:
> arch/um/kernel/skas/clone.c:24:16: error: expected declaration specifiers or
> '...' before string constant
> arch/x86/um/stub_segv
This is in preparation for maintaining signal_pending() as the decider
of whether or not a schedule() loop should be broken, or continue
sleeping. This is different than the core signal use cases, where we
really want to know if an actual signal is pending or not.
task_sigpending() returns non-zero
Add devicetree bindings to support regulators based on SCMI Voltage
Domain Protocol.
Signed-off-by: Cristian Marussi
---
v2 --> v3
- avoid awkard examples based on _cpu/_gpu regulators
v1 --> v2
- removed any reference to negative voltages
---
.../devicetree/bindings/arm/arm,scmi.txt | 42 +
This adds TIF_NOTIFY_SIGNAL handling in the generic code, which if set,
will return true if signal_pending() is used in a wait loop. That causes
an exit of the loop so that notify_signal tracehooks can be run. If the
wait loop is currently inside a system call, the system call is restarted
once tas
Hi,
The goal is this patch series is to decouple TWA_SIGNAL based task_work
from real signals and signal delivery. The motivation is speeding up
TWA_SIGNAL based task_work, particularly for threaded setups where
->sighand is shared across threads. See the last patch for numbers.
On top of this I
If the arch supports TIF_NOTIFY_SIGNAL, then use that for TWA_SIGNAL as
it's more efficient than using the signal delivery method. This is
especially true on threaded applications, where ->sighand is shared
across threads, but it's also lighter weight on non-shared cases.
io_uring is a heavy consu
All we need to do is define _TIF_NOTIFY_SIGNAL, the generic entry code
already handles everything else for us.
Signed-off-by: Jens Axboe
---
arch/x86/include/asm/thread_info.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/include/asm/thread_info.h
b/arch/x86/include/asm/thread_
Add SCMI Voltage Domain device name to the core list of supported protocol
devices.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/driver.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/firmware/arm_scmi/driver.c
b/drivers/firmware/arm_scmi/driver.c
index ada35e63fe
Add SCMI Voltage Domain protocol support.
Signed-off-by: Cristian Marussi
---
v2 --> v3
- restrict segmented voltage domain descriptors to one triplet
- removed unneeded inline
- free allocated resources for invalid voltage domain
- added __must_check to info_get voltage operations
- added a few
Hi,
this series introduces the support for the new SCMI Voltage Domain Protocol
defined by the upcoming SCMIv3.0 specification, whose BETA release is
available at [1].
Afterwards, a new generic SCMI Regulator driver is developed on top of the
new SCMI VD Protocol.
The series is currently based o
Add a simple regulator based on SCMI Voltage Domain Protocol.
Signed-off-by: Cristian Marussi
v2 --> v3
- remove multiple linear mappings support
- removed duplicated voltage name printout
- added a few comments
- simplified return path in scmi_reg_set_voltage_sel()
v1 --> v2
- removed dupl
On Mon, Oct 26, 2020 at 4:59 PM Thomas Gleixner wrote:
>
> On Mon, Oct 26 2020 at 12:06, Guilherme Piccoli wrote:
> > On Sun, Oct 25, 2020 at 8:12 AM Pingfan Liu wrote:
> >
> > Some time ago (2 years) we faced a similar issue in x86-64, a hard to
> > debug problem in kdump, that eventually was na
Applied. Thanks!
Alex
On Mon, Oct 26, 2020 at 2:14 PM Sumera Priyadarsini
wrote:
>
> Bool initialisation should use 'true' and 'false' values instead of 0
> and 1.
>
> Modify amdgpu_amdkfd_gpuvm.c to initialise variable is_imported
> to false instead of 0.
>
> Issue found with Coccinelle.
>
> S
> On Oct 22, 2020, at 8:18 AM, Johannes Weiner wrote:
>
> As huge page usage in the page cache and for shmem files proliferates
> in our production environment, the performance monitoring team has
> asked for per-cgroup stats on those pages.
>
> We already track and export anon_thp per cgroup
onfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a002-20201026
i386 randconfig-a00
Reviewed-by: Nicholas Kazlauskas
Looks fine to me. Feel free to apply.
Regards,
Nicholas Kazlauskas
On 2020-10-26 3:34 p.m., Alex Deucher wrote:
Yes, looks good to me as well. Series is:
Acked-by: Alex Deucher
I'll give the display guys a few more days to look this over, but if
there are no
From: "Steven Rostedt (VMware)"
Commit cad6967ac108 ("fork: introduce kernel_clone()") replaced "_do_fork()"
with "kernel_clone()". The ftrace selftests reference the fork function in
several of the tests. The rename will make the tests break, but if those
names are changed in the tests, they wou
Hi Arpitha,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on ext4/dev]
[also build test WARNING on linus/master v5.10-rc1 next-20201026]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '-
On Wed, Oct 07, 2020 at 05:37:44PM -0700, Nicolin Chen wrote:
> This is a cleanup change to prepare for new swgroups.
>
> Signed-off-by: Nicolin Chen
> ---
> drivers/memory/tegra/tegra210.c | 20 ++--
> 1 file changed, 10 insertions(+), 10 deletions(-)
Thanks, applied with adjus
On Fri, Oct 09, 2020 at 08:52:18AM -0700, Nicolin Chen wrote:
> On Fri, Oct 09, 2020 at 02:21:10PM +0200, Thierry Reding wrote:
> > On Wed, Oct 07, 2020 at 05:37:45PM -0700, Nicolin Chen wrote:
> > > According to Tegra X1 TRM, there are missing swgroups in the
> > > tegra210_swgroups list. So this
Geert Uytterhoeven writes:
> On Mon, Oct 26, 2020 at 10:46 AM Geert Uytterhoeven
> wrote:
>> Below is the list of build error/warning regressions/improvements in
>> v5.10-rc1[1] compared to v5.9[2].
>>
>> Summarized:
>> - build errors: +3/-7
>> - build warnings: +26/-28
>>
>> Happy fixing! ;-
On Wed, Oct 07, 2020 at 05:37:43PM -0700, Nicolin Chen wrote:
> Some def values are mismatched with Tegra X1 TRM, probably because
> being copied from tegra124.c file. So this patch fixes them.
>
> Signed-off-by: Nicolin Chen
> ---
> drivers/memory/tegra/tegra210.c | 28 ++---
On Wed, Oct 07, 2020 at 05:37:42PM -0700, Nicolin Chen wrote:
> According to Tegra X1 TRM, ALLOWANCE_SESWR is located in field
> [23:16] of register at address 0x3e0 with a reset value of 0x80
> at register 0x3e0, while bit-1 of register 0xb98 is for enable
> bit of seswr.
> So this patch fixes it
Daniel,
> When the fcport is about to be deleted we should return EBUSY instead
> of ENODEV. Only for EBUSY the request will be requeued in a multipath
> setup.
>
> Also when the firmware has not yet started return EBUSY to avoid
> dropping the request.
Applied to 5.10/scsi-fixes, thanks!
--
Hi,
this series is meant to add support for the new SCMI Sensor Protocol
features defined by the upcoming SCMIv3.0 specification, whose BETA
release is available at [1].
The series is currently based on for-next/scmi [2] on top of:
commit b9ceca6be432 ("firmware: arm_scmi: Fix duplicate workqueu
Properly handle return values from initialization helpers and avoid
setting sensor_ops before sensor_priv.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/sensors.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/drivers/firmware/arm_scmi/senso
Add new .reading_get_timestamped() method to sensor_ops to support SCMIv3.0
timestamped reads.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/sensors.c | 134 ++--
include/linux/scmi_protocol.h | 22 +
2 files changed, 151 insertions(+), 5 deleti
Add support for new SCMIv3.0 Sensors extensions related to new sensors'
features, like multiple axis and update intervals, while keeping
compatibility with SCMIv2.0 features.
While at that, refactor and simplify all the internal helpers macros and
move struct scmi_sensor_info to use only non-fixed-
Add SCMIv3.0 Sensor support for CONFIG_GET/CONFIG_SET commands.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/sensors.c | 75 +
include/linux/scmi_protocol.h | 37 ++
2 files changed, 112 insertions(+)
diff --git a/drivers/firmware/a
On Mon, Oct 26 2020 at 12:21, Jacob Keller wrote:
> On 10/26/2020 12:00 PM, Thomas Gleixner wrote:
>> How does userspace know about the driver internals? Number of management
>> interrupts, optimal number of interrupts per queue?
>
> I guess this is the problem solved in part by the queue managemen
Use an int to calculate scale values inside scmi_hwmon_scale() to match
the updated scale data type in struct scmi_sensor_info.
Signed-off-by: Cristian Marussi
---
drivers/hwmon/scmi-hwmon.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/scmi-hwmon.c b/drivers/
Add support for new SCMIv3.0 SENSOR_UPDATE notification.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/sensors.c | 124
include/linux/scmi_protocol.h | 9 ++
2 files changed, 116 insertions(+), 17 deletions(-)
diff --git a/drivers/firmware/ar
From: Eric Biggers
Commit 3f69cc60768b ("crypto: af_alg - Allow arbitrarily long algorithm
names") made the kernel start accepting arbitrarily long algorithm names
in sockaddr_alg. However, the actual length of the salg_name field
stayed at the original 64 bytes.
This is broken because the kern
On Wed, Sep 30, 2020 at 03:06:23PM +0800, Yong Wu wrote:
> This patch mainly adds support for mt8192 IOMMU and SMI.
>
> mt8192 also is MTK IOMMU gen2 which uses ARM Short-Descriptor translation
> table format. The M4U-SMI HW diagram is as below:
>
> EMI
>
> -Original Message-
> From: Robin Murphy [mailto:robin.mur...@arm.com]
> Sent: Tuesday, October 27, 2020 1:25 AM
> To: h...@lst.de
> Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org; Song Bao
> Hua (Barry Song)
> Subject: [PATCH] dma: Per-NUMA-node CMA should depend o
On Wed, Jul 08, 2020 at 04:34:20PM +0100, Lukasz Luba wrote:
> The interrupts in Dynamic Memory Controller in Exynos5422 and Odroid
> XU3-family boards are no longer needed. They have been used in order
> to workaround some issues in scheduled work in devfreq. Now when the
> devfreq framework desig
On Mon, Oct 26 2020 at 12:06, Guilherme Piccoli wrote:
> On Sun, Oct 25, 2020 at 8:12 AM Pingfan Liu wrote:
>
> Some time ago (2 years) we faced a similar issue in x86-64, a hard to
> debug problem in kdump, that eventually was narrowed to a buggy NIC FW
> flooding IRQs in kdump kernel, and no mes
- On Oct 22, 2020, at 6:30 PM, paulmck paul...@kernel.org wrote:
> The current code can lose RCU callbacks at shutdown time, which can
> result in hangs. This lossage can happen as follows:
>
> o A thread invokes call_rcu_data_free(), which executes up through
>the wake_call_rc
Thanks Hans
On 26/10/2020 14:33, Hans de Goede wrote:
Hi Mark,
Thank you for this new version.
On 10/26/20 6:44 PM, Mark Pearson wrote:
From: Hans de Goede
+
+If for some reason there is no good match when mapping then a new profile-name
+may be added. Drivers which wish to introduce ne
On 10/20/20 7:18 AM, David Hildenbrand wrote:
> On 20.10.20 08:18, Kirill A. Shutemov wrote:
>> If the protected memory feature enabled, unmap guest memory from
>> kernel's direct mappings.
>
> Gah, ugly. I guess this also defeats compaction, swapping, ... oh gosh.
> As if all of the encrypted VM
On 2020-10-26 20:15:23 [+0100], Mike Galbraith wrote:
> --- a/drivers/gpu/drm/nouveau/nvkm/subdev/pci/base.c
> +++ b/drivers/gpu/drm/nouveau/nvkm/subdev/pci/base.c
> @@ -116,7 +116,17 @@ nvkm_pci_oneinit(struct nvkm_subdev *sub
> return ret;
> }
>
> + /*
> + *
On 10/23/2020 12:46 PM, Tom Lendacky wrote:
> On 10/23/20 2:03 AM, Peter Zijlstra wrote:
>> On Thu, Oct 22, 2020 at 10:10:35PM +0200, Giovanni Gherdovich wrote:
>>> * for the AMD EPYC machines we haven't yet implemented frequency invariant
>>> accounting, which might explain why schedutil looses
From: Jaegeuk Kim
Must have WQ_MEM_RECLAIM
``WQ_MEM_RECLAIM``
All wq which might be used in the memory reclaim paths **MUST**
have this flag set. The wq is guaranteed to have at least one
execution context regardless of memory pressure.
Signed-off-by: Jaegeuk Kim
Reviewed-by: Asutosh Das
Change log from v3:
- use __ufshcd_release with a fix in __ufshcd_release
Change log from v2:
- use active_req-- instead of __ufshcd_release to avoid UFS timeout
Change log from v1:
- remove clkgating_enable check in __ufshcd_release
- use __uhfshcd_release instead of active_req.
From: Jaegeuk Kim
When giving a stress test which enables/disables clkgating, we hit device
timeout sometimes. This patch avoids subtle racy condition to address it.
Note that, this requires a patch to address the device stuck by REQ_CLKS_OFF in
__ufshcd_release().
The fix is "scsi: ufs: avoid
From: Jaegeuk Kim
In order to conduct FFU or RPMB operations, UFS needs to clear UAC. This patch
clears it explicitly, so that we could get no failure given early execution.
Signed-off-by: Jaegeuk Kim
---
drivers/scsi/ufs/ufshcd.c | 70 +++
drivers/scsi/ufs/
From: Jaegeuk Kim
This adds user-friendly tracepoints with group id.
Signed-off-by: Jaegeuk Kim
Reviewed-by: Can Guo
---
drivers/scsi/ufs/ufshcd.c | 6 --
include/trace/events/ufs.h | 21 +
2 files changed, 21 insertions(+), 6 deletions(-)
diff --git a/drivers/scsi/
The below call stack prevents clk_gating at every IO completion.
We can remove the condition, ufshcd_any_tag_in_use(), since clkgating_work
will check it again.
ufshcd_complete_requests(struct ufs_hba *hba)
ufshcd_transfer_req_compl()
__ufshcd_transfer_req_compl()
__ufshcd_release(hba)
Hey Angelo,
I can't functionally test the code myself, but the series looks good to me now.
Reviewed-by: Robert Foss
On Thu, 22 Oct 2020 at 19:47, wrote:
>
> From: AngeloGioacchino Del Regno
>
> This patch series implements support for the entire camera subsystem
> found in SDM630/636/660 and
On 10/26, Can Guo wrote:
> On 2020-10-26 14:13, Jaegeuk Kim wrote:
> > On 10/26, Can Guo wrote:
> > > On 2020-10-24 23:06, Jaegeuk Kim wrote:
> > > > From: Jaegeuk Kim
> > > >
> > > > When giving a stress test which enables/disables clkgating, we hit
> > > > device
> > > > timeout sometimes. This
On Mon, Oct 26, 2020 at 12:36:52PM -0700, Guenter Roeck wrote:
> On Wed, Oct 21, 2020 at 07:36:07PM -0700, Joe Perches wrote:
> > Use a more generic form for __section that requires quotes to avoid
> > complications with clang and gcc differences.
> >
> > Remove the quote operator # from compiler_
On Mon, Oct 26, 2020 at 12:41 PM Arnd Bergmann wrote:
>
> From: Arnd Bergmann
>
> clang warns about functions returning a 'const int' result:
>
> drivers/gpu/drm/imx/imx-tve.c:487:8: warning: type qualifiers ignored on
> function return type [-Wignored-qualifiers]
>
> Remove the extraneous 'cons
On 10/26, asuto...@codeaurora.org wrote:
> On 2020-10-24 08:06, Jaegeuk Kim wrote:
> > From: Jaegeuk Kim
> >
> > In order to conduct FFU or RPMB operations, UFS needs to clear UAC. This
> > patch
> > clears it explicitly, so that we could get no failure given early
> > execution.
> >
>
> What's
901 - 1000 of 2009 matches
Mail list logo
