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 v3 4/8] ACPI: property: Generate camera swnodes for ACPI and DisCo for Imaging
Date: Fri, 27 Jan 2023 12:35:12 +0200 [thread overview]
Message-ID: <Y9Oo4L0ToRTZye2Z@smile.fi.intel.com> (raw)
In-Reply-To: <20230125224101.401285-5-sakari.ailus@linux.intel.com>
On Thu, Jan 26, 2023 at 12:40:57AM +0200, Sakari Ailus wrote:
> Generate software nodes for information parsed from ACPI _CRS for CSI-2 as
> well as MIPI DisCo for Imaging spec. The software nodes are compliant with
> existing ACPI or DT definitions and are parsed by relevant drivers without
> changes.
...
> +static unsigned int next_csi2_port_index(struct acpi_device_software_nodes *ads,
> + unsigned int port_nr)
> +{
> + unsigned int i;
> +
> + for (i = 0; i < ads->num_ports; i++) {
> + struct acpi_device_software_node_port *port = &ads->ports[i];
> +
> + if (port->port_nr == port_nr)
> + return i;
> + if (port->port_nr != NO_CSI2_PORT)
> + continue;
> +
> + port->port_nr = port_nr;
> +
> + return i;
Maybe it would be better to use the same pattern as above?
if (port->port_nr == NO_CSI2_PORT) {
port->port_nr = port_nr;
return i;
}
> + }
> +
> + return NO_CSI2_PORT;
> +}
...
> +static struct fwnode_handle *get_mipi_port_handle(struct acpi_device *device,
> + unsigned int port)
> +{
> + static const char mipi_port_prefix[] = "mipi-img-port-";
> + char mipi_port_name[sizeof(mipi_port_prefix) + 2];
I think the following will be better:
char mipi_port_name[16];
> + if (snprintf(mipi_port_name, sizeof(mipi_port_name), "%s%u",
> + mipi_port_prefix, port) >= sizeof(mipi_port_name)) {
if (snprintf(mipi_port_name, sizeof(mipi_port_name), "mipi-img-port-%u",
port) >= sizeof(mipi_port_name)) {
> + acpi_handle_info(acpi_device_handle(device),
> + "mipi port name too long for port %u\n", port);
> + return NULL;
> + }
> +
> + return fwnode_get_named_child_node(acpi_fwnode_handle(device),
> + mipi_port_name);
> +}
...
> + union {
> + u32 val;
OK. I stopped here, because I'm not sure you have really sent an updated
version. For sure the val and union is not used.
> + /* Data lanes + the clock lane */
> + u8 val8[BITS_TO_BYTES(ARRAY_SIZE(port->data_lanes) + 1)];
> + } u;
...
Please, address all in v3.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-01-27 10:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 22:40 [PATCH v3 0/8] ACPI _CRS CSI-2 and MIPI DisCo for Imaging support Sakari Ailus
2023-01-25 22:40 ` [PATCH v3 1/8] ACPI: property: Parse data node string references in properties Sakari Ailus
2023-01-27 9:57 ` Andy Shevchenko
2023-01-30 18:21 ` Rafael J. Wysocki
2023-01-30 21:34 ` Andy Shevchenko
2023-01-25 22:40 ` [PATCH v3 2/8] ACPI: property: Parse _CRS CSI-2 descriptor Sakari Ailus
2023-01-27 10:08 ` Andy Shevchenko
2023-01-30 21:18 ` Sakari Ailus
2023-01-30 21:37 ` Andy Shevchenko
2023-01-30 21:45 ` Sakari Ailus
2023-02-02 19:57 ` Rafael J. Wysocki
2023-02-02 20:57 ` Sakari Ailus
2023-01-25 22:40 ` [PATCH v3 3/8] device property: Add SOFTWARE_NODE() macro for defining software nodes Sakari Ailus
2023-01-25 22:40 ` [PATCH v3 4/8] ACPI: property: Generate camera swnodes for ACPI and DisCo for Imaging Sakari Ailus
2023-01-27 10:35 ` Andy Shevchenko [this message]
2023-01-27 10:35 ` Andy Shevchenko
2023-01-30 21:22 ` Sakari Ailus
2023-01-30 21:39 ` Andy Shevchenko
2023-01-30 21:46 ` Sakari Ailus
2023-01-25 22:40 ` [PATCH v3 5/8] ACPI: property: Dig "rotation" property for devices with CSI2 _CRS Sakari Ailus
2023-01-25 22:40 ` [PATCH v3 6/8] ACPI: property: Rename parsed MIPI DisCo for Imaging properties Sakari Ailus
2023-01-25 22:41 ` [PATCH v3 7/8] ACPI: property: Skip MIPI property table without "mipi-img" prefix Sakari Ailus
2023-01-25 22:41 ` [PATCH v3 8/8] 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=Y9Oo4L0ToRTZye2Z@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