From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 93DCE489860 for ; Mon, 5 Oct 2026 13:23:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791206622; cv=none; b=tYqp7z2zse3h2Mq9c/Y2tK4a1no6XZA+kU25tQv9ExKkNf0ossX/+b6dJvekMNCcf8T34xpAWE91yKl66QpPvZpLz4mKDJA5RxHJkD16elJDs07NBpQyED/SNdebpw8cSnGDNFwVEZLuWSSy72E05i/kB7Q8HP9LI95hv9AP90w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791206622; c=relaxed/simple; bh=JGwAdHTtbsQdeT0z/GNJ23TE2Xpp5jku8tDptxYdRzM=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=dkrTmVbNBT3ipaAkzWgY6dNO5xH78hb/xiTjcCP4yw/yhCpiGOzPVd+HjQRVdEeMZlN3KfeG+PgQsbHBNLr8UROkD1Wfpw8ZxEiOLKEMciGI1Nb/gq6PmQQzRR5mSIuVF3oB5SV0kc7V1IPkahh0xnqOPOFS3qLmtZ9YTKA745M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=XenInBBx; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="XenInBBx" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B9C0B1F00893; Mon, 5 Oct 2026 13:23:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791206586; bh=0BYJY+NUhEgcsadVVJs/4kxZrY0MfH4MzDtly8EKg0Y=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=XenInBBx69+gWV8YSYDP9sraunC8cyoE8WxrN7A7eIZReQzd2ARRcyTNyGVFL+MYX ARd0djSIEDI6E6GoJ/U6ZPcoJPf09xykdhfY4QyXwWal5JCmNLJk72IwQoMWeJQyNf DJC3PXwxFn33O2LBPZQvnx4wPtcDyX2qu4Ns0gybbkDJwLKAUQX62MZ+j4DF0Fx74X 0c25x1a/4McAzOLbcUYIGSRrXNe3EBZJ7+Hoh8YJBt8RFEJjAavf9VrQyCbpQj0NGB KFh17mYA7KMEpGc7b4M1YH2h/CuwjAoNkeN58pSPSjVCvKEBYU5e4TIHjyCWmLbWXT Wxne/oUcB6yaw== From: Sasha Levin To: stable@vger.kernel.org Cc: =?UTF-8?q?Francisco=20Beltr=C3=A1n=20Millal=C3=A9n?= , =?UTF-8?q?Christian=20K=C3=B6nig?= , Alex Deucher , Sasha Levin Subject: [PATCH 7.2.y 2/2] drm/amdgpu: reset VI ASIC on MacBookPro14,3 Date: Mon, 5 Oct 2026 09:23:02 -0400 Message-ID: <20261005132251.2627312-2-sashal@kernel.org> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20261005132251.2627312-1-sashal@kernel.org> References: <2026100525-showcase-spirited-0675@gregkh> <20261005132251.2627312-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Francisco Beltrán Millalén [ Upstream commit a22e5e4f2ebbdbb962cc3233094d189c4dfaa051 ] On a MacBookPro14,3 with a Radeon Pro 555 (Polaris11), the framebuffer is at MC address 0 when amdgpu loads after a cold boot, as the firmware leaves it (MC_VM_FB_LOCATION = 0x007f0000), while the VBIOS ASIC_Init table places it at 0xF4_0000_0000 (0xf47ff400). amdgpu reads the location once, at init, so after a re-POST (S3 resume or GPU reset) the framebuffer has moved and the driver keeps programming the old one: the SMU is handed a table that was never written and the GPU does not come back, which leaves the internal panel black. Resetting the ASIC on load makes ASIC_Init run before the driver reads the location, so the driver uses the VBIOS placement from the start and every later re-POST puts the framebuffer back where it already is. Add the Radeon Pro 555 used in this machine to the existing VI reset quirk table. Tested on a MacBookPro14,3 on 6.18.49 with the quirk table backported (the kernel also carries unrelated local PCI and ACPI patches for this machine). The framebuffer is at 0x000000F400000000 after both cold and warm boot, and the GPU survived 9 S3 cycles (lid close and rtcwake, one of them with the lid closed for about 7.5 minutes and a USB-C disk attached), each followed by a few minutes of 3D load; no ring timeouts or VM faults were reported. The reset adds about 0.23 s to amdgpu init. Suggested-by: Christian König Suggested-by: Alex Deucher Link: https://lore.kernel.org/all/20260924132952.25054-1-fbeltranmillalen@gmail.com/ Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Francisco Beltrán Millalén Signed-off-by: Alex Deucher (cherry picked from commit b6b1d97218518003107d4446fac278fa3e0a19a0) Cc: stable@vger.kernel.org Signed-off-by: Sasha Levin --- drivers/gpu/drm/amd/amdgpu/vi.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/amd/amdgpu/vi.c b/drivers/gpu/drm/amd/amdgpu/vi.c index 320c43143e5d3..fcc93c76ad74e 100644 --- a/drivers/gpu/drm/amd/amdgpu/vi.c +++ b/drivers/gpu/drm/amd/amdgpu/vi.c @@ -1417,6 +1417,7 @@ struct vi_reset_quirk { static const struct vi_reset_quirk vi_reset_quirks[] = { { 0x67ef, PCI_VENDOR_ID_APPLE, 0x0190, 0xe3 }, /* Radeon Pro 555X */ { 0x67ef, PCI_VENDOR_ID_APPLE, 0x018f, 0xc2 }, /* Radeon Pro 560X */ + { 0x67ef, PCI_VENDOR_ID_APPLE, 0x017a, 0xc7 }, /* Radeon Pro 555 */ }; static bool vi_need_reset_on_init(struct amdgpu_device *adev) -- 2.53.0