From: Hans de Goede <hdegoede@redhat.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, bingbu.cao@intel.com,
laurent.pinchart@ideasonboard.com,
andriy.shevchenko@linux.intel.com, ilpo.jarvinen@linux.intel.com,
claus.stovgaard@gmail.com, tomi.valkeinen@ideasonboard.com,
tfiga@chromium.org, senozhatsky@chromium.org,
andreaskleist@gmail.com, bingbu.cao@linux.intel.com,
tian.shu.qiu@intel.com, hongju.wang@intel.com
Subject: Re: [PATCH v4 00/19] Intel IPU6 and IPU6 input system drivers
Date: Wed, 17 Apr 2024 10:59:37 +0200 [thread overview]
Message-ID: <0ce5cc60-da32-4e0a-89bb-fa481d4a15b1@redhat.com> (raw)
In-Reply-To: <Zh-Jr2gfdoCeB5-4@valkosipuli.retiisi.eu>
Hi Sakari,
On 4/17/24 10:34 AM, Sakari Ailus wrote:
> Hi Hans,
>
> On Wed, Apr 17, 2024 at 09:56:40AM +0200, Hans de Goede wrote:
>> Hi Sakari,
>> On 4/16/24 10:10 PM, Sakari Ailus wrote:
>>> Hello everyone,
>>>
>>> This patch series adds a driver for Intel IPU6 input system.
>>> IPU6 is the sixth generation of Imaging Processing Unit, it is a PCI
>>> device which can be found in some Intel Client Platforms. User can use
>>> IPU6 to capture images from MIPI camera sensors.
>>>
>>> IPU6 has its own firmware which exposes ABIs to driver, and communicates
>>> with CSE to do firmware authentication. IPU6 has its MMU hardware, so
>>> the driver sets up a page table to allow IPU6 DMA to access the system
>>> memory.
>>>
>>> IPU6 input system driver uses MC and V4L2 sub-device APIs besides V4L2.
>>>
>>> I can now capture images from ov01a10 and ov2740 sensors (including
>>> metadata from the latter).
>>>
>>> The series applies on top of the metadata patchset
>>> <URL:https://lore.kernel.org/linux-media/20240416193319.778192-1-sakari.ailus@linux.intel.com/T/#t>.
>>
>> Thank you for the new version!
>>
>> I assume that the posting of this new version means that you have solved
>> the stability issues where the laptop would freeze after sttreaming from
>> an ov2740 sensor with metadata once ?
>>
>> What about the unrelated ov2740 driver issue where the sensor would not
>> always start streaming for which you temporarily disabled runtime pm
>> for the sensor as a workaround any progress on that ?
>
> I'm afraid these issues remain.
You mean both issues remain? I'm not that worried about the runtime-pm ov2740
issue, but if the lockup after streaming issue also remains that is a lot
more worrying.
I've been running an older version of this series without the metadata
support and that is pretty rock solid, so this seems to be caused by
enabling metadata support.
AFAIK the current out of tree solution with partly closed-source
userspace stack does not use metadata right /
Do you know if the Windows stack uses metadata capture from the sensor?
If neither the existing out of tree Linux stack nor the Windows stack
is using metadata capture then chances are we are actually hitting
hw/firmware bugs here. This would not be the first time that the Linux
community tries to enable a hw-feature not used by the factory installed
OS for the hw and ends up failing miserably because the feature was
never fully tested and turns out to be full of bugs.
IMHO if we cannot get the stability issue fixed real soon it would
be best to move forward with this patch series without adding
the metadata support. So basically drop patch 17/19 .
>> Do you have a git branch available with the metadata + this series
>> somewhere for easy testing ? I would like to give this a test run on
>> my own IPU6 + ov2740 laptop.
>
> Both of the sets can be found here:
>
> <URL:https://git.linuxtv.org/sailus/media_tree.git/log/?h=ipu6>
Thank you.
Regards,
Hans
next prev parent reply other threads:[~2024-04-17 8:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 20:10 [PATCH v4 00/19] Intel IPU6 and IPU6 input system drivers Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 01/19] media: ipu6: Add PCI device table header Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 02/19] media: ivsc: csi: Use IPU bridge Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 03/19] media: intel/ipu6: add Intel IPU6 PCI device driver Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 04/19] media: intel/ipu6: add IPU auxiliary devices Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 05/19] media: intel/ipu6: add IPU6 buttress interface driver Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 06/19] media: intel/ipu6: CPD parsing for get firmware components Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 07/19] media: intel/ipu6: add IPU6 DMA mapping API and MMU table Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 08/19] media: intel/ipu6: add syscom interfaces between firmware and driver Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 09/19] media: intel/ipu6: input system ABI " Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 10/19] media: intel/ipu6: add IPU6 CSI2 receiver v4l2 sub-device Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 11/19] media: intel/ipu6: add the CSI2 DPHY implementation Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 12/19] media: intel/ipu6: input system video nodes and buffer queues Sakari Ailus
2024-04-16 20:10 ` [PATCH v4 13/19] media: intel/ipu6: add the main input system driver Sakari Ailus
2024-04-16 20:11 ` [PATCH v4 14/19] media: intel/ipu6: add Kconfig and Makefile Sakari Ailus
2024-04-16 20:11 ` [PATCH v4 15/19] media: Kconfig: Select MEDIA_CONTROLLER for VIDEO_V4L2_SUBDEV_API Sakari Ailus
2024-04-16 20:11 ` [PATCH v4 16/19] MAINTAINERS: add maintainers for Intel IPU6 input system driver Sakari Ailus
2024-04-16 20:11 ` [PATCH v4 17/19] media: intel/ipu6: support line-based metadata capture support Sakari Ailus
2024-04-16 20:11 ` [PATCH v4 18/19] Documentation: add Intel IPU6 ISYS driver admin-guide doc Sakari Ailus
2024-04-16 20:11 ` [PATCH v4 19/19] Documentation: add documentation of Intel IPU6 driver and hardware overview Sakari Ailus
2024-04-17 7:56 ` [PATCH v4 00/19] Intel IPU6 and IPU6 input system drivers Hans de Goede
2024-04-17 8:34 ` Sakari Ailus
2024-04-17 8:59 ` Hans de Goede [this message]
2024-04-17 11:33 ` Bingbu Cao
2024-04-17 12:29 ` Sakari Ailus
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=0ce5cc60-da32-4e0a-89bb-fa481d4a15b1@redhat.com \
--to=hdegoede@redhat.com \
--cc=andreaskleist@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=claus.stovgaard@gmail.com \
--cc=hongju.wang@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@linux.intel.com \
--cc=senozhatsky@chromium.org \
--cc=tfiga@chromium.org \
--cc=tian.shu.qiu@intel.com \
--cc=tomi.valkeinen@ideasonboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.