From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jammy Huang <jammy_huang@aspeedtech.com>,
eajames@linux.ibm.com, mchehab@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, joel@jms.id.au,
andrew@aj.id.au, linux-media@vger.kernel.org,
openbmc@lists.ozlabs.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media: dt-bindings: aspeed,video-engine: Convert to json schema
Date: Tue, 4 Feb 2025 11:46:57 +0100 [thread overview]
Message-ID: <d705e66d-8a5c-490b-b277-f29429c207dd@kernel.org> (raw)
In-Reply-To: <20250204085041.3724290-1-jammy_huang@aspeedtech.com>
On 04/02/2025 09:50, Jammy Huang wrote:
> Convert aspeed-video.txt to yaml format.
> Update aspeed-video.txt to aspeed,video-engine.yaml in MAINTAINER file.
>
> NOTE: The following checkpatch warning is generated since we do include
> the header in the example, but this is a false positive warning.
> WARNING: DT binding docs and includes should be a separate patch. See: Documentation/devicetree/bindings/submitting-patches.rst
This does not belong to commit message, it's irrelevant. You can mention
in the changelog, though, but IMO, that's really not important for this
patch.
>
> Signed-off-by: Jammy Huang <jammy_huang@aspeedtech.com>
> ---
> v2:
> - Update commit subject
> - Add NOTE for false positive warning
> ---
...
> +
> + memory-region:
> + maxItems: 1
> + description: |
> + Phandle to the reserved memory nodes to be associated with the
> + VE. VE will acquires memory space for 3 purposes:
> + 1. JPEG header
> + 2. Compressed result
> + 3. Temporary transformed image data
> +
> + aspeed,scu:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description: |
Do not need '|' unless you need to preserve formatting.
> + 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
None of these two properties were in original binding with
*justification*. You must describe any changes done during conversion,
otherwise you could add here whatever property you wish, right?
> + 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: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/clock/ast2600-clock.h>
> +
> + video@1e700000 {
Looks rather like: isp@
> + 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>;
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-04 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 8:50 [PATCH v2] media: dt-bindings: aspeed,video-engine: Convert to json schema Jammy Huang
2025-02-04 10:46 ` Krzysztof Kozlowski [this message]
2025-02-05 1:13 ` 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=d705e66d-8a5c-490b-b277-f29429c207dd@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@aj.id.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=jammy_huang@aspeedtech.com \
--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=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;
as well as URLs for NNTP newsgroup(s).