Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Felipe Balbi <balbi@ti.com>, Nishanth Menon <nm@ti.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Olof Johansson <olof@lixom.net>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: New l3-noc error with CPUFREQ_DT built-in with v4.0-rc1
Date: Tue, 24 Feb 2015 08:46:39 -0600	[thread overview]
Message-ID: <20150224144639.GE29829@saruman.tx.rr.com> (raw)
In-Reply-To: <20150224032450.GT32521@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]

Hi,

On Mon, Feb 23, 2015 at 07:24:50PM -0800, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [150223 19:29]:
> > * Felipe Balbi <balbi@ti.com> [150223 19:19]:
> > > On Mon, Feb 23, 2015 at 07:01:42PM -0800, Tony Lindgren wrote:
> > > > * Tony Lindgren <tony@atomide.com> [150223 18:43]:
> > > > 
> > > > Looks like the address is 0 for "Custom Error". Anyways, reverting
> > > 
> > > yeah, that's because the error comes from l4per2, not l3 :-)
> > 
> > Right so it seems :)
> >  
> > > > a fix for similar issue found on omap3 so far seems to help, that's
> > > > 3d009c8c61f9 ("gpio: omap: Fix bad device access with setup_irq()").
> > > 
> > > if we revert that, we regress omap3, right ?
> > 
> > Yes we saw that getting triggered on omap3/4 before 3d009c8c61f9.
> > 
> > Now looking at the stack trace again, it actually has something:
> > 
> > ...
> > [<c05999a4>] (__irq_svc) from [<c0599164>] (_raw_spin_unlock_irqrestore+0x34/0x44)
> > [<c0599164>] (_raw_spin_unlock_irqrestore) from [<c0027120>] (omap_hwmod_idle+0x34/0x44)
> > [<c0027120>] (omap_hwmod_idle) from [<c00283f8>] (omap_device_idle+0x38/0x78)
> > [<c00283f8>] (omap_device_idle) from [<c0028454>] (_od_runtime_suspend+0x1c/0x24)
> > [<c0028454>] (_od_runtime_suspend) from [<c03b5214>] (__rpm_callback+0x2c/0x60)
> > [<c03b5214>] (__rpm_callback) from [<c03b5268>] (rpm_callback+0x20/0x80)
> > [<c03b5268>] (rpm_callback) from [<c03b56b8>] (rpm_suspend+0xe8/0x55c)
> > [<c03b56b8>] (rpm_suspend) from [<c03b6bdc>] (pm_runtime_work+0x74/0xa8)
> > [<c03b6bdc>] (pm_runtime_work) from [<c0054608>] (process_one_work+0x1b0/0x4a0)
> > ...
> > 
> > If it's the gpio-omap, there's probably some confusion still in
> > the driver regarding the GPIO bank idle status. Anyways, will look
> > more into it tomorrow.
> 
> And now I'm seeing the error with 3d009c8c61f9 reverted, so it
> does not seem to be that either..

well, that's good :-)

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-02-24 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 23:59 New l3-noc error with CPUFREQ_DT built-in with v4.0-rc1 Tony Lindgren
2015-02-24  1:59 ` Tony Lindgren
2015-02-24  2:24   ` Felipe Balbi
2015-02-24  2:35     ` Tony Lindgren
2015-02-24  3:01       ` Tony Lindgren
2015-02-24  3:15         ` Felipe Balbi
2015-02-24  3:21           ` Tony Lindgren
2015-02-24  3:24             ` Tony Lindgren
2015-02-24 14:46               ` Felipe Balbi [this message]
2015-02-24  3:12       ` Felipe Balbi

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=20150224144639.GE29829@saruman.tx.rr.com \
    --to=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=nm@ti.com \
    --cc=olof@lixom.net \
    --cc=tony@atomide.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