From: Hans de Goede <hdegoede@redhat.com>
To: Wentong Wu <wentong.wu@intel.com>,
sakari.ailus@linux.intel.com, djrscally@gmail.com,
laurent.pinchart@ideasonboard.com, linux-media@vger.kernel.org
Cc: bingbu.cao@linux.intel.com, zhifeng.wang@intel.com,
xiang.ye@intel.com, tian.shu.qiu@intel.com
Subject: Re: [PATCH v6 3/3] ACPI: delay enumeration of devices with a _DEP pointing to IVSC device
Date: Tue, 25 Apr 2023 10:05:30 +0200 [thread overview]
Message-ID: <d8da36f6-0796-ceef-8ea5-0ade836acda4@redhat.com> (raw)
In-Reply-To: <1682387039-16674-4-git-send-email-wentong.wu@intel.com>
Hi Wentong,
On 4/25/23 03:43, 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.
>
> 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 mei bus ACPI device, so
> adding IVSC mei bus ACPI device 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 IVSC mei bus ACPI
> device.
>
> On TGL platform, the HID of IVSC mei bus ACPI device is INTC1059,
> and on ADL platform, the HID is INTC1095. So add both of them to
> acpi_honor_dep_ids.
>
> Signed-off-by: Wentong Wu <wentong.wu@intel.com>
> ---
> drivers/acpi/scan.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
> index 2743444..89368d7 100644
> --- a/drivers/acpi/scan.c
> +++ b/drivers/acpi/scan.c
> @@ -796,6 +796,8 @@ static const char * const acpi_ignore_dep_ids[] = {
> /* List of HIDs for which we honor deps of matching ACPI devs, when checking _DEP lists. */
> static const char * const acpi_honor_dep_ids[] = {
> "INT3472", /* Camera sensor PMIC / clk and regulator info */
> + "INTC1059",
> + "INTC1095",
Can you please add a short comment after these to explain what they are for,
e.g.:
"INTC1059", /* IVSC (TGL) driver must be loaded to allow i2c access to camera sensors */
"INTC1095", /* IVSC (ADL) driver must be loaded to allow i2c access to camera sensors */
> NULL
> };
>
Regards,
Hans
next prev parent reply other threads:[~2023-04-25 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 1:43 [PATCH v6 0/3] media: pci: intel: ivsc: Add driver of Intel Visual Sensing Controller(IVSC) Wentong Wu
2023-04-25 1:43 ` [PATCH v6 1/3] media: pci: intel: ivsc: Add CSI submodule Wentong Wu
2023-04-25 1:43 ` [PATCH v6 2/3] media: pci: intel: ivsc: Add ACE submodule Wentong Wu
2023-04-25 1:43 ` [PATCH v6 3/3] ACPI: delay enumeration of devices with a _DEP pointing to IVSC device Wentong Wu
2023-04-25 8:05 ` Hans de Goede [this message]
2023-04-25 8:13 ` Wu, Wentong
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=d8da36f6-0796-ceef-8ea5-0ade836acda4@redhat.com \
--to=hdegoede@redhat.com \
--cc=bingbu.cao@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--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