linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robh@kernel.org (Rob Herring)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 1/4] dt-bindings: media: add Amlogic Video Decoder Bindings
Date: Mon, 3 Sep 2018 20:30:01 -0500	[thread overview]
Message-ID: <20180904012958.GA14387@bogus> (raw)
In-Reply-To: <20180831085205.14760-2-mjourdan@baylibre.com>

On Fri, Aug 31, 2018 at 10:52:02AM +0200, Maxime Jourdan wrote:
> Add documentation for the meson vdec dts node.
> 
> Signed-off-by: Maxime Jourdan <mjourdan@baylibre.com>
> ---
>  .../bindings/media/amlogic,vdec.txt           | 63 +++++++++++++++++++
>  1 file changed, 63 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/media/amlogic,vdec.txt
> 
> diff --git a/Documentation/devicetree/bindings/media/amlogic,vdec.txt b/Documentation/devicetree/bindings/media/amlogic,vdec.txt
> new file mode 100644
> index 000000000000..c6450f2e7f28
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/amlogic,vdec.txt
> @@ -0,0 +1,63 @@
> +Amlogic Video Decoder
> +================================
> +
> +The VDEC IP is composed of the following blocks :
> +
> +- ESPARSER is a bitstream parser that outputs to a VIFIFO. Further VDEC blocks
> +then feed from this VIFIFO.
> +- VDEC_1 can decode MPEG-1, MPEG-2, MPEG-4 part 2, H.263, H.264.
> +- VDEC_2 is used as a helper for corner cases like H.264 4K on older SoCs.
> +It is not handled by this driver.

Bindings should be complete, not a reflection of what a particular 
driver supports.

> +- VDEC_HCODEC is the H.264 encoding block. It is not handled by this driver.
> +- VDEC_HEVC can decode HEVC and VP9.
> +
> +Device Tree Bindings:
> +---------------------
> +
> +VDEC: Video Decoder
> +--------------------------
> +
> +Required properties:
> +- compatible: value should be different for each SoC family as :
> +	- GXBB (S905) : "amlogic,gxbb-vdec"
> +	- GXL (S905X, S905D) : "amlogic,gxl-vdec"
> +	- GXM (S912) : "amlogic,gxm-vdec"
> +- reg: base address and size of he following memory-mapped regions :
> +	- dos
> +	- esparser
> +- reg-names: should contain the names of the previous memory regions
> +- interrupts: should contain the vdec and esparser IRQs.
> +- amlogic,ao-sysctrl: should point to the AOBUS sysctrl node
> +- amlogic,canvas: should point to a canvas provider node
> +- clocks: should contain the following clocks :
> +	- dos_parser
> +	- dos
> +	- vdec_1
> +	- vdec_hevc
> +- clock-names: should contain the names of the previous clocks
> +- resets: should contain the parser reset.
> +- reset-names: should be "esparser".
> +
> +Example:
> +
> +vdec: video-decoder at c8820000 {
> +	compatible = "amlogic,gxbb-vdec";
> +	reg = <0x0 0xc8820000 0x0 0x10000>,
> +	      <0x0 0xc110a580 0x0 0xe4>;
> +	reg-names = "dos", "esparser";
> +
> +	interrupts = <GIC_SPI 44 IRQ_TYPE_EDGE_RISING>,
> +		     <GIC_SPI 32 IRQ_TYPE_EDGE_RISING>;
> +
> +	amlogic,ao-sysctrl = <&sysctrl_AO>;
> +	amlogic,canvas = <&canvas>;
> +
> +	clocks = <&clkc CLKID_DOS_PARSER>,
> +		 <&clkc CLKID_DOS>,
> +		 <&clkc CLKID_VDEC_1>,
> +		 <&clkc CLKID_VDEC_HEVC>;
> +	clock-names = "dos_parser", "dos", "vdec_1", "vdec_hevc";
> +
> +	resets = <&reset RESET_PARSER>;
> +	reset-names = "esparser";
> +};
> -- 
> 2.18.0
> 

  reply	other threads:[~2018-09-04  1:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31  8:52 [PATCH 0/4] Add Amlogic video decoder driver Maxime Jourdan
2018-08-31  8:52 ` [PATCH 1/4] dt-bindings: media: add Amlogic Video Decoder Bindings Maxime Jourdan
2018-09-04  1:30   ` Rob Herring [this message]
2018-08-31  8:52 ` [PATCH 2/4] media: meson: add v4l2 m2m video decoder driver Maxime Jourdan
2018-08-31 22:37   ` kbuild test robot
2018-09-03 11:18   ` Hans Verkuil
2018-09-03 12:04     ` Maxime Jourdan
2018-08-31  8:52 ` [PATCH 3/4] ARM64: dts: meson-gx: add vdec entry Maxime Jourdan
2018-08-31  8:52 ` [PATCH 4/4] ARM64: dts: meson: add vdec entries Maxime Jourdan
2018-08-31  9:00 ` [PATCH 0/4] Add Amlogic video decoder driver Hans Verkuil
2018-08-31  9:09   ` Maxime Jourdan

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=20180904012958.GA14387@bogus \
    --to=robh@kernel.org \
    --cc=linus-amlogic@lists.infradead.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).