From: Hans Verkuil <hverkuil@xs4all.nl>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: omap4: how to get the HDMI core IRQ?
Date: Thu, 31 Mar 2016 17:46:50 -0700 [thread overview]
Message-ID: <56FDC4FA.2080001@xs4all.nl> (raw)
In-Reply-To: <56FBAC79.6060405@ti.com>
Hi Tomi,
On 03/30/2016 03:37 AM, Tomi Valkeinen wrote:
> Hi Hans,
>
> On 24/03/16 23:20, Hans Verkuil wrote:
>> Hi Tomi,
>>
>> I hope you (or someone else on this list) can help me find the problem in this code.
>>
>> I am working on a kernel framework for HDMI CEC (see https://lwn.net/Articles/680942/).
>> In order to get as much experience with different devices as possible I am trying to
>> implement it on my omap4430 Pandaboard. The big problem I am facing is that the CEC
>> interrupts come in through the HDMI_IRQ_CORE interrupt, and that just refuses to
>> trigger.
>>
>> The code below adds support for this core interrupt and it is supposed to trigger it
>> using the Software Induced interrupt to keep the code as simple as possible.
>
> So this irq is just for testing?
Yes, that was the easiest way to check the core irq without requiring lots of other changes.
>> On boot I get this debug line from the pr_info in my code:
>>
>> irqstat 02000000 wp_irq 06000001 raw 20010000 intr_state 00000001 intr1 00000080 unmask1 00000080 intr_ctrl 0000000a
>>
>> As far as I can see everything looks perfectly fine, except for the fact that bit 0
>> of the irqstat is stubbornly 0.
>>
>> This is using kernel 4.5 with only this patch applied.
>>
>> What am I missing?
>
> Set SYS_CTRL1:PD to 1 (I presume you have the NDA HDMI TRM?).
Yes, I have it.
> Apparently we set it always to 0 in
> hdmi4_core.c:hdmi_core_powerdown_disable(), but never enable it. I guess
> it only affects core irqs, so there have been no side effects.
>
> But it would make sense to either have a matching call in the enable
> path, or then just set it to 0 when initializing the IP.
I think it should be set in hdmi_core_video_config(). It sets other SYS_CTRL1 bits there as
well, and that is probably why I missed it. I just never realized that the PD bit wasn't set
there.
Thank you very much! I'm abroad right now, but once I'm back I'll test this first thing.
>
>>
>> The reward for the right answer will be HDMI CEC support for omap4 (and any other TI device
>> with the same CEC IP).
>
> Ok. When is it ready? ;)
Once I get the irq working the omap4 support should be ready very quickly, getting the CEC framework
merged takes a bit longer, but I am aiming for kernel 4.7 pending some final tests. I'm cross-posting
the patch series to dri-devel, so with luck when I post v15 it will have an omap4 driver as well.
Regards,
Hans
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-01 0:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 21:20 omap4: how to get the HDMI core IRQ? Hans Verkuil
2016-03-30 10:37 ` Tomi Valkeinen
2016-04-01 0:46 ` Hans Verkuil [this message]
2016-04-01 7:03 ` Tomi Valkeinen
2016-04-01 7:35 ` Tomi Valkeinen
2016-04-01 16:56 ` Hans Verkuil
2016-04-01 16:59 ` Tomi Valkeinen
2016-04-10 12:02 ` Hans Verkuil
2016-04-01 16:51 ` Hans Verkuil
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=56FDC4FA.2080001@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=dri-devel@lists.freedesktop.org \
--cc=tomi.valkeinen@ti.com \
/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