From: Rob Herring <robh@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: hverkuil-cisco@xs4all.nl, mchehab@kernel.org, lars@metafoo.de,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH] media: dt-bindings: adv7180: Document the 'interrupts' property
Date: Fri, 10 Jan 2025 10:09:26 -0600 [thread overview]
Message-ID: <20250110160926.GA2966032-robh@kernel.org> (raw)
In-Reply-To: <20250109000503.45264-1-festevam@gmail.com>
On Wed, Jan 08, 2025 at 09:05:03PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> The ADV7180 family of chips have an INTRQ pin that can be connected
> to a SoC GPIO.
>
> Allow the 'interrupts' property to be described to fix the following
> dt-schema warning:
>
> camera@21: 'interrupt-parent', 'interrupts' do not match any of the regexes: 'pinctrl-[0-9]+'
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
> Documentation/devicetree/bindings/media/i2c/adv7180.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/adv7180.yaml b/Documentation/devicetree/bindings/media/i2c/adv7180.yaml
> index 4371a0ef2761..572f06d12a39 100644
> --- a/Documentation/devicetree/bindings/media/i2c/adv7180.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/adv7180.yaml
> @@ -49,6 +49,8 @@ properties:
> Indicates that the output is a BT.656-4 compatible stream.
> type: boolean
>
> + interrupts: true
> +
How many interrupts are there?
> port:
> $ref: /schemas/graph.yaml#/$defs/port-base
> unevaluatedProperties: false
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-01-10 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 0:05 [PATCH] media: dt-bindings: adv7180: Document the 'interrupts' property Fabio Estevam
2025-01-10 16:09 ` Rob Herring [this message]
2025-01-10 18:51 ` Fabio Estevam
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=20250110160926.GA2966032-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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).