From: Rob Herring <robh@kernel.org>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
kernel@pengutronix.de, robh+dt@kernel.org, mchehab@kernel.org,
tfiga@chromium.org, dshah@xilinx.com
Subject: Re: [PATCH v3 1/3] media: dt-bindings: media: document allegro-dvt bindings
Date: Mon, 18 Feb 2019 12:12:30 -0600 [thread overview]
Message-ID: <20190218181230.GA13153@bogus> (raw)
In-Reply-To: <20190213175124.3695-2-m.tretter@pengutronix.de>
On Wed, 13 Feb 2019 18:51:22 +0100, Michael Tretter wrote:
> Add device-tree bindings for the Allegro DVT video IP core found on the
> Xilinx ZynqMP EV family.
>
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> ---
> v2 -> v3:
> - rename node to video-codec
> - drop interrupt-names
> - fix compatible in example
> - add clocks to required properties
>
> v1 -> v2:
> none
> ---
> .../devicetree/bindings/media/allegro.txt | 43 +++++++++++++++++++
> 1 file changed, 43 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/allegro.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-02-18 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 17:51 [PATCH v3 0/3] Add ZynqMP VCU/Allegro DVT H.264 encoder driver Michael Tretter
2019-02-13 17:51 ` [PATCH v3 1/3] media: dt-bindings: media: document allegro-dvt bindings Michael Tretter
2019-02-18 18:12 ` Rob Herring [this message]
2019-02-13 17:51 ` [PATCH v3 2/3] [media] allegro: add Allegro DVT video IP core driver Michael Tretter
2019-02-14 11:15 ` kbuild test robot
2019-02-24 20:01 ` kbuild test robot
2019-02-25 11:10 ` Hans Verkuil
2019-02-13 17:51 ` [PATCH v3 3/3] [media] allegro: add SPS/PPS nal unit writer Michael Tretter
2019-02-25 11:13 ` Hans Verkuil
2019-02-13 17:54 ` [PATCH v3 0/3] Add ZynqMP VCU/Allegro DVT H.264 encoder driver Michael Tretter
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=20190218181230.GA13153@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dshah@xilinx.com \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tfiga@chromium.org \
/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).