From: Hans Verkuil <hverkuil@xs4all.nl>
To: Jose Abreu <Jose.Abreu@synopsys.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH v2 2/4] [media] platform: Add Synopsys Designware HDMI RX Controller Driver
Date: Fri, 16 Jun 2017 17:59:46 +0200 [thread overview]
Message-ID: <ef24f72c-bb8e-8b9e-3cd5-e19d03fd4342@xs4all.nl> (raw)
In-Reply-To: <900bfa50-2cc3-2b33-8531-2c65ebd3a981@synopsys.com>
On 06/16/2017 05:52 PM, Jose Abreu wrote:
> Hi Hans,
>
>
> On 16-06-2017 14:44, Hans Verkuil wrote:
>>
>>>> <snip>
>>>>
>>>>> + /* CEC */
>>>>> + dw_dev->cec_adap = cec_allocate_adapter(&dw_hdmi_cec_adap_ops,
>>>>> + dw_dev, dev_name(dev), CEC_CAP_TRANSMIT |
>>>>> + CEC_CAP_PHYS_ADDR | CEC_CAP_LOG_ADDRS,
>>>> Add CEC_CAP_RC and CEC_CAP_PASSTHROUGH.
>>>>
>>>> I'm not sure about CEC_CAP_PHYS_ADDR. The problem here is that this driver
>>>> doesn't handle the EDID, but without that it doesn't know what physical
>>>> address to use.
>>>>
>>>> I wonder if the cec-notifier can be used for this, possibly with adaptations.
>>>> Relying on users to set the physical address is a last resort since it is very
>>>> painful to do so. cec-notifier was specifically designed to solve this.
>>> Yes, EDID ROM is not integrated into the controller so I can't
>>> add the code. How exactly can I use cec-notifier here?
>> drivers/media/platform/sti/cec/stih-cec.c is a good example. The notifier is
>> called by drivers/gpu/drm/sti/sti_hdmi.c.
>
> Done! Implemented and working :) I'm wondering if you want me to
> wait some more time for other comments or just send the v3 now? I
> also added support for SCDC read request (its a matter of
> activating a bit).
Well, if it is ready, then just send a v3!
> BTW, I used the DT node name "hdmi-phandle" but I don't know if
> it is the best because it can cause confusion about the
> hdmi-phandle that you documented in media/cec.txt
I had the same thought. It doesn't really fit for CEC adapters on
HDMI receivers.
Perhaps edid-phandle? Or something else?
Regards,
Hans
next prev parent reply other threads:[~2017-06-16 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 10:07 [PATCH v2 0/4] Synopsys Designware HDMI Video Capture Controller + PHY Jose Abreu
2017-06-16 10:07 ` [PATCH v2 1/4] [media] platform: Add Synopsys Designware HDMI RX PHY e405 Driver Jose Abreu
2017-06-16 10:07 ` [PATCH v2 2/4] [media] platform: Add Synopsys Designware HDMI RX Controller Driver Jose Abreu
2017-06-16 12:38 ` Hans Verkuil
2017-06-16 13:21 ` Jose Abreu
2017-06-16 13:44 ` Hans Verkuil
2017-06-16 15:52 ` Jose Abreu
2017-06-16 15:59 ` Hans Verkuil [this message]
2017-06-16 10:07 ` [PATCH v2 3/4] MAINTAINERS: Add entry for Synopsys Designware HDMI drivers Jose Abreu
2017-06-16 10:07 ` [PATCH v2 4/4] dt-bindings: media: Document Synopsys Designware HDMI RX Jose Abreu
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=ef24f72c-bb8e-8b9e-3cd5-e19d03fd4342@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=Jose.Abreu@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®