Re: kprobes broken since 0d00449c7a28 ("x86: Replace ist_enter() with nmi_enter()")

On Sat, 30 Jan 2021 09:28:32 +0100 Peter Zijlstra wrote: > On Fri, Jan 29, 2021 at 04:24:54PM -0500, Steven Rostedt wrote: > > Specifically, kprobe and ftrace callbacks may have this: > > > > if (in_nmi()) > > return; > > > > raw_spin_lock_irqsave(&lock, flags); > > [..]

Re: [PATCH] drm/i915: Remove unreachable code

Quoting Vinicius Tinti (2021-01-30 12:34:11) > On Fri, Jan 29, 2021 at 08:55:54PM +, Chris Wilson wrote: > > Quoting Vinicius Tinti (2021-01-29 18:15:19) > > > By enabling -Wunreachable-code-aggressive on Clang the following code > > > paths are unreachable. > > > > That code exists as comment

Re: [PATCH 5.10 00/32] 5.10.12-rc1 review

On Fri, Jan 29, 2021 at 01:59:14PM +0100, Pavel Machek wrote: > On Fri 2021-01-29 12:07:10, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.10.12 release. > > There are 32 patches in this series, all will be posted as a response > > to this one. If anyone has a

[PATCH v3] kvfree_rcu: Release page cache under memory pressure

From: Zqiang Add free per-cpu existing krcp's page cache operation, when the system is under memory pressure. Signed-off-by: Zqiang --- kernel/rcu/tree.c | 26 ++ 1 file changed, 26 insertions(+) diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c index c1ae1e52f638..64

Re: [PATCH 5.10 00/32] 5.10.12-rc1 review

On Fri, Jan 29, 2021 at 11:52:04PM +0530, Naresh Kamboju wrote: > On Fri, 29 Jan 2021 at 16:47, Greg Kroah-Hartman > wrote: > > > > This is the start of the stable review cycle for the 5.10.12 release. > > There are 32 patches in this series, all will be posted as a response > > to this one. If a

Re: [PATCH 5.10 00/32] 5.10.12-rc1 review

On Fri, Jan 29, 2021 at 10:23:16AM -0800, Guenter Roeck wrote: > On Fri, Jan 29, 2021 at 12:07:10PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.10.12 release. > > There are 32 patches in this series, all will be posted as a response > > to this one.

[PATCH v2] rtl8xxxu: remove unused assignment value

From: wengjianfeng at first, ret was assigned to zero, but later assigned to a funciton,so the assignment to zero is no use, which can simple be removed instead. Signed-off-by: wengjianfeng --- drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_8192e.c | 2 -- 1 file changed, 2 deletions(-) diff

[GIT PULL 1/2] MAINTAINERS: Update to TI maintainer for v5.12

Hi, Please pull the following MAINTAINERS file update for v5.12 cycle. Made sense to send via ARM path since the main PR path was for TI platforms. The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e: Linux 5.11-rc1 (2020-12-27 15:30:22 -0800) are available in the Git

[GIT PULL 2/2] arm64: TI K3 DT updates for v5.12

Hi, Please pull the following device tree changes for v5.12 cycle. The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e: Linux 5.11-rc1 (2020-12-27 15:30:22 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git

Re: [Patch v2 0/3] Enable flexcan support in LS1028A/LX2160A

On Thu, Jan 21, 2021 at 04:27:36PM +0530, Kuldeep Singh wrote: > This patch set adds device-tree support for LX2160A-RDB/QDS. > > Also, update flexcan entry for LS1028A and enable support further for > LS1028A-RDB/QDS. > > Patch1: Add dtsi and dts properties for LX2160A > Patch2: Update dtsi pro

Re: [PATCH v3 2/5] x86/sgx: Optimize the locking range in sgx_sanitize_section()

On Sun, Jan 24, 2021 at 02:29:04PM +0800, Tianjia Zhang wrote: > The spin lock of sgx_epc_section only locks the page_list. The > EREMOVE operation and init_laundry_list is not necessary in the > protection range of the spin lock. This patch reduces the lock > range of the spin lock in the function

Re: [PATCH v3 4/5] x86/sgx: Allows ioctl PROVISION to execute before CREATE

On Sun, Jan 24, 2021 at 02:29:06PM +0800, Tianjia Zhang wrote: > In the function sgx_create_enclave(), the direct assignment > operation of attributes_mask determines that the ioctl PROVISION > operation must be executed after the ioctl CREATE operation, > which will limit the flexibility of sgx de

Re: [PATCH] arm64: dts: freescale: fix dcfg address range

On Thu, Jan 21, 2021 at 04:52:37PM +0100, Zyta Szpak wrote: > Dcfg was overlapping with clockgen address space which resulted > in failure in memory allocation for dcfg. According regs description > dcfg size should not be bigger than 4KB. > > Signed-off-by: Zyta Szpak I changed subject prefix t

Re: [PATCH v2 4/8] KVM: arm64: Generate hyp relocation data

On Fri, 29 Jan 2021 21:43:25 +, Guenter Roeck wrote: > > Hi, > > On Tue, Jan 05, 2021 at 06:05:37PM +, David Brazdil wrote: > > Add a post-processing step to compilation of KVM nVHE hyp code which > > calls a custom host tool (gen-hyprel) on the partially linked object > > file (hyp sect

[PATCH net] net: dsa: mv88e6xxx: override existent unicast portvec in port_fdb_add

Having multiple destination ports for a unicast address does not make sense. Make port_db_load_purge override existent unicast portvec instead of adding a new port bit. Fixes: 884729399260 ("net: dsa: mv88e6xxx: handle multiple ports in ATU") Signed-off-by: DENG Qingfang --- drivers/net/dsa/mv88

Re: [PATCH 5.10 00/32] 5.10.12-rc1 review

On 29/01/2021 18:22, Naresh Kamboju wrote: > On Fri, 29 Jan 2021 at 16:47, Greg Kroah-Hartman > wrote: >> >> This is the start of the stable review cycle for the 5.10.12 release. >> There are 32 patches in this series, all will be posted as a response >> to this one. If anyone has any issues wi

Re: [PATCH 4.19 00/26] 4.19.172-rc1 review

On 29/01/2021 18:22, Guenter Roeck wrote: > On Fri, Jan 29, 2021 at 12:06:57PM +0100, Greg Kroah-Hartman wrote: >> This is the start of the stable review cycle for the 4.19.172 release. >> There are 26 patches in this series, all will be posted as a response >> to this one. If anyone has any iss

Re: [PATCH 4.14 00/50] 4.14.218-rc1 review

On 29/01/2021 18:21, Guenter Roeck wrote: > On Fri, Jan 29, 2021 at 12:06:25PM +0100, Greg Kroah-Hartman wrote: >> This is the start of the stable review cycle for the 4.14.218 release. >> There are 50 patches in this series, all will be posted as a response >> to this one. If anyone has any iss

Re: [PATCH 4.4 00/24] 4.4.254-rc1 review

On 29/01/2021 18:21, Guenter Roeck wrote: > On Fri, Jan 29, 2021 at 12:06:35PM +0100, Greg Kroah-Hartman wrote: >> This is the start of the stable review cycle for the 4.4.254 release. >> There are 24 patches in this series, all will be posted as a response >> to this one. If anyone has any issu

Re: [PATCH 5.4 00/18] 5.4.94-rc1 review

On 29/01/2021 18:22, Guenter Roeck wrote: > On Fri, Jan 29, 2021 at 12:07:14PM +0100, Greg Kroah-Hartman wrote: >> This is the start of the stable review cycle for the 5.4.94 release. >> There are 18 patches in this series, all will be posted as a response >> to this one. If anyone has any issue

Re: [PATCH] drm/lima: Use delayed timer as default in devfreq profile

Thanks for the patch. But I can't observe any difference on glmark2 with or without this patch. Maybe you can provide other test which can benefit from it. Considering it will wake up CPU more frequently, and user may choose to change this by sysfs, I'd like to not apply it. Regards, Qiang On We

Re: [PATCH v2] drm/lima: add governor data with pre-defined thresholds

This patch gets minor improvement on glmark2 (160->162). Seems there's no way for user to change this value, do we? Or there's work pending to expose it to sysfs? Regards, Qiang On Thu, Jan 28, 2021 at 3:40 AM Christian Hewitt wrote: > > This patch adapts the panfrost pre-defined thresholds cha

Re: [PATCH 1/5] docs: arm: marvell: turn the automatic links into labels

On Fri, Jan 29, 2021 at 05:20:28PM -0700, Jonathan Corbet wrote: > Lubomir Rintel writes: > > > Lines ending with obscenely long URLs at the end don't look good. > > > > Even if these links are not that long at this point, they will be when > > replaced with an archive link in a subsequent patch

Linux 4.4.254

I'm announcing the release of the 4.4.254 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.4.254

diff --git a/Makefile b/Makefile index 8175b77e5105..5abb21c7d852 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 253 +SUBLEVEL = 254 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/sh/drivers/dma/Kconfig b/arch/sh/drivers/dma/Kconfig index

Re: Linux 4.9.254

diff --git a/Makefile b/Makefile index 62a07bdcfacb..ea9ea119460d 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 253 +SUBLEVEL = 254 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/sh/drivers/dma/Kconfig b/arch/sh/drivers/dma/Kconfig index 7

Linux 4.9.254

I'm announcing the release of the 4.9.254 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.14.218

diff --git a/Makefile b/Makefile index 2dabcc4f0d16..494420ad33a1 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 VERSION = 4 PATCHLEVEL = 14 -SUBLEVEL = 217 +SUBLEVEL = 218 EXTRAVERSION = NAME = Petit Gorille diff --git a/arch/arm/xen/enlighten.c b/ar

Linux 4.14.218

I'm announcing the release of the 4.14.218 kernel. All users of the 4.14 kernel series must upgrade. The updated 4.14.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.14.y and can be browsed at the normal kernel.org git web browser

Re: Linux 4.19.172

diff --git a/Documentation/device-mapper/dm-integrity.txt b/Documentation/device-mapper/dm-integrity.txt index 297251b0d2d5..bf6af2ade0a6 100644 --- a/Documentation/device-mapper/dm-integrity.txt +++ b/Documentation/device-mapper/dm-integrity.txt @@ -146,6 +146,13 @@ block_size:number Supp

Re: Linux 5.4.94

diff --git a/Documentation/admin-guide/device-mapper/dm-integrity.rst b/Documentation/admin-guide/device-mapper/dm-integrity.rst index a30aa91b5fbe..3463883844c0 100644 --- a/Documentation/admin-guide/device-mapper/dm-integrity.rst +++ b/Documentation/admin-guide/device-mapper/dm-integrity.rst @@

Linux 4.19.172

I'm announcing the release of the 4.19.172 kernel. All users of the 4.19 kernel series must upgrade. The updated 4.19.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.19.y and can be browsed at the normal kernel.org git web browser

Re: Linux 5.10.12

diff --git a/Makefile b/Makefile index 7a5d906f6ee3..a6b2e64bcf6c 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 VERSION = 5 PATCHLEVEL = 10 -SUBLEVEL = 11 +SUBLEVEL = 12 EXTRAVERSION = NAME = Kleptomaniac Octopus diff --git a/drivers/gpio/gpio-mvebu.

[PATCH v2 0/3] Convert the mtk_disp driver to aotmic API

Changes since v1: - Seperate clock operation as single patch. - Seperate apply() as single patch. - Seperate get_state() operation as single patch. Jitao Shi (3): pwm: mtk_disp: clear the clock operations pwm: mtk_disp: convert the driver to atomic API pwm: mtk_disp: implement .get_state(

[PATCH v2 3/3] pwm: mtk_disp: implement .get_state()

Signed-off-by: Jitao Shi --- drivers/pwm/pwm-mtk-disp.c | 46 ++ 1 file changed, 46 insertions(+) diff --git a/drivers/pwm/pwm-mtk-disp.c b/drivers/pwm/pwm-mtk-disp.c index 502228adf718..166e0a8ca703 100644 --- a/drivers/pwm/pwm-mtk-disp.c +++ b/driver

[PATCH v2 1/3] pwm: mtk_disp: clear the clock operations

Remove the clk_prepare from mtk_disp_pwm_probe. Remove the clk_unprepare from mtk_disp_pwm_remove. Signed-off-by: Jitao Shi --- drivers/pwm/pwm-mtk-disp.c | 23 ++- 1 file changed, 2 insertions(+), 21 deletions(-) diff --git a/drivers/pwm/pwm-mtk-disp.c b/drivers/pwm/pwm-mtk

Re: [PATCH 20/21] clk: imx: Move 'imx6sl_set_wait_clk()'s prototype out to accessible header

On Tue, Jan 26, 2021 at 12:45:39PM +, Lee Jones wrote: > Fixes the following W=1 kernel build warning(s): > > drivers/clk/imx/clk-imx6sl.c:156:6: warning: no previous prototype for > ‘imx6sl_set_wait_clk’ [-Wmissing-prototypes] > > Cc: Russell King > Cc: Shawn Guo > Cc: Sascha Hauer > Cc

Re: [Patch v2 net-next 2/7] octeontx2-af: Add new CGX_CMD to get PHY FEC statistics

On Sat, Jan 30, 2021 at 4:53 AM Hariprasad Kelam wrote: > > Hi Willem, > > > -Original Message- > > From: Willem de Bruijn > > Sent: Thursday, January 28, 2021 1:50 AM > > To: Hariprasad Kelam > > Cc: Network Development ; LKML > ker...@vger.kernel.org>; David Miller ; Jakub > > Kicinsk

[PATCH] soc: qcom: ocmem: don't return NULL in of_get_ocmem

If ocmem probe fails for whatever reason, of_get_ocmem returned NULL. Without this, users must check for both NULL and IS_ERR on the returned pointer - which didn't happen in drivers/gpu/drm/msm/adreno/adreno_gpu.c leading to a NULL pointer dereference. Fixes: 88c1e9404f1d ("soc: qcom: add OCMEM d

Re: [PATCH 2/2] ARM: dts: exynos: use Exynos5420 dedicated USB2 PHY compatible

On Sat, Jan 30, 2021 at 03:14:22PM +0100, Arnd Bergmann wrote: > On Wed, Jan 27, 2021 at 8:59 AM Krzysztof Kozlowski wrote: > > On Tue, Jan 26, 2021 at 11:44:26PM +0100, Arnd Bergmann wrote: > > > On Fri, Nov 20, 2020 at 12:10 PM Marek Szyprowski > > > wrote: > > > > > It won't work easily with

Re: [PATCHv1] ASoC: cpcap: fix microphone timeslot mask

* Sebastian Reichel [210123 17:30]: > This is compile tested only, since I currently do not have > my Droid 4 ready for running some tests. Maybe Tony, Pavel or > Merlijn can give it a go using e.g. arecord. I just tried recording with arecord -D plughw:CARD=Audio,DEV=1 | hd but only see the head

Re: [PATCH] media: allegro-dvt: Use __packed sentence

Hi, > > Spelling check please? > > And _why_ are you making this change, what does this do "better" than > the original? > Actually, I'm really new here, and this is my first patch. I run the checkpatch.pl, and give me that recommendation. I would like to look the David comments. Thanks! eama

Re: [PATCH v4 06/13] ASoC/extcon: arizona: Move arizona jack code to sound/soc/codecs/arizona-jack.c

On Sat, Jan 23, 2021 at 01:13:06PM +0100, Hans de Goede wrote: > The jack handling for arizona codecs is being refactored so that it is > done directly by the codec drivers, instead of having an extcon-driver > bind to a separate "arizona-extcon" child-device for this. > > drivers/mfd/arizona-core

Re: [PATCH v5] tracepoint: Do not fail unregistering a probe due to memory failure

On Sat, 30 Jan 2021 23:30:18 +1100 Alexey Kardashevskiy wrote: > I still need the following chunk (same "if (it_func_ptr)" as in the v2's > reply) in order to stop crashes: > > And this is on powerpc, correct? Do you still have the same crash with v3 (that's the one I'm going to go with for

Re: [PATCH stable v5.4 2/2] IPv6: reply ICMP error if the first fragment don't include all headers

On Sat, Jan 30, 2021 at 05:24:52PM +0530, Aviraj CJ wrote: > From: Hangbin Liu > > commit 2efdaaaf883a143061296467913c01aa1ff4b3ce upstream. > > Based on RFC 8200, Section 4.5 Fragment Header: > > - If the first fragment does not include all headers through an > Upper-Layer header, then

Re: [PATCH v4 05/13] extcon: arizona: Always use pm_runtime_get_sync() when we need the device to be awake

On Sat, Jan 23, 2021 at 01:13:05PM +0100, Hans de Goede wrote: > Before this commit the extcon-arizona code was mixing pm_runtime_get() > and pm_runtime_get_sync() in different places. > > In all places where pm_runtime_get[_sync]() is called, the code > makes use of the device immediately after t

Re: [PATCH v4 03/13] extcon: arizona: Fix various races on driver unbind

On Sat, Jan 23, 2021 at 01:13:03PM +0100, Hans de Goede wrote: > We must free/disable all interrupts and cancel all pending works > before doing further cleanup. > > Before this commit arizona_extcon_remove() was doing several > register writes to shut things down before disabling the IRQs > and i

ERROR: modpost: ".__warn_printk" undefined!

ago config: powerpc64-randconfig-c003-20210130 (attached as .config) compiler: powerpc64-linux-gcc (GCC) 9.3.0 reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # ht

Re: [PATCH net-next 9/9] net: ipa: don't disable NAPI in suspend

On Fri, Jan 29, 2021 at 3:29 PM Alex Elder wrote: > > The channel stop and suspend paths both call __gsi_channel_stop(), > which quiesces channel activity, disables NAPI, and (on other than > SDM845) stops the channel. Similarly, the start and resume paths > share __gsi_channel_start(), which sta

Re: [PATCH v2 3/4] arm64: dts: qcom: Disable MDSS by default for 8916/8016 devices

On 30.01.2021 11:57, Vincent Knecht wrote: > Disable MDSS (Mobile Display Subsystem) by default in msm8916.dtsi > and only explicitly enable it in devices' DT which actually use it. > > This leads to faster boot and cleaner logs for other devices, > which also won't have to explicitly disable MDS

Re: [PATCH v4 13/13] ASoC: Intel: bytcr_wm5102: Add jack detect support

On Sat, Jan 23, 2021 at 01:17:20PM +0100, Hans de Goede wrote: > Add jack detect support by creating a jack and calling > snd_soc_component_set_jack to register the created jack > with the codec. > > Reviewed-by: Andy Shevchenko > Signed-off-by: Hans de Goede > --- > +static struct snd_soc_jack_

Re: [PATCH v2 4/4] arm64: dts: qcom: msm8916-alcatel-idol347: Add framebuffer support

On 30.01.2021 11:57, Vincent Knecht wrote: > Add simple-framebuffer support and related reserved-memory block. > > Signed-off-by: Vincent Knecht > --- > .../boot/dts/qcom/msm8916-alcatel-idol347.dts | 31 +++ > 1 file changed, 31 insertions(+) > > diff --git a/arch/arm64/boot/dt

Re: short-circuit and over-current IRQs

Il 29/01/21 10:14, Matti Vaittinen ha scritto: On Thu, 2021-01-28 at 12:10 +, Mark Brown wrote: On Thu, Jan 28, 2021 at 09:23:08AM +, Vaittinen, Matti wrote: On Wed, 2021-01-27 at 16:32 +, Mark Brown wrote: Note that the events the API currently has are expected to be for the actu

Re: [PATCH v2 2/4] arm64: dts: qcom: Add device tree for Alcatel Idol 3 (4.7")

On 30.01.2021 11:57, Vincent Knecht wrote: > The Alcatel Idol 3 (4.7") is a smartphone based on MSM8916. > Add a device tree with support for USB, eMMC, SD-Card, WiFi, > BT, power/volume buttons, vibrator and the following sensors: > magnetometer, accelerometer, gyroscope, ambient light+proximity

Re: [PATCH v4 12/13] ASoC: arizona: Make the wm5102, wm5110, wm8997 and wm8998 drivers use the new jack library

On Sat, Jan 23, 2021 at 01:17:19PM +0100, Hans de Goede wrote: > Make all arizona codec drivers for which drivers/mfd/arizona-core.c used > to instantiate a "arizona-extcon" child-device use the new arizona-jack.c > library for jack-detection. > > This has been tested on a Lenovo Yoga Tablet 2 105

Re: [PATCH v4 10/13] ASoC: arizona-jack: Use snd_soc_jack to report jack events

On Sat, Jan 23, 2021 at 01:17:17PM +0100, Hans de Goede wrote: > Use the snd_soc_jack code to report jack events, instead of using extcon > for reporting the cable-type + an input_dev for reporting the button > presses. > > The snd_soc_jack code will report the cable-type through both input_dev >

[GIT PULL] s390 updates for 5.11-rc6

Hello Linus, please pull s390 fixes for 5.11-rc6. Thank you, Vasily The following changes since commit 6ee1d745b7c9fd573fba142a2efdad76a9f1cb04: Linux 5.11-rc5 (2021-01-24 16:47:14 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git

Re: [RESEND PATCH net v4] udp: ipv4: manipulate network header of NATed UDP GRO fraglist

From: Dongseok Yi Date: Sat, 30 Jan 2021 08:13:27 +0900 > UDP/IP header of UDP GROed frag_skbs are not updated even after NAT > forwarding. Only the header of head_skb from ip_finish_output_gso -> > skb_gso_segment is updated but following frag_skbs are not updated. > > A call path skb_mac_gso_s

Re: [PATCH v4 07/13] ASoC: arizona-jack: Move jack-detect variables to struct arizona_priv

On Sat, Jan 23, 2021 at 01:13:07PM +0100, Hans de Goede wrote: > Move all the jack-detect variables from struct arizona_extcon_info to > struct arizona_priv. > > This is part of a patch series converting the arizona extcon driver into > a helper library for letting the arizona codec-drivers direct

Re: [PATCH v4 08/13] ASoC: arizona-jack: Use arizona->dev for runtime-pm

On Sat, Jan 23, 2021 at 01:13:08PM +0100, Hans de Goede wrote: > Drivers for MFD child-devices such as the arizona codec drivers > and the arizona-extcon driver can choose to either make > runtime_pm_get/_put calls on their own child-device, which will > then be propagated to their parent; or they

Re: [PATCH v4 02/13] extcon: arizona: Fix some issues when HPDET IRQ fires after the jack has been unplugged

On Sat, Jan 23, 2021 at 01:13:02PM +0100, Hans de Goede wrote: > When the jack is partially inserted and then removed again it may be > removed while the hpdet code is running. In this case the following > may happen: > > 1. The "JACKDET rise" or ""JACKDET fall" IRQ triggers > 2. arizona_jackdet r

Re: [PATCH v4 09/13] ASoC: arizona-jack: convert into a helper library for codec drivers

On Sat, Jan 23, 2021 at 01:13:09PM +0100, Hans de Goede wrote: > Convert the arizona extcon driver into a helper library for direct use > from the arizona codec-drivers, rather then being bound to a separate > MFD cell. > > Note the probe (and remove) sequence is split into 2 parts: > > 1. The ar

Re: [PATCH] hwmon: lm75: Use zero lm75_type for lm75

On 1/30/21 7:43 AM, Matwey V. Kornilov wrote: > > > сб, 30 янв. 2021 г. в 18:31, Guenter Roeck >: >> >> On 1/30/21 2:10 AM, Matwey V. Kornilov wrote: >> > There is a logical flaw in lm75_probe() function introduced in >> > >> >     e97a45f1b460 ("hwmon: (lm75) Add OF d

Re: [PATCH v2 3/5] pcie-qcom: provide a way to power up qca6390 chip on RB5 platform

On Sat, 30 Jan 2021 at 06:53, Bjorn Andersson wrote: > > On Fri 29 Jan 16:19 CST 2021, Dmitry Baryshkov wrote: > > > On Sat, 30 Jan 2021 at 00:50, Bjorn Helgaas wrote: > > > > > > On Fri, Jan 29, 2021 at 06:45:21AM +0300, Dmitry Baryshkov wrote: > > > > On 28/01/2021 22:26, Rob Herring wrote: > >

Re: [PATCH] drm/msm/dsi: save PLL registers across first PHY reset

On Sat, 30 Jan 2021 at 05:00, Benjamin Li wrote: > > > On 10/30/20 6:55 AM, Dmitry Baryshkov wrote: > > Hello, > > > > On 07/10/2020 03:10, benl-kernelpatc...@squareup.com wrote: > >> From: Benjamin Li > >> > >> Take advantage of previously-added support for persisting PLL > >> registers across D

Re: [PATCH v2 3/5] pcie-qcom: provide a way to power up qca6390 chip on RB5 platform

On Sat, 30 Jan 2021 at 11:04, Yassine Oudjana wrote: > > On Thu, Jan 28, 2021 at 11:52 AM Dmitry Baryshkov > wrote: > > > > Some Qualcomm platforms require to power up an external device before > > probing the PCI bus. E.g. on RB5 platform the QCA6390 WiFi/BT chip needs > > to be powered up befor

Re: [PATCH v2 4/8] KVM: arm64: Generate hyp relocation data

On Sat, Jan 30, 2021 at 01:44:15PM +, Marc Zyngier wrote: > On Fri, 29 Jan 2021 21:43:25 +, > Guenter Roeck wrote: > > > > Hi, > > > > On Tue, Jan 05, 2021 at 06:05:37PM +, David Brazdil wrote: > > > Add a post-processing step to compilation of KVM nVHE hyp code which > > > calls a c

Φόρμα επικοινωνίας Autokollises.gr

Από: 💙 Do you want to chat? My profile is here: https://bit.ly/3r11zyz?e6u 💙 Μήνυμα: 8xep0y2t -- Το email αυτό στάλθηκε από τη φόρμα επικοινωνίας του www.autokollises.gr

Re: [PATCH v2 net-next 3/4] net: introduce common dev_page_is_reserved()

From: Jakub Kicinski Date: Fri, 29 Jan 2021 18:39:07 -0800 > On Wed, 27 Jan 2021 20:11:23 + Alexander Lobakin wrote: > > + * dev_page_is_reserved - check whether a page can be reused for network Rx > > + * @page: the page to test > > + * > > + * A page shouldn't be considered for reusing/recy

Re: [PATCH 1/2] hwmon: lm75: Add NXP LM75A to of_match list

On 1/30/21 2:38 AM, Matwey V. Kornilov wrote: > NXP LM75A is compatible with original LM75A while it has improved > 11-bit precision. > > https://www.nxp.com/docs/en/data-sheet/LM75A.pdf > > Signed-off-by: Matwey V. Kornilov > --- > drivers/hwmon/lm75.c | 4 > 1 file changed, 4 insertions(

Re: [PATCH] hwmon: lm75: Use zero lm75_type for lm75

On 1/30/21 2:10 AM, Matwey V. Kornilov wrote: > There is a logical flaw in lm75_probe() function introduced in > > e97a45f1b460 ("hwmon: (lm75) Add OF device ID table") > > Note, that of_device_get_match_data() returns NULL when no match > found. This is the case when OF node exists but has u

[PATCH 1/1] iommu/vt-d: Fix compile error [-Werror=implicit-function-declaration]

trace_qi_submit() could be used when interrupt remapping is supported, but DMA remapping is not. In this case, the following compile error occurs. ../drivers/iommu/intel/dmar.c: In function 'qi_submit_sync': ../drivers/iommu/intel/dmar.c:1311:3: error: implicit declaration of function 'trace_qi_s

Re: [PATCH v5] tracepoint: Do not fail unregistering a probe due to memory failure

On Sat, 30 Jan 2021 09:36:26 -0500 Steven Rostedt wrote: > Do you still have the same crash with v3 (that's the one I'm going to > go with for now.) > > https://lore.kernel.org/r/20201118093405.7a6d2...@gandalf.local.home Just curious, does the following patch fix it for v5? -- Steve diff --

Re: [PATCH v4 01/13] mfd: arizona: Drop arizona-extcon cells

On Sat, Jan 23, 2021 at 01:13:01PM +0100, Hans de Goede wrote: > The arizona jack-dection handling is being reworked so that the > codec-child-device drivers directly handle jack-detect themselves, > so it is no longer necessary to instantiate "arizona-extcon" > child-devices. > > Signed-off-by: H

[PATCH] spi: fsl: invert spisel_boot signal on MPC8309

Commit 7a2da5d7960a ("spi: fsl: Fix driver breakage when SPI_CS_HIGH is not set in spi->mode") broke our MPC8309 board by effectively inverting the boolean value passed to fsl_spi_cs_control. The SPISEL_BOOT signal is used as chipselect, but it's not a gpio, so we cannot rely on gpiolib handling th

Re: [PATCH v6 1/3] dt-bindings: arm: imx: add imx8mm nitrogen support

On Thu, Jan 28, 2021 at 08:35:52PM +0100, Adrien Grassein wrote: > The Nitrogen8M Mini is an ARM based single board computer (SBC). > > Signed-off-by: Adrien Grassein > Reviewed-by: Krzysztof Kozlowski Applied all 3, thanks.

Re: [PATCH v3 5/5] x86/sgx: Remove redundant if conditions in sgx_encl_create

On Sun, Jan 24, 2021 at 02:29:07PM +0800, Tianjia Zhang wrote: > In this scenario, there is no case where va_page is NULL, and > the error has been checked. The if condition statement here is > redundant, so remove the condition detection. > > Signed-off-by: Tianjia Zhang > --- > arch/x86/kernel

Re: [PATCH v4 11/13] ASoC: arizona-jack: Cleanup logging

On Sat, Jan 23, 2021 at 01:17:18PM +0100, Hans de Goede wrote: > Cleanup the use of dev_foo functions used for logging: > > 1. Many of these are unnecessarily split over multiple lines > 2. Use dev_err_probe() in cases where we might get a -EPROBE_DEFER >return value > > Suggested-by: Andy Sh

Re: [PATCH net] net: hdlc_x25: Use qdisc to queue outgoing LAPB frames

On Fri, Jan 29, 2021 at 5:36 PM Jakub Kicinski wrote: > > I'm still struggling to wrap my head around this. > > Did you test your code with lockdep enabled? Which Qdisc are you using? > You're queuing the frames back to the interface they came from - won't > that cause locking issues? Hmm... Than

Linux 5.4.94

I'm announcing the release of the 5.4.94 kernel. All users of the 5.4 kernel series must upgrade. The updated 5.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.4.y and can be browsed at the normal kernel.org git web browser:

Re: [PATCH 2/2] ARM: dts: exynos: use Exynos5420 dedicated USB2 PHY compatible

On Wed, Jan 27, 2021 at 8:59 AM Krzysztof Kozlowski wrote: > On Tue, Jan 26, 2021 at 11:44:26PM +0100, Arnd Bergmann wrote: > > On Fri, Nov 20, 2020 at 12:10 PM Marek Szyprowski > > wrote: > > > It won't work easily with both compatibles, because in the 5420 variant > > > I've also changed the

Re: [PATCH] usb: host: xhci: mvebu: make USB 3.0 PHY optional for Armada 3720

On Saturday 30 January 2021 17:31:41 Tomasz Maciej Nowak wrote: > W dniu 23.12.2020 o 17:24, Pali Rohár pisze: > > Older ATF does not provide SMC call for USB 3.0 phy power on functionality > > and therefore initialization of xhci-hcd is failing when older version of > > ATF is used. In this case p

[PATCH v2 2/3] pwm: mtk_disp: convert the driver to atomic API

Switch the driver to atomic API apply(). Signed-off-by: Jitao Shi --- drivers/pwm/pwm-mtk-disp.c | 114 +++-- 1 file changed, 58 insertions(+), 56 deletions(-) diff --git a/drivers/pwm/pwm-mtk-disp.c b/drivers/pwm/pwm-mtk-disp.c index 21416a8b6b47..502228

Linux 5.10.12

I'm announcing the release of the 5.10.12 kernel. All users of the 5.10 kernel series must upgrade. The updated 5.10.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.10.y and can be browsed at the normal kernel.org git web browser:

Re: [PATCH] usb: host: xhci: mvebu: make USB 3.0 PHY optional for Armada 3720

W dniu 30.01.2021 o 17:35, Pali Rohár pisze: > On Saturday 30 January 2021 17:31:41 Tomasz Maciej Nowak wrote: >> W dniu 23.12.2020 o 17:24, Pali Rohár pisze: >>> Older ATF does not provide SMC call for USB 3.0 phy power on functionality >>> and therefore initialization of xhci-hcd is failing when

Re: [PATCH] usb: host: xhci: mvebu: make USB 3.0 PHY optional for Armada 3720

W dniu 23.12.2020 o 17:24, Pali Rohár pisze: > Older ATF does not provide SMC call for USB 3.0 phy power on functionality > and therefore initialization of xhci-hcd is failing when older version of > ATF is used. In this case phy_power_on() function returns -EOPNOTSUPP. > > [3.108467] mvebu-a3

[PATCH] pinctrl: nuvoton: npcm7xx: Fix alignment of table header comment

Make it so that each column label is in the column that it is supposed to refer to. Signed-off-by: Jonathan Neuschäfer --- drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c b/drivers/pinctrl/nu

[PATCH v11 0/5] arm64: ARMv8.5-A: MTE: Add async mode support

This patchset implements the asynchronous mode support for ARMv8.5-A Memory Tagging Extension (MTE), which is a debugging feature that allows to detect with the help of the architecture the C and C++ programmatic memory errors like buffer overflow, use-after-free, use-after-return, etc. MTE is bui

[PATCH v11 2/5] kasan: Add KASAN mode kernel parameter

Architectures supported by KASAN_HW_TAGS can provide a sync or async mode of execution. On an MTE enabled arm64 hw for example this can be identified with the synchronous or asynchronous tagging mode of execution. In synchronous mode, an exception is triggered if a tag check fault occurs. In asynch

[PATCH v11 3/5] kasan: Add report for async mode

KASAN provides an asynchronous mode of execution. Add reporting functionality for this mode. Cc: Dmitry Vyukov Cc: Andrey Ryabinin Cc: Alexander Potapenko Cc: Andrey Konovalov Reviewed-by: Andrey Konovalov Signed-off-by: Vincenzo Frascino Signed-off-by: Andrey Konovalov --- include/linux/

arm: sunxi: &83t: WARNING: CPU: 2 PID: 57 at drivers/thermal/thermal_core.c:563 thermal_zone_device_update

Hello When booting next-20210128, I got the following warning on by bpim3 6.148421] [ cut here ] [6.153145] WARNING: CPU: 2 PID: 57 at drivers/thermal/thermal_core.c:563 thermal_zone_device_update+0x134/0x154 [6.163378] 'thermal_zone_device_update' must not be

[PATCH v11 5/5] kasan: don't run tests in async mode

From: Andrey Konovalov Asynchronous KASAN mode doesn't guarantee that a tag fault will be detected immediately and causes tests to fail. Forbid running them in asynchronous mode. Signed-off-by: Andrey Konovalov --- lib/test_kasan.c | 4 1 file changed, 4 insertions(+) diff --git a/lib/te

[PATCH v11 4/5] arm64: mte: Enable async tag check fault

MTE provides a mode that asynchronously updates the TFSR_EL1 register when a tag check exception is detected. To take advantage of this mode the kernel has to verify the status of the register at: 1. Context switching 2. Return to user/EL0 (Not required in entry from EL0 since the kernel did

[PATCH v11 1/5] arm64: mte: Add asynchronous mode support

MTE provides an asynchronous mode for detecting tag exceptions. In particular instead of triggering a fault the arm64 core updates a register which is checked by the kernel after the asynchronous tag check fault has occurred. Add support for MTE asynchronous mode. The exception handling mechanism

Re: [PATCH v11 5/5] kasan: don't run tests in async mode

On 1/30/21 4:52 PM, Vincenzo Frascino wrote: > From: Andrey Konovalov > > Asynchronous KASAN mode doesn't guarantee that a tag fault will be > detected immediately and causes tests to fail. Forbid running them > in asynchronous mode. > > Signed-off-by: Andrey Konovalov Reviewed-by: Vincenzo

Fail to boot on bpim3 with next-20210128

Hello next-20210128 cannot be booted on my bpim3. It start booting then freeze. [0.00] Linux version 5.11.0-rc5-03084-g7426957d237f (compile@Red) (armv7a-unknown-linux-gnueabihf-gcc (Gentoo 9.3.0-r2 p4) 9.3.0, GNU ld (Gentoo 2.34 p6) 2.34.0) #390 SMP Sat Jan 30 14:59:48 CET 2021 [0.

[net-next 00/14] Add Marvell CN10K support

The current admin function (AF) driver and the netdev driver supports OcteonTx2 silicon variants. The same OcteonTx2's Resource Virtualization Unit (RVU) is carried forward to the next-gen silicon ie OcteonTx3, with some changes and feature enhancements. This patch set adds support for OcteonTx3

[net-next 05/14] octeontx2-pf: cn10k: Initialise NIX context

On CN10K platform NIX RQ and SQ context structure got changed. This patch uses new mbox message "NIX_CN10K_AQ_ENQ" for NIX context initialization on CN10K platform. This patch also updates the nix_rx_parse_s and nix_sqe_sg_s structures to add packet steering bit feilds. Signed-off-by: Geetha sowj

[net-next 06/14] octeontx2-pf: cn10k: Map LMTST region

On CN10K platform transmit/receive buffer alloc and free from/to hardware had changed to support burst operation. Whereas pervious silicon's only support single buffer free at a time. To Support the same firmware allocates a DRAM region for each PF/VF for storing LMTLINES. These LMTLINES are used f

[net-next 04/14] octeontx2-af: cn10k: Update NIX and NPA context in debugfs

On CN10K platform NPA and NIX context structure bit fields had changed to support new features like bandwidth steering etc. This patch dumps approprate context for CN10K platform. Signed-off-by: Geetha sowjanya Signed-off-by: Sunil Goutham --- .../ethernet/marvell/octeontx2/af/rvu_debugfs.c

<    1   2   3   4   5   6   >