All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V7 02/17] SPEAr13xx: Add PCIe host controller base driver support.
Date: Wed, 27 Apr 2011 11:03:00 +0200	[thread overview]
Message-ID: <201104271103.00284.arnd@arndb.de> (raw)
In-Reply-To: <4DB7BD41.50108@st.com>

On Wednesday 27 April 2011, Pratyush Anand wrote:
> > I would suggest in general to make the code as generic as easily possible
> > and put it into an appropriate location for sharing, but not spending
> 
> Our next SOC has new revision of Synopsys PCIe Controller, which has more
> generic application interface registers. I am planning to divide code for
> this new SOC, so that it would be easily usable if someone has same controller.
> What could be the best location for shared code?
 
Traditionally, that would be arch/arm/common.

Since we are now in the process of increasingly moving drivers into the
drivers/*/ directory, we could also discuss starting a new
drivers/pci/hosts/ directory and moving some of the existing host
controllers from arch/arm over there.

	Arnd

      reply	other threads:[~2011-04-27  9:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1298977728.git.viresh.kumar@st.com>
2011-03-23  4:52 ` [PATCH V7 02/17] SPEAr13xx: Add PCIe host controller base driver support Viresh Kumar
2011-03-23  8:28   ` Arnd Bergmann
2011-04-11 12:26     ` pratyush
2011-04-11 15:22       ` Arnd Bergmann
2011-04-13 12:11         ` pratyush
2011-04-12 15:32   ` Rob Herring
2011-04-13 12:25     ` pratyush
2011-04-17 20:19       ` Arnd Bergmann
2011-04-27  6:52         ` Pratyush Anand
2011-04-27  9:03           ` Arnd Bergmann [this message]

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=201104271103.00284.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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.