From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-acpi@vger.kernel.org, linux-media@vger.kernel.org,
rafael@kernel.org, heikki.krogerus@linux.intel.com
Subject: Re: [PATCH v7 06/10] ACPI: scan: Generate software nodes based on MIPI DisCo for Imaging
Date: Tue, 28 Mar 2023 18:51:29 +0300 [thread overview]
Message-ID: <ZCMNAR3VJAzOZww3@smile.fi.intel.com> (raw)
In-Reply-To: <20230328101303.1458570-7-sakari.ailus@linux.intel.com>
On Tue, Mar 28, 2023 at 01:12:59PM +0300, Sakari Ailus wrote:
> Generate software nodes for driver use, based on MIPI DisCo for Imaging
> definitions.
>
> During the (sub-)namespace walk, ACPI device nodes are created but the
> drivers aren't probed for the devices yet. A convenient way to determine
> which ACPI devices this applies to is to find a hierarchical data node that
> begins with "mipi-img-port-". These devices need software nodes that need
> to be present before probing, and can only be constructed once the related
> _CRS CSI2 records have been parsed.
...
> - static const char mipi_port_prefix[] = "mipi-img-port-";
> - char mipi_port_name[sizeof(mipi_port_prefix) + 2];
> + char mipi_port_name[sizeof(MIPI_IMG_PORT_PREFIX) + 2];
>
> if (snprintf(mipi_port_name, sizeof(mipi_port_name), "%s%u",
> - mipi_port_prefix, port) >= sizeof(mipi_port_name)) {
> + MIPI_IMG_PORT_PREFIX, port) >= sizeof(mipi_port_name)) {
You are modifying lines you just brought by the previous patch. Why this mess?
...
> -static void acpi_bus_handle_postpone(acpi_handle handle,
> - struct list_head *head)
> +static void acpi_bus_handle_postpone(acpi_handle handle, struct list_head *head)
Unrelated change?
...
> +/**
> + * acpi_bus_device_postpone - Add an ACPI device to a given postponed list
> + * @device: The ACPI device
> + * @head: Postponed list head
> + *
> + * Add a given ACPI device to a list of ACPI objects for which the creation
> + * of the device objects is to be postponed.
> + */
> +void acpi_bus_device_postpone(struct acpi_device *device,
> + struct list_head *head)
Taking into account above indentation, why not to have them on one line to
begin with?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-03-28 15:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 10:12 [PATCH v7 00/10] ACPI _CRS CSI-2 and MIPI DisCo for Imaging support Sakari Ailus
2023-03-28 10:12 ` [PATCH v7 01/10] ACPI: scan: Remove the second DSDT traversal Sakari Ailus
2023-03-28 14:45 ` Andy Shevchenko
2023-03-28 14:48 ` Sakari Ailus
2023-03-28 14:55 ` Sakari Ailus
2023-03-28 10:12 ` [PATCH v7 02/10] ACPI: property: Parse data node string references in properties Sakari Ailus
2023-03-28 10:12 ` [PATCH v7 03/10] ACPI: property: Parse _CRS CSI-2 descriptor Sakari Ailus
2023-03-28 15:12 ` Andy Shevchenko
2023-03-28 15:27 ` Sakari Ailus
2023-03-28 15:46 ` Andy Shevchenko
2023-03-28 15:48 ` Sakari Ailus
2023-03-28 15:53 ` Andy Shevchenko
2023-03-28 19:26 ` Sakari Ailus
2023-03-28 10:12 ` [PATCH v7 04/10] device property: Add SOFTWARE_NODE() macro for defining software nodes Sakari Ailus
2023-03-28 10:12 ` [PATCH v7 05/10] ACPI: property: Prepare generating swnodes for ACPI and DisCo for Imaging Sakari Ailus
2023-03-28 15:44 ` Andy Shevchenko
2023-03-28 19:21 ` Sakari Ailus
2023-03-29 14:38 ` Andy Shevchenko
2023-03-29 15:20 ` Sakari Ailus
2023-03-28 10:12 ` [PATCH v7 06/10] ACPI: scan: Generate software nodes based on MIPI " Sakari Ailus
2023-03-28 15:51 ` Andy Shevchenko [this message]
2023-03-28 19:11 ` Sakari Ailus
2023-03-28 10:13 ` [PATCH v7 07/10] ACPI: property: Dig "rotation" property for devices with CSI2 _CRS Sakari Ailus
2023-03-28 10:13 ` [PATCH v7 08/10] ACPI: property: Rename parsed MIPI DisCo for Imaging properties Sakari Ailus
2023-03-28 10:13 ` [PATCH v7 09/10] ACPI: property: Skip MIPI property table without "mipi-img" prefix Sakari Ailus
2023-03-28 10:13 ` [PATCH v7 10/10] ACPI: property: Document _CRS CSI-2 and DisCo for Imaging support 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=ZCMNAR3VJAzOZww3@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.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;
as well as URLs for NNTP newsgroup(s).