From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Fernando Rimoli <fernandorimoli11@gmail.com>
Cc: Daniel Scally <dan.scally@ideasonboard.com>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Arsalan Naeem <naeemarsalan@gmail.com>,
Jakob Berg Jespersen <dev@berg.pm>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 4/6] media: ipu-bridge: Assign endpoint property indices dynamically
Date: Wed, 2 Sep 2026 09:33:59 +0300 [thread overview]
Message-ID: <apfDVz8nQ43yEl6i@kekkonen.localdomain> (raw)
In-Reply-To: <20260831181858.325109-5-fernandorimoli11@gmail.com>
On Mon, Aug 31, 2026 at 08:18:56PM +0200, Fernando Rimoli wrote:
> The endpoint property array is populated with hardcoded indices, so a
> property that is only set conditionally has to be placed at a fixed slot.
> As the array is NULL-terminated, such a property is silently dropped when
> an earlier optional slot is left empty: "link-frequencies" is skipped for
> configs with nr_link_freqs == 0, which would truncate the array before
> anything following it.
>
> Name the endpoint property slots in an enum, size the array accordingly
> and assign the indices through a bounds-checked running index, as done
> for the MIPI DisCo for Imaging properties in mipi-disco-img.c. No
> functional change intended: the same properties are set in the same
> order.
There's a lot of unneeded information here. For simple patches like this
there's no need to go deep in details that can be easily seen from the
code. How about:
Index the ep_properties array dynamically instead of plain numerical values
as is done in mipi-disco-img.c.
>
> Signed-off-by: Fernando Rimoli <fernandorimoli11@gmail.com>
> ---
> drivers/media/pci/intel/ipu-bridge.c | 27 ++++++++++++++-------------
> include/media/ipu-bridge.h | 19 ++++++++++++++++++-
> 2 files changed, 32 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/media/pci/intel/ipu-bridge.c b/drivers/media/pci/intel/ipu-bridge.c
> index 131c70844..cd3c36d44 100644
> --- a/drivers/media/pci/intel/ipu-bridge.c
> +++ b/drivers/media/pci/intel/ipu-bridge.c
> @@ -449,6 +449,7 @@ static void ipu_bridge_create_fwnode_properties(
> struct ipu_bridge *bridge,
> const struct ipu_sensor_config *cfg)
> {
> + unsigned int i = IPU_SENSOR_EP_BUS_TYPE;
You can just initialise this to 0.
> struct ipu_property_names *names = &sensor->prop_names;
> struct software_node *nodes = sensor->swnodes;
>
> @@ -508,21 +509,21 @@ static void ipu_bridge_create_fwnode_properties(
> PROPERTY_ENTRY_REF_ARRAY("lens-focus", sensor->vcm_ref);
> }
>
> - sensor->ep_properties[0] = PROPERTY_ENTRY_U32(
> - sensor->prop_names.bus_type,
> - V4L2_FWNODE_BUS_TYPE_CSI2_DPHY);
> - sensor->ep_properties[1] = PROPERTY_ENTRY_U32_ARRAY_LEN(
> - sensor->prop_names.data_lanes,
> - bridge->data_lanes, sensor->lanes);
> - sensor->ep_properties[2] = PROPERTY_ENTRY_REF_ARRAY(
> - sensor->prop_names.remote_endpoint,
> - sensor->local_ref);
> + sensor->ep_properties[IPU_NEXT_EP_PROPERTY(i, NUM_OF)] =
You should use the maximum value of the property index here. Same below.
Right now it's fairly simple, but in more complicated cases it helps
keeping track of the properties.
> + PROPERTY_ENTRY_U32(names->bus_type,
> + V4L2_FWNODE_BUS_TYPE_CSI2_DPHY);
> + sensor->ep_properties[IPU_NEXT_EP_PROPERTY(i, NUM_OF)] =
> + PROPERTY_ENTRY_U32_ARRAY_LEN(names->data_lanes,
> + bridge->data_lanes, sensor->lanes);
> + sensor->ep_properties[IPU_NEXT_EP_PROPERTY(i, NUM_OF)] =
> + PROPERTY_ENTRY_REF_ARRAY(names->remote_endpoint,
> + sensor->local_ref);
>
> if (cfg->nr_link_freqs > 0)
> - sensor->ep_properties[3] = PROPERTY_ENTRY_U64_ARRAY_LEN(
> - sensor->prop_names.link_frequencies,
> - cfg->link_freqs,
> - cfg->nr_link_freqs);
> + sensor->ep_properties[IPU_NEXT_EP_PROPERTY(i, NUM_OF)] =
> + PROPERTY_ENTRY_U64_ARRAY_LEN(names->link_frequencies,
> + cfg->link_freqs,
> + cfg->nr_link_freqs);
>
> sensor->ipu_properties[0] = PROPERTY_ENTRY_U32_ARRAY_LEN(
> sensor->prop_names.data_lanes,
> diff --git a/include/media/ipu-bridge.h b/include/media/ipu-bridge.h
> index 16fac7654..61e10cef1 100644
> --- a/include/media/ipu-bridge.h
> +++ b/include/media/ipu-bridge.h
> @@ -64,6 +64,23 @@ enum ipu_sensor_swnodes {
> SWNODE_COUNT
> };
>
> +enum ipu_sensor_ep_props {
> + IPU_SENSOR_EP_BUS_TYPE,
> + IPU_SENSOR_EP_DATA_LANES,
> + IPU_SENSOR_EP_REMOTE_EP,
> + IPU_SENSOR_EP_LINK_FREQUENCIES,
> + IPU_SENSOR_EP_NUM_OF,
> + IPU_SENSOR_EP_NUM_ENTRIES
> +};
> +
> +/*
> + * Get the index of the next endpoint property in the property array, with a
> + * given maximum value.
> + */
> +#define IPU_NEXT_EP_PROPERTY(index, max) \
The macro isn't limited to endpoint properties, how about calling it
e.g. IPU_BRIDGE_NEXT_PROPERTY?
> + (WARN_ON((index) > IPU_SENSOR_EP_##max) ? \
How about:
s/SENSOR_EP/BRIDGE/
> + IPU_SENSOR_EP_##max : (index)++)
> +
> /* Data representation as it is in ACPI SSDB buffer */
> struct ipu_sensor_ssdb {
> u8 version;
> @@ -141,7 +158,7 @@ struct ipu_sensor {
> const char *vcm_type;
>
> struct ipu_property_names prop_names;
> - struct property_entry ep_properties[5];
> + struct property_entry ep_properties[IPU_SENSOR_EP_NUM_ENTRIES];
> struct property_entry dev_properties[5];
> struct property_entry ipu_properties[3];
> struct property_entry ivsc_properties[1];
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-09-02 6:34 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 21:36 [PATCH] media: ov5693: add OVTI5693 ACPI HID for IPU6 Surface devices Fernando Rimoli
2026-07-09 13:17 ` Dan Scally
2026-07-14 9:32 ` Sakari Ailus
2026-07-17 13:20 ` [PATCH v2 0/3] media: Enable the OV5693 front camera on " Fernando Rimoli
2026-07-17 13:20 ` [PATCH v2 1/3] media: i2c: ov5693: Add OVTI5693 ACPI HID Fernando Rimoli
2026-07-17 13:20 ` [PATCH v2 2/3] media: ipu-bridge: Add OVTI5693 to the list of supported sensors Fernando Rimoli
2026-07-17 13:20 ` [PATCH v2 3/3] media: i2c: ov5693: Gate the MIPI clock lane for IPU6 Fernando Rimoli
2026-07-19 16:25 ` Jakob Berg Jespersen
2026-07-19 22:42 ` Sakari Ailus
2026-07-20 16:38 ` [PATCH v3 0/4] media: Enable the OV5693 front camera on IPU6 Surface devices Fernando Rimoli
2026-07-20 16:38 ` [PATCH v3 1/4] media: i2c: ov5693: Add OVTI5693 ACPI HID Fernando Rimoli
2026-07-20 16:38 ` [PATCH v3 2/4] media: ipu-bridge: Add OVTI5693 to the list of supported sensors Fernando Rimoli
2026-07-20 21:09 ` Dan Scally
2026-07-20 16:38 ` [PATCH v3 3/4] media: i2c: ov5693: Gate the MIPI clock lane for non-continuous clock Fernando Rimoli
2026-07-20 21:49 ` Dan Scally
2026-07-30 7:46 ` Sakari Ailus
2026-08-31 18:16 ` Fernando Rimoli
2026-07-20 16:38 ` [PATCH v3 4/4] media: ipu-bridge: Request non-continuous clock for ov5693 on IPU6 Fernando Rimoli
2026-07-20 21:56 ` Dan Scally
2026-07-20 23:50 ` Fernando Rimoli
2026-07-30 7:32 ` Sakari Ailus
2026-08-31 18:17 ` Fernando Rimoli
2026-08-31 18:18 ` Fernando Rimoli
2026-08-31 18:18 ` [PATCH v4 0/6] media: Enable the OV5693 front camera on IPU6 Surface devices Fernando Rimoli
2026-08-31 18:18 ` [PATCH v4 1/6] media: i2c: ov5693: Add OVTI5693 ACPI HID Fernando Rimoli
2026-08-31 18:18 ` [PATCH v4 2/6] media: ipu-bridge: Add OVTI5693 to the list of supported sensors Fernando Rimoli
2026-08-31 18:18 ` [PATCH v4 3/6] media: i2c: ov5693: Gate the MIPI clock lane for non-continuous clock Fernando Rimoli
2026-09-01 9:32 ` Jakob Berg Jespersen
2026-09-01 9:56 ` Fernando Rimoli
2026-09-01 16:34 ` Fernando Rimoli
2026-09-01 18:32 ` Jakob Berg Jespersen
2026-09-01 18:46 ` Fil Dunsky
2026-09-02 7:27 ` Sakari Ailus
2026-08-31 18:18 ` [PATCH v4 4/6] media: ipu-bridge: Assign endpoint property indices dynamically Fernando Rimoli
2026-09-02 6:33 ` Sakari Ailus [this message]
2026-08-31 18:18 ` [PATCH v4 5/6] media: ipu-bridge: Match sensor configs per IPU and add config flags Fernando Rimoli
2026-09-01 9:57 ` Fernando Rimoli
2026-09-02 6:42 ` Sakari Ailus
2026-08-31 18:18 ` [PATCH v4 6/6] media: ipu-bridge: Request non-continuous clock for ov5693 on IPU6 Fernando Rimoli
2026-09-02 4:42 ` Kengo Oki
2026-09-02 14:23 ` [PATCH v5 0/7] media: Enable the OV5693 front camera on IPU6 Surface devices Fernando Rimoli
2026-09-02 14:23 ` [PATCH v5 1/7] media: i2c: ov5693: Add OVTI5693 ACPI HID Fernando Rimoli
2026-09-02 14:23 ` [PATCH v5 2/7] media: ipu-bridge: Add OVTI5693 to the list of supported sensors Fernando Rimoli
2026-09-02 14:23 ` [PATCH v5 3/7] dt-bindings: media: ov5693: Add clock-noncontinuous Fernando Rimoli
2026-09-02 17:27 ` Conor Dooley
2026-09-02 14:23 ` [PATCH v5 4/7] media: i2c: ov5693: Gate the MIPI clock lane for non-continuous clock Fernando Rimoli
2026-09-02 19:11 ` Fil Dunsky
2026-09-02 14:23 ` [PATCH v5 5/7] media: ipu-bridge: Assign endpoint property indices dynamically Fernando Rimoli
2026-09-02 14:23 ` [PATCH v5 6/7] media: ipu-bridge: Match sensor configs per IPU and add config flags Fernando Rimoli
2026-09-02 14:23 ` [PATCH v5 7/7] media: ipu-bridge: Request non-continuous clock for ov5693 on IPU6 Fernando Rimoli
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=apfDVz8nQ43yEl6i@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=dev@berg.pm \
--cc=fernandorimoli11@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=naeemarsalan@gmail.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