From: Thierry Reding <thierry.reding@avionic-design.de>
To: Stephen Warren <swarren@nvidia.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"Olof Johansson (olof@lixom.net)" <olof@lixom.net>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@vger.kernel.org
Subject: Re: PCIe device tree support
Date: Wed, 22 Feb 2012 09:24:52 +0100 [thread overview]
Message-ID: <20120222082449.GA15157@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17BD8BC302@HQMAIL01.nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
[Adding Jesse Barnes and the linux-pci mailing list to CC.]
* Stephen Warren wrote:
> Thierry Reding wrote at Monday, February 20, 2012 12:18 PM:
> > I would like to add device tree support for the Tegra2 PCIe controller. From
> > what I understand this will require the PCIe code to be rewritten as a proper
> > platform driver in order to be able to instantiate it via the device tree. Is
> > that correct?
>
> That's probably the cleanest way, yes.
>
> Is there a drivers/ directory for PCI/PCIe host controllers? Moving the
> code there might be nice if so, although IIRC when I asked Olof about
> that a number of months back, he said quite a few host controllers were
> in arch/...
Most PCI/PCIe host controller drivers seem to currently be in arch/. Is there
a specific reason for this? Would it be acceptable to put any new drivers
below drivers/pci/?
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next parent reply other threads:[~2012-02-22 8:25 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 ` Thierry Reding [this message]
2012-02-22 16:01 ` PCIe device tree support 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
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=20120222082449.GA15157@avionic-0098.adnet.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
--cc=swarren@nvidia.com \
/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).