From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 1/2] platform: Add Amlogic Meson AO CEC Controller driver
Date: Thu, 27 Jul 2017 17:14:32 +0200 [thread overview]
Message-ID: <b3cc0f02-7bd0-a6c9-c223-6902f448d276@baylibre.com> (raw)
In-Reply-To: <9acecab0-7dda-9aa1-fa07-886d40f6c7df@baylibre.com>
On 07/27/2017 04:43 PM, Neil Armstrong wrote:
> On 07/25/2017 03:45 PM, Hans Verkuil wrote:
>> On 07/25/17 14:34, Neil Armstrong wrote:
>>> Hi Hans,
>>
>>>>> +static int meson_ao_cec_probe(struct platform_device *pdev)
>>>>> +{
>>>>> + struct meson_ao_cec_device *ao_cec;
>>>>> + struct platform_device *hdmi_dev;
>>>>> + struct device_node *np;
>>>>> + struct resource *res;
>>>>> + int ret, irq;
>>>>> +
>>>>> + np = of_parse_phandle(pdev->dev.of_node, "hdmi-phandle", 0);
>>>>> + if (!np) {
>>>>> + dev_err(&pdev->dev, "Failed to find hdmi node\n");
>>>>> + return -ENODEV;
>>>>> + }
>>>>> +
>>>>> + hdmi_dev = of_find_device_by_node(np);
>>>>> + if (hdmi_dev == NULL)
>>>>> + return -EPROBE_DEFER;
>>>>> +
>>>>> + ao_cec = devm_kzalloc(&pdev->dev, sizeof(*ao_cec), GFP_KERNEL);
>>>>> + if (!ao_cec)
>>>>> + return -ENOMEM;
>>>>> +
>>>>> + spin_lock_init(&ao_cec->cec_reg_lock);
>>>>> +
>>>>> + ao_cec->notify = cec_notifier_get(&hdmi_dev->dev);
>>>>> + if (!ao_cec->notify)
>>>>> + return -ENOMEM;
>>>>> +
>>>>> + ao_cec->adap = cec_allocate_adapter(&meson_ao_cec_ops, ao_cec,
>>>>> + "meson_ao_cec",
>>>>> + CEC_CAP_LOG_ADDRS |
>>>>> + CEC_CAP_TRANSMIT |
>>>>> + CEC_CAP_RC |
>>>>> + CEC_CAP_PASSTHROUGH,
>>>>> + 1); /* Use 1 for now */
>>>>
>>>> I recommend that you add support for 2 logical addresses. More isn't allowed
>>>> by the CEC 2.0 spec anyway (no such restriction for CEC 1.4, but more than
>>>> two really isn't needed).
>>>
>>> I know, but in the "communication" register with the suspend/poweroff firmware
>>> that handles the wake up, only a single logical address is supported...
>>>
>>> What should I do in this case ? Which logical adress should I pass to the firmware when implementing ir ?
>>
>> Ah, OK. Interesting.
>>
>> From cec-adap.c:
>>
>> if (log_addrs->num_log_addrs == 2) {
>> if (!(type_mask & ((1 << CEC_LOG_ADDR_TYPE_AUDIOSYSTEM) |
>> (1 << CEC_LOG_ADDR_TYPE_TV)))) {
>> dprintk(1, "two LAs is only allowed for audiosystem and TV\n");
>> return -EINVAL;
>> }
>> if (!(type_mask & ((1 << CEC_LOG_ADDR_TYPE_PLAYBACK) |
>> (1 << CEC_LOG_ADDR_TYPE_RECORD)))) {
>> dprintk(1, "an audiosystem/TV can only be combined with record or playback\n");
>> return -EINVAL;
>> }
>> }
>>
>> So you would store the TV or AUDIOSYSTEM logical address in the firmware, since those
>> describe the system best.
>>
>> I.e. it is a TV/Audiosystem with recording/playback capabilities.
>>
>> The problem is that for CEC 1.4 no such restriction is imposed (the test above is
>> specific to CEC 2.0). But I think it makes sense to just check if TV/Audiosystem
>> is selected and pick that as the LA to store in the firmware, and otherwise just
>> pick the first LA (log_addr[0]).
>
>
> Ok I'll add support for dual LA, and I'll do this LA selection when I'll add firmware support.
Sorry, but having more than 1 LA makes the CEC controller very unstable, I'll need more info from amlogic to activate multiple LAs.
Neil
>
> Thanks,
> Neil
>
>
>> Regards,
>>
>> Hans
>>
>
next prev parent reply other threads:[~2017-07-27 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 8:01 [PATCH v2 0/2] media: Add Amlogic Meson AO CEC Controller support Neil Armstrong
2017-07-10 8:01 ` [PATCH v2 1/2] platform: Add Amlogic Meson AO CEC Controller driver Neil Armstrong
2017-07-17 8:01 ` Hans Verkuil
2017-07-25 12:34 ` Neil Armstrong
2017-07-25 13:45 ` Hans Verkuil
2017-07-27 14:43 ` Neil Armstrong
2017-07-27 15:14 ` Neil Armstrong [this message]
2017-07-10 8:01 ` [PATCH v2 2/2] dt-bindings: media: Add Amlogic Meson AO-CEC bindings Neil Armstrong
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=b3cc0f02-7bd0-a6c9-c223-6902f448d276@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®