devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Russell King <rmk+kernel@armlinux.org.uk>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, Rob Herring <robh+dt@kernel.org>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v3 7/7] dt-bindings: tda998x: add the calibration gpio
Date: Tue, 24 Apr 2018 11:27:47 +0200	[thread overview]
Message-ID: <201abf9a-74b0-f8db-0950-403f251b15d6@xs4all.nl> (raw)
In-Reply-To: <E1f5Vj1-0002Lx-Hz@rmk-PC.armlinux.org.uk>

On 04/09/18 14:16, Russell King wrote:
> Add the optional calibration gpio for integrated TDA9950 CEC support.
> This GPIO corresponds with the interrupt from the TDA998x, as the
> calibration requires driving the interrupt pin low.
> 
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>

Acked-by: Hans Verkuil <hans.verkuil@cisco.com>

Regards,

	Hans

> ---
>  Documentation/devicetree/bindings/display/bridge/tda998x.txt | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/display/bridge/tda998x.txt b/Documentation/devicetree/bindings/display/bridge/tda998x.txt
> index 24cc2466185a..1a4eaca40d94 100644
> --- a/Documentation/devicetree/bindings/display/bridge/tda998x.txt
> +++ b/Documentation/devicetree/bindings/display/bridge/tda998x.txt
> @@ -27,6 +27,9 @@ Required properties;
>  	in question is used. The implementation allows one or two DAIs. If two
>  	DAIs are defined, they must be of different type.
>  
> +  - nxp,calib-gpios: calibration GPIO, which must correspond with the
> +	gpio used for the TDA998x interrupt pin.
> +
>  [1] Documentation/sound/alsa/soc/DAI.txt
>  [2] include/dt-bindings/display/tda998x.h
>  
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2018-04-24  9:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180409121529.GA31403@n2100.armlinux.org.uk>
2018-04-09 12:16 ` [PATCH v3 1/7] drm/i2c: tda998x: move mutex/waitqueue/timer/work init early Russell King
2018-04-09 12:16 ` [PATCH v3 2/7] drm/i2c: tda998x: fix error cleanup paths Russell King
2018-04-09 12:16 ` [PATCH v3 3/7] drm/i2c: tda998x: move CEC device initialisation later Russell King
2018-04-09 12:16 ` [PATCH v3 4/7] drm/i2c: tda998x: always disable and clear interrupts at probe Russell King
2018-04-09 12:16 ` [PATCH v3 5/7] drm/i2c: tda9950: add CEC driver Russell King
2018-04-20 15:31   ` Russell King - ARM Linux
2018-04-20 15:48     ` Hans Verkuil
2018-04-20 16:07       ` Russell King - ARM Linux
2018-04-24  9:27   ` Hans Verkuil
2018-04-09 12:16 ` [PATCH v3 6/7] drm/i2c: tda998x: add CEC support Russell King
2018-04-24  9:27   ` Hans Verkuil
2018-04-09 12:16 ` [PATCH v3 7/7] dt-bindings: tda998x: add the calibration gpio Russell King
2018-04-24  9:27   ` Hans Verkuil [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=201abf9a-74b0-f8db-0950-403f251b15d6@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=airlied@linux.ie \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=robh+dt@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).