From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Pratyush Anand <pratyush.anand@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Olof Johansson (olof@lixom.net)" <olof@lixom.net>,
linux-pci@vger.kernel.org,
Thierry Reding <thierry.reding@avionic-design.de>,
Stephen Warren <swarren@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: PCIe device tree support
Date: Fri, 24 Feb 2012 09:27:06 -0800 [thread overview]
Message-ID: <20120224092706.7e33aa9c@jbarnes-desktop> (raw)
In-Reply-To: <CAHM4w1k1_Yp56tpfPqDxT1WHQWRB5xe_Zs-BEj+n5rVmuyAJiw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
On Fri, 24 Feb 2012 22:46:06 +0530
Pratyush Anand <pratyush.anand@gmail.com> wrote:
> I too had similar query.
> I have written a PCIe host driver for SPEAr platform (ARM Arch).
> This driver is registered on paltform bus.
> It is for Designware IP, so I believe that most of its part
> can be re-usaable for other person.
> have kept common and SPEAr specific part separately.
> But, I am not sure about its best location.
> I believe best would have been to keep in driver/pci/pcie/hosts/.
> But it uses pci_common_init function which is specific to ARM platform.
> So it limits option to arch/arm.
> But, if I keep it in arch/arm/mach-spear13xx/ , then it will limit others
> from using synopsys specific code.
>
> What do you suggest?
Maybe arch/arm/pci until there are non-ARM users of the IP? In fact,
you may want to put off moving it to arch/arm/pci until you have
someone to share it with. Premature sharing is like premature
optimization after all...
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-24 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120220191804.GA14499@avionic-0098.adnet.avionic-design.de>
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF17BD8BC302@HQMAIL01.nvidia.com>
2012-02-22 8:24 ` PCIe device tree support Thierry Reding
2012-02-22 16:01 ` Bjorn Helgaas
2012-02-23 6:03 ` Thierry Reding
2012-02-23 16:16 ` Jesse Barnes
2012-02-23 16:17 ` Olof Johansson
2012-02-23 17:49 ` Bjorn Helgaas
2012-02-24 6:59 ` Thierry Reding
2012-02-24 17:16 ` Pratyush Anand
2012-02-24 17:25 ` Bjorn Helgaas
2012-02-24 17:27 ` Jesse Barnes [this message]
2012-02-28 18:17 ` 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=20120224092706.7e33aa9c@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
--cc=pratyush.anand@gmail.com \
--cc=swarren@nvidia.com \
--cc=thierry.reding@avionic-design.de \
/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).