From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Genes Lists <lists@sapience.com>,
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,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [PATCH 1/1] ACPI: scan: Ignore Dell XPS 9320 camera graph port nodes
Date: Thu, 13 Jun 2024 11:50:48 +0200 [thread overview]
Message-ID: <CAJZ5v0jN3CXM9vWQniu1Q2t1NvG9n5KoG0VGHnMgdPU2iHpBvw@mail.gmail.com> (raw)
In-Reply-To: <ZmoCUZxlSHy_PclO@kekkonen.localdomain>
Hi Sakari,
On Wed, Jun 12, 2024 at 10:17 PM Sakari Ailus
<sakari.ailus@linux.intel.com> wrote:
>
> Hi Hans,
>
> On Wed, Jun 12, 2024 at 04:30:30PM +0200, Hans de Goede wrote:
> > Sakari I know you have been pushing for MIPI camera descriptions under
> > ACPI to move to a standardized format and I can see how that is a good
> > thing, but atm it seems to mainly cause things to break and before
> > the ACPI MIPI DISCO support landed in 6.8 we did not have these issues,
> > since the information used by the ipu-bridge code does seem to be correct.
>
> Support for capturing from cameras on IPU6 systems (IPU6 ISYS driver and
> IPU bridge changes) was upstreamed for 6.10, with some drivers such as IVSC
> (four of them) and IVSC related IPU bridge changes merged for 6.8 already.
>
> We can't guarantee the continued functioning of downstream drivers in cases
> where new upstream drivers for the same devices get merged to the kernel,
> often with different APIs. You know that as well as I do.
>
> In other words, there was no regression with respect to the upstream
> kernel.
Users' opinions on this may differ I suppose.
If a user sees a new kernel warning on boot, they will easily count it
as a regression, and with panic_on_warn this becomes a full-fledged
kernel crash.
This is bad, even though it may be coming from a new driver strictly speaking.
next prev parent reply other threads:[~2024-06-13 9:51 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 16:34 6.10-rc1 : crash in mei_csi_probe Genes Lists
2024-05-27 19:57 ` Sakari Ailus
2024-05-27 20:58 ` Genes Lists
2024-05-28 8:44 ` [PATCH 1/1] ACPI: scan: Ignore Dell XPS 9320 camera graph port nodes Sakari Ailus
2024-05-28 17:09 ` 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 [this message]
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
2024-06-06 15:39 ` 6.10-rc1 : crash in mei_csi_probe Genes Lists
2024-06-06 15:50 ` Sakari Ailus
2024-06-06 16:17 ` Genes Lists
2024-06-06 17:07 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-07 7:57 ` Rafael J. Wysocki
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=CAJZ5v0jN3CXM9vWQniu1Q2t1NvG9n5KoG0VGHnMgdPU2iHpBvw@mail.gmail.com \
--to=rafael@kernel.org \
--cc=hdegoede@redhat.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=regressions@lists.linux.dev \
--cc=sakari.ailus@linux.intel.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).