From: Jacopo Mondi <jacopo+renesas@jmondi.org>
To: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org, "Lad,
Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
hverkuil-cisco@xs4all.nl, laurent.pinchart@ideasonboard.com,
linux-renesas-soc@vger.kernel.org
Subject: [PATCH v4 0/3] dt-bindings: media: ov772x: Convert to json-schema
Date: Thu, 3 Sep 2020 15:10:26 +0200 [thread overview]
Message-ID: <20200903131029.18334-1-jacopo+renesas@jmondi.org> (raw)
Convert the ov722x bindings to json-schema and add endpoint properties and
bus-type.
Compared to v3 in 1/3 I have not documented 'endpoint'
Then 2/3 introduces the 'bus-type' endpoint properties, so I had to document
'endpoint' and list 'remote-endpoint' as required (which makes me think I
could have kept it in 1/3, but for sake of consistency...)
3/3 adds endpoint properties, whose presence is conditional to the specified
bus-type.
Thanks
j
Jacopo Mondi (3):
dt-bindings: media: ov772x: Convert to json-schema
dt-bindings: media: ov772x: Make bus-type mandatory
dt-bindings: media: ov772x: Document endpoint props
.../devicetree/bindings/media/i2c/ov772x.txt | 40 -----
.../bindings/media/i2c/ovti,ov772x.yaml | 138 ++++++++++++++++++
MAINTAINERS | 2 +-
3 files changed, 139 insertions(+), 41 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/media/i2c/ov772x.txt
create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov772x.yaml
--
2.28.0
next reply other threads:[~2020-09-03 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 13:10 Jacopo Mondi [this message]
2020-09-03 13:10 ` [PATCH v4 1/3] dt-bindings: media: ov772x: Convert to json-schema Jacopo Mondi
2020-09-03 13:10 ` [PATCH v4 2/3] dt-bindings: media: ov772x: Make bus-type mandatory Jacopo Mondi
2020-09-04 8:05 ` Jacopo Mondi
2020-09-04 15:06 ` Laurent Pinchart
2020-09-04 15:16 ` Jacopo Mondi
2020-09-03 13:10 ` [PATCH v4 3/3] dt-bindings: media: ov772x: Document endpoint props Jacopo Mondi
2020-09-03 21:33 ` Laurent Pinchart
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=20200903131029.18334-1-jacopo+renesas@jmondi.org \
--to=jacopo+renesas@jmondi.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.