linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: devicetree and IRQ7 mapping for T1042(mpic)
Date: Wed, 14 Oct 2015 19:11:38 -0500	[thread overview]
Message-ID: <1444867898.5185.213.camel@freescale.com> (raw)
In-Reply-To: <1444851451.28972.59.camel@transmode.se>

On Wed, 2015-10-14 at 19:37 +0000, Joakim Tjernlund wrote:
> I am trying to figure out how to describe/map external IRQ7 in the 
> devicetree.
> 
> Basically either IRQ7 to be left alone by Linux(becase u-boot already set 
> it up)
> or map IRQ7 to sie 0(MPIC_EILR7=0xf0) and prio=0xf(MPIC_EIVPR7=0x4f0000)
> 
> There is no need for SW handler because IRQ7 will be routed to the DDR 
> controller
> and case an automatic Self Refresh just before CPU reset.
> 
> I cannot figure out how to do this. Any ideas?
> 
> If not possible from devicetree, then can one do it from board code?

The device tree describes the hardware.  Priority is configuration, and thus 
doesn't belong there.  You can call mpic_irq_set_priority() from board code.

Likewise, the fact that you want to route irq7 to sie0 is configuration, not 
hardware description.  At most, the device tree should describe is what is 
connected to each sie output.  There's no current Linux support for routing 
an interrupt to sie or anything other than "int".

-Scott

  reply	other threads:[~2015-10-15  0:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 19:37 devicetree and IRQ7 mapping for T1042(mpic) Joakim Tjernlund
2015-10-15  0:11 ` Scott Wood [this message]
2015-10-15  0:14   ` Scott Wood
2015-10-15  7:11   ` Joakim Tjernlund
2015-10-15  7:14     ` Scott Wood

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=1444867898.5185.213.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linuxppc-dev@lists.ozlabs.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).