Hi Sakari, On Wed, Jun 12, 2024 at 10:17 PM Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx> 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.
