From patchwork Mon Aug 15 18:20:53 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Philip Cox X-Patchwork-Id: 1666557 Return-Path: X-Original-To: patchwork-incoming@bilbo.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: bilbo.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=canonical.com header.i=@canonical.com header.a=rsa-sha256 header.s=20210705 header.b=K/DKkl+e; dkim-atps=neutral Received: from legolas.ozlabs.org (legolas.ozlabs.org [IPv6:2404:9400:2:0:216:3eff:fee2:8c49]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by bilbo.ozlabs.org (Postfix) with ESMTPS id 4M62gH1Y1tz9s09 for ; Tue, 16 Aug 2022 04:22:03 +1000 (AEST) Received: by legolas.ozlabs.org (Postfix) id 4M62gG0c7kz1ygT; Tue, 16 Aug 2022 04:22:02 +1000 (AEST) Delivered-To: patchwork-incoming@legolas.ozlabs.org Authentication-Results: legolas.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=lists.ubuntu.com (client-ip=91.189.94.19; helo=huckleberry.canonical.com; envelope-from=kernel-team-bounces@lists.ubuntu.com; receiver=) Authentication-Results: legolas.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=canonical.com header.i=@canonical.com header.a=rsa-sha256 header.s=20210705 header.b=K/DKkl+e; dkim-atps=neutral Received: from huckleberry.canonical.com (huckleberry.canonical.com [91.189.94.19]) (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 4M62gF417Yz1yf9 for ; Tue, 16 Aug 2022 04:22:00 +1000 (AEST) Received: from localhost ([127.0.0.1] helo=huckleberry.canonical.com) by huckleberry.canonical.com with esmtp (Exim 4.86_2) (envelope-from ) id 1oNeim-0003r3-5g; Mon, 15 Aug 2022 18:21:52 +0000 Received: from smtp-relay-internal-1.internal ([10.131.114.114] helo=smtp-relay-internal-1.canonical.com) by huckleberry.canonical.com with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1oNeij-0003qp-W8 for kernel-team@lists.ubuntu.com; Mon, 15 Aug 2022 18:21:49 +0000 Received: from mail-il1-f199.google.com (mail-il1-f199.google.com [209.85.166.199]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id B8B2D3F11A for ; Mon, 15 Aug 2022 18:21:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1660587709; bh=JtgFfy1teLSSBgEjFdTOfJ5XVoiGMudJyiV0NyEBbtk=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=K/DKkl+eCVv2XicS1YXPlgNfAZzNQWmvjo0DTD2lQ2SQ6o8yIebYHfOqC9Qk+Ej2n RshHas3qTBPr8e4m2VkZot3j7ypoyPZRbhiMeTjpOGPrgzNie4zP05DAr2XxF+NYWK c1+tCennLPnsZY7gbL4y8++Cvvo0zX3ruEOl1AGMtWx7innI8jNJZlex5knY4zOiRD 0TvJ2rUgmdKOKB6bgYR0Sz3SGNxzcU4HyT2xnHvjwDcxEzZIKtI1PnfjxU0lkvQBIJ uXe22qBM+kOaREEHaLdtGAsByvkZf9AiqNK5MM7hxghYd1UBhnyaNw7tejkGIDVhZ3 tSE7RKGUtjV9w== Received: by mail-il1-f199.google.com with SMTP id c7-20020a056e020bc700b002e59be6ce85so2999338ilu.12 for ; Mon, 15 Aug 2022 11:21:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc; bh=JtgFfy1teLSSBgEjFdTOfJ5XVoiGMudJyiV0NyEBbtk=; b=kAa5+XQWd6/4q7RmxNhDdjtiteTzImRUOYTG520mPRV7W51gqtIwPVvIMzKHElXy6h vCPyIdGSMQ6L+O83VhRwGgYHR0Dk8WcgTs82Wl679xq0GGLTRpRwyYkfgiMmDuqny0VB TrZjNhEAKTHoFrjyHc/tFmytCtm2lEPFzU0LPUNbWQ0btfz7I53cc37ArtK/gxOni6gt PUVuGW1lT3YrAVMMXRmtNPsBHcBzKPkj1Hu+121hpQuSToJkjrWq5wSJr28AtkQNTqra ItCP5fCdxejXAsFDUIYwzodyvcAIlG9kV4eMDlgauwzcPNwc3Xk2/yLZt+Qnqw7aESLg ZN6A== X-Gm-Message-State: ACgBeo01JDrEM88Zfl3ZM5Xut0c22tArDFO3GBwKWzZRaQ5Z6AbdOOWt cu7iRnfj/O9WYpuGjpsdK3ipq17qdjZJKLAHCKn7qPneL4hq6CUMnb0g4gfrupfevDdB0GY91OT TFfcF3lbty7LdFgcGEV8mIW0insIshj7qBk2mmJySiw== X-Received: by 2002:a05:6602:2d4f:b0:67b:f7c9:a3e with SMTP id d15-20020a0566022d4f00b0067bf7c90a3emr6975487iow.77.1660587708486; Mon, 15 Aug 2022 11:21:48 -0700 (PDT) X-Google-Smtp-Source: AA6agR4iy3a4F191V9Fx3QWkTY9cDI/e1+TDiLg7sqxKSIjFORkK3pGabzUFAxEl5fQyHjCj481SHg== X-Received: by 2002:a05:6602:2d4f:b0:67b:f7c9:a3e with SMTP id d15-20020a0566022d4f00b0067bf7c90a3emr6975482iow.77.1660587708268; Mon, 15 Aug 2022 11:21:48 -0700 (PDT) Received: from localhost.localdomain ([104.247.231.135]) by smtp.gmail.com with ESMTPSA id k2-20020a92c9c2000000b002cc20b48163sm4094394ilq.3.2022.08.15.11.21.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 15 Aug 2022 11:21:47 -0700 (PDT) From: Philip Cox To: kernel-team@lists.ubuntu.com Subject: [SRU][Jammy:linux-intel-iotg][PATCH 0/2] i915: Enable HuC authentication for EHL, ICL, and ADL-S Date: Mon, 15 Aug 2022 14:20:53 -0400 Message-Id: <20220815182055.1142354-1-philip.cox@canonical.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 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/1981971 [Impact] * In the i915 Intel gfx driver, we need to explicitly enable HuC authentication. * This fixes an issue with the Gstreamer media pipeline. * This only applies to the ICL, ADL-S, and EHL platforms. * This patch is only for the linux-intel-iotg kernel. We have pulled in patches from upstream, so the state of this driver is in between the upstream 5.15 driver, and the upstream tip-of-tree driver. [Test Plan] * Intel has tested this patch. * I have tested the patch as well. * To test, the system is booted, and issuing the command: sudo cat /sys/kernel/debug/dri/0/gt/uc/huc_info will either return the huc info, or it will display "HuC disabled" [Where problems could occur] * If the installed firmware has been trimmed so that only blobs that were in use were retained, when the kernel tried to load the HuC blob, it would fail. This scenario should not happen unless someone is mucking about with the installed firmware. If that is the case, other things will likely start failing as well.