public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: soc for v4.9 (#1)
Date: Wed, 21 Sep 2016 10:10:58 +0200	[thread overview]
Message-ID: <4634141.55loc00AVg@wuerfel> (raw)
In-Reply-To: <87eg4e5xop.fsf@free-electrons.com>

On Tuesday, September 20, 2016 6:43:34 PM CEST Gregory CLEMENT wrote:
> 
> Do you mean board-wnr854t.c?

Yes.
 
> If it is the case then I can just drop the patch adding this file because
> the only things done in this file are about the PCI.

Ah, that's perfect. Just for more background, I think it shouldn't be too
hard to convert the existing orion5x PCI support into a proper host driver,
and I can assist anyone willing to work on this and test it.

I think the steps here would roughly be:

- change PCI (not PCIe) host initialization to call
  pci_scan_root_bus() directly, bypassing the pci_common_init
  logic
- move PCI code into a separate file
- change PCI code into a driver by adding platform_device based
  probing
- add DT support for that driver.

For the PCIe code, the obvious strategy is to replace it with
the existing pcie-mvebu driver, adding any missing parts
in the process.

	Arnd

  reply	other threads:[~2016-09-21  8:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 15:34 [GIT PULL] ARM: mvebu: soc for v4.9 (#1) Gregory CLEMENT
2016-09-19 21:46 ` Arnd Bergmann
2016-09-19 21:49   ` Arnd Bergmann
2016-09-20  7:25     ` Gregory CLEMENT
2016-09-20  9:45       ` Arnd Bergmann
2016-09-20 16:43         ` Gregory CLEMENT
2016-09-21  8:10           ` Arnd Bergmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-21 10:19 Gregory CLEMENT
2016-09-21 20:36 ` Arnd Bergmann

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=4634141.55loc00AVg@wuerfel \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox