All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 1 Apr 2016 09:51:39 -0700	[thread overview]
Message-ID: <56FEA71B.8030407@xs4all.nl> (raw)
In-Reply-To: <56FE1D39.1080303@ti.com>



On 04/01/2016 12:03 AM, Tomi Valkeinen wrote:
> On 01/04/16 03:46, Hans Verkuil wrote:
>
>>> 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.
>
> Hmm. Well, it's "power-down". It's quite unclear what it actually does,
> but from the name of it, I think it makes sense to set it only when HDMI
> core is enabled.
>
> In hdmi4.c, there are hdmi_power_on_core() and hdmi_power_off_core()
> functions, those might be good places to handle the bit.
>
> Ehh... Actually, looking at the code more carefully...
>
> hdmi_core_powerdown_disable() is called from hdmi4_configure() when
> setting everything up, and there's a comment "power down off". So
> apparently the intention of the code is to disable power-down mode, but
> it sets the bit to a wrong state.
>
> So probably we could just fix hdmi_core_powerdown_disable(), so that it
> sets PD to 1, which is what it was meant to do. This assumes that there
> are no bad side effects having PD 1 even if the HDMI is blanked, which
> is something we need to verify. I can do a few tests with that.

Sounds good. BTW, I got confused yesterday by the name 'powerdown_disable()'.
How about calling it 'powerup()'? :-)

Regards,

	Hans
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2016-04-01 16:51 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
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 [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=56FEA71B.8030407@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.