linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/3] ARM: bios32: use pci_enable_resource to enable PCI resources
Date: Tue, 18 Feb 2014 15:41:39 +0000	[thread overview]
Message-ID: <20140218154139.GF21483@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1392726043-31088-3-git-send-email-will.deacon@arm.com>

On Tue, Feb 18, 2014 at 12:20:42PM +0000, Will Deacon wrote:
> This patch moves bios32 over to using the generic code for enabling PCI
> resources. Since the core code takes care of bridge resources too, we
> can also drop the explicit IO and MEMORY enabling for them in the arch
> code.
> 
> A side-effect of this change is that we no longer explicitly enable
> devices when running in PCI_PROBE_ONLY mode. This stays closer to the
> meaning of the option and prevents us from trying to enable devices
> without any assigned resources (the core code refuses to enable
> resources without parents).
> 
> Tested-By: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
> Tested-by: Jingoo Han <jg1.han@samsung.com>
> Signed-off-by: Will Deacon <will.deacon@arm.com>

Tested acceptably fine here with crudbus-from-hell.

Tested-by: Russell King <rmk+kernel@arm.linux.org.uk>

-- 
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up.  Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".

  reply	other threads:[~2014-02-18 15:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 12:20 [PATCH v3 0/3] ARM: PCI: implement generic PCI host controller Will Deacon
2014-02-18 12:20 ` [PATCH v3 1/3] ARM: mach-virt: allow PCI support to be selected Will Deacon
2014-02-18 12:20 ` [PATCH v3 2/3] ARM: bios32: use pci_enable_resource to enable PCI resources Will Deacon
2014-02-18 15:41   ` Russell King - ARM Linux [this message]
2014-02-18 19:10     ` Will Deacon
2014-02-20 11:12     ` Will Deacon
2014-02-20 19:39       ` Bjorn Helgaas
2014-02-21  0:36         ` Jason Gunthorpe
2014-02-21 13:49           ` Will Deacon
2014-02-18 12:20 ` [PATCH v3 3/3] PCI: ARM: add support for generic PCI host controller Will Deacon
2014-02-18 13:46   ` Arnd Bergmann
2014-02-18 19:10     ` Will Deacon
2014-02-19 11:07       ` Will Deacon
2014-02-19 14:17         ` Arnd Bergmann
2014-02-19 15:25           ` Will Deacon
2014-02-18 18:21   ` Jason Gunthorpe
2014-02-18 18:44     ` Will Deacon
2014-02-18 18:47       ` Arnd Bergmann
2014-02-18 18:51         ` Will Deacon
2014-02-18 19:11           ` Arnd Bergmann
2014-02-18 19:16             ` Will Deacon
2014-02-18 18:59       ` Jason Gunthorpe
2014-02-18 19:09         ` Will Deacon
2014-02-18 19:32           ` Arnd Bergmann
2014-02-18 19:36             ` Will Deacon
2014-02-18 19:57               ` Will Deacon
2014-02-18 20:19                 ` Arnd Bergmann
2014-02-19 10:57                   ` Will Deacon
2014-02-18 20:15       ` Arnd Bergmann
2014-02-19 10:54         ` Will Deacon

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=20140218154139.GF21483@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).