All of lore.kernel.org
 help / color / mirror / Atom feed
From: linus.walleij@stericsson.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: vic: register the VIC for ST-modified VIC's
Date: Wed, 23 Nov 2011 16:53:38 +0100	[thread overview]
Message-ID: <4ECD1702.90808@stericsson.com> (raw)
In-Reply-To: <20111123154332.GE7382@totoro>

On 11/23/2011 04:43 PM, Jamie Iles wrote:
> On Wed, Nov 23, 2011 at 04:39:26PM +0100, Linus Walleij wrote:
>    
>> On 11/23/2011 04:28 PM, Jamie Iles wrote:
>>      
>>> When probing the VIC, the ST variant has a different probing method to
>>> account for the extra interrupts which meant we didn't previously call
>>> vic_register() which registered the irq_domain.
>>>
>>> Cc: Linus Walleij<linus.walleij@stericsson.com>
>>> Cc: Russell King<rmk+linux@arm.linux.org.uk>
>>> Cc: Marc Zyngier<marc.zyngier@arm.com>
>>> Signed-off-by: Jamie Iles<jamie@jamieiles.com>
>>> ---
>>>
>>> I _think_ it's just Nomadik affected here which I don't have access to.
>>> I can send an updated pull request or put it in Russell's tracker,
>>> whichever is easiest.
>>>        
>> This also affects mach-u300 and mach-ep93xx OTOH.
>>
>> This seems to be based on something else that is out-of-tree
>> so I don't get the whole picture...
>>      
> Sorry, should have specified the base - this is the VIC device
> tree/MULTI_IRQ_HANDLER stuff that is in next.  I did look at u300 and
> ep93xx, but it looks like their VIC's are 0x1000/0x10000 apart
> respectively when registered so weren't the ST type that supported 64
> IRQ's.
>    

Aha OK now I get the difference.
Acked-by: Linus Walleij <linus.walleij@linaro.org>

Thanks!
Linus Walleij

  reply	other threads:[~2011-11-23 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 15:28 [PATCH] ARM: vic: register the VIC for ST-modified VIC's Jamie Iles
2011-11-23 15:39 ` Linus Walleij
2011-11-23 15:43   ` Jamie Iles
2011-11-23 15:53     ` Linus Walleij [this message]
2011-11-24 10:59 ` Jamie Iles

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=4ECD1702.90808@stericsson.com \
    --to=linus.walleij@stericsson.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.