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 v4 6/8] ACPI: property: Rename parsed MIPI DisCo for Imaging properties
Date: Wed, 8 Feb 2023 18:56:27 +0200 [thread overview]
Message-ID: <Y+PUO3a8ZOq0Haa2@smile.fi.intel.com> (raw)
In-Reply-To: <20230208152807.3064242-7-sakari.ailus@linux.intel.com>
On Wed, Feb 08, 2023 at 05:28:05PM +0200, Sakari Ailus wrote:
> MIPI DisCo for Imaging defines properties for sensor-adjacent devices such
> as EEPROM, LED flash or lens VCM as either device or sub-node references.
> This is compliant with existing DT definitions apart from property names.
>
> Rename parsed MIPI-defined properties so drivers will have a unified view
> of them as defined in DT and already parsed by drivers. This can be done
> in-place as the MIPI-defined property strings are always longer than the
> DT one. This also results in loss of constness in parser function
> arguments.
>
> Individual bindings to devices could define the references differently
> between MIPI DisCo for Imaging and DT, in terms of device or sub-node
> references. This will still need to be handled in the drivers themselves.
...
> +void acpi_properties_prepare_mipi(union acpi_object *elements)
> +{
> + unsigned int i;
> +
> + /* Replace MIPI DisCo for Imaging property names with DT equivalents. */
> + for (i = 0; i < ARRAY_SIZE(mipi_disco_props); i++) {
> + if (!strcmp(mipi_disco_props[i].mipi_prop,
> + elements[0].string.pointer)) {
/* const ? */ char *e0 = elements[0].string.pointer;
...
if (!strcmp(mipi_disco_props[i].mipi_prop, e0)) {
> + WARN_ON(strscpy(elements[0].string.pointer,
> + mipi_disco_props[i].dt_prop,
> + elements[0].string.length) < 0);
WARN_ON(strscpy(e0, mipi_disco_props[i].dt_prop,
elements[0].string.pointer) < 0);
?
> + break;
> + }
> + }
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-02-08 16:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 15:27 [PATCH v4 0/8] ACPI _CRS CSI-2 and MIPI DisCo for Imaging support Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 1/8] ACPI: property: Parse data node string references in properties Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 2/8] ACPI: property: Parse _CRS CSI-2 descriptor Sakari Ailus
2023-02-08 16:43 ` Andy Shevchenko
2023-02-08 20:26 ` Sakari Ailus
2023-02-08 20:43 ` kernel test robot
2023-02-08 22:16 ` Sakari Ailus
2023-02-08 21:04 ` kernel test robot
2023-02-09 2:43 ` Philip Li
2023-02-08 15:28 ` [PATCH v4 3/8] device property: Add SOFTWARE_NODE() macro for defining software nodes Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 4/8] ACPI: property: Generate camera swnodes for ACPI and DisCo for Imaging Sakari Ailus
2023-02-08 16:48 ` Andy Shevchenko
2023-02-08 15:28 ` [PATCH v4 5/8] ACPI: property: Dig "rotation" property for devices with CSI2 _CRS Sakari Ailus
2023-02-08 16:51 ` Andy Shevchenko
2023-02-08 20:56 ` Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 6/8] ACPI: property: Rename parsed MIPI DisCo for Imaging properties Sakari Ailus
2023-02-08 16:56 ` Andy Shevchenko [this message]
2023-02-08 21:27 ` Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 7/8] ACPI: property: Skip MIPI property table without "mipi-img" prefix Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 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=Y+PUO3a8ZOq0Haa2@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