public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Scally <djrscally@gmail.com>
To: kieran.bingham+renesas@ideasonboard.com,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-media@vger.kernel.org, devel@acpica.org,
	gregkh@linuxfoundation.org, rjw@rjwysocki.net,
	sergey.senozhatsky@gmail.com, mchehab@kernel.org
Cc: lenb@kernel.org, yong.zhi@intel.com,
	sakari.ailus@linux.intel.com, bingbu.cao@intel.com,
	tian.shu.qiu@intel.com, robert.moore@intel.com,
	erik.kaneda@intel.com, pmladek@suse.com, rostedt@goodmis.org,
	andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
	laurent.pinchart+renesas@ideasonboard.com,
	jacopo+renesas@jmondi.org, hverkuil-cisco@xs4all.nl,
	m.felsch@pengutronix.de, niklas.soderlund+renesas@ragnatech.se,
	slongerbeam@gmail.com, heikki.krogerus@linux.intel.com,
	linus.walleij@linaro.org,
	Jordan Hand <jorhand@linux.microsoft.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v4 15/15] ipu3-cio2: Add cio2-bridge to ipu3-cio2 driver
Date: Mon, 4 Jan 2021 13:55:57 +0000	[thread overview]
Message-ID: <9026519f-1f33-9df0-de18-0881069f7aaa@gmail.com> (raw)
In-Reply-To: <3d881e2b-747f-dcd7-a0cf-e7309419914b@ideasonboard.com>

Hi Kieran

On 04/01/2021 13:35, Kieran Bingham wrote:
>> +/*
>> + * Extend this array with ACPI Hardware IDs of devices known to be working
>> + * plus the number of link-frequencies expected by their drivers, along with
>> + * the frequency values in hertz. This is somewhat opportunistic way of adding
>> + * support for this for now in the hopes of a better source for the information
>> + * (possibly some encoded value in the SSDB buffer that we're unaware of)
>> + * becoming apparent in the future.
>> + *
>> + * Do not add an entry for a sensor that is not actually supported.
>> + */
>> +static const struct cio2_sensor_config cio2_supported_sensors[] = {
>> +	CIO2_SENSOR_CONFIG("INT33BE", 0),
>> +	CIO2_SENSOR_CONFIG("OVTI2680", 0),
> I don't know if these are expressed anywhere else but would it be
> helpful to add a comment, or indicator as to what the actual sensor is
> that is represented by this HID?
>
> I can make an assumption about what an OVTI2680 might be, but the
> INT33BE is quite opaque. It's not clear what support that adds.
>
> Unless no one cares what the sensor is that is, but I would anticipate
> anyone looking here to add a new sensor might want to investigate what
> was already in the table?

Yeah good point. I'll probably alternate comment and entry then, like:


+static const struct cio2_sensor_config cio2_supported_sensors[] = {
+	/* Sensor OVTI5693 */
+	CIO2_SENSOR_CONFIG("INT33BE", 0),
+	/* Sensor OVTI2680 */
+	CIO2_SENSOR_CONFIG("OVTI2680", 0),

As an inline comment won't fit for the sensors that we know link-frequencies for. That sound ok?

>> +static void cio2_bridge_create_fwnode_properties(
>> +	struct cio2_sensor *sensor,
>> +	const struct cio2_sensor_config *cfg)
>> +{
>> +	unsigned int i;
>> +
>> +	sensor->prop_names = prop_names;
>> +
>> +	for (i = 0; i < CIO2_MAX_LANES; i++)
>> +		sensor->data_lanes[i] = i + 1;
> Does something support lane swapping somewhere?
> I assume this is just mapping each lane directly through.

I think Sakari said remapping isn't supported in the CIO2 - so yeah this
is just mapping them directly

> Otherwise, I'm quite looking forwards to all of this ;-)
>
> Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Thanks very much!

  reply	other threads:[~2021-01-04 13:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 23:12 [PATCH v4 00/15] Add functionality to ipu3-cio2 driver allowing software_node connections to sensors on platforms designed for Windows Daniel Scally
2021-01-03 23:12 ` [PATCH v4 01/15] software_node: Fix refcounts in software_node_get_next_child() Daniel Scally
2021-01-03 23:12 ` [PATCH v4 02/15] media: ipu3-cio2: Add headers that ipu3-cio2.h is direct user of Daniel Scally
2021-01-03 23:12 ` [PATCH v4 03/15] property: Return true in fwnode_device_is_available for NULL ops Daniel Scally
2021-01-03 23:12 ` [PATCH v4 04/15] property: Call fwnode_graph_get_endpoint_by_id() for fwnode->secondary Daniel Scally
2021-01-03 23:12 ` [PATCH v4 05/15] software_node: Enforce parent before child ordering of nodes arrays Daniel Scally
2021-01-03 23:12 ` [PATCH v4 06/15] software_node: unregister software_nodes in reverse order Daniel Scally
2021-01-03 23:12 ` [PATCH v4 07/15] include: fwnode.h: Define format macros for ports and endpoints Daniel Scally
2021-01-04 14:24   ` Andy Shevchenko
2021-01-04 14:25     ` Daniel Scally
2021-01-03 23:12 ` [PATCH v4 08/15] software_node: Add support for fwnode_graph*() family of functions Daniel Scally
2021-01-04 10:22   ` Andy Shevchenko
2021-01-04 10:35     ` Daniel Scally
2021-01-03 23:12 ` [PATCH v4 09/15] lib/test_printf.c: Use helper function to unwind array of software_nodes Daniel Scally
2021-01-03 23:12 ` [PATCH v4 10/15] ipu3-cio2: Add T: entry to MAINTAINERS Daniel Scally
2021-01-03 23:12 ` [PATCH v4 11/15] ipu3-cio2: Rename ipu3-cio2.c Daniel Scally
2021-01-03 23:12 ` [PATCH v4 12/15] media: v4l2-core: v4l2-async: Check sd->fwnode->secondary in match_fwnode() Daniel Scally
2021-01-03 23:12 ` [PATCH v4 13/15] acpi: Add acpi_dev_get_next_match_dev() and helper macro Daniel Scally
2021-01-04 12:42   ` Andy Shevchenko
2021-01-04 12:57     ` Daniel Scally
2021-01-04 14:26   ` Andy Shevchenko
2021-01-03 23:12 ` [PATCH v4 14/15] include: media: v4l2-fwnode: Include v4l2_fwnode_bus_type Daniel Scally
2021-01-04 14:22   ` Andy Shevchenko
2021-01-03 23:12 ` [PATCH v4 15/15] ipu3-cio2: Add cio2-bridge to ipu3-cio2 driver Daniel Scally
2021-01-04 12:09   ` Andy Shevchenko
2021-01-04 13:00     ` Daniel Scally
2021-01-04 13:38       ` Andy Shevchenko
2021-01-04 13:56         ` Daniel Scally
2021-01-04 13:35   ` Kieran Bingham
2021-01-04 13:55     ` Daniel Scally [this message]
2021-01-04 14:12       ` Andy Shevchenko
2021-01-04 15:13       ` Kieran Bingham
2021-01-04 15:31         ` Daniel Scally
2021-01-04 16:13           ` Kieran Bingham
2021-01-04 22:02             ` Daniel Scally
2021-01-05  6:55               ` Kieran Bingham
2021-01-05  8:22                 ` Daniel Scally

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=9026519f-1f33-9df0-de18-0881069f7aaa@gmail.com \
    --to=djrscally@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bingbu.cao@intel.com \
    --cc=devel@acpica.org \
    --cc=erik.kaneda@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jacopo+renesas@jmondi.org \
    --cc=jorhand@linux.microsoft.com \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lenb@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=m.felsch@pengutronix.de \
    --cc=mchehab@kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=pmladek@suse.com \
    --cc=rjw@rjwysocki.net \
    --cc=robert.moore@intel.com \
    --cc=rostedt@goodmis.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=slongerbeam@gmail.com \
    --cc=tian.shu.qiu@intel.com \
    --cc=yong.zhi@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