public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Wentong Wu <wentong.wu@intel.com>
Cc: hdegoede@redhat.com, djrscally@gmail.com,
	laurent.pinchart@ideasonboard.com, linux-media@vger.kernel.org,
	bingbu.cao@linux.intel.com, zhifeng.wang@intel.com,
	xiang.ye@intel.com, tian.shu.qiu@intel.com
Subject: Re: [PATCH v3 3/3] ACPI: delay enumeration of devices with a _DEP pointing to INTC1059 device
Date: Mon, 27 Mar 2023 10:06:54 +0300	[thread overview]
Message-ID: <ZCFAjoaIG2VxtLJr@kekkonen.localdomain> (raw)
In-Reply-To: <1679898188-14426-4-git-send-email-wentong.wu@intel.com>

Hi Wentong,

On Mon, Mar 27, 2023 at 02:23:08PM +0800, Wentong Wu wrote:
> Inside IVSC, switching ownership requires an interface with two different
> hardware modules, ACE and CSI. The software interface to these modules is
> based on Intel MEI framework. Usually mei client devices are dynamically
> created, so the info of consumers depending on mei client devices is not
> present in the firmware tables.

Ouch.

> 
> This causes problems with the probe ordering with respect to drivers for
> consumers of these mei client devices. But on these camera sensor devices,
> the ACPI nodes describing the sensors all have a _DEP dependency on the
> matching INTC1059 ACPI device, so adding INTC1059 to acpi_honor_dep_ids
> allows solving the probe-ordering problem by delaying the enumeration of
> ACPI-devices which have a _DEP dependency on an INTC1059 device.

What does the INTC1059 device represent?

-- 
Sakari Ailus

  reply	other threads:[~2023-03-27  7:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  6:23 [PATCH v3 0/3] media: pci: intel: ivsc: Add driver of Intel Visual Sensing Controller(IVSC) Wentong Wu
2023-03-27  6:23 ` [PATCH v3 1/3] media: pci: intel: ivsc: Add CSI submodule Wentong Wu
2023-03-27 10:01   ` kernel test robot
2023-03-28 13:59   ` kernel test robot
2023-03-29  8:48   ` Sakari Ailus
2023-03-30  3:58     ` Wu, Wentong
2023-03-30  8:23       ` Sakari Ailus
2023-03-29  8:49   ` Sakari Ailus
2023-03-27  6:23 ` [PATCH v3 2/3] media: pci: intel: ivsc: Add ACE submodule Wentong Wu
2023-03-29  8:03   ` Sakari Ailus
2023-03-30  7:32     ` Wu, Wentong
2023-03-30  8:27       ` Sakari Ailus
2023-03-27  6:23 ` [PATCH v3 3/3] ACPI: delay enumeration of devices with a _DEP pointing to INTC1059 device Wentong Wu
2023-03-27  7:06   ` Sakari Ailus [this message]
2023-03-27  7:17     ` Wu, Wentong
2023-03-27  7:32       ` Sakari Ailus
2023-03-27  7:36         ` Wu, Wentong
2023-03-27  7:21 ` [PATCH v3 0/3] media: pci: intel: ivsc: Add driver of Intel Visual Sensing Controller(IVSC) Sakari Ailus
2023-03-27  7:33   ` Wu, Wentong
2023-03-27  7:49     ` Sakari Ailus
2023-03-27  8:13       ` Wu, Wentong
2023-03-27  9:36         ` Sakari Ailus
2023-03-28  7:32           ` Wu, Wentong
2023-03-28 19:48             ` Sakari Ailus
2023-03-29  0:42               ` Wu, Wentong
2023-03-29  7:39                 ` 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=ZCFAjoaIG2VxtLJr@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=bingbu.cao@linux.intel.com \
    --cc=djrscally@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=tian.shu.qiu@intel.com \
    --cc=wentong.wu@intel.com \
    --cc=xiang.ye@intel.com \
    --cc=zhifeng.wang@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