Support mipi camera on Intel Meteor Lake platform

It appears linux/mantic is going to receive updates of v6.5 kernel.

linux-firmware SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-September/142977.html (jammy)
* https://lists.ubuntu.com/archives/kernel-team/2023-September/142978.html (mantic)

linux-firmware SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-September/143027.html (mantic, V2, rebase only)

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/20220329.git681281e4-0ubuntu3.19 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

This bug was fixed in the package linux-firmware - 20230919.git3672ccab-0ubuntu2

---------------
linux-firmware (20230919.git3672ccab-0ubuntu2) mantic; urgency=medium

  * Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
    - SAUCE: Update Intel IPU6 firmware

 -- Juerg Haefliger <email address hidden> Fri, 22 Sep 2023 15:21:03 +0200

Affects linux-oem-6.5/jammy, linux/mantic for IOMMU passthrough for Intel Meteor Lake B stepping.

This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.19

---------------
linux-firmware (20220329.git681281e4-0ubuntu3.19) jammy; urgency=medium

  * Missing firmware for Intel VPU on Intel Meteor Lake platforms (LP: #2031882)
    - SAUCE: Add firmware for Intel VPU on Meteor Lake platforms
  * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672)
    - rtl_bt: Add firmware v2 file for RTL8852C
    - rtw89: 8852c: update fw to v0.27.56.8
    - rtw89: 8852c: update fw to v0.27.56.9
    - rtw89: 8852c: update fw to v0.27.56.10
    - rtw89: 8852c: update fw to v0.27.56.13
  * S3 stress issue for amdgpu Navi 31/Navi33 (LP: #2024427)
    - amdgpu: update GC 11.0.0 firmware for amd.5.5 release
    - amdgpu: update GC 11.0.2 firmware for amd.5.5 release
  * Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
    - SAUCE: Update Intel IPU6 firmware

 -- Juerg Haefliger <email address hidden> Fri, 22 Sep 2023 15:10:51 +0200

The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

SRU draft for oem-6.5: http://10.131.201.69/kernel/jammy-linux-oem/pulls/77

SRU: http://10.131.201.69/kernel/jammy-linux-oem/pulls/77 (linux-oem-6.5)

SRU: https://lists.ubuntu.com/archives/kernel-team/2023-October/146403.html (unstable, mantic)

SRU v2: https://lists.ubuntu.com/archives/kernel-team/2023-October/146475.html (mantic)

Attach debdiff for noble. Need sponsoring.

Attach debdiff for ivsc-driver/noble. Need sponsoring.

Re-do debdiff against latest version 0~git202302081010.7fdfb5eb-0ubuntu0.23.10.2 instead.

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done-jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-linux-oem-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux/6.5.0-12.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic-linux' to 'verification-failed-mantic-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug was fixed in the package ivsc-driver - 0~git202212210258.94ecb88b-0ubuntu0.24.04.1

---------------
ivsc-driver (0~git202212210258.94ecb88b-0ubuntu0.24.04.1) noble; urgency=low

  [ You-Sheng Yang ]
  * Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
    - ljca: try to find acpi device from hub device
    - mei-vsc: port mei api change in v6.2
    - mfd: ljca: Fix try_match_acpi_hid return value checking
    - misc: spi-vsc: Fix cvfd_ids array with terminator

 -- You-Sheng Yang <email address hidden> Wed, 23 Aug 2023 00:11:46 +0800

This bug was fixed in the package ipu6-drivers - 0~git202310180730.3f813580-0ubuntu0.24.04.1

---------------
ipu6-drivers (0~git202310180730.3f813580-0ubuntu0.24.04.1) noble; urgency=low

  [ Hao Yao ]
  * New upstream 20230802_1500_mtl_plat release.
  * New upstream 20230911_0620_mtl_plat_pv release.

  [ Hans de Goede ]
  * Fix compilation with kernels >= 6.5.0 (LP: #2026402)
    - ipu-psys: Fix compilation with kernels >= 6.5.0
    - ipu6: Fix compilation with kernels >= 6.6.0
    - ipu6: Fix sensor driver compilation with kernels >= 6.6.0

  [ You-Sheng Yang ]
  * Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
    - debian: refresh patches
  * dkms: add CONFIG_VIDEO_V4L2_I2C to BUILD_EXCLUSIVE_CONFIG (LP: #2012407)
  * debian: add modaliases (LP: #2021740)
  * UBUNTU: SAUCE: i2c: compile omitted sensor drivers

 -- You-Sheng Yang <email address hidden> Fri, 01 Sep 2023 17:51:53 +0800

Add debdiff for ipu6-drivers/mantic since it's landed in Noble already. This is identical to that in ipu6-drivers/noble except for the version string. It's a version bump, as we need this for linux-oem-6.5 builds that tracks ipu6-drivers/mantic.

Add debdiff for ivsc-driver/mantic since it's landed in Noble already. This is identical to that in ivsc-driver/noble except for the version string. It's a version bump, as we need this for linux-oem-6.5 builds that tracks ivsc-driver/mantic.

Need sponsors for Mantic SRU.

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1007.7

---------------
linux-oem-6.5 (6.5.0-1007.7) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1007.7 -proposed tracker (LP: #2041654)

  * Support speaker mute hotkey for Cirrus CS35L41 HDA codec (LP: #2039151)
    - ALSA: hda: cs35l41: Support systems with missing _DSD properties
    - ALSA: hda: cs35l41: Fix the loop check in cs35l41_add_dsd_properties
    - ALSA: hda: cs35l41: Add notification support into component binding
    - ALSA: hda/realtek: Support ACPI Notification framework via component binding
    - ALSA: hda: cs35l41: Support mute notifications for CS35L41 HDA
    - ALSA: hda: cs35l41: Add read-only ALSA control for forced mute

  * Unable to power off the system with MTL CPU (LP: #2039405)
    - Revert "x86/smp: Put CPUs into INIT on shutdown if possible"

  * Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
    - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on Meteor
      Lake
    - SAUCE: platform/x86: int3472: Add handshake GPIO function

  * Miscellaneous upstream changes
    - Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in
      modversion"
    - Revert "UBUNTU: [Packaging] ZSTD compress modules"

  [ Ubuntu: 6.5.0-10.10 ]

  * mantic/linux: 6.5.0-10.10 -proposed tracker (LP: #2039204)
  * CVE-2023-4921
    - net: sched: sch_qfq: Fix UAF in qfq_dequeue()
  * CVE-2023-42756
    - netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP
  * CVE-2023-4881
    - netfilter: nftables: exthdr: fix 4-byte stack OOB write
  * CVE-2023-5197
    - netfilter: nf_tables: disallow rule removal from chain binding

 -- Timo Aaltonen <email address hidden> Fri, 27 Oct 2023 15:50:55 +0300

Hi,

this review is about the ivsc-driver portion of this SRU, which I will paste below and add inline comments to:

> ========== ivsc-driver ==========
>
> [Impact]
>
> Missing Intel MIPI firmware for Meteor Lake platform.

The patches added to the ivsc-driver package do not seem to be about a missing firmware, like the impact section above claims:

+ - ljca: try to find acpi device from hub device
+ - mei-vsc: port mei api change in v6.2
+ - mfd: ljca: Fix try_match_acpi_hid return value checking
+ - misc: spi-vsc: Fix cvfd_ids array with terminator

Please clarify.

>
> [Fix]
>
> 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver.
>
> [Test Case]
>
> With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well.
>
> To actually verify the camera framework:
> ```
> $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
> $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
> $ sudo apt install linux-oem-22.04d-exp
> $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
> $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
> $ sudo apt install linux-modules-usbio-oem-22.04d-exp
> $ sudo apt install gstreamer1.0-icamera v4l2-relayd
> ```

This is problematic: why do we have to add ppas, and install other kernel modules? Can you come up with a test case that does NOT need packages from an out-of-archive source? And specifically, using the mantic kernel (6.5). Is there another way to test it? Why do we need so many out-of-archive components?

If pure mantic with the updated ivsc-driver and ipu6-drivers packages from this bug is not enough to support the MIPI camera, then what is the benefit this SRU is bringing to mantic users?

> And then browse https://webcamtests.com/ for testing.
>
> [Where problems could occur]
>
> While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL.
>
> [Other Info]
>
> While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
> linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead.

Not sure what you mean with the above. I see the same fixes proposed for mantic landed in noble, so that's good. Maybe the comment above was written before the noble packages were updated?

Also, the "linux" task of this bug, for mantic, is "fix committed". It's this one I believe:

https://launchpad.net/ubuntu/+source/linux/6.5.0-14.14

So can the tests be made using that kernel? It is claiming to have added support for MIPI cameras, to some extent:

  * Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
    - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on Meteor
      Lake
    - SAUCE: platform/x86: int3472: Add handshake GPIO function

> Is there another way to test it? Why do we need so many out-of-archive components?

That PPA contains prebuilt modules to ease the verification process. The Intel MIPI IPU6 relies on both kernel drivers and a user space hal framework, and the versions must match because Intel fails to keep compatibility across releases, so you don't want to deal with these mess, the PPAs have the right version for verification.

> So can the tests be made using that kernel?

Yes and no. MIPI on MTL is only available on developing platforms, and developing platforms may take additional fixes to construct a usable system before you may take it for verification. The 6.5.0-14.14 is already sufficient for IPU6 alone though.

Hi,

this review is about the ipu6-driver portion of this SRU, which I will paste below and add inline comments to:

> ========== ipu6-driver ==========
>
> [Impact]
>
> Missing Intel MIPI firmware for Meteor Lake platform.

The changes in ipu6-drivers are not adding a new firmware as far as I can tell, could you please clarify?

Overall, after this update, what will be the status of MIPI cameras for mantic users on intel meteor lake?

>
> [Fix]
>
> Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules.

Since this includes a new upstream code drop, could you summarize the highlights? Have you inspected them for backwards incompatible changes?

>
> [Test Case]
>
> This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL.
>
> To actually verify the camera framework:
> ```
> $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
> $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
> $ sudo apt install linux-oem-22.04d-exp
> $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
> $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
> $ sudo apt install linux-modules-usbio-oem-22.04d-exp
> $ sudo apt install gstreamer1.0-icamera v4l2-relayd
> ```
> And then browse https://webcamtests.com/ for testing.

Like my comment #24 above, is there a way to test this that does not involve out-of-archive packages? If not, what is the benefit of this update to mantic users?

>
> [Where problems could occur]
>
> This is a new platform. We've been verifying its functions and features, and
> are still polishing it.

That doesn't sound very reassuring :) Having said that, you think it's ready for a stable release update for mantic users? Mantic users will benefit from this update?

>
> [Other Info]
>
> While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
> linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead.

> The patches added to the ivsc-driver package do not seem to be about a missing firmware, like the impact section above claims:
> Please clarify.

Updated SRU justification in the description.

> Not sure what you mean with the above. I see the same fixes proposed for mantic landed in noble, so that's good. Maybe the comment above was written before the noble packages were updated?

This SRU justification was prepared before Noble is named/released, and yet since Noble is out, we copy to both series.

> The changes in ipu6-drivers are not adding a new firmware as far as I can tell, could you please clarify?

linux-firmware changes have been released at version 20230919.git3672ccab-0ubuntu2 as shown in comment #5.

> Overall, after this update, what will be the status of MIPI cameras for mantic users on intel meteor lake?

There are still some more different models under development, but Intel MIPI IPU6 on Intel Meteor Lake with OV02E and serveral camera sensors we have enabled before should be working.

> Since this includes a new upstream code drop, could you summarize the highlights?

For people are interested in some more readable git history, we have https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/experimental-dkms.

For a quick review here, there have been like a dozen engineering code releases, and they're all one commit code dump without details. For what we can tell, they cover:

1. camera sensor fixes/additions: hm2170, hm2172, gc5035, ov02e10, ov08a10, ov8856, etc.
2. fix build against new kernel releases, inclusive of gpio/V4L2 kernel API changes
3. gpio addition to int3472 for camera sensor controls
4. documentation changes
5. a few changes for the V4L2 interface to ensure a right device number could be chosen
6. support new hardware platform RPL-P, ADL-N, MTL-P
7. support additional V4L2 image format
8. drop test pattern generator
9. new Lattice MIPI aggregator

> Have you inspected them for backwards incompatible changes?

Yes, we tested all released, MIPI camera equipped platforms, TGL & ADL, as commented in the SRU justification.

> Like my comment #24 above, is there a way to test this that does not involve out-of-archive packages? If not, what is the benefit of this update to mantic users?

The PPAs are for easy of verification. In reality you may simply install the dkms or prebuilt linux-modules-{ipu6,ivsc,usbio}-generic packages. General users still need that intel-ipu6 PPA, because it hosts userspace HAL frameworks that are still being MIRed.

> That doesn't sound very reassuring :) Having said that, you think it's ready for a stable release update for mantic users? Mantic users will benefit from this update?

Yes, or they got nothing.

If they're to manually fix IPU6 cameras on their notebook, the same things are mandatory to them, and the same things are only available to them as these are what we can get from Intel.

Hi Andreas Hasenack, do you think I've addressed your concern at the most extend? Please comment.

The src:ivsc-driver package produces bin:intel-vsc-dkms

The src:ipu6-drivers package produces bin:intel-ipu6-dkms

We need the test case to use these binary dkms packages from mantic-proposed (once they get accepted). These are the packages being proposed for the SRU, so they are the ones that have to be used for the test, not packages from a ppa. I understand these dkms packages replace the linux-modules-{ipu6,ivsc}-oem ones from the ppa?

As you said, the ppa is for ease/convenience, but we need to test the dkms packages that this update is providing, even if that means an extra step for users (install dkms, wait for build).

Can you change your testing instructions to use the dkms packages produced by this SRU, and the current mantic kernel from proposed (6.5.0-14.14)?

@Andreas, done.

ok, so let's see:

> [Test Case]
>
> With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well.
>
> To actually verify the camera framework:
> ```
> $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
> $ sudo apt install linux-oem-22.04d

What is this "linux-oem-22.04d" package, why is it needed, and where does it come from?

> $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
> $ sudo apt install intel-usbio-dkms # from bug 2041800

So we need that to land in mantic-proposed too, right? Looks like it still needs sponsoring?

> $ sudo apt install gstreamer1.0-icamera v4l2-relayd

These come from the oem ppa?
What can we test without these two packages installed, i.e., what can be tested with a pristine mantic installation?
Will these two packages make it into the ubuntu archive for mantic at some point? Is there a bug for that effort?

linux-oem-22.04d is oem-6.5 kernel from jammy, that is not needed here since the mantic kernel should be enough

the extra packages likely won't get in mantic, maybe in noble

Can we change the test case to this:

# enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
# reboot into the 6.5.0-14.14 kernel
$ sudo apt install intel-ipu6-dkms intel-vsc-dkms
$ sudo apt install intel-usbio-dkms # from bug 2041800
$ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
$ sudo apt install gstreamer1.0-icamera v4l2-relayd

In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive.

And then browse https://webcamtests.com/ for testing.

@Andreas, sure, and I saw you have updated the steps.

Removed mentioning usbio from verification steps as that doesn't block MIPI on MTL in general, but on a couple of models.

Hello You-Sheng, or anyone else affected,

Accepted ivsc-driver into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ivsc-driver/0~git202212210258.94ecb88b-0ubuntu0.23.10.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Verified ivsc-driver/mantic-proposed version 0~git202212210258.94ecb88b-0ubuntu0.23.10.3.

@Andreas, is there a problem in ipu6-drivers? ivsc-driver is in -proposed, but ipu6-drivers is not.

ipu6-drivers in mantic unapproved is addressing more than just this bug: its changes[1] file lists 2012407 2021740 2026402 2031412.

#2021740 had a question about using a ppa in the test case
#2026402 didn't have a test case, and Timo recently added a comment saying that this bug was actually already fixed in mantic

It's not my SRU shift today, but other SRU team members can review these pending issues and their current status.

1. https://launchpadlibrarian.net/697874516/ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.23.10.1_source.changes

Sorry to cut in at the very last moment.

Considering there's a new release tag from upstream code for ipu6-drivers to fix the Mayabay MLK issue (lp:2044991), shall we include the changes for ipu6-drivers at this time? Thank you!

Generally, it's your call, unless what you mean is that the current version in unapproved, without the fix for 2044991, is broken/bad/not-worth-it. Keep in mind that you would be adding another bug to the sru, requiring again the full SRU template (impact, test plan, validation), and all of the listed bugs have to be accepted and pass validation for the SRU to be released to updates.

Nothing broken. It's just one more change to load as soon as possible.

This bug is awaiting verification that the linux-lowlatency/6.5.0-14.14.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-lowlatency' to 'verification-done-mantic-linux-lowlatency'. If the problem still exists, change the tag 'verification-needed-mantic-linux-lowlatency' to 'verification-failed-mantic-linux-lowlatency'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux-laptop/6.5.0-1007.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-laptop' to 'verification-done-mantic-linux-laptop'. If the problem still exists, change the tag 'verification-needed-mantic-linux-laptop' to 'verification-failed-mantic-linux-laptop'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux-azure/6.5.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done-mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux-gcp/6.5.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-gcp' to 'verification-done-mantic-linux-gcp'. If the problem still exists, change the tag 'verification-needed-mantic-linux-gcp' to 'verification-failed-mantic-linux-gcp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the linux-hwe-6.5/6.5.0-14.14~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

It turns out we need the patch of ivsc-driver and ipu6-driver for lp:2044991.
Then we should unblock the SRU process we already had for this bug.

Sorry the all the inconvenience.

We will fix lp:2044991 in a separate SRU cycle run, please proceed the SRU cycle for lp:2031412 first. Thank you!

LP#2031412
- ipu6
  - noble: done
  - mantic: to be submitted into -proposed for review
- ivsc
  - noble: done
  - mantic: already in -proposed, verified, should move to -updates in a couple days
LP#2044991
- ipu6:
  - noble: to create debdiff when LP#2031412 in -proposed
  - mantic: TBD.
- ivsc
  - noble: nothing blocked. WIP
  - mantic: TBD

Attach a second proprosed revision of ipu6-drivers/mantic. Changes:
* removed v6.6 patches
* removed patch to build additional camera sensors that are not yet required for mantic.

Hello You-Sheng, or anyone else affected,

Accepted ipu6-drivers into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ipu6-drivers/0~git202310180730.3f813580-0ubuntu0.23.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

verified ipu6-drivers/mantic-proposed version 0~git202310180730.3f813580-0ubuntu0.23.10.1

This was uploaded, removing sponsors as there is nothing further to sponsor.

This bug is awaiting verification that the linux-nvidia-6.5/6.5.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-done-jammy-linux-nvidia-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-failed-jammy-linux-nvidia-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

I just ran this command on my mantic laptop, according to the [test plan]:

  sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u

And that PPA does not have mantic packages:
Err:24 https://ppa.launchpadcontent.net/oem-solutions-group/intel-ipu6/ubuntu mantic Release
  404 Not Found [IP: 185.125.190.80 443]
Reading package lists... Done
E: The repository 'https://ppa.launchpadcontent.net/oem-solutions-group/intel-ipu6/ubuntu mantic Release' does not have a Release file.

How did you perform the mantic verification of this bug?

Using that PPA from jammy pocket. Hi, that PPA contains HAL framework packages that are not yet in Ubuntu archive but packaged into Jammy oem image.

This bug was fixed in the package linux - 6.6.0-14.14

---------------
linux (6.6.0-14.14) noble; urgency=medium

  * noble/linux: 6.6.0-14.14 -proposed tracker (LP: #2045243)

  * Noble update: v6.6.3 upstream stable release (LP: #2045244)
    - locking/ww_mutex/test: Fix potential workqueue corruption
    - btrfs: abort transaction on generation mismatch when marking eb as dirty
    - lib/generic-radix-tree.c: Don't overflow in peek()
    - x86/retpoline: Make sure there are no unconverted return thunks due to KCSAN
    - perf/core: Bail out early if the request AUX area is out of bound
    - srcu: Fix srcu_struct node grpmask overflow on 64-bit systems
    - selftests/lkdtm: Disable CONFIG_UBSAN_TRAP in test config
    - clocksource/drivers/timer-imx-gpt: Fix potential memory leak
    - clocksource/drivers/timer-atmel-tcb: Fix initialization on SAM9 hardware
    - srcu: Only accelerate on enqueue time
    - smp,csd: Throw an error if a CSD lock is stuck for too long
    - cpu/hotplug: Don't offline the last non-isolated CPU
    - workqueue: Provide one lock class key per work_on_cpu() callsite
    - x86/mm: Drop the 4 MB restriction on minimal NUMA node memory size
    - wifi: plfxlc: fix clang-specific fortify warning
    - wifi: ath12k: Ignore fragments from uninitialized peer in dp
    - wifi: mac80211_hwsim: fix clang-specific fortify warning
    - wifi: mac80211: don't return unset power in ieee80211_get_tx_power()
    - atl1c: Work around the DMA RX overflow issue
    - bpf: Detect IP == ksym.end as part of BPF program
    - wifi: ath9k: fix clang-specific fortify warnings
    - wifi: ath12k: fix possible out-of-bound read in ath12k_htt_pull_ppdu_stats()
    - wifi: ath10k: fix clang-specific fortify warning
    - wifi: ath12k: fix possible out-of-bound write in
      ath12k_wmi_ext_hal_reg_caps()
    - ACPI: APEI: Fix AER info corruption when error status data has multiple
      sections
    - net: sfp: add quirk for Fiberstone GPON-ONU-34-20BI
    - wifi: mt76: mt7921e: Support MT7992 IP in Xiaomi Redmibook 15 Pro (2023)
    - wifi: mt76: fix clang-specific fortify warnings
    - net: annotate data-races around sk->sk_tx_queue_mapping
    - net: annotate data-races around sk->sk_dst_pending_confirm
    - wifi: ath12k: mhi: fix potential memory leak in ath12k_mhi_register()
    - wifi: ath10k: Don't touch the CE interrupt registers after power up
    - net: sfp: add quirk for FS's 2.5G copper SFP
    - vsock: read from socket's error queue
    - bpf: Ensure proper register state printing for cond jumps
    - wifi: iwlwifi: mvm: fix size check for fw_link_id
    - Bluetooth: btusb: Add date->evt_skb is NULL check
    - Bluetooth: Fix double free in hci_conn_cleanup
    - ACPI: EC: Add quirk for HP 250 G7 Notebook PC
    - tsnep: Fix tsnep_request_irq() format-overflow warning
    - gpiolib: acpi: Add a ignore interrupt quirk for Peaq C1010
    - platform/chrome: kunit: initialize lock for fake ec_dev
    - of: address: Fix address translation when address-size is greater than 2
    - platform/x86: thinkpad_acpi: Add battery quirk for Thinkpad X120e
    - drm/gma500: Fix call trace when psb_gem_mm_init() fails
    - drm/amdkfd: rateli...

This bug is awaiting verification that the linux-lowlatency-hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-linux-lowlatency-hwe-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug was fixed in the package ivsc-driver - 0~git202212210258.94ecb88b-0ubuntu0.23.10.3

---------------
ivsc-driver (0~git202212210258.94ecb88b-0ubuntu0.23.10.3) mantic; urgency=low

  [ You-Sheng Yang ]
  * Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
    - ljca: try to find acpi device from hub device
    - mei-vsc: port mei api change in v6.2
    - mfd: ljca: Fix try_match_acpi_hid return value checking
    - misc: spi-vsc: Fix cvfd_ids array with terminator

 -- You-Sheng Yang <email address hidden> Wed, 23 Aug 2023 00:11:46 +0800

This bug was fixed in the package ipu6-drivers - 0~git202310180730.3f813580-0ubuntu0.23.10.1

---------------
ipu6-drivers (0~git202310180730.3f813580-0ubuntu0.23.10.1) mantic; urgency=low

  [ You-Sheng Yang ]
  * New upstream release
    - Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
    - debian: refresh patches, drop upstreamed ones
  * d/patches/0007: add CONFIG_VIDEO_V4L2_I2C to BUILD_EXCLUSIVE_CONFIG
    (LP: #2012407)
  * debian: add modaliases (LP: #2021740)

 -- You-Sheng Yang <email address hidden> Fri, 01 Sep 2023 17:51:53 +0800

The IPU6 webcam still does not work on my Dell XPS 16 (9640). I've tested it with Ubuntu 24.04 daily builds including with the 6.9-rc1 kernel. What information would you need to check the problem?

The Intel IPU6 in my Dell Precision 5680 fails in any which way I'm trying to get it to work with ubuntu 24.04 (kernel 6.8.0-31-generic). The clickyclicky 'Additional drivers' doesn't work, the oem-solutions-group/intel-ipu6 PPA doesn't work. The failures are various, from not even having a /dev/video* showing up to just having a buffer ioctl-related error in v4l2-dependant software, to not finding the .zst compressed firmware under /lib/firmware.

To add to the already confusing heap of issues, there's also a libcamera0.2, that may or may not work - it didn't in my case, but I've got to spend a few hours trying to explore that route.

I have to say this was a humiliating experience; there is virtually no documentation, now HOWTO, only some vague guides that all end up with a non-existant or non-working camera.

Is there some movement to get this fixed before the ubuntu 24.04 release?

Following the above guides results in:

$ cheese -d "Intel MIPI Camera"
[0:00:46.050565361] [4778] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found
[0:00:46.050587032] [4778] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
[0:00:46.050602739] [4778] INFO Camera camera_manager.cpp:284 libcamera v0.2.0

(cheese:4778): cheese-WARNING **: 10:01:53.240: stream error: can't negotiate buffers on port: ../src/gst/gstpipewiresrc.c(692): on_state_changed (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1