All of lore.kernel.org
 help / color / mirror / Atom feed
From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx6q: work around faulty PMU irq routing
Date: Fri, 25 Apr 2014 07:33:24 +0200	[thread overview]
Message-ID: <5359F3A4.2060307@de.bosch.com> (raw)
In-Reply-To: <CAOMZO5DjiZnOHL9t3GeqSGu7=zU5ajKSs4__aVBRM0eHdHa3JA@mail.gmail.com>

On 24.04.2014 22:32, Fabio Estevam wrote:
> On Thu, Apr 24, 2014 at 5:23 PM, Lucas Stach <l.stach@pengutronix.de> wrote:
>> The i.MX6 PMU has a design errata where the interrupts of all cores are
>> wired together into a single irq line. To work around this we have to
>
> Is there an erratum reference number for this, please?

First, many thanks to Lucas for working on this! Up to now, it was my 
impression that the PMU on i.MX6 is completely useless for !single core 
SoCs. So maybe there is some hope, now :)

Regarding the erratum: To my knowledge there is no erratum. In 2013 I've 
had a discussion with the FSL support about this and got the answer:

-- cut --
This is the IC design issue, we have OR'ed the interrupt pin of the four 
PMU and provide one interrupt to the CPU. currently, we don't have the 
SW workaround available for it.
-- cut --

This is just what has been called as "braindead, broken system" in

http://lists.infradead.org/pipermail/linux-arm-kernel/2012-August/113802.html

Best regards

Dirk

  reply	other threads:[~2014-04-25  5:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 20:23 [PATCH] ARM: imx6q: work around faulty PMU irq routing Lucas Stach
2014-04-24 20:32 ` Fabio Estevam
2014-04-25  5:33   ` Dirk Behme [this message]
2014-04-25  5:37 ` Dirk Behme
2014-04-25  9:13   ` Lucas Stach
2014-04-29  5:28     ` Shawn Guo
2014-04-29  9:55       ` Lucas Stach
2014-04-29 11:17         ` Dirk Behme
2014-04-29 18:33           ` Frank Li
2014-04-30  9:21             ` Lucas Stach

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=5359F3A4.2060307@de.bosch.com \
    --to=dirk.behme@de.bosch.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 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.