linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	Gala Kumar-B11780 <B11780@freescale.com>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 2/2] powerpc/85xx: create 32-bit DTS for the P1022DS
Date: Thu, 8 Dec 2011 11:51:17 -0600	[thread overview]
Message-ID: <4EE0F915.2010507@freescale.com> (raw)
In-Reply-To: <4EE00D6D.70805@freescale.com>

On 12/07/2011 07:05 PM, Tabi Timur-B04825 wrote:
> Scott Wood wrote:
>>> +			interrupts =<8 8 0 0>;
>>>>  +		};
>> It's not new to this patch, but... what does "8" mean in the second cell
>> of an mpic interrupt specifier?
> 
> I have no idea.

Valid values are 0 through 3.

>> And why does the indirect pixis node
>> not have the interrupt?
> 
> Hmmm... I suppose I could add it, but I don't know what good it would do. 
>   The code that's looking for the interrupt is probing on "fsl,p1022ds-fpga".

Is there a reason why this functionality couldn't be used in indirect
mode?  The device tree describes the hardware, not the limitations of
current Linux support.

-Scott

      reply	other threads:[~2011-12-08 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08  0:04 [PATCH 1/2] [v2] powerpc/85xx: p1022ds: disable the NOR flash node if video is enabled Timur Tabi
2011-12-08  0:04 ` [PATCH 2/2] powerpc/85xx: create 32-bit DTS for the P1022DS Timur Tabi
2011-12-08  0:08   ` Scott Wood
2011-12-08  1:05     ` Tabi Timur-B04825
2011-12-08 17:51       ` Scott Wood [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=4EE0F915.2010507@freescale.com \
    --to=scottwood@freescale.com \
    --cc=B04825@freescale.com \
    --cc=B07421@freescale.com \
    --cc=B11780@freescale.com \
    --cc=linuxppc-dev@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).