From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Naushir Patuck <naush@raspberrypi.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [PATCH v2 2/4] dt-bindings: media: Add bindings for raspberrypi,rp1-cfe
Date: Wed, 28 Aug 2024 12:30:21 +0000 [thread overview]
Message-ID: <Zs8YXVQ4armJJN4X@kekkonen.localdomain> (raw)
In-Reply-To: <b3fe348b-60a3-4480-8a8e-89760c5bb7ae@ideasonboard.com>
Heippa,
On Wed, Aug 28, 2024 at 03:14:47PM +0300, Tomi Valkeinen wrote:
> Hi,
>
> On 28/08/2024 14:12, Laurent Pinchart wrote:
> > On Wed, Aug 28, 2024 at 11:06:23AM +0000, Sakari Ailus wrote:
> > > On Thu, Jun 20, 2024 at 02:07:51PM +0300, Tomi Valkeinen wrote:
> > > > Add DT bindings for raspberrypi,rp1-cfe.
> > > >
> > > > Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
> > > > ---
> > > > .../bindings/media/raspberrypi,rp1-cfe.yaml | 98 ++++++++++++++++++++++
> > > > 1 file changed, 98 insertions(+)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/media/raspberrypi,rp1-cfe.yaml b/Documentation/devicetree/bindings/media/raspberrypi,rp1-cfe.yaml
> > > > new file mode 100644
> > > > index 000000000000..851533de2305
> > > > --- /dev/null
> > > > +++ b/Documentation/devicetree/bindings/media/raspberrypi,rp1-cfe.yaml
> > > > @@ -0,0 +1,98 @@
> > > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > > +%YAML 1.2
> > > > +---
> > > > +$id: http://devicetree.org/schemas/media/raspberrypi,rp1-cfe.yaml#
> > > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > > +
> > > > +title: Raspberry Pi PiSP Camera Front End
> > > > +
> > > > +maintainers:
> > > > + - Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
> > > > + - Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>
> > > > +
> > > > +description: |
> > > > + The Raspberry Pi PiSP Camera Front End is a module in Raspberrypi 5's RP1 I/O
> > > > + controller, that contains:
> > > > + - MIPI D-PHY
> > > > + - MIPI CSI-2 receiver
> > > > + - Simple image processor (called PiSP Front End, or FE)
> > > > +
> > > > + The FE documentation is available at:
> > > > + https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf
> > > > +
> > > > + The PHY and CSI-2 receiver part have no public documentation.
> > > > +
> > > > +properties:
> > > > + compatible:
> > > > + items:
> > > > + - const: raspberrypi,rp1-cfe
> > > > +
> > > > + reg:
> > > > + items:
> > > > + - description: CSI-2 registers
> > > > + - description: D-PHY registers
> > > > + - description: MIPI CFG (a simple top-level mux) registers
> > > > + - description: FE registers
> > > > +
> > > > + interrupts:
> > > > + maxItems: 1
> > > > +
> > > > + clocks:
> > > > + maxItems: 1
> > > > +
> > > > + port:
> > > > + $ref: /schemas/graph.yaml#/$defs/port-base
> > > > + additionalProperties: false
> > > > + description: CSI-2 RX Port
> > > > +
> > > > + properties:
> > > > + endpoint:
> > > > + $ref: video-interfaces.yaml#
> > > > + unevaluatedProperties: false
> > > > +
> > > > + properties:
> > > > + data-lanes:
> > > > + minItems: 1
> > > > + maxItems: 4
> > > > +
> > > > + clock-lanes:
> > > > + maxItems: 1
> > >
> > > minItems needs to be 1 as well.
>
> Hmm, I see a lot of
>
> clock-lanes:
> maxItems: 1
>
> in the device tree bindings. And
> https://docs.kernel.org/devicetree/bindings/writing-schema.html says "Cases
> that have only a single entry just need to express that with maxItems".
Fair enough.
>
> > >
> > > Or... is this actually configurable in hardware?
> >
> > Looking at the driver, lane reordering is not supported, so we could
> > drop this property. If the hardware is found to support it later, it can
> > easily be added back without any backward compatibility issue.
>
> Re-ordering is not supported. I guess clock-lanes can be dropped, although I
> feel that if we have the clock lane in the hardware, and the numbering of
> data-lanes must take that into account, then:
>
> clock-lanes = <0>;
> data-lanes = <1 2>;
>
> looks better than:
>
> data-lanes = <1 2>; /* and implicit clk lane 0 */
>
> But I can't think of any practical benefit it brings...
The clock-lanes property is optional, it only provides any information if
the clock lane is configurable. Please drop it.
--
Terveisin,
Sakari Ailus
next prev parent reply other threads:[~2024-08-28 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 11:07 [PATCH v2 0/4] media: raspberrypi: Support RPi5's CFE Tomi Valkeinen
2024-06-20 11:07 ` [PATCH v2 1/4] media: uapi: Add meta formats for PiSP FE config and stats Tomi Valkeinen
2024-06-20 11:07 ` [PATCH v2 2/4] dt-bindings: media: Add bindings for raspberrypi,rp1-cfe Tomi Valkeinen
2024-06-20 15:41 ` Krzysztof Kozlowski
2024-08-28 11:06 ` Sakari Ailus
2024-08-28 11:12 ` Laurent Pinchart
2024-08-28 12:14 ` Tomi Valkeinen
2024-08-28 12:30 ` Sakari Ailus [this message]
2024-08-28 12:53 ` Laurent Pinchart
2024-06-20 11:07 ` [PATCH v2 3/4] media: raspberrypi: Add support for RP1-CFE Tomi Valkeinen
2024-06-20 16:23 ` Laurent Pinchart
2024-06-20 11:07 ` [PATCH v2 4/4] media: admin-guide: Document the Raspberry Pi CFE (rp1-cfe) Tomi Valkeinen
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=Zs8YXVQ4armJJN4X@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kernel-list@raspberrypi.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=naush@raspberrypi.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tomi.valkeinen@ideasonboard.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
all inboxes | Powered by JetHome®