linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX6/PCIe and MSI interrupts
Date: Fri, 6 Dec 2013 12:43:55 +0100	[thread overview]
Message-ID: <201312061243.56069.marex@denx.de> (raw)
In-Reply-To: <201312061032.31944.jbe@pengutronix.de>

On Friday, December 06, 2013 at 10:32:31 AM, J?rgen Beisert wrote:
> Hi,
> 
> is anybody out there who has MSI interrupts successfully working on i.MX6?
> I tried with my i.MX6 and a Gbit network card but without success. In
> legacy interrupt mode it works.

What precise model of card do you use ? Do you have a PCIe switch in the path or 
just direct RC-EP connection ?

> I'm using various patches here from the list and the PCIe itself works. The
> designware driver is prepared for MSI interrupts and the Exynos driver
> makes use of it.

OK

> I added the same glue code to the i.MX6 driver but I can't get the INTD
> interrupt to fire when MSI arrives (while the INTA fires in legacy
> interrupt mode). Some idea what needs to be done in the i.MX6 to get MSI
> working? The Exynos driver additionally changes some bits in its chipset
> beside the PCIe unit to enable the MSI interrupt to its CPU. Are there
> some 'hidden' bits in the i.MX6 as well?

Can you post your prototype patch for the PCIe MSI so we can see what you did 
there please?

Best regards,
Marek Vasut

  reply	other threads:[~2013-12-06 11:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06  9:32 i.MX6/PCIe and MSI interrupts Jürgen Beisert
2013-12-06 11:43 ` Marek Vasut [this message]
2013-12-06 12:39   ` Harro Haan
2013-12-06 14:15     ` Jürgen Beisert
     [not found]       ` <5osi8whb6ebv6ffon2b3alai.1386368340782@email.android.com>
2013-12-07 12:55         ` 回复:Re: " Marek Vasut
2013-12-10 14:12       ` Marek Vasut
2013-12-12 18:43         ` Harro Haan

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=201312061243.56069.marex@denx.de \
    --to=marex@denx.de \
    --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 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).