On Wed, Jan 13, 2021 at 3:08 AM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:1710: warning:
> Function parameter or member 'old_stream' not described in
> 'dc_is_stream_unchanged'
> drivers/gpu/drm/amd/amd
On Wed, Jan 13, 2021 at 3:08 AM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:214: warning:
> Function parameter or member 'link' not described in 'dc_link_detect_sink'
> drivers/gpu/drm/amd/amdgpu/../display/dc
Respin of George's patch series enabling UBSAN for hyp/nVHE code.
Modification in v2:
* CONFIG_KVM_ARM_DEBUG_BUFFER removed; __kvm_check_ubsan_buffer is
called directly instead of via __kvm_arm_check_debug_buffer.
* Bugfixing commits removed as these are already upstream.
* Some code bro
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 65f0d2414b7079556fbbcc070b3d1c9f9587606d
commit: f90cf6079bf67988f8b1ad1ade70fc89d0080905 media: vidtv: add a bridge
driver
date: 4 months ago
config: mips-randconfig-r026-20210114 (attached as .config
From: George-Aurelian Popescu
Implement UBSan handlers inside nVHe hyp code, as empty functions for the
moment, so the undefined behaviours, that are triggered there, will be
linked to them, not to the ones defined in kernel-proper lib/ubsan.c.
In this way, enabling UBSAN_MISC won't cause a link
From: George Popescu
If an out of bounds happens inside the hyp/nVHE code, the ubsan_out_of_bounds
handler stores the logging data inside the kvm_ubsan_buffer. The one responsible
for printing is the kernel ubsan_out_of_bounds handler. The process of
decapsulating the data from the buffer is stra
From: George Popescu
The data from __ubsan_handle_builtin_unreachable is passed to the buffer
and printed inside the kernel by its simetric handler.
Signed-off-by: George Popescu
Change-Id: I71d789b7f4ec3d4c787012a061b7f5d7952cee19
Signed-off-by: Elena Petrova
---
arch/arm64/include/asm/kvm_u
From: George Popescu
The handler for the load invalid value undefined behaviour is
implemented at EL2. The EL2 handler's parameters are stored inside the buffer.
They are used by the symetric handler from EL1.
Signed-off-by: George Popescu
Signed-off-by: Elena Petrova
---
arch/arm64/include/a
From: George Popescu
__ubsan_handle_shift_out_of_bounds data is passed to the buffer inside
hyp/nVHE. This data is passed to the original handler from kernel.
The 64bit values of the shift expression operands are stored as the lhs
and rhs pointers, so there is no need to dereference them.
Signe
From: George Popescu
Type mismatch undefiend behaviour handler provides two handlers with two
data structures type_mismatch_data and type_mismatch_data_v1. Both can be
stored inside a common data structure: type_mismatch_data_common, which
differs of type_mismatch_data only by keeping a pointer t
From: George Popescu
Whenever an arithmetic overflow: addition, substraction, multiplication,
division or negating happens inside the hyp/nVHE code,
an __ubsan_handle_*_overflow is called.
All the overflow handlers are sharing the same structure called
overflow_data.
Signed-off-by: George Popes
On 1/13/21 7:27 PM, Ming Lei wrote:
> On Wed, Jan 13, 2021 at 11:13:07AM -0600, Brian King wrote:
>> On 1/12/21 6:33 PM, Tyrel Datwyler wrote:
>>> On 1/12/21 2:54 PM, Brian King wrote:
On 1/11/21 5:12 PM, Tyrel Datwyler wrote:
> Introduce several new vhost fields for managing MQ state of t
From: George-Aurelian Popescu
Test the UBsan functionality inside hyp/nVHE.
Because modules are not supported inside of hyp/nVHE code, the default
testing module for UBSan can not be used.
New functions have to be defined inside of hyp/nVHE.
They are called in kvm_get_mdcr_el2, to test UBSAN when
From: George Popescu
Share a buffer between the kernel and the hyp/nVHE code by using the
macros from kvm_debug_buffer.h.
The hyp/nVHE code requires a write index which counts how many elements
have been writtens inside the buffer and the kernel requires a read
index which counts how many element
On Mon, 11 Jan 2021 14:51:18 -0800
Ben Widawsky wrote:
> CXL devices must implement the Device Command Interface (described in
> 8.2.9 of the CXL 2.0 spec). While the driver already maintains a list of
> commands it supports, there is still a need to be able to distinguish
> between commands that
Zheng Yongjun wrote:
> The parameter of kfree function is NULL, so kfree code is useless, delete it.
>
> Signed-off-by: Zheng Yongjun
> Acked-by: Ping-Ke Shih
Patch applied to wireless-drivers-next.git, thanks.
8873e8f56f74 rtw88: Delete useless kfree code
--
https://patchwork.kernel.org/p
On Wed, Jan 13, 2021 at 11:20:13PM +0100, Adrien Grassein wrote:
> +++ b/Documentation/devicetree/bindings/regulator/nxp,pf8x00-regulator.yaml
> @@ -64,6 +64,8 @@ properties:
> maximum: 4500
> description:
>BUCK regulators current limit in mA.
> +
YANG LI wrote:
> Fix the following coccicheck warning:
> ./drivers/net/wireless/realtek/rtw88/debug.c:800:17-23: WARNING:
> Comparison of 0/1 to bool variable
>
> Reported-by: Abaci Robot
> Signed-off-by: YANG LI
Patch applied to wireless-drivers-next.git, thanks.
d3a78c7a9daa rtw88: Simpli
Geert Uytterhoeven wrote:
> As the Marvell PCIE WiFi-Ex driver does not have any code or data
> located in initmem, there is no need to annotate the mwifiex_pcie
> structure with __refdata. Drop the annotation, to avoid suppressing
> future section warnings.
>
> Signed-off-by: Geert Uytterhoeve
Colin King wrote:
> From: Colin Ian King
>
> There is a spelling mistake in the Kconfig help text. Fix it.
>
> Signed-off-by: Colin Ian King
Patch applied to wireless-drivers-next.git, thanks.
e4c748ee4af1 wilc1000: fix spelling mistake in Kconfig "devision" -> "division"
--
https://patch
Amey Narkhede wrote:
> Use module_pci_driver for drivers whose init and exit functions
> only register and unregister, respectively.
>
> Signed-off-by: Amey Narkhede
Patch applied to wireless-drivers-next.git, thanks.
0924ba9fbc26 qtnfmac_pcie: Use module_pci_driver
--
https://patchwork.ker
Zheng Yongjun wrote:
> A null pointer will be passed to a kfree() call after a kzalloc() call failed.
> This code is useless. Thus delete the extra function call.
>
> A goto statement is also no longer needed. Thus adjust an if branch.
>
> Signed-off-by: Zheng Yongjun
Patch applied to wireles
Hi Eric,
On Thu, Jan 14, 2021 at 05:58:27PM +0100, Auger Eric wrote:
> >> The uacce-devel branches from
> >>> https://github.com/Linaro/linux-kernel-uadk do provide this at the moment
> >>> (they track the latest sva/zip-devel branch
> >>> https://jpbrucker.net/git/linux/ which is roughly based o
When building with clang when CONFIG_CPU_LOONGSON3_WORKAROUNDS is
enabled:
In file included from lib/errseq.c:4:
In file included from ./include/linux/atomic.h:7:
./arch/mips/include/asm/atomic.h:52:1: warning: converting the result of
'<<' to a boolean always evaluates to true
[-Wtautologica
Hello Michal,
Michal Koutný writes:
> On Sun, Jan 03, 2021 at 02:50:01AM +, Hao Lee
> wrote:
>> The string buf will be stripped in cgroup_procs_write_start() before it
>> is converted to int, so remove this unnecessary call to strstrip().
> Good catch, Hao.
>
> Perhaps the code be then simp
The phy USB3 driver for Hisilicon 970 (hi3670) is ready
for mainstream. Mode it from staging into the main driver's
phy/ directory.
Signed-off-by: Mauro Carvalho Chehab
---
.../bindings/phy/phy-hi3670-usb3.yaml | 72 ++
MAINTAINERS | 9 +-
drivers/phy
Instead of running a loop up to 100k times, add a small
delay inside it, running it up to 10 times, waiting up
to 100-200 us.
It should be noticed that I don't have the datasheet for
this PHY. So, not sure if this time will cover all
situations.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/
Cleanup the bitfield macros by using FIELD_PREP() and GENMASK().
While here, place all hexadecimal values in lowercase.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/hikey9xx/phy-hi3670-usb3.c | 61 ++
1 file changed, 28 insertions(+), 33 deletions(-)
diff --git
Instead of using 1/0 for true/false, change the type to boolean
and change the returned value.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/hikey9xx/phy-hi3670-usb3.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/hikey9xx/phy-hi3670-us
Hi Vinod,
This series contain just the PHY patch I sent in Nov, 30 from this series:
Move Hikey 970 USB support out of staging and add DT
The 3 initial patches address the issues you pointed during your
review:
patch 1 change the logic to use GENMASK and FIELD_GET/FIELD_PREP macro
On Thu, Jan 14, 2021 at 2:53 AM Mauro Carvalho Chehab
wrote:
>
> There's a missing colon, causing the markup to be ignored,
> solving those warnings:
>
> ../drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:340: warning:
> Incorrect use of kernel-doc format: * @active_vblank_irq_
On Mon, 11 Jan 2021 14:51:11 -0800
Ben Widawsky wrote:
> Provide enough functionality to utilize the mailbox of a memory device.
> The mailbox is used to interact with the firmware running on the memory
> device.
>
> The CXL specification defines separate capabilities for the mailbox and
> the m
On Thu, Jan 14, 2021 at 4:29 AM ZhiJie.Zhang wrote:
>
> Signed-off-by: ZhiJie.Zhang
Applied. Thanks!
Alex
> ---
> drivers/gpu/drm/amd/display/dc/dce110/dce110_resource.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/display/dc/dce110/dce110_resource.c
> b/drive
On Wed, Jan 13, 2021 at 02:12:59PM -0800, Sagi Grimberg wrote:
>> But this only catches a physical block size < 512 for NVMe, not any other
>> block device.
>>
>> Please fix it for the general case in blk_queue_physical_block_size().
>
> We actually call that later and would probably be better to
On Wed, Jan 13, 2021 at 8:17 PM Masahiro Yamada wrote:
>
> Paul Gortmaker reported a regression in the GCC version check [1].
> If you use GCC 4.8, the build breaks before showing the error message
> "error Sorry, your version of GCC is too old - please use 4.9 or newer."
>
> I do not want to appl
On Wed, Jan 13, 2021 at 8:51 AM Yang Li wrote:
>
> Fix the following coccicheck warning:
> ./drivers/gpu/drm/amd/display/dc/dml/dcn20/display_mode_vba_20.c:3141:30-39:
> WARNING: Comparison to bool
>
> Reported-by: Abaci Robot
> Signed-off-by: Yang Li
Applied all 4 patches. Thanks!
Alex
> --
On Wed 13 Jan 17:01 CST 2021, Siddharth Gupta wrote:
>
> On 1/7/2021 4:21 PM, Bjorn Andersson wrote:
> > On Wed 06 Jan 15:23 CST 2021, Siddharth Gupta wrote:
> >
> > > Since the split elf blobs will always contain the hash segment, we rely on
> > I think it will sounds better if we add "should"
pf8x00 module build was not documented.
Signed-off-by: Adrien Grassein
Reviewed-by: Jagan Teki
---
drivers/regulator/Kconfig | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
index eafa13be6e3e..ba8c09d90701 100644
--- a/drivers/regula
On Thu, 14 Jan 2021 12:07:38 +0200 stef...@marvell.com wrote:
> From: Stefan Chulski
>
> This patch doesn't change any functionality, but just extend
> MIB counter register and ethtool-statistic names with "err".
>
> The counter MVPP2_MIB_FRAGMENTS_RCVD in fact is Error counter.
> Extend REG nam
This property seems useless because we can use the
regulator-max-microamp generic property to do the same
and using generic code.
As this property was already released in a kernel version,
we can't remove it, just mark it as deprecated.
Signed-off-by: Adrien Grassein
---
drivers/regulator/pf8x0
nxp,phase-shift is an enum so use enum format to describe it.
Minimum and maximum values are also wrong.
Signed-off-by: Adrien Grassein
Reviewed-by: Rob Herring
---
.../bindings/regulator/nxp,pf8x00-regulator.yaml | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --g
Hello,
this patch set aims is to fix some issues contains in the pf8x00 driver.
Some issues are documentation ones, some others are in code.
These issues where found while developing another version of the same
driver. I prefer to share with you the patch for it.
I do these patches on the master
Fix the ternary condition which is a bad coding style
in the kernel
I also remove the defering configuration of the nxp,phase-shift.
The configuration is now done at parsing time. It save some memory
and it's better for comprehension.
I also use the OTP default configuration when the parameter is
The TCSR's PHY_CLK_SCHEME register is not available on all SoC
models, but some may still use a differential reference clock.
In preparation for these SoCs, add a se_clk_scheme_default
configuration entry and declare it to true for all currently
supported SoCs (retaining the previous defaults.
Th
Support for the SDM630/660 series of SoCs was added to the driver:
document the qcom,sdm660-qusb2-phy compatible here.
Signed-off-by: AngeloGioacchino Del Regno
---
Documentation/devicetree/bindings/phy/qcom,qusb2-phy.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/device
Use a linear range to describe the voltages of the
bucks 1-6 instead of listing it one by one (via a macro)
Signed-off-by: Adrien Grassein
---
drivers/regulator/pf8x00-regulator.c | 83 +---
1 file changed, 51 insertions(+), 32 deletions(-)
diff --git a/drivers/regulator
This property seems useless because we can use the
regulator-max-microamp generic property to do the same
and using generic code.
As this property was already released in a kernel version,
we can't remove it, just mark it as deprecated
Signed-off-by: Adrien Grassein
---
.../devicetree/bindings/
The SDM660 SoC uses the same configuration as MSM8996, but the
clock scheme uses a differential reference clock and none of
the SoCs in this series (630, 636 and others) have got a usable
PHY_CLK_SCHEME register in the TCSR for clk scheme detection.
Signed-off-by: AngeloGioacchino Del Regno
---
On Thu, Jan 14, 2021 at 9:34 AM Nathan Chancellor
wrote:
>
> When building with clang when CONFIG_CPU_LOONGSON3_WORKAROUNDS is
> enabled:
>
> In file included from lib/errseq.c:4:
> In file included from ./include/linux/atomic.h:7:
> ./arch/mips/include/asm/atomic.h:52:1: warning: converting th
On 1/14/21 8:50 AM, Mimi Zohar wrote:
On Thu, 2021-01-14 at 11:44 -0500, Mimi Zohar wrote:
[Cc'ing Sasha]
Hi Lakshmi,
On Thu, 2021-01-14 at 08:22 -0800, Lakshmi Ramasubramanian wrote:
On 1/13/21 6:49 PM, Mimi Zohar wrote:
Lakshmi is trying to address the situation where an event changes a
Some I2C devices may be glitchy due to electrical noise coming
from the device itself or because of possible board design issues.
To overcome this issue, the QUP's I2C in Qualcomm SoCs supports
a noise rejection setting for both SCL and SDA lines.
Introduce a setting for noise rejection through de
On Thu, 14 Jan 2021 16:13:23 + Stefan Chulski wrote:
> > > From: Stefan Chulski
> > >
> > > This patch doesn't change any functionality, but just extend MIB
> > > counter register and ethtool-statistic names with "err".
> > >
> > > The counter MVPP2_MIB_FRAGMENTS_RCVD in fact is Error counter.
Convert the qcom,i2c-qup binding to YAML schema.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/i2c/qcom,i2c-qup.txt | 40 -
.../devicetree/bindings/i2c/qcom,i2c-qup.yaml | 87 +++
2 files changed, 87 insertions(+), 40 deletions(-)
delete mode 10
This patch series converts the i2c-qup bindings to YAML and then
adds support for noise rejection, which is needed for some noisy
hardware, like the touchscreen on the F(x)Tec Pro1.
After adding noise rejection, the touchscreen stopped showing
ghost touch issues and lockups.
Tested on F(x)Tec Pro1
On Thu, Jan 14, 2021 at 08:36:50AM -0600, Josh Poimboeuf wrote:
> On Thu, Jan 14, 2021 at 11:54:18AM +, Mark Rutland wrote:
> > On Wed, Jan 13, 2021 at 01:33:13PM -0600, Josh Poimboeuf wrote:
> > > On Wed, Jan 13, 2021 at 04:57:43PM +, Mark Brown wrote:
> > > > From: Mark Rutland
> > > > +
Hello, lkml.
This is my first post to the list.
From: Linus Torvalds <>
Date: Fri, 8 Jan 2021 15:11:34 -0800
Subject:Re: fbcon: remove soft scrollback code (missing Doc. patch)
>On Fri, Jan 8, 2021 at 11:13 AM Phillip Susi
> wrote:
>> > Could we pause this madness? Scrollback is still u
Document the new noise rejection properties "qcom,noise-reject-sda"
and "qcom,noise-reject-scl".
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/i2c/qcom,i2c-qup.yaml | 14 ++
1 file changed, 14 insertions(+)
diff --git a/Documentation/devicetree/bindings
This adds support for the BOE BF060Y8M-AJ0 5.99" AMOLED module
that can be found in some F(x)Tec Pro1 and Elephone U1 devices.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/gpu/drm/panel/Kconfig | 11 +
drivers/gpu/drm/panel/Makefile| 1 +
.../gpu/drm/
On Thu, 2021-01-14 at 09:12 +0200, Jani Nikula wrote:
> On Wed, 13 Jan 2021, Lyude Paul wrote:
> > Currently, every different type of backlight hook that i915 supports is
> > pretty straight forward - you have a backlight, probably through PWM
> > (but maybe DPCD), with a single set of platform-sp
On 21-01-14 17:40:12, Jonathan Cameron wrote:
> On Mon, 11 Jan 2021 14:51:11 -0800
> Ben Widawsky wrote:
>
> > Provide enough functionality to utilize the mailbox of a memory device.
> > The mailbox is used to interact with the firmware running on the memory
> > device.
> >
> > The CXL specifica
On 14/01/2021 09:51, menglong8.d...@gmail.com wrote:
> From: Menglong Dong
>
> Replace the check for ETH_P_8021Q and ETH_P_8021AD in
> br_dev_queue_push_xmit with eth_type_vlan.
>
> Signed-off-by: Menglong Dong
> ---
> net/bridge/br_forward.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deleti
On 1/14/21 3:35 AM, Viresh Kumar wrote:
> The "oprofile" user-space tools don't use the kernel OPROFILE support
> any more, and haven't in a long time. User-space has been converted to
> the perf interfaces.
>
> Remove the old oprofile's architecture specific support.
>
> Suggested-by: Christoph He
Document the boe,bf060y8m-aj0 panel.
Signed-off-by: AngeloGioacchino Del Regno
---
.../display/panel/boe,bf060y8m-aj0.yaml | 67 +++
1 file changed, 67 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/panel/boe,bf060y8m-aj0.yaml
diff --git
a/D
On Thu 14 Jan 11:47 CST 2021, AngeloGioacchino Del Regno wrote:
> The TCSR's PHY_CLK_SCHEME register is not available on all SoC
> models, but some may still use a differential reference clock.
>
> In preparation for these SoCs, add a se_clk_scheme_default
> configuration entry and declare it to
On Thu 14 Jan 11:47 CST 2021, AngeloGioacchino Del Regno wrote:
> The SDM660 SoC uses the same configuration as MSM8996, but the
> clock scheme uses a differential reference clock and none of
> the SoCs in this series (630, 636 and others) have got a usable
> PHY_CLK_SCHEME register in the TCSR fo
On Thu 14 Jan 11:47 CST 2021, AngeloGioacchino Del Regno wrote:
> Support for the SDM630/660 series of SoCs was added to the driver:
> document the qcom,sdm660-qusb2-phy compatible here.
>
Reviewed-by: Bjorn Andersson
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
> Documentation/devic
On Thu, Jan 14, 2021 at 6:36 AM Jonathan Corbet wrote:
>
> On Wed, 13 Jan 2021 17:19:59 -0800
> Nick Desaulniers wrote:
>
> > Patch looks fine, but `make -j htmldocs` seems to be taking forever
> > for me so I can't render it. Is this a known issue?
> >
> > $ make -j htmldocs
> > SPHINX htmldo
From: Rafał Miłecki
BCM63138 has SATA controller that needs to be powered up using PMB.
Signed-off-by: Rafał Miłecki
---
Florian: this is based on your patches
ARM: dts: BCM63xx: enable SATA PHY and AHCI controller
reset: bcm63xx: Add Broadcom BCM63138 reset controller driver
I didn't test it
From: Rafał Miłecki
PMB can be also found on bcm63xx chipsets. It uses difference device
addresses so a new binding is required.
Signed-off-by: Rafał Miłecki
---
Documentation/devicetree/bindings/power/brcm,bcm-pmb.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetr
On 1/13/21 6:37 PM, Sean Christopherson wrote:
Drop the sev_enabled flag and switch its one user over to sev_active().
sev_enabled was made redundant with the introduction of sev_status in
commit b57de6cd1639 ("x86/sev-es: Add SEV-ES Feature Detection").
sev_enabled and sev_active() are guarantee
On 1/11/21 3:40 PM, Halil Pasic wrote:
On Tue, 22 Dec 2020 20:15:57 -0500
Tony Krowiak wrote:
The current implementation does not allow assignment of an AP adapter or
domain to an mdev device if each APQN resulting from the assignment
does not reference an AP queue device that is bound to t
On Tue, Jan 12, 2021 at 04:24:01PM -0800, Dave Hansen wrote:
> On 12/16/20 5:50 AM, Jarkko Sakkinen wrote:
> > Create a pointer array for each NUMA node with the references to the
> > contained EPC sections. Use this in __sgx_alloc_epc_page() to knock the
> > current NUMA node before the others.
>
Hi,
Since I don't have a cover letter I forgot the changes list.
V1->V2:
Add SMC_PCI_FEATURES calls to verify _READ, _WRITE and _SEG_INFO
functions exist.
Add a _SEG_INFO bus start, end validation against the ACPI table.
Adjust some function naming, and log messages.
On 1/13/21 4:40 PM, Jer
On Thu, 2021-01-14 at 18:35 +0100, Mauro Carvalho Chehab wrote:
> Instead of using 1/0 for true/false, change the type to boolean
> and change the returned value.
[]
> diff --git a/drivers/staging/hikey9xx/phy-hi3670-usb3.c
> b/drivers/staging/hikey9xx/phy-hi3670-usb3.c
[]
> @@ -326,24 +326,24 @@
On 2021-01-13 6:09 p.m., Mimi Zohar wrote:
On Thu, 2021-01-07 at 20:07 -0800, Tushar Sugandhi wrote:
Integrity critical data may belong to a single subsystem or it may
arise from cross subsystem interaction. Currently there is no mechanism
to group or limit the data based on certain label.
Il 14/01/21 18:52, Bjorn Andersson ha scritto:
On Thu 14 Jan 11:47 CST 2021, AngeloGioacchino Del Regno wrote:
The TCSR's PHY_CLK_SCHEME register is not available on all SoC
models, but some may still use a differential reference clock.
In preparation for these SoCs, add a se_clk_scheme_defaul
On Thu 14 Jan 11:49 CST 2021, AngeloGioacchino Del Regno wrote:
> Some I2C devices may be glitchy due to electrical noise coming
> from the device itself or because of possible board design issues.
> To overcome this issue, the QUP's I2C in Qualcomm SoCs supports
> a noise rejection setting for bo
If hvcs_probe() succeeded dev_set_drvdata() is called with a non-NULL
value, and if hvcs_probe() failed hvcs_remove() isn't called.
So there is no way dev_get_drvdata() can return NULL in hvcs_remove() and
the check can just go away.
Signed-off-by: Uwe Kleine-König
---
drivers/tty/hvc/hvcs.c |
If vcc_probe() succeeded dev_set_drvdata() is called with a non-NULL
value, and if vcc_probe() failed vcc_remove() isn't called.
So there is no way dev_get_drvdata() can return NULL in vcc_remove() and
the check can just go away.
Signed-off-by: Uwe Kleine-König
---
drivers/tty/vcc.c | 3 ---
1
Hello,
while working on changing the prototype of struct vio_driver::remove to
return void I noticed a few exit paths in such callbacks that return an
error code.
This is a bad thing because the return value is ignored (which is the
motivation to make it void) and the corresponding device then en
Hi,
On Thu, Jan 14, 2021 at 9:15 AM Bjorn Andersson
wrote:
>
> > > @@ -195,6 +201,20 @@ static int msm_pinmux_set_mux(struct pinctrl_dev
> > > *pctldev,
> > > if (WARN_ON(i == g->nfuncs))
> > > return -EINVAL;
> > >
> > > + /*
> > > +* If an GPIO interrupt i
vcc_get() returns the port that has provided port->index. As the port that
is about to be removed isn't removed yet this trivially will find this
port. So simplify the call to not assign an identical value to the port
pointer and drop the warning that is never hit.
Signed-off-by: Uwe Kleine-König
On Thu 14 Jan 11:49 CST 2021, AngeloGioacchino Del Regno wrote:
> Document the new noise rejection properties "qcom,noise-reject-sda"
> and "qcom,noise-reject-scl".
>
I presume these are unit-less levels?
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
> Signed-off-by: AngeloGioacchino Del Regn
Hi,
On Wed, Jan 13, 2021 at 11:14 PM Stephen Boyd wrote:
>
> > @@ -195,6 +201,20 @@ static int msm_pinmux_set_mux(struct pinctrl_dev
> > *pctldev,
> > if (WARN_ON(i == g->nfuncs))
> > return -EINVAL;
> >
> > + /*
> > +* If an GPIO interrupt is setup on this
On Wed, Jan 13, 2021 at 5:54 PM Marco Elver wrote:
>
> > +bool __kasan_check_byte(const void *addr, unsigned long ip);
> > +static __always_inline bool kasan_check_byte(const void *addr, unsigned
> > long ip)
> > +{
> > + if (kasan_enabled())
> > + return __kasan_check_byte(ad
On Thu, Jan 14, 2021 at 01:04:02PM +0800, Peter Chen wrote:
> On 21-01-14 11:59:07, Daewoong Kim wrote:
> > DMA mapping of urb->setup_packet is not necessary for xHCI host
> > controllers. The xHCI specification says that Setup Stage TRB includes
> > whole Setup Data; therefore, urb->setup_dma will
Commit 5c0a85fad949 ("mm: make faultaround produce old ptes") changed
the "faultaround" behaviour to initialise prefaulted PTEs as 'old',
since this avoids vmscan wrongly assuming that they are hot, despite
having never been explicitly accessed by userspace. The change has been
shown to benefit num
On CPUs with hardware AF/DBM, initialising prefaulted PTEs as 'old'
improves vmscan behaviour and does not appear to introduce any overhead
elsewhere.
Implement arch_wants_old_prefaulted_pte() to return 'true' if we detect
hardware access flag support at runtime. This can be extended in future
bas
Hi again folks,
This is the third version of the patches I previously posted here:
v1: https://lore.kernel.org/r/20201209163950.8494-1-w...@kernel.org
v2: https://lore.kernel.org/r/20210108171517.5290-1-w...@kernel.org
The patches allow architectures to opt-in at runtime for faultaround
mapp
From: "Kirill A. Shutemov"
alloc_set_pte() has two users with different requirements: in the
faultaround code, it called from an atomic context and PTE page table
has to be preallocated. finish_fault() can sleep and allocate page table
as needed.
PTL locking rules are also strange, hard to follo
The field is only ever read after being initialised, so mark it 'const'
before somebody tries to modify it again.
Cc: Kirill A. Shutemov
Cc: Linus Torvalds
Signed-off-by: Will Deacon
---
include/linux/mm.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/mm.h b
In preparation for const-ifying the 'info' field of 'struct vm_fault',
ensure that it is initialised using static initialisers.
Cc: Kirill A. Shutemov
Cc: Linus Torvalds
Signed-off-by: Will Deacon
---
mm/shmem.c| 8 +---
mm/swapfile.c | 13 -
2 files changed, 13 insertions
In preparation for const-ifying the 'info' field of 'struct vm_fault',
rework __collapse_huge_page_swapin() to avoid continously updating
vmf.info.address and instead populate a new 'struct vm_fault' on the
stack for each page being processed.
Cc: Kirill A. Shutemov
Cc: Linus Torvalds
Signed-off
Rather than modifying the 'address' field of the 'struct vm_fault_info'
passed to do_set_pte(), leave that to identify the real faulting address
and pass in the virtual address to be mapped by the new pte as a
separate argument.
This makes FAULT_FLAG_PREFAULT redundant, as a prefault entry can be
Hi Jean,
On 1/14/21 6:33 PM, Jean-Philippe Brucker wrote:
> Hi Eric,
>
> On Thu, Jan 14, 2021 at 05:58:27PM +0100, Auger Eric wrote:
The uacce-devel branches from
> https://github.com/Linaro/linux-kernel-uadk do provide this at the moment
> (they track the latest sva/zip-devel branc
On Tue, Dec 29 2020 at 3:55am -0500,
Satya Tangirala wrote:
> Update the device-mapper core to support exposing the inline crypto
> support of the underlying device(s) through the device-mapper device.
>
> This works by creating a "passthrough keyslot manager" for the dm
> device, which declare
On Wed, Jan 13, 2021 at 5:54 PM Marco Elver wrote:
>
> > +/*
> > + * Unlike kasan_check_read/write(), kasan_check_byte() is performed even
> > for
> > + * the hardware tag-based mode that doesn't rely on compiler
> > instrumentation.
> > + */
> > +bool __kasan_check_byte(const void *addr, unsign
On 1/14/21 11:12 AM, Sean Christopherson wrote:
On Thu, Jan 14, 2021, Tom Lendacky wrote:
On 1/13/21 6:36 PM, Sean Christopherson wrote:
Free sev_asid_bitmap if the reclaim bitmap allocation fails, othwerise
KVM will unnecessarily keep the bitmap when SEV is not fully enabled.
Freeing the page
Permissions are necessary to get a tracepoint id. Fail the test when the
read fails.
Signed-off-by: Ian Rogers
---
tools/lib/perf/tests/test-evlist.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/lib/perf/tests/test-evlist.c
b/tools/lib/perf/tests/test-evlist.c
index d913241d4135..b
On Mon, 11 Jan 2021 14:51:19 -0800
Ben Widawsky wrote:
> The Command Effects Log (CEL) is specified in the CXL 2.0 specification.
> The CEL is one of two types of logs, the other being vendor specific.
> They are distinguished in hardware/spec via UUID. The CEL is immediately
> useful for 2 thing
701 - 800 of 1491 matches
Mail list logo
