From: Rob Herring <robh@kernel.org>
To: Maxime Ripard <maxime@cerno.tech>
Cc: linux-media@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Frank Rowand <frowand.list@gmail.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Steve Longerbeam <slongerbeam@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3] dt-bindings: media: Convert OV5640 binding to a schema
Date: Fri, 15 Oct 2021 17:07:49 -0500 [thread overview]
Message-ID: <YWn7tW6v6aooogJO@robh.at.kernel.org> (raw)
In-Reply-To: <20211015072830.8580-1-maxime@cerno.tech>
On Fri, 15 Oct 2021 09:28:30 +0200, Maxime Ripard wrote:
> The Omnivision OV5640 is supported by Linux thanks to its device tree
> binding.
>
> Now that we have the DT validation in place, let's convert the device
> tree bindings for that driver over to a YAML schema.
>
> Cc: linux-media@vger.kernel.org
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: Steve Longerbeam <slongerbeam@gmail.com>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
>
> ---
>
> Changes from v2:
> - Fix whitespace error
> - Changed schema referenced for the port validation
> ---
> .../devicetree/bindings/media/i2c/ov5640.txt | 92 -----------
> .../bindings/media/i2c/ovti,ov5640.yaml | 154 ++++++++++++++++++
> 2 files changed, 154 insertions(+), 92 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/media/i2c/ov5640.txt
> create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov5640.yaml
>
Applied, thanks!
prev parent reply other threads:[~2021-10-15 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 7:28 [PATCH v3] dt-bindings: media: Convert OV5640 binding to a schema Maxime Ripard
2021-10-15 13:53 ` Rob Herring
2021-10-15 14:18 ` Maxime Ripard
2021-10-15 22:07 ` Rob Herring [this message]
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=YWn7tW6v6aooogJO@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=slongerbeam@gmail.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).