From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/3] dw-hdmi: add property to disable CEC
Date: Mon, 19 Mar 2018 14:10:50 +0100 [thread overview]
Message-ID: <0d341d4b-64f4-2d6e-555c-43136e74807e@baylibre.com> (raw)
In-Reply-To: <20180319114345.29837-1-hverkuil@xs4all.nl>
Hi Hans,
On 19/03/2018 12:43, Hans Verkuil wrote:
> From: Hans Verkuil <hans.verkuil@cisco.com>
>
> Some boards (amlogic) have two CEC controllers: the DesignWare controller
> and their own CEC controller (meson ao-cec).
>
> Since the CEC line is not hooked up to the DW controller we need a way
> to disable that controller. This patch series adds the cec-disable
> property for that purpose.
>
> Neil, I have added cec-disable to meson-gxl-s905x-libretech-cc.dts
> only, but I suspect it is probably valid for all meson-glx devices?
> Should I move it to meson-gxl.dtsi?
It's valid on all GX devices, so you can add to meson-gx.dtsi
Neil
>
> Regards,
>
> Hans
>
> Hans Verkuil (3):
> dt-bindings: display: dw_hdmi.txt
> drm: bridge: dw-hdmi: check the cec-disable property
> arm64: dts: meson-gxl-s905x-libretech-cc: add cec-disable
>
> Documentation/devicetree/bindings/display/bridge/dw_hdmi.txt | 3 +++
> arch/arm64/boot/dts/amlogic/meson-gxl-s905x-libretech-cc.dts | 1 +
> drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 3 ++-
> 3 files changed, 6 insertions(+), 1 deletion(-)
>
prev parent reply other threads:[~2018-03-19 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 11:43 Hans Verkuil
2018-03-19 11:43 ` [PATCH 1/3] dt-bindings: display: dw_hdmi.txt Hans Verkuil
2018-03-19 11:46 ` Fabio Estevam
2018-03-19 11:48 ` Hans Verkuil
2018-03-19 13:11 ` Neil Armstrong
2018-03-19 11:43 ` [PATCH 2/3] drm: bridge: dw-hdmi: check the cec-disable property Hans Verkuil
2018-03-19 13:11 ` Neil Armstrong
2018-03-19 11:43 ` [PATCH 3/3] arm64: dts: meson-gxl-s905x-libretech-cc: add cec-disable Hans Verkuil
2018-03-19 13:11 ` Neil Armstrong
2018-03-19 13:10 ` Neil Armstrong [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=0d341d4b-64f4-2d6e-555c-43136e74807e@baylibre.com \
--to=narmstrong@baylibre.com \
--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®