From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-acpi@vger.kernel.org, rafael@kernel.org,
linux-media@vger.kernel.org, heikki.krogerus@linux.intel.com
Subject: Re: [PATCH 4/8] ACPI: property: Generate camera swnodes for ACPI and DisCo for Imaging
Date: Tue, 17 Jan 2023 16:59:18 +0200 [thread overview]
Message-ID: <Y8a3xixlrr4AVBjJ@smile.fi.intel.com> (raw)
In-Reply-To: <20230117122244.2546597-5-sakari.ailus@linux.intel.com>
On Tue, Jan 17, 2023 at 02:22:40PM +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.
...
> +#define GRAPH_PORT_NAME(var, num) \
> + (snprintf((var), sizeof(var), "port@%u", (num)) > sizeof(var))
SWNODE_GRAPH_PORT_NAME_FMT ?
...
> +#define NEXT_PROPERTY(index, max) \
> + (WARN_ON(++(index) > ACPI_DEVICE_SWNODE_##max + 1) ? \
'>' -- > '>=' and drop ' + 1'?
> + ACPI_DEVICE_SWNODE_##max : (index) - 1)
...
> + static const char mipi_port_prefix[] = "mipi-img-port-";
It's harder to read in the code, please put it in place.
...
> + port->ep_props[NEXT_PROPERTY(*ep_prop_index,
> + EP_DATA_LANES)] =
It's hard to read, taking into account that you split on index of the array.
How much a new monitor costs for you? Maybe I can donate to make you use more
than 80 from time to time? :-)
> + PROPERTY_ENTRY_U32_ARRAY_LEN("data-lanes",
> + port->data_lanes,
> + num_lanes);
...
> + ret = fwnode_property_read_u8_array(mipi_port_fwnode,
> + "mipi-img-lane-polarities",
> + u.val8, sizeof(u.val8));
> + if (ret > 0) {
> + unsigned int bytes = ret;
> +
> + /* Total number of lanes here is clock lane + data lanes */
> + if (bytes << 3 >= 1 + num_lanes) {
bytes * BITS_PER_BYTE? Or if you want to be super precise BITS_PER_TYPE(u8).
> + unsigned int i;
> +
> + /* Move polarity bits to the lane polarity u32 array */
> + for (i = 0; i < 1 + num_lanes; i++)
> + port->lane_polarities[i] =
> + (u.val8[i >> 3] & (1 << (i & 7))) ?
> + 1U : 0U;
> + port->ep_props[NEXT_PROPERTY(*ep_prop_index,
> + EP_LANE_POLARITIES)] =
Index on one line?
> + PROPERTY_ENTRY_U32_ARRAY_LEN("lane-polarities",
> + port->lane_polarities,
> + 1 + num_lanes);
> + } else {
> + acpi_handle_warn(acpi_device_handle(device),
> + "too few lane polarity bytes (%u)\n",
> + bytes);
> + }
> + }
...
> + unsigned int port_index = next_csi2_port_index(device->swnodes,
> + port_nr);
One line easier to read.
...
> + if (!ret)
Why not positive conditional?
Also seems like {} are missing since the body is multi-line.
> + port->ep_props[NEXT_PROPERTY(ep_prop_index,
> + EP_LINK_FREQUENCIES)] =
Index on one line?
> + PROPERTY_ENTRY_U64_ARRAY_LEN("link-frequencies",
> + port->link_frequencies,
> + num_link_freqs);
> + else
> + acpi_handle_info(acpi_device_handle(device),
> + "can't get link frequencies (%d)\n",
> + ret);
...
> + if (acpi_get_name(device->handle, ACPI_FULL_PATHNAME, &buffer) != AE_OK) {
We have ACPI_SUCCESS() / ACPI_FAILURE()
> + acpi_handle_warn(acpi_device_handle(device), "cannot get path name\n");
> + return;
> + }
...
> + ads->nodes[ACPI_DEVICE_SWNODE_ROOT] = (struct software_node) {
> + .name = buffer.pointer,
> + .properties = ads->dev_props,
> + };
Aren't you provided a macro for this?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-01-17 15:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 12:22 [PATCH 0/8] ACPI _CRS CSI-2 and MIPI DisCo for Imaging support Sakari Ailus
2023-01-17 12:22 ` [PATCH 1/8] ACPI: property: Parse data node string references in properties Sakari Ailus
2023-01-17 14:29 ` Andy Shevchenko
2023-01-19 14:03 ` Sakari Ailus
2023-01-17 12:22 ` [PATCH 2/8] ACPI: property: Parse _CRS CSI-2 descriptor Sakari Ailus
2023-01-17 14:34 ` Andy Shevchenko
2023-01-19 14:04 ` Sakari Ailus
2023-01-17 12:22 ` [PATCH 3/8] device property: Add SOFTWARE_NODE() macro for defining software nodes Sakari Ailus
2023-01-17 14:35 ` Andy Shevchenko
2023-01-17 14:37 ` Andy Shevchenko
2023-01-17 14:37 ` Andy Shevchenko
2023-01-17 12:22 ` [PATCH 4/8] ACPI: property: Generate camera swnodes for ACPI and DisCo for Imaging Sakari Ailus
2023-01-17 14:59 ` Andy Shevchenko [this message]
2023-01-19 15:03 ` Sakari Ailus
2023-01-19 15:44 ` Andy Shevchenko
2023-01-23 11:15 ` Sakari Ailus
2023-01-17 12:22 ` [PATCH 5/8] ACPI: property: Dig "rotation" property for devices with CSI2 _CRS Sakari Ailus
2023-01-17 15:22 ` Andy Shevchenko
2023-01-19 15:40 ` Sakari Ailus
2023-01-17 12:22 ` [PATCH 6/8] ACPI: property: Rename parsed MIPI DisCo for Imaging properties Sakari Ailus
2023-01-17 15:27 ` Andy Shevchenko
2023-01-19 15:45 ` Sakari Ailus
2023-01-17 12:22 ` [PATCH 7/8] ACPI: property: Skip MIPI property table without "mipi-img" prefix Sakari Ailus
2023-01-17 15:29 ` Andy Shevchenko
2023-01-19 15:51 ` Sakari Ailus
2023-01-19 16:09 ` Andy Shevchenko
2023-01-19 16:11 ` Andy Shevchenko
2023-01-20 12:07 ` Sakari Ailus
2023-01-20 13:59 ` Andy Shevchenko
2023-01-20 11:58 ` Sakari Ailus
2023-01-20 15:11 ` Andy Shevchenko
2023-01-20 22:34 ` Sakari Ailus
2023-01-17 12:22 ` [PATCH 8/8] ACPI: property: Document _CRS CSI-2 and DisCo for Imaging support Sakari Ailus
2023-01-17 15:32 ` Andy Shevchenko
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=Y8a3xixlrr4AVBjJ@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