From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: David Plowman <david.plowman@raspberrypi.com>,
Naushir Patuck <naush@raspberrypi.com>,
Nick Hollinghurst <nick.hollinghurst@raspberrypi.org>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 6/8] media: dt-bindings: Add bindings for Raspberry Pi PiSP Back End
Date: Mon, 12 Feb 2024 09:12:11 +0100 [thread overview]
Message-ID: <7f7979af-8eda-48cd-a334-bb64ddf5b9b8@linaro.org> (raw)
In-Reply-To: <20240209164825.166800-7-jacopo.mondi@ideasonboard.com>
On 09/02/2024 17:48, Jacopo Mondi wrote:
> Add bindings for the Raspberry Pi PiSP Back End memory-to-memory image
> signal processor.
>
> Datasheet:
> https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf
>
> +---
> +$id: http://devicetree.org/schemas/media/raspberrypi,pispbe.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Raspberry Pi PiSP Image Signal Processor (ISP) Back End
> +
> +maintainers:
> + - Dave Stevenson <dave.stevenson@raspberrypi.com>
> + - David Plowman <david.plowman@raspberrypi.com>
> + - Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> + - Naushir Patuck <naush@raspberrypi.com>
> + - Nick Hollinghurst <nick.hollinghurst@raspberrypi.com>
I assume all folks are fine being here?
> +
> +description: |
> + The Raspberry Pi PiSP Image Signal Processor (ISP) Back End is an image
> + processor that fetches images in Bayer or Grayscale format from DRAM memory
> + in tiles and produces images consumable by applications.
> +
> + The full ISP documentation is available at:
> + https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf
> +
> +properties:
> + compatible:
> + const: raspberrypi,pispbe
Nothing more specific? No model name, no version? It's quite generic
compatible which in general should not be allowed. I would assume that
at least version of Pi could denote some sort of a model... unless
version is detectable?
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + const: isp_be
You can skip clock-names if they have only one entry and it matches
block name. Quite useless.
> +
> + iommus:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + rpi1 {
soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + isp: pisp_be@880000 {
Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
so: isp@
and drop unused label
> + compatible = "raspberrypi,pispbe";
ds,
Krzysztof
next prev parent reply other threads:[~2024-02-12 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240209164825.166800-1-jacopo.mondi@ideasonboard.com>
2024-02-09 16:48 ` [PATCH 6/8] media: dt-bindings: Add bindings for Raspberry Pi PiSP Back End Jacopo Mondi
2024-02-12 8:12 ` Krzysztof Kozlowski [this message]
2024-02-12 8:50 ` Jacopo Mondi
2024-02-12 9:05 ` Krzysztof Kozlowski
2024-02-13 7:28 ` Tomi Valkeinen
2024-02-13 7:57 ` Jacopo Mondi
2024-02-13 8:35 ` Naushir Patuck
2024-02-13 10:44 ` Laurent Pinchart
2024-02-13 18:42 ` Conor Dooley
2024-02-15 14:00 ` Rob Herring
2024-02-12 8:57 ` Naushir Patuck
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=7f7979af-8eda-48cd-a334-bb64ddf5b9b8@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=david.plowman@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=naush@raspberrypi.com \
--cc=nick.hollinghurst@raspberrypi.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
--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;
as well as URLs for NNTP newsgroup(s).