public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Genes Lists <lists@sapience.com>
Cc: linux-kernel@vger.kernel.org, mchehab@kernel.org,
	hverkuil-cisco@xs4all.nl, laurent.pinchart@ideasonboard.com,
	wentong.wu@intel.com, linux-media@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: [PATCH 1/1] ACPI: scan: Ignore Dell XPS 9320 camera graph port nodes
Date: Tue, 28 May 2024 11:44:13 +0300	[thread overview]
Message-ID: <20240528084413.2624435-1-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <988e48090982c89ce0c906954832fdfb09a1ce34.camel@sapience.com>

Ignore camera related graph port nodes on Dell XPS 9320. They data in BIOS
is buggy, just like it is for Dell XPS 9315. The corresponding software
nodes are created by the ipu-bridge.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
Hi,

Could you test this and see whether it fixes the warning?

The camera might work with this change, too.

- Sakari

 drivers/acpi/mipi-disco-img.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/acpi/mipi-disco-img.c b/drivers/acpi/mipi-disco-img.c
index d05413a0672a..bf9a5cee32ac 100644
--- a/drivers/acpi/mipi-disco-img.c
+++ b/drivers/acpi/mipi-disco-img.c
@@ -732,6 +732,12 @@ static const struct dmi_system_id dmi_ignore_port_nodes[] = {
 			DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "XPS 9315"),
 		},
 	},
+	{
+		.matches = {
+			DMI_EXACT_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
+			DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "XPS 9320"),
+		},
+	},
 	{ }
 };
 
-- 
2.39.2


       reply	other threads:[~2024-05-28  8:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <988e48090982c89ce0c906954832fdfb09a1ce34.camel@sapience.com>
2024-05-28  8:44 ` Sakari Ailus [this message]
2024-05-28 17:09   ` [PATCH 1/1] ACPI: scan: Ignore Dell XPS 9320 camera graph port nodes Hans de Goede
2024-06-06 18:12     ` Hans de Goede
2024-06-07  7:55       ` Rafael J. Wysocki
2024-06-07  9:24         ` Sakari Ailus
2024-06-12 10:08       ` Hans de Goede
2024-06-12 10:25         ` Rafael J. Wysocki
2024-06-12 12:10         ` Sakari Ailus
2024-06-12 12:21           ` Rafael J. Wysocki
2024-06-12 12:26             ` Sakari Ailus
2024-06-12 12:32               ` Rafael J. Wysocki
2024-06-12 12:47                 ` Sakari Ailus
2024-06-12 13:06                   ` Rafael J. Wysocki
2024-06-12 14:30                     ` Hans de Goede
2024-06-12 14:39                       ` Laurent Pinchart
2024-06-12 18:24                         ` Sakari Ailus
2024-06-12 19:07                         ` Rafael J. Wysocki
2024-06-12 20:08                           ` Laurent Pinchart
2024-06-12 15:26                       ` Rafael J. Wysocki
2024-06-12 18:33                         ` Sakari Ailus
2024-06-12 18:41                           ` Rafael J. Wysocki
2024-06-12 19:06                             ` Sakari Ailus
2024-06-12 19:12                               ` Rafael J. Wysocki
2024-06-12 19:17                                 ` Sakari Ailus
2024-06-12 19:32                                   ` Rafael J. Wysocki
2024-06-12 20:00                                     ` Sakari Ailus
2024-06-12 20:17                       ` Sakari Ailus
2024-06-13  9:50                         ` Rafael J. Wysocki
2024-06-12 18:21                     ` Sakari Ailus
2024-06-12 18:29                       ` Rafael J. Wysocki
2024-06-12 18:40                         ` Sakari Ailus
2024-06-12 18:50                           ` Rafael J. Wysocki
2024-06-12 19:11                             ` Sakari Ailus
2024-06-12 19:26                               ` Rafael J. Wysocki
2024-06-12 20:00                             ` Laurent Pinchart
2024-06-12 20:31                               ` Rafael J. Wysocki
2024-06-12 20:41                                 ` Laurent Pinchart
2024-06-13 12:37                                   ` Rafael J. Wysocki
2024-06-12 20:01                           ` Laurent Pinchart
2024-05-30  0:35   ` Wu, Wentong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240528084413.2624435-1-sakari.ailus@linux.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lists@sapience.com \
    --cc=mchehab@kernel.org \
    --cc=wentong.wu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox