From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Requestirq() = freeze for touchscreendriver
Date: Sat, 09 Feb 2008 03:54:06 +0000 [thread overview]
Message-ID: <20080209035406.GA24581@linux-sh.org> (raw)
In-Reply-To: <20080207020600.1651cbf5.Kristoffer.ericson@gmail.com>
On Fri, Feb 08, 2008 at 07:30:42PM +0100, Kristoffer Ericson wrote:
> On Fri, 8 Feb 2008 11:57:07 +0900
> "Magnus Damm" <magnus.damm@gmail.com> wrote:
> > On Feb 7, 2008 10:24 PM, Kristoffer Ericson
> > <kristoffer.ericson@gmail.com> wrote:
> > > These patches are against vanilla 2.6.24, but should apply cleanly
> > > to linux-2.6 also. hp6xx_ts_input.patch creates platform_driver for
> > > the touchscreen, not much is kept from the old.
> > >
> > > The booting comes to "waiting to aquire IRQ" and then freezes. So
> > > it happens in one of these lines :
> > >
> > > printk(KERN_INFO "ts: waiting to request IRQ\n");
> > > error = request_irq(HP680_TS_IRQ, hp680_ts_interrupt,
> > > IRQF_DISABLED, "HP6XX Touchscreen Driver", pdev);
> >
> > You need to track down exactly why the system is freezing. Some
> > recommendations:
>
> I added some printk's into the interrupt and when I startup I end up
> with a massive loop of those printk's. Atleast its not frozen :)
>
From the sounds of it the IRQ is being enabled and not being acked
correctly. The behaviour you describe is generally what happens with
unacked level IRQs that remain asserted.
Do any of the other IRQ0-IRQ7 IRQs work properly for you on hp6xx?
Compare with before and after the INTC changes, and double check your pin
setup.
prev parent reply other threads:[~2008-02-09 3:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 1:06 Requestirq() = freeze for touchscreendriver Kristoffer Ericson
2008-02-07 2:38 ` Paul Mundt
2008-02-07 13:24 ` Kristoffer Ericson
2008-02-08 2:57 ` Magnus Damm
2008-02-08 18:30 ` Kristoffer Ericson
2008-02-08 22:46 ` Kristoffer Ericson
2008-02-09 3:54 ` Paul Mundt [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=20080209035406.GA24581@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.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