From: Wolfram Sang <wsa@the-dreams.de>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
SH-Linux <linux-sh@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH] drm: adv7511: really enable interrupts for EDID detection
Date: Wed, 25 Nov 2015 06:48:51 +0000 [thread overview]
Message-ID: <20151125064851.GA1511@tetsubishi> (raw)
In-Reply-To: <CANqRtoTAPU3zni__J2MQR+KK=SUUGYLgHz5j9s04CjEq55s3hg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
> > This has been tackled as well now. The clock for the GPIO controller was
> > off, so no interrupt was passed through.
>
> Thanks a lot for your efforts! When you have time, can you please show
> me the patch that fixes that GPIO interrupt problem? I'm asking
> because I may have ran into a similar issue on Gose or Alt.
For Koelsch, this simply meant I reverted Geert's clocks-off patch. But
there is a fundamental problem below: GPIO interrupts described with the
"interrupts" property in DT do not get the underlying GPIO requested.
And if noone else is using the GPIO block, its clock may be turned off.
I have an idea how to fix it, need to check priorities of the other
tasks, though.
BTW, the continous EDID read test on your board is currently at >360000
successful reads, a not a single failure :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-25 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 14:50 [PATCH] drm: adv7511: really enable interrupts for EDID detection Wolfram Sang
2015-11-24 21:05 ` Wolfram Sang
2015-11-25 6:34 ` Magnus Damm
2015-11-25 6:48 ` Wolfram Sang [this message]
2015-11-25 7:58 ` Magnus Damm
2015-11-25 8:27 ` Wolfram Sang
2015-11-26 12:43 ` Lars-Peter Clausen
2015-11-26 13:51 ` Wolfram Sang
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=20151125064851.GA1511@tetsubishi \
--to=wsa@the-dreams.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=lars@metafoo.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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