From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCHv2 1/3] dt-bindings: display: dw_hdmi.txt: add cec-disable property
Date: Fri, 29 Jun 2018 09:17:39 +0200 [thread overview]
Message-ID: <714ee0ef-25c4-e065-8120-aebc27a1add7@baylibre.com> (raw)
In-Reply-To: <05e7ade1-89be-0f0f-18a5-88ff0310a70b@xs4all.nl>
Hi Hans,
On 03/04/2018 10:27, Hans Verkuil wrote:
> On 27/03/18 00:25, Rob Herring wrote:
>> 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.
>
> So there are three situations:
>
> 1) The cec pin is connected to the DW HDMI TX. That's already supported.
> 2) The cec pin is not connected at all, but the CEC IP is instantiated.
> We need the cec-disable property for that. This simply states that the
> CEC pin is not connected.
> 3) The cec pin is connected to an HDMI RX. We do not support this at the
> moment. If we want to support this, then we need a 'hdmi-rx' phandle
> that points to the HDMI receiver that the CEC pin is associated with.
> This will be similar to the already existing 'hdmi-phandle' property
> used to associate a CEC driver with an HDMI transmitter. In hindsight
> it would have been better if 'hdmi-phandle' was named 'hdmi-tx' :-(
>
> I can make a binding proposal for 3, but I have no hardware to test it,
> so I think it is better to add this only when someone has hardware. It
> will require quite a few changes to the driver and likely also the CEC core.
Can't we simply add a property to override the HW config fields in this case ?
It will be then usable with any feature the is enabled by reading the config
bits like AHB Audio, I2c, CEC, ... and maybe many more in the future.
Neil
>
> Regards,
>
> Hans
>
>>
>>>
>>> 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-06-29 7:17 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
2018-04-03 8:27 ` Hans Verkuil
2018-06-29 7:17 ` Neil Armstrong [this message]
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=714ee0ef-25c4-e065-8120-aebc27a1add7@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