From: Kevin Hilman <khilman@ti.com>
To: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: GPIO abort on 3630/Zoom3
Date: Thu, 15 Mar 2012 10:37:21 -0700 [thread overview]
Message-ID: <87k42lbwa6.fsf@ti.com> (raw)
In-Reply-To: <CAC83ZvLMWxxr7QSca0a9+wJR_gJ6-s6ddfUQdVqQ-XbWSoNa+w@mail.gmail.com> (Tarun Kanti DebBarma's message of "Thu, 15 Mar 2012 08:43:54 +0530")
"DebBarma, Tarun Kanti" <tarun.kanti@ti.com> writes:
> On Thu, Mar 15, 2012 at 3:35 AM, Kevin Hilman <khilman@ti.com> wrote:
>> Tarun,
>>
>> Can you investigate an abort during boot on 3630/Zoom3?
>>
>> Both Tony and I are seeing the abort below on 3630/Zoom3. I'm using
>> arm-soc/for-next and Tony is using linux-next, but we see the same abort.
> The crash looks very similar to what we fixed yesterday. The problem was
> basically due to usage of OMAP_GPIO_IRQ macro instead of gpio_to_irq()
> which came as part of Benoit's dynamic irq allocation change. The fix is to
> replace those macros in the board files.
> (The same problem is seen on OMAP3430 SDP as well.)
> Anyways, I will confirm.
>
>>
>> Adding in your latest fixes series doesn't make the problem go away, but
>> backing out the GPIO runtime PM series does make the problem go away.
> Because of dynamic irq allocation we end up into wrong GPIO Bank unless
> we use the new gpio_to_irq(). As a result _set_gpio_triggering() tries
> to operate
> on a GPIO Bank whose clock was not turned on using omap_gpio_request().
> Probably, that is why we do not see the problem when the runtime PM series
> is removed because in this case all the GPIO banks are turned on.
Yeah, this sounds like the same bug. Thanks for investigating.
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-03-15 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 22:05 GPIO abort on 3630/Zoom3 Kevin Hilman
2012-03-15 3:13 ` DebBarma, Tarun Kanti
2012-03-15 6:43 ` Shilimkar, Santosh
2012-03-15 17:37 ` Kevin Hilman [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=87k42lbwa6.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tarun.kanti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox