All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Jisheng Zhang <jszhang@marvell.com>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
	"robh@kernel.org" <robh@kernel.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Query] Direction of adding arm64 support to PCIe designware driver
Date: Mon, 13 Apr 2015 10:16:00 +0100	[thread overview]
Message-ID: <20150413091559.GA13091@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <20150403174621.02681f0d@xhacker>

On Fri, Apr 03, 2015 at 10:46:21AM +0100, Jisheng Zhang wrote:
> 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
> 

Hi Jisheng,

Sorry for my delay in answering, I was on holiday.

AFAIK there is no ready made version of the designware driver that will work for
arm64. Depending on your actual IP implementation, if is is SBSA compliant then
it should work with the generic host bridge driver rather than using the current
designware driver. If that doesn't fit your requirements then you will have to
update the existing driver to use the generic pci framework that arm64 needs.

Best regards,
Liviu

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯


WARNING: multiple messages have this Message-ID (diff)
From: Liviu.Dudau@arm.com (Liviu Dudau)
To: linux-arm-kernel@lists.infradead.org
Subject: [Query] Direction of adding arm64 support to PCIe designware driver
Date: Mon, 13 Apr 2015 10:16:00 +0100	[thread overview]
Message-ID: <20150413091559.GA13091@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <20150403174621.02681f0d@xhacker>

On Fri, Apr 03, 2015 at 10:46:21AM +0100, Jisheng Zhang wrote:
> 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
> 

Hi Jisheng,

Sorry for my delay in answering, I was on holiday.

AFAIK there is no ready made version of the designware driver that will work for
arm64. Depending on your actual IP implementation, if is is SBSA compliant then
it should work with the generic host bridge driver rather than using the current
designware driver. If that doesn't fit your requirements then you will have to
update the existing driver to use the generic pci framework that arm64 needs.

Best regards,
Liviu

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ?\_(?)_/?

  parent reply	other threads:[~2015-04-13  9:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03  9:46 [Query] Direction of adding arm64 support to PCIe designware driver Jisheng Zhang
2015-04-03  9:46 ` 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 [this message]
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=20150413091559.GA13091@e106497-lin.cambridge.arm.com \
    --to=liviu.dudau@arm.com \
    --cc=Lorenzo.Pieralisi@arm.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=jszhang@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --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: 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.