From: Jisheng Zhang <jszhang@marvell.com> To: <Liviu.Dudau@arm.com>, <bhelgaas@google.com>, <robh@kernel.org>, <arnd@arndb.de>, <lorenzo.pieralisi@arm.com> Cc: <linux-pci@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org> Subject: [Query] Direction of adding arm64 support to PCIe designware driver Date: Fri, 3 Apr 2015 17:46:21 +0800 [thread overview] Message-ID: <20150403174621.02681f0d@xhacker> (raw) Hi all, Currently, the pci designware driver still lacks of arm64 support and I noticed that many works are done to achieve this goal. Some patches are merged and some are under discussion. And Per my understanding, even w/ these patches merged, the driver still doesn't support arm64. Could you please kindly point out the direction to add arm64 support to the PCIe designware driver? Thanks in advance, Jisheng
WARNING: multiple messages have this Message-ID (diff)
From: jszhang@marvell.com (Jisheng Zhang) To: linux-arm-kernel@lists.infradead.org Subject: [Query] Direction of adding arm64 support to PCIe designware driver Date: Fri, 3 Apr 2015 17:46:21 +0800 [thread overview] Message-ID: <20150403174621.02681f0d@xhacker> (raw) Hi all, Currently, the pci designware driver still lacks of arm64 support and I noticed that many works are done to achieve this goal. Some patches are merged and some are under discussion. And Per my understanding, even w/ these patches merged, the driver still doesn't support arm64. Could you please kindly point out the direction to add arm64 support to the PCIe designware driver? Thanks in advance, Jisheng
next reply other threads:[~2015-04-03 9:49 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-03 9:46 Jisheng Zhang [this message] 2015-04-03 9:46 ` [Query] Direction of adding arm64 support to PCIe designware driver Jisheng Zhang 2015-04-08 10:32 ` Lorenzo Pieralisi 2015-04-08 10:32 ` Lorenzo Pieralisi 2015-04-09 1:36 ` Jaehoon Chung 2015-04-09 1:36 ` Jaehoon Chung 2015-04-09 2:43 ` Jisheng Zhang 2015-04-09 2:43 ` Jisheng Zhang 2015-04-09 2:47 ` Minghuan.Lian 2015-04-09 2:47 ` Minghuan.Lian at freescale.com 2015-04-09 3:29 ` Jisheng Zhang 2015-04-09 3:29 ` Jisheng Zhang 2015-04-13 9:16 ` Liviu Dudau 2015-04-13 9:16 ` Liviu Dudau
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=20150403174621.02681f0d@xhacker \ --to=jszhang@marvell.com \ --cc=Liviu.Dudau@arm.com \ --cc=arnd@arndb.de \ --cc=bhelgaas@google.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-pci@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=robh@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: linkBe 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.