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 v5 0/3] dt-bindings: media: ov772x: Convert to json-schema
Date: Thu, 10 Sep 2020 18:20:52 +0200 [thread overview]
Message-ID: <20200910162055.614089-1-jacopo+renesas@jmondi.org> (raw)
Convert the ov722x bindings to json-schema and add endpoint properties and
bus-type.
Compared to v4 in 2/3 I have not documented endpoint properties and deferred it
to a forthcoming of-graph.yaml by using 'unevaluatedProperties: false'
in the endpoint properties.
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 | 134 ++++++++++++++++++
MAINTAINERS | 2 +-
3 files changed, 135 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-10 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 16:20 Jacopo Mondi [this message]
2020-09-10 16:20 ` [PATCH v5 1/3] dt-bindings: media: ov772x: Convert to json-schema Jacopo Mondi
2020-09-15 20:10 ` Rob Herring
2020-09-10 16:20 ` [PATCH v5 2/3] dt-bindings: media: ov772x: Make bus-type mandatory Jacopo Mondi
2020-09-11 5:37 ` Sakari Ailus
2020-09-11 8:58 ` Jacopo Mondi
2020-09-11 8:59 ` Prabhakar Mahadev Lad
2020-09-11 9:23 ` Sakari Ailus
2020-09-11 9:46 ` Jacopo Mondi
2020-09-10 16:20 ` [PATCH v5 3/3] dt-bindings: media: ov772x: Document endpoint props Jacopo Mondi
2020-09-15 20:12 ` Rob Herring
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=20200910162055.614089-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.