All of lore.kernel.org
 help / color / mirror / Atom feed
From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Recent GIC v1 patch
Date: Thu, 17 Sep 2015 19:22:41 +0200	[thread overview]
Message-ID: <55FAF6E1.7020107@free.fr> (raw)
In-Reply-To: <55FAEB4D.30306@arm.com>

On 17/09/2015 18:33, Marc Zyngier wrote:
> Hi Mason,
> 
> On 17/09/15 16:55, Mason wrote:
>> Hello Thomas, Marc,
>>
>> Mans pointed me to a recent patch of yours.
>> irqchip/gic: Use IRQD_FORWARDED_TO_VCPU flag
>> Get rid of the handler_data abuse.
>>
>> I'm using a Cortex A9 based SoC. The platform's interrupt
>> controller is cascaded into the GIC. I've been trying to
>> get this to work for two weeks with no success.
>>
>> Details can be found here:
>> http://thread.gmane.org/gmane.linux.ports.arm.kernel/440327
>>
>> Do you think your patch my help with my situation?
> 
> Not sure. A GICv1 shouldn't use EOImode==1 at all, so I don't quite see
> how you end-up there. Also, you seem to be using 4.2, and this code only
> landed during the 4.3 merge window.

Sorry for being unclear. I'm having problems /without/ the patch,
and Mans suggested I try the patch.

>> Do you have any idea what might causing the problem?
> 
> Not without more information, I'm afraid.

Being the unimaginative type, I provided boot log, .config,
full port source code, and device tree description. Can you
explain what kind of information would be required to identify
the problem? (Maybe that would help me diagnose the problem.)

Regards.

  reply	other threads:[~2015-09-17 17:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 15:55 Recent GIC v1 patch Mason
2015-09-17 16:11 ` Måns Rullgård
2015-09-17 16:53   ` Mason
2015-09-17 16:33 ` Marc Zyngier
2015-09-17 17:22   ` Mason [this message]
2015-09-17 17:49     ` Marc Zyngier
2015-09-18  9:18       ` Mason
2015-09-18 11:08         ` Marc Zyngier
2015-09-18 13:12           ` Måns Rullgård
2015-09-18 13:59             ` Mason
2015-09-18 14:14               ` Marc Zyngier
2015-09-18 15:19                 ` Måns Rullgård
2015-09-18 12:40       ` Måns Rullgård

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=55FAF6E1.7020107@free.fr \
    --to=slash.tmp@free.fr \
    --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.