All of lore.kernel.org
 help / color / mirror / Atom feed
From: jbe@pengutronix.de (Jürgen Beisert)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX6/PCIe and MSI interrupts
Date: Fri, 6 Dec 2013 15:15:50 +0100	[thread overview]
Message-ID: <201312061515.50436.jbe@pengutronix.de> (raw)
In-Reply-To: <CAB5oZtC_X6Tk+6c5sZB06kDmhOgqmqW0_QG1GKWAJgqNpg2tag@mail.gmail.com>

Hi Harro,

On Friday 06 December 2013 13:39:09 Harro Haan wrote:
> [...]
> Attached are my patches of the first attempt to get MSI working for
> the i.MX6. It looks like MSI is working but MSIX is not in combination
> with e1000e and SabreSD. I did some successful iperf tests in MSI
> mode. I did the following hack in
> drivers/net/ethernet/intel/e1000e/param.c to disable MSIX:
>
> -		if (adapter->flags & FLAG_HAS_MSIX) {
> +		if (!(adapter->flags & FLAG_HAS_MSIX)/*TEMP*/) {

Arrrgh, after applying this change it starts to work immediately. So many 
hours...

> My MSI tests are not successful when testing it with a Xilinx PCIe
> development board, while this FPGA design works properly with FSL
> imx_3.0.35 (or on x86).

Same here. Network chip works with MSI, PCIe FPGA does not.

Regards and thanks for your help,
Juergen

-- 
Pengutronix e.K. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| Juergen Beisert ? ? ? ? ? ? |
Linux Solutions for Science and Industry ? ? ?| http://www.pengutronix.de/  |

  reply	other threads:[~2013-12-06 14:15 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
2013-12-06 12:39   ` Harro Haan
2013-12-06 14:15     ` Jürgen Beisert [this message]
     [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=201312061515.50436.jbe@pengutronix.de \
    --to=jbe@pengutronix.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 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.