From: rjui@broadcom•com (Ray Jui)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/2] PCI: iproc: add bcma PCIe 2.0 controller
Date: Tue, 12 May 2015 15:05:13 -0700 [thread overview]
Message-ID: <55527919.2030206@broadcom.com> (raw)
In-Reply-To: <1431465781-10753-1-git-send-email-hauke@hauke-m.de>
Hi Hauke,
On 5/12/2015 2:22 PM, Hauke Mehrtens wrote:
> After Ray submitted the PCIe controller for the iProc devices using
> pure device tree this adds support for the devices using bcma to scan
> the bus. This should replaces the driver I initially send for inclusion.
>
> @Ray The driver found in the Broadcom SDK does some more stuff:
> * setting up some DMA memory areas
> * chaining MPS and MRRS to 512
> * PHY changes:
> * "improving" the PCIe jitter
> * some special initializations for the 3rd PCIe port
>
> For me it works without these additions, but I haven't tested for
> performance or stability or 3rd port. Can you check if this is needed
> at all for the devices found on the market?
Good work, Hauke!
I'll eventually get to these. It may take a while but I'll eventually
get to them.
Thanks,
Ray
next prev parent reply other threads:[~2015-05-12 22:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 21:22 [PATCH 0/2] PCI: iproc: add bcma PCIe 2.0 controller Hauke Mehrtens
2015-05-12 21:23 ` [PATCH 1/2] PCI: iproc: make of_irq_parse_and_map_pci() configurable Hauke Mehrtens
2015-05-12 22:14 ` Ray Jui
2015-05-12 21:23 ` [PATCH 2/2] PCI: iproc: add bcma pcie driver Hauke Mehrtens
2015-05-12 22:18 ` Ray Jui
2015-05-13 6:27 ` Rafał Miłecki
2015-05-13 15:56 ` Ray Jui
2015-05-13 16:19 ` Rafał Miłecki
2015-05-13 16:30 ` Ray Jui
2015-05-13 18:43 ` Hauke Mehrtens
2015-05-19 23:14 ` Bjorn Helgaas
2015-05-19 23:17 ` Ray Jui
2015-05-20 5:27 ` Rafał Miłecki
2015-05-12 22:05 ` Ray Jui [this message]
2015-05-20 14:52 ` [PATCH 0/2] PCI: iproc: add bcma PCIe 2.0 controller Bjorn Helgaas
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=55527919.2030206@broadcom.com \
--to=rjui@broadcom$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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