From: robh@kernel.org (Rob Herring)
To: linus-amlogic@lists.infradead.org
Subject: [PATCHv2 1/3] dt-bindings: display: dw_hdmi.txt: add cec-disable property
Date: Mon, 26 Mar 2018 17:25:02 -0500 [thread overview]
Message-ID: <20180326072830.iphtbw5mkeciv4kj@rob-hp-laptop> (raw)
In-Reply-To: <20180323125915.13986-2-hverkuil@xs4all.nl>
On Fri, Mar 23, 2018 at 01:59:13PM +0100, Hans Verkuil wrote:
> From: Hans Verkuil <hans.verkuil@cisco.com>
>
> Some boards have both a DesignWare and their own CEC controller.
> The CEC pin is only hooked up to their own CEC controller and not
> to the DW controller.
>
> Add the cec-disable property to disable the DW CEC controller.
>
> This particular situation happens on Amlogic boards that have their
> own meson CEC controller.
Seems like we could avoid this by describing how the CEC line is hooked
up which could be needed for other reasons.
>
> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> Acked-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
> Documentation/devicetree/bindings/display/bridge/dw_hdmi.txt | 3 +++
> 1 file changed, 3 insertions(+)
next prev parent reply other threads:[~2018-03-26 22:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 12:59 [PATCHv2 0/3] dw-hdmi: add property to disable CEC Hans Verkuil
2018-03-23 12:59 ` [PATCHv2 1/3] dt-bindings: display: dw_hdmi.txt: add cec-disable property Hans Verkuil
2018-03-26 22:25 ` Rob Herring [this message]
2018-04-03 8:27 ` Hans Verkuil
2018-06-29 7:17 ` Neil Armstrong
2018-07-02 9:02 ` Hans Verkuil
2018-03-23 12:59 ` [PATCHv2 2/3] drm: bridge: dw-hdmi: check the " Hans Verkuil
2018-03-23 12:59 ` [PATCHv2 3/3] arm64: dts: meson-gx.dtsi: add cec-disable Hans Verkuil
2018-03-24 11:00 ` [PATCHv2 0/3] dw-hdmi: add property to disable CEC Martin Blumenstingl
2018-03-24 13:41 ` Neil Armstrong
2018-03-24 14:25 ` Martin Blumenstingl
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=20180326072830.iphtbw5mkeciv4kj@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linus-amlogic@lists.infradead.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®