From: Rob Herring <robh@kernel.org>
To: Jernej Skrabec <jernej.skrabec@siol.net>
Cc: maxime.ripard@bootlin.com, wens@csie.org, mchehab@kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH 1/6] dt-bindings: media: cedrus: Add H6 compatible
Date: Mon, 25 Feb 2019 08:27:17 -0600 [thread overview]
Message-ID: <20190225142717.GA27983@bogus> (raw)
In-Reply-To: <20190128205504.11225-2-jernej.skrabec@siol.net>
On Mon, 28 Jan 2019 21:54:59 +0100, Jernej Skrabec wrote:
> This adds a compatible for H6. H6 VPU supports 10-bit HEVC decoding and
> additional AFBC output format for HEVC.
>
> Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
> ---
> Documentation/devicetree/bindings/media/cedrus.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-02-25 14:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 20:54 [PATCH 0/6] H6 Cedrus support Jernej Skrabec
2019-01-28 20:54 ` [PATCH 1/6] dt-bindings: media: cedrus: Add H6 compatible Jernej Skrabec
2019-01-29 9:07 ` Maxime Ripard
2019-02-25 14:27 ` Rob Herring [this message]
2019-01-28 20:55 ` [PATCH 2/6] media: cedrus: Add a quirk for not setting DMA offset Jernej Skrabec
2019-01-29 9:07 ` Maxime Ripard
2019-01-28 20:55 ` [PATCH 3/6] media: cedrus: Add support for H6 Jernej Skrabec
2019-01-29 9:08 ` Maxime Ripard
2019-01-28 20:55 ` [PATCH 4/6] dt-bindings: sram: sunxi: Add compatible for the H6 SRAM C1 Jernej Skrabec
2019-01-29 9:08 ` Maxime Ripard
2019-01-28 20:55 ` [PATCH 5/6] arm64: dts: allwinner: h6: Add support for the SRAM C1 section Jernej Skrabec
2019-01-29 9:08 ` Maxime Ripard
2019-01-28 20:55 ` [PATCH 6/6] arm64: dts: allwinner: h6: Add Video Engine node Jernej Skrabec
2019-03-19 8:50 ` [linux-sunxi] " Paul Kocialkowski
2019-03-19 9:49 ` Maxime Ripard
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=20190225142717.GA27983@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).