[PATCH v3 4/5] dt-bindings: input/touchscreen: imagis: add compatible for IST3032C

From: Karel Balej Document possible usage of the Imagis driver with the IST3032C touchscreen. Signed-off-by: Karel Balej --- .../devicetree/bindings/input/touchscreen/imagis,ist3038c.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/input/touchscreen

[PATCH v3 1/5] input/touchscreen: imagis: Correct the maximum touch area value

From: Markuss Broks As specified in downstream IST3038B driver and proved by testing, the correct maximum reported value of touch area is 16. Signed-off-by: Markuss Broks Signed-off-by: Karel Balej --- drivers/input/touchscreen/imagis.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) d

[PATCH v3 5/5] input/touchscreen: imagis: add support for IST3032C

From: Karel Balej IST3032C is a touchscreen chip used for instance in the samsung,coreprimevelte smartphone, with which this was tested. Add the chip specific information to the driver. Signed-off-by: Karel Balej --- drivers/input/touchscreen/imagis.c | 10 ++ 1 file changed, 10 insert

[PATCH v3 3/5] input/touchscreen: imagis: Add support for Imagis IST3038B

From: Markuss Broks Imagis IST3038B is another variant of Imagis IST3038 IC, which has a different register interface from IST3038C (possibly firmware defined). This should also work for IST3044B (though untested), however other variants using this interface/protocol(IST3026, IST3032, IST3026B, I

[PATCH v3 2/5] dt-bindings: input/touchscreen: Add compatible for IST3038B

From: Markuss Broks Imagis IST3038B is a variant (firmware?) of Imagis IST3038 IC, add the compatible for it to the IST3038C bindings. Signed-off-by: Markuss Broks Signed-off-by: Karel Balej --- .../devicetree/bindings/input/touchscreen/imagis,ist3038c.yaml | 1 + 1 file changed, 1 insertio

[PATCH v3 0/5] input/touchscreen: imagis: add support for IST3032C

From: Karel Balej This patch series generalizes the Imagis touchscreen driver to support other Imagis chips, namely IST3038B, which use a slightly different protocol. It also adds necessary information to the driver so that the IST3032C touchscreen can be used with it. The motivation for this is

[PATCH RESEND] mac802154: Fix uninit-value access in ieee802154_hdr_push_sechdr

The syzkaller reported an issue: BUG: KMSAN: uninit-value in ieee802154_hdr_push_sechdr net/ieee802154/header_ops.c:54 [inline] BUG: KMSAN: uninit-value in ieee802154_hdr_push+0x971/0xb90 net/ieee802154/header_ops.c:108 ieee802154_hdr_push_sechdr net/ieee802154/header_ops.c:54 [inline] ieee802

Re: [PATCH net-next v5 2/3] virtio/vsock: send credit update during setting SO_RCVLOWAT

On Fri, Dec 01, 2023 at 01:40:41PM +0300, Arseniy Krasnov wrote: > > > On 01.12.2023 12:48, Stefano Garzarella wrote: > > On Fri, Dec 01, 2023 at 11:35:56AM +0300, Arseniy Krasnov wrote: > >> > >> > >> On 01.12.2023 11:27, Stefano Garzarella wrote: > >>> On Thu, Nov 30, 2023 at 12:40:43PM -0500,

Re: [PATCH net-next v5 2/3] virtio/vsock: send credit update during setting SO_RCVLOWAT

On 02.12.2023 23:22, Michael S. Tsirkin wrote: > On Fri, Dec 01, 2023 at 01:40:41PM +0300, Arseniy Krasnov wrote: >> >> >> On 01.12.2023 12:48, Stefano Garzarella wrote: >>> On Fri, Dec 01, 2023 at 11:35:56AM +0300, Arseniy Krasnov wrote: On 01.12.2023 11:27, Stefano Garzarella wr

Re: [PATCH vhost 0/7] vdpa/mlx5: Add support for resumable vqs

On Fri, Dec 01, 2023 at 12:48:50PM +0200, Dragos Tatulea wrote: > Add support for resumable vqs in the driver. This is a firmware feature > that can be used for the following benefits: > - Full device .suspend/.resume. > - .set_map doesn't need to destroy and create new vqs anymore just to > upda

Re: [PATCH v2 1/2] arm64: dts: qcom: msm8953: Set initial address for memory

On Sat, Nov 25, 2023 at 01:19:27PM +0100, Luca Weiss wrote: > The dtbs_check really doesn't like having memory without reg set. > > The base address depends on the amount of RAM you have: > > <= 2.00 GiB RAM: 0x8000 >= 3.00 GiB RAM: 0x4000 >= 3.75 GiB RAM: 0x1000 > (more do

Re: [PATCH v2] arm64: dts: qcom: qcm6490-fairphone-fp5: Enable UFS

On Mon, Oct 02, 2023 at 02:30:41PM +0200, Luca Weiss wrote: > Enable the UFS phy and controller so that we can access the internal > storage of the phone. > > At the same time we need to bump the minimum voltage used for UFS VCC, > otherwise it doesn't initialize properly. The 2.952V is taken from

Re: [PATCH v2] arm64: dts: qcom: msm8939-longcheer-l9100: Add proximity-near-level

On Sun, 26 Nov 2023 22:46:20 +0100, André Apitzsch wrote: > Consider an object near to the sensor when their distance is about 4 cm > or below. > > Applied, thanks! [1/1] arm64: dts: qcom: msm8939-longcheer-l9100: Add proximity-near-level commit: fbe0870c48ac84f117860096048055a4f078a976

Re: [PATCH 0/4] Add Fairphone 5 thermals (PMK7325, PM7250B, PM7325)

On Fri, 13 Oct 2023 10:09:52 +0200, Luca Weiss wrote: > Configure the necessary components to register some thermal zones in > Linux for the different thermistors found on the Fairphone 5. > > The names for the thermal zones and ADCs were taken from the downstream > kernel but double checked aga

Re: [PATCH] arm64: dts: qcom: sdm632-fairphone-fp3: Enable LPASS

On Sun, 15 Oct 2023 22:06:56 +0200, Luca Weiss wrote: > Enable the LPASS/ADSP found on the phone. > > Applied, thanks! [1/1] arm64: dts: qcom: sdm632-fairphone-fp3: Enable LPASS commit: 2dee68e77cb5322d7cfe44f3c84ff8ae2eaf4aee Best regards, -- Bjorn Andersson

Re: (subset) [PATCH 0/3] Add watchdog nodes to msm8226 & msm8974

On Wed, 11 Oct 2023 18:33:12 +0200, Luca Weiss wrote: > Document the compatible for the watchdog found on both SoCs, and add > them to the SoC dtsi file. And especially for the case where the > bootloader has already enabled the watchdog we need to start petting it > on time, otherwise the system

Re: (subset) [PATCH v2 0/2] Small dtsi fixes for msm8953 SoC

On Sat, 25 Nov 2023 13:19:26 +0100, Luca Weiss wrote: > Fix some small things in the qcom/msm8953.dtsi file to make dtbs_check > happier than before. > > Applied, thanks! [2/2] arm64: dts: qcom: msm8953: Use non-deprecated qcom,domain in LPASS commit: 2e0dcbf164fb02d2558bd08b9609a30ef59

Re: [PATCH v2] arm64: dts: qcom: sdm632-fairphone-fp3: Enable WiFi/Bluetooth

On Mon, 27 Nov 2023 22:55:38 +0100, Luca Weiss wrote: > Configure and enable the WCNSS which provides WiFi and Bluetooth on this > device using the WCN3680B chip. > > Applied, thanks! [1/1] arm64: dts: qcom: sdm632-fairphone-fp3: Enable WiFi/Bluetooth commit: 5b006a82a2bbc0ce18bc6b084fc

Re: (subset) [PATCH v3 1/2] arm64: dts: qcom: sm8250-xiaomi-elish: Fix typos

On Sun, 26 Nov 2023 10:28:48 +0800, Jianhua Lu wrote: > There are two typos in this dtsi, so fix it. > classis -> chassis. > 8070 -> 8060 > > Applied, thanks! [1/2] arm64: dts: qcom: sm8250-xiaomi-elish: Fix typos commit: 608168b4d6079f2c43944bdfd64fd6c405d9a767 [2/2] arm64:

Re: [PATCH v3 0/3] Add support for HTC One Mini 2 smartphone

On Sat, 25 Nov 2023 13:05:32 +0100, Luca Weiss wrote: > Add support for this smartphone from HTC which is based on the MSM8926 > SoC and codenamed "memul". > > Depends on, runtime-only, bootloader enables watchdog so we need to pet > it to stay alive: > https://lore.kernel.org/linux-arm-msm/2023

Re: (subset) [PATCH 1/2] dt-bindings: arm: qcom: Add Huawei Honor 5X / GR5 (2016)

On Sat, 21 Oct 2023 16:30:24 +0200, Lukas Walter wrote: > Add a compatible for Huawei Honor 5X / GR5 (2016). > > Applied, thanks! [1/2] dt-bindings: arm: qcom: Add Huawei Honor 5X / GR5 (2016) commit: 01a3c3739183003640f8468ecf75d7eeb15f808a [2/2] arm64: dts: qcom: msm8939-huawei-kiwi: