From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>, <catalin.marinas@arm.com>,
"Bjorn Helgaas" <helgaas@kernel.org>
Cc: <linux-pci@vger.kernel.org>
Subject: Request for Info: Designware PCIe Root Complex support in ARM64
Date: Fri, 11 Mar 2016 11:33:12 +0000 [thread overview]
Message-ID: <56E2ACF8.6030503@synopsys.com> (raw)
Hi Liviu, Catalin and Bjorn,
I am currently working on the PCIe Root Complex based on the Designware Core
(/pci/host/pcie-desigware.c). I have noticed that currently building a solution
based on the previous for an ARM64 CPU is problematic and demands some tweaking
in the ARM64 arch (like adding some functions in the pcibios, etc.).
I would like to know if any specific work is being planned for this matter and
in what I could contribute to make it happen.
Thanks,
Joao Pinto
next reply other threads:[~2016-03-11 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 11:33 Joao Pinto [this message]
2016-03-11 11:49 ` Request for Info: Designware PCIe Root Complex support in ARM64 Liviu Dudau
2016-03-11 19:46 ` Bjorn Helgaas
2016-03-14 12:15 ` Lorenzo Pieralisi
2016-03-15 11:33 ` Joao Pinto
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=56E2ACF8.6030503@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=Liviu.Dudau@arm.com \
--cc=catalin.marinas@arm.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.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).