From: hauke@hauke-m.de (Hauke Mehrtens)
To: linux-arm-kernel@lists.infradead.org
Subject: PCIe host controller without IO port access.
Date: Mon, 03 Nov 2014 00:37:08 +0100 [thread overview]
Message-ID: <5456C024.4060103@hauke-m.de> (raw)
Hi,
I am currently writing a driver for a PCIe host controller which does
not support IO port access.
My plan was to only provide IORESOURCE_MEM to pci_sys_data->resources,
but then it allocates some generic IORESOURCE_IO memory in
arch/arm/kernel/bios32.c:pcibios_init_resources(). This will work for
the fist PCIe controller, but when the second controller gets registered
I am getting this: "unable to allocate I/O port region (-16)".
Is there an example for an arm driver for a PCIe controller which does
not support IO port access?
Should I change arch/arm/kernel/bios32.c in a way so that it would
ignore the io port mem?
Hauke
next reply other threads:[~2014-11-02 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 23:37 Hauke Mehrtens [this message]
2014-11-03 17:41 ` PCIe host controller without IO port access Bjorn Helgaas
2014-11-03 22:00 ` Rob Herring
2014-11-03 23:08 ` Hauke Mehrtens
2014-11-04 10:19 ` 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=5456C024.4060103@hauke-m.de \
--to=hauke@hauke-m.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