From: Jammy Huang <jammy_huang@aspeedtech.com>
To: <robh@kernel.org>, <conor+dt@kernel.org>, <eajames@linux.ibm.com>,
<mchehab@kernel.org>, <joel@jms.id.au>, <andrew@aj.id.au>,
<hverkuil@xs4all.nl>, <pmenzel@molgen.mpg.de>,
<krzk+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-media@vger.kernel.org>,
<openbmc@lists.ozlabs.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v5 1/2] dt-bindings: arm: aspeed: Add aspeed,video binding
Date: Mon, 19 Aug 2024 16:08:58 +0800 [thread overview]
Message-ID: <20240819080859.1304671-2-jammy_huang@aspeedtech.com> (raw)
In-Reply-To: <20240819080859.1304671-1-jammy_huang@aspeedtech.com>
The Video Engine block in ASPEED Silicon SoCs is responsible for video
compressions with a wide range of video quality and compression
ratio options. It can capture and compress video data from digital or
analog sources.
Signed-off-by: Jammy Huang <jammy_huang@aspeedtech.com>
---
.../bindings/arm/aspeed/aspeed,video.yaml | 81 +++++++++++++++++++
1 file changed, 81 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/aspeed/aspeed,video.yaml
diff --git a/Documentation/devicetree/bindings/arm/aspeed/aspeed,video.yaml b/Documentation/devicetree/bindings/arm/aspeed/aspeed,video.yaml
new file mode 100644
index 000000000000..bef7bd2f310a
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/aspeed/aspeed,video.yaml
@@ -0,0 +1,81 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/arm/aspeed/aspeed,video.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: ASPEED Video Engine
+
+maintainers:
+ - Eddie James <eajames@linux.ibm.com>
+ - Jammy Huang <jammy_huang@aspeedtech.com>
+
+description: |
+ The ASPEED video engine can be configured to capture and compress video
+ data from digital or analog sources.
+
+select:
+ properties:
+ compatible:
+ pattern: "^aspeed,ast[0-9]+-video-engine$"
+ required:
+ - compatible
+
+properties:
+ compatible:
+ oneOf:
+ - description: Preferred naming style for compatibles of video components
+ pattern: "^aspeed,ast[0-9]+-video-engine$"
+
+ - enum:
+ - aspeed,ast2400-video-engine
+ - aspeed,ast2500-video-engine
+ - aspeed,ast2600-video-engine
+
+ reg:
+ minItems: 1
+
+ clocks:
+ minItems: 2
+
+ clock-names:
+ items:
+ - const: vclk
+ - const: eclk
+
+ interrupts:
+ minItems: 1
+
+ aspeed,scu:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description: |
+ Specifies the scu node that is needed if video wants to capture
+ from sources other than Host VGA.
+
+ aspeed,gfx:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description: |
+ Specifies the Soc Display(gfx) node that needs to be queried to get
+ related information if video wants to use gfx as capture source.
+
+required:
+ - compatible
+ - reg
+ - clocks
+ - clock-names
+ - interrupts
+
+additionalProperties: true
+
+examples:
+ - |
+ video: video@1e700000 {
+ compatible = "aspeed,ast2600-video-engine";
+ reg = <0x1e700000 0x1000>;
+ clocks = <&syscon ASPEED_CLK_GATE_VCLK>,
+ <&syscon ASPEED_CLK_GATE_ECLK>;
+ clock-names = "vclk", "eclk";
+ interrupts = <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>;
+ aspeed,scu = <&syscon>;
+ aspeed,gfx = <&gfx>;
+ };
--
2.25.1
next prev parent reply other threads:[~2024-08-19 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 8:08 [PATCH v5 0/2] media: aspeed: Allow to capture from SoC display (GFX) Jammy Huang
2024-08-19 8:08 ` Jammy Huang [this message]
2024-08-19 8:24 ` [PATCH v5 1/2] dt-bindings: arm: aspeed: Add aspeed,video binding Krzysztof Kozlowski
2024-08-23 1:11 ` Jammy Huang
2024-08-23 6:13 ` Krzysztof Kozlowski
2024-08-28 6:05 ` Jammy Huang
2024-08-28 9:10 ` Krzysztof Kozlowski
2024-08-19 8:08 ` [PATCH v5 2/2] media: aspeed: Allow to capture from SoC display (GFX) Jammy Huang
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=20240819080859.1304671-2-jammy_huang@aspeedtech.com \
--to=jammy_huang@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=hverkuil@xs4all.nl \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®