All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [-mm patch 3/5] SharpSL: Abstract c7x0 specifics from Corgi Touchscreen driver
Date: Thu, 08 Sep 2005 15:56:43 +0100	[thread overview]
Message-ID: <1126191403.8147.67.camel@localhost.localdomain> (raw)
In-Reply-To: <20050908131028.B31595@flint.arm.linux.org.uk>

On Thu, 2005-09-08 at 13:10 +0100, Russell King wrote: 
> On Tue, Sep 06, 2005 at 12:53:50PM +0100, Richard Purdie wrote:
> > Separate out the Sharp Zaurus c7x0 series specific code from the Corgi
> > Touchscreen driver. Use the new functions in corgi_lcd.c via sharpsl.h
> > for hsync handling and pass the IRQ as a platform device resource. Move
> > a function prototype into the w100fb header file where it belongs.
> 
> This patch looks a little confused.
> 
> > +	corgi_ts->irq_gpio = platform_get_irq(pdev, 0);
> 
> So irq_gpio is an IRQ number.
> 
> > @@ -313,14 +324,14 @@
> >  	input_register_device(&corgi_ts->input);
> >  	corgi_ts->power_mode = PWR_MODE_ACTIVE;
> >  
> > -	if (request_irq(CORGI_IRQ_GPIO_TP_INT, ts_interrupt, SA_INTERRUPT, "ts", corgi_ts)) {
> > +	if (request_irq(IRQ_GPIO(corgi_ts->irq_gpio), ts_interrupt, SA_INTERRUPT, "ts", corgi_ts)) {
> 
> Or is it.  It _should_ be an IRQ number.

This is a problem because of this code:

if ((GPLR(corgi_ts->irq_gpio) & GPIO_bit(corgi_ts->irq_gpio)) == 0) {

which needs the GPIO number. Perhaps we need to add a IRQ_TO_GPIO define
in pxa-regs.h to deal with this? Would that be acceptable?

Richard


      reply	other threads:[~2005-09-08 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 11:53 [-mm patch 3/5] SharpSL: Abstract c7x0 specifics from Corgi Touchscreen driver Richard Purdie
2005-09-06 12:40 ` Richard Purdie
2005-09-08 12:10 ` Russell King
2005-09-08 14:56   ` Richard Purdie [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=1126191403.8147.67.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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.