From patchwork Tue Jun 25 09:35:13 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: You-Sheng Yang X-Patchwork-Id: 1952016 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@legolas.ozlabs.org Authentication-Results: legolas.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=lists.ubuntu.com (client-ip=185.125.189.65; helo=lists.ubuntu.com; envelope-from=kernel-team-bounces@lists.ubuntu.com; receiver=patchwork.ozlabs.org) Received: from lists.ubuntu.com (lists.ubuntu.com [185.125.189.65]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by legolas.ozlabs.org (Postfix) with ESMTPS id 4W7fpG28Slz20X1 for ; Tue, 25 Jun 2024 19:35:50 +1000 (AEST) Received: from localhost ([127.0.0.1] helo=lists.ubuntu.com) by lists.ubuntu.com with esmtp (Exim 4.86_2) (envelope-from ) id 1sM2aW-0001ur-F3; Tue, 25 Jun 2024 09:35:44 +0000 Received: from mail-pl1-f176.google.com ([209.85.214.176]) by lists.ubuntu.com with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1sM2aU-0001uS-DV for kernel-team@lists.ubuntu.com; Tue, 25 Jun 2024 09:35:42 +0000 Received: by mail-pl1-f176.google.com with SMTP id d9443c01a7336-1f9b52ef481so42765745ad.1 for ; Tue, 25 Jun 2024 02:35:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719308140; x=1719912940; h=content-transfer-encoding:mime-version:message-id:date:subject:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ZMe4FCCVJC20sqEK0ppiLLF+CmkYxttSL+X/4wMyheE=; b=Gc1c+u+R/qyRt4UxqhYGvBTbvW6nxBWfU69OUNixzLukD73a7BeAkK/Aee2aHlJfZD 17qDAnQdM+u+6yQW/zvi2A1tGRJ3VSvMsZvHeYQjGsIui1MdBc+4hf3wiiPn5jf+IGk0 kMVBBi5WDth2+/TFqNQWrOmH841Sn2v7LDRLRZSUO96UzcZdDQ+eIBayeaeBp7GvoZs+ z1FtKfoAcaQE75DgQBm7zb+qoNnMozg9sr5lHsNH+swVEbQ1n3Mc/G5AV8++XBH5R40b ZCmTOqt4QJSqaz7HVAZOD7Y5bziP/CT9xe8MNJRZGfqRVgZjkVn5dJ9S74gvDKrjpkfR +3Cw== X-Gm-Message-State: AOJu0YxWNwuJoTW0HHaD3OvrTTJW4rklpqjk2abSZdcA46zCtzUWjjT1 /+ju5IH9Lo3G8BjHPYf6E1nmMs7tUf+bIJdEI+jD16sksnShigTLIMYZ4Qlv X-Google-Smtp-Source: AGHT+IEll8jFqlBRDQWNev3gxM8ERKWema8KeRoT2dRd58PYWBxm6vJHq0hvHwofIjWUev58Pozdjw== X-Received: by 2002:a17:90a:bd88:b0:2c4:a1c9:b76d with SMTP id 98e67ed59e1d1-2c861409efamr4930289a91.37.1719308140273; Tue, 25 Jun 2024 02:35:40 -0700 (PDT) Received: from localhost.localdomain (125-229-129-140.hinet-ip.hinet.net. [125.229.129.140]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2c819db9803sm8176683a91.45.2024.06.25.02.35.39 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 25 Jun 2024 02:35:39 -0700 (PDT) From: You-Sheng Yang To: kernel-team@lists.ubuntu.com Subject: [PATCH 0/7][Unstable] Fix vsc ace set host command timeout Date: Tue, 25 Jun 2024 17:35:13 +0800 Message-ID: <20240625093520.3804382-1-vicamo.yang@canonical.com> X-Mailer: git-send-email 2.43.0 MIME-Version: 1.0 Received-SPF: pass client-ip=209.85.214.176; envelope-from=vicamo@gmail.com; helo=mail-pl1-f176.google.com X-BeenThere: kernel-team@lists.ubuntu.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Kernel team discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kernel-team-bounces@lists.ubuntu.com Sender: "kernel-team" BugLink: https://bugs.launchpad.net/bugs/2067364 [Impact] With IVSC switched to in-tree driver since 6.8 kernels in bug 2061747, it's still suffering from various problems that blocks camera driver stack being loaded correctly. The ivsc-ace driver may fail to communicate with the underlying firmware with error messages: ivsc_ace intel_vsc-5db76cf6-0a68-4ed6-9b78-0361635e2447: switch camera to host failed: -110 This happens after warm reboots. In addition, ivs may block suspend resume, too. [Fix] These symptoms are to be addressed by upstream reviewing patchsets: * https://lore.kernel.org/all/20240624014223.4171341-1-wentong.wu@intel.com/ * https://lore.kernel.org/all/20240607132547.2820515-1-wentong.wu@intel.com/ * commit 9b5e045029d8 ("mei: vsc: Don't stop/restart mei device during system suspend/resume") from v6.10-rc4 [Test Case] 1. test camera after rebooting into a proposed kernel, 2. run suspend/resume stress test plan. 3. verify camera still working [Where problems could occur] These fixes are quite limited to ipu6/ivsc platforms, and affected no power-consumption or other notisible problem. [Other Info] While some of the fixes are still under upstream review, meaning they're not yet available in any kernel release, linux-unstable/oracular/noble and oem-6.8/6.1x will be nominated for fix. Wentong Wu (7): UBUNTU: SAUCE: media: ivsc: csi: don't count privacy on as error UBUNTU: SAUCE: media: ivsc: csi: add separate lock for v4l2 control handler UBUNTU: SAUCE: media: ivsc: csi: remove privacy status in struct mei_csi UBUNTU: SAUCE: mei: vsc: Enhance IVSC chipset stability during warm reboot UBUNTU: SAUCE: mei: vsc: Enhance SPI transfer of IVSC rom UBUNTU: SAUCE: mei: vsc: Utilize the appropriate byte order swap function UBUNTU: SAUCE: mei: vsc: Prevent timeout error with added delay post-firmware download drivers/media/pci/intel/ivsc/mei_csi.c | 24 +++++++++++++++--------- drivers/misc/mei/platform-vsc.c | 4 ++-- drivers/misc/mei/vsc-tp.c | 18 ++++++++++++++++-- 3 files changed, 33 insertions(+), 13 deletions(-) Acked-by: Paolo Pisati