From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 5/6] ACPI: scan: Extract MIPI DiSco for Imaging data into swnodes
Date: Tue, 31 Oct 2023 14:00:15 +0000 [thread overview]
Message-ID: <ZUEIb81Bbzgvf2Uf@kekkonen.localdomain> (raw)
In-Reply-To: <CAJZ5v0j_Uv=qVo6eFdz-Q7Ne7W7aTf9ThN128Ust+YEQQ9Gy+Q@mail.gmail.com>
Hi Rafael,
On Tue, Oct 31, 2023 at 02:46:51PM +0100, Rafael J. Wysocki wrote:
> Hi Sakari,
>
> On Tue, Oct 31, 2023 at 11:33 AM Sakari Ailus
> <sakari.ailus@linux.intel.com> wrote:
> >
> > Hi Rafael,
> >
> > On subject:
> >
> > s/DiSco/DisCo/
>
> Huh
>
> Thanks for catching this!
>
> > On Fri, Oct 20, 2023 at 04:39:27PM +0200, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > >
> > > Add information extracted from the MIPI DiSco for Imaging device
> >
> > Ditto.
> >
> > > properties to software nodes created during the CSI-2 connection graph
> > > discovery.
> > >
> > > Link: https://www.mipi.org/specifications/mipi-di
> >
> > This URL is broken. The correct URL is:
> >
> > https://www.mipi.org/specifications/mipi-disco-imaging
>
> OK
>
> > > Co-developed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > ---
> > > drivers/acpi/internal.h | 1
> > > drivers/acpi/mipi-di.c | 240 +++++++++++++++++++++++++++++++++++++++++++++++-
> >
> > How about mipi-disco.c? I wouldn't mind having mipi-disco-imaging.c either.
>
> Well, mipi-disco-imaging is a bit too long and the meaning of
> mipi-disco would not be clear IMO.
>
> What about mipi-disco-img?
Seems fine to me.
>
> [cut]
>
> > > + ret = fwnode_property_count_u8(port_fwnode, "mipi-img-lane-polarities");
> > > + if (ret > 0) {
> > > + unsigned long mask;
> > > + unsigned int i;
> > > +
> > > + /*
> > > + * Total number of lanes here is clock lane + data lanes.
> > > + * Require that number to be low enough so they all can be
> > > + * covered by the bits in one byte.
> > > + */
> > > + BUILD_BUG_ON(BITS_PER_TYPE(u8) <= ARRAY_SIZE(port->data_lanes));
> > > +
> > > + fwnode_property_read_u8_array(port_fwnode,
> > > + "mipi-img-lane-polarities",
> > > + val, 1);
> > > +
> > > + for (mask = val[0], i = 0; i < num_lanes + 1; i++)
> > > + port->lane_polarities[i] = test_bit(i, &mask);
> >
> > This works only up to seven lanes.
>
> True, but then ACPI_DEVICE_CSI2_DATA_LANES is defined as 4.
The spec has no limit and in practice 4 is relatively common while 8 exists
(but is somewhat rare). I actually think it'd be a good idea to bump this
to 8 already.
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2023-10-31 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 14:33 [PATCH v2 0/6] ACPI: scan: MIPI DiSco for Imaging support Rafael J. Wysocki
2023-10-20 14:35 ` [PATCH v2 1/6] ACPI: property: Support using strings in reference properties Rafael J. Wysocki
2023-10-20 14:36 ` [PATCH v2 2/6] ACPI: scan: Extract CSI-2 connection graph from _CRS Rafael J. Wysocki
2023-10-31 8:47 ` Sakari Ailus
2023-10-31 13:36 ` Rafael J. Wysocki
2023-10-20 14:37 ` [PATCH v2 3/6] ACPI: scan: Extract _CRS CSI-2 connection information into swnodes Rafael J. Wysocki
2023-10-20 14:38 ` [PATCH v2 4/6] device property: Add SOFTWARE_NODE() macro for defining software nodes Rafael J. Wysocki
2023-10-20 14:39 ` [PATCH v2 5/6] ACPI: scan: Extract MIPI DiSco for Imaging data into swnodes Rafael J. Wysocki
2023-10-31 8:58 ` Sakari Ailus
2023-10-31 13:46 ` Rafael J. Wysocki
2023-10-31 14:00 ` Sakari Ailus [this message]
2023-10-31 15:19 ` Rafael J. Wysocki
2023-10-20 14:40 ` [PATCH v2 6/6] ACPI: property: Dig "rotation" property for devices with CSI2 _CRS Rafael J. Wysocki
2023-10-31 8:45 ` [PATCH v2 0/6] ACPI: scan: MIPI DiSco for Imaging support Sakari Ailus
2023-10-31 13:21 ` Rafael J. Wysocki
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=ZUEIb81Bbzgvf2Uf@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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