From: Conor Dooley <conor@kernel.org>
To: Jammy Huang <jammy_huang@aspeedtech.com>
Cc: 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] dt-bindings: media: convert aspeed-video.txt to dt-schema
Date: Tue, 4 Feb 2025 19:30:53 +0000 [thread overview]
Message-ID: <20250204-from-catsup-132a4af05f49@spud> (raw)
In-Reply-To: <20250204-acronym-unshaved-18b89a389091@spud>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
On Tue, Feb 04, 2025 at 07:30:03PM +0000, Conor Dooley wrote:
> On Tue, Feb 04, 2025 at 02:28:22PM +0800, Jammy Huang wrote:
> > + 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.
>
> These two phandle properties are new and not mentioned in your commit
> message. Why have they been added?
nvm, I see Krzysztof has already responded to the v2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-02-04 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 6:28 [PATCH] dt-bindings: media: convert aspeed-video.txt to dt-schema Jammy Huang
2025-02-04 19:30 ` Conor Dooley
2025-02-04 19:30 ` Conor Dooley [this message]
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=20250204-from-catsup-132a4af05f49@spud \
--to=conor@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).