linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] gpio/omap: Fix IRQ handling for SPARSE_IRQ
Date: Fri, 24 Feb 2012 14:32:11 +0100	[thread overview]
Message-ID: <4F47915B.7050507@ti.com> (raw)
In-Reply-To: <CAC83ZvJ-mCZFYzOPQ177th7qVC9GBrKnB2pL=R3knMktOeau2g@mail.gmail.com>

On 2/24/2012 2:24 PM, DebBarma, Tarun Kanti wrote:
> Hi Benoit,
>
> On Fri, Feb 24, 2012 at 4:07 PM, DebBarma, Tarun Kanti
> <tarun.kanti@ti.com>  wrote:
>> On Fri, Feb 24, 2012 at 3:41 PM, Cousson, Benoit<b-cousson@ti.com>  wrote:
>>> + Tarun
>>>
>>>
>>> On 2/24/2012 12:08 AM, Tony Lindgren wrote:
>>>>
>>>> * Cousson, Benoit<b-cousson@ti.com>    [120223 14:14]:
>>>>>
>>>>> The GPIO driver is still relying on internal OMAP IRQ defines that
>>>>> are not relevant anymore if OMAP is built with SPARSE_IRQ.
>>>>
>>>>
>>>> Great :)
>>>>
>>>>> Please note that this patch is still RFC, because I do not know
>>>>> how to fix properly the ugly cpu_class_is_omap1 and the dependency
>>>>> with IH_MPUIO_BASE to detect a MPUIO.
>>>>
>>>>
>>>> Sounds like gpio_to_irq() needs to be set in the
>>>> arch/arm/*omap*/gpio*.c then.
>>>
>>>
>>> In fact, after a second thought, that might even work for OMAP1 because I'm
>>> using the proper base (IRQ and GPIO) to convert the IRQ number.
>>>
>>>
>>> static int irq_to_gpio(struct gpio_bank *bank, unsigned int gpio_irq)
>>> {
>>>
>>>         return gpio_irq - bank->irq_base + bank->chip.base;
>>> }
>>>
>>> But it might be good to test it on OMAP1 platform.
>>>
>>>
>>> Tarun,
>>>
>>> Do you have an OMAP1 board to test that.
>> Yes, I will test on OMAP1 board.
> I have booted the image on OMAP1 with following change.
> I guess bank->irq_base was a typo?

Not at all :-), it was done on purpose to get rid if the static IRQ 
definition.
I was expecting that kind of issue because OMAP1 is populating 
virtual_irq_start with the IH_MPUIO_BASE, but was expecting the dynamic 
alloc_decs to still provide the good value. The easy fix is to still use 
that for OMAP1 GPIO since nobody will want to spend time fixing OMAP1 
boards to do that properly :-(

I'll update the patch accordingly.

> static int irq_to_gpio(struct gpio_bank *bank, unsigned int gpio_irq)
> {
>          //return gpio_irq - bank->irq_base + bank->chip.base;
>          return gpio_irq - bank->virtual_irq_start + bank->chip.base;
> }
> --

Thanks for the help,
Benoit

  reply	other threads:[~2012-02-24 13:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 22:46 [RFC PATCH] gpio/omap: Fix IRQ handling for SPARSE_IRQ Cousson, Benoit
2012-02-23 23:08 ` Tony Lindgren
2012-02-24 10:11   ` Cousson, Benoit
2012-02-24 10:37     ` DebBarma, Tarun Kanti
2012-02-24 13:24       ` DebBarma, Tarun Kanti
2012-02-24 13:32         ` Cousson, Benoit [this message]
2012-02-24 13:53           ` DebBarma, Tarun Kanti
2012-02-24 13:56             ` Cousson, Benoit
2012-02-24 15:09               ` DebBarma, Tarun Kanti
2012-02-24 15:12                 ` Cousson, Benoit
2012-02-24 14:14 ` Rob Herring
2012-02-24 14:54   ` Cousson, Benoit

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=4F47915B.7050507@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).