From: Lucas Stach <l.stach@pengutronix.de>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
barebox@lists.infradead.org
Subject: Re: [PATCH v3 0/8] Marvell EBU PCIe driver
Date: Wed, 30 Jul 2014 11:16:17 +0200 [thread overview]
Message-ID: <1406711777.4654.2.camel@weser.hi.pengutronix.de> (raw)
In-Reply-To: <1406709580-5585-1-git-send-email-sebastian.hesselbarth@gmail.com>
Am Mittwoch, den 30.07.2014, 10:39 +0200 schrieb Sebastian Hesselbarth:
> Third and hopefully last round of the Marvell EBU PCIe driver patch
> set. Compared to v2, I disabled MBUS error propagation on Armada
> 370/XP as it hangs the SoC on unanswered PCIe accesses. Also, 64b
> BARs are now properly handled. I added two more pci core fixes that
> move PCI device registration after BAR setup and temporarely disable
> PCI_COMMAND' IO and MEM bits during BAR setup.
>
> The MVEBU PCIe driver now gained support for Armada XP PHY setup
> which is anticipating a minor DT binding tweak to allow more than
> one marvell,pcie-lane passed to the node. Also, PCI address space
> does now also start at where we see it on MBUS. Some devices were
> not so happy about starting at 0.
>
> The whole series has been tested on Armada 370 Mirabox and
> Armada XP Lenovo Iomega ix4-300d (not mainline yet).
>
> Sebastian
>
This looks good to me.
Patches 3-7 are
Reviewed-by: Lucas Stach <l.stach@pengutronix.de
Series is
Acked-by: Lucas Stach <l.stach@pengutronix.de>
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-07-30 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 8:39 Sebastian Hesselbarth
2014-07-30 8:39 ` [PATCH v3 1/8] bus: mvebu: fix resource size handling Sebastian Hesselbarth
2014-07-30 8:39 ` [PATCH v3 2/8] ARM: mvebu: armada-370-xp: disable MBUS error propagation Sebastian Hesselbarth
2014-07-30 8:39 ` [PATCH v3 3/8] pci: pci_scan_bus: respect 64b BARs Sebastian Hesselbarth
2014-07-30 8:39 ` [PATCH v3 4/8] pci: register device after BAR setup Sebastian Hesselbarth
2014-07-30 8:39 ` [PATCH v3 5/8] pci: ensure device does ignore BAR mangling Sebastian Hesselbarth
2014-07-30 8:39 ` [PATCH v3 6/8] pci: set auto-incremented bus number Sebastian Hesselbarth
2014-07-30 8:39 ` [PATCH v3 7/8] of: pci: import of_pci_get_devfn() Sebastian Hesselbarth
2014-07-30 8:39 ` [PATCH v3 8/8] pci: mvebu: Add PCIe driver Sebastian Hesselbarth
2014-07-30 9:16 ` Lucas Stach [this message]
2014-07-31 5:30 ` [PATCH v3 0/8] Marvell EBU " Sascha Hauer
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=1406711777.4654.2.camel@weser.hi.pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
/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