From: Will Deacon <will.deacon@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"jgunthorpe@obsidianresearch.com"
<jgunthorpe@obsidianresearch.com>
Subject: Re: [PATCH v3 3/3] PCI: ARM: add support for generic PCI host controller
Date: Tue, 18 Feb 2014 19:10:23 +0000 [thread overview]
Message-ID: <20140218191023.GG2010@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <2340480.VAU4NNbBD8@wuerfel>
On Tue, Feb 18, 2014 at 01:46:44PM +0000, Arnd Bergmann wrote:
> On Tuesday 18 February 2014 12:20:43 Will Deacon wrote:
>
> > +static int gen_pci_alloc_io_offset(u32 sz, resource_size_t *offset)
> > +{
> > + static DECLARE_BITMAP(io_map, (IO_SPACE_LIMIT + 1) / SZ_64K);
> > + int idx, num_wins;
> > +
> > + if (sz > SZ_64K)
> > + return -ENOSPC;
> > +
> > + num_wins = (IO_SPACE_LIMIT + 1) / SZ_64K;
> > + idx = 0;
> > + do {
> > + idx = find_next_zero_bit(io_map, num_wins, idx);
> > + if (idx == num_wins)
> > + return -ENOSPC;
> > + } while (test_and_set_bit(idx, io_map));
> > +
> > + *offset = idx * SZ_64K;
> > + return 0;
> > +}
>
> Sicne you're always starting the search at 0 and you never free
> the map, this is essentially the same as remembering the last number
> that was used and using the next one, right?
Yes, I can implement that easily enough. I was wondering if there was a case
for allowing windows to be freed, but it doesn't feel especially compelling.
> You should also pass the rang->pci_addr here to calculate the
> offset in case the pci_addr is not zero.
>
> > + /* Register our I/O and Memory resources */
> > + res_valid = 0;
> > + list_for_each_entry(win, &pci->host.windows, list) {
> > + struct resource *parent;
> > +
> > + if (resource_type(win->res) == IORESOURCE_IO) {
> > + parent = &ioport_resource;
> > + err = pci_ioremap_io(win->offset, win->res->start);
>
> and consequently pass the pci_addr rather than the offset here. How about
> moving the pci_ioremap_io() call into gen_pci_alloc_io_offset()?
Can do.
Thanks for the feedback.
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] PCI: ARM: add support for generic PCI host controller
Date: Tue, 18 Feb 2014 19:10:23 +0000 [thread overview]
Message-ID: <20140218191023.GG2010@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <2340480.VAU4NNbBD8@wuerfel>
On Tue, Feb 18, 2014 at 01:46:44PM +0000, Arnd Bergmann wrote:
> On Tuesday 18 February 2014 12:20:43 Will Deacon wrote:
>
> > +static int gen_pci_alloc_io_offset(u32 sz, resource_size_t *offset)
> > +{
> > + static DECLARE_BITMAP(io_map, (IO_SPACE_LIMIT + 1) / SZ_64K);
> > + int idx, num_wins;
> > +
> > + if (sz > SZ_64K)
> > + return -ENOSPC;
> > +
> > + num_wins = (IO_SPACE_LIMIT + 1) / SZ_64K;
> > + idx = 0;
> > + do {
> > + idx = find_next_zero_bit(io_map, num_wins, idx);
> > + if (idx == num_wins)
> > + return -ENOSPC;
> > + } while (test_and_set_bit(idx, io_map));
> > +
> > + *offset = idx * SZ_64K;
> > + return 0;
> > +}
>
> Sicne you're always starting the search at 0 and you never free
> the map, this is essentially the same as remembering the last number
> that was used and using the next one, right?
Yes, I can implement that easily enough. I was wondering if there was a case
for allowing windows to be freed, but it doesn't feel especially compelling.
> You should also pass the rang->pci_addr here to calculate the
> offset in case the pci_addr is not zero.
>
> > + /* Register our I/O and Memory resources */
> > + res_valid = 0;
> > + list_for_each_entry(win, &pci->host.windows, list) {
> > + struct resource *parent;
> > +
> > + if (resource_type(win->res) == IORESOURCE_IO) {
> > + parent = &ioport_resource;
> > + err = pci_ioremap_io(win->offset, win->res->start);
>
> and consequently pass the pci_addr rather than the offset here. How about
> moving the pci_ioremap_io() call into gen_pci_alloc_io_offset()?
Can do.
Thanks for the feedback.
Will
next prev parent reply other threads:[~2014-02-18 19:10 UTC|newest]
Thread overview: 60+ 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 ` 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 ` 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 12:20 ` Will Deacon
2014-02-18 15:41 ` Russell King - ARM Linux
2014-02-18 15:41 ` Russell King - ARM Linux
2014-02-18 19:10 ` Will Deacon
2014-02-18 19:10 ` Will Deacon
2014-02-20 11:12 ` Will Deacon
2014-02-20 11:12 ` Will Deacon
2014-02-20 19:39 ` Bjorn Helgaas
2014-02-20 19:39 ` Bjorn Helgaas
2014-02-21 0:36 ` Jason Gunthorpe
2014-02-21 0:36 ` Jason Gunthorpe
2014-02-21 13:49 ` Will Deacon
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 12:20 ` Will Deacon
2014-02-18 13:46 ` Arnd Bergmann
2014-02-18 13:46 ` Arnd Bergmann
2014-02-18 19:10 ` Will Deacon [this message]
2014-02-18 19:10 ` Will Deacon
2014-02-19 11:07 ` Will Deacon
2014-02-19 11:07 ` Will Deacon
2014-02-19 14:17 ` Arnd Bergmann
2014-02-19 14:17 ` Arnd Bergmann
2014-02-19 15:25 ` Will Deacon
2014-02-19 15:25 ` Will Deacon
2014-02-18 18:21 ` Jason Gunthorpe
2014-02-18 18:21 ` Jason Gunthorpe
2014-02-18 18:44 ` Will Deacon
2014-02-18 18:44 ` Will Deacon
2014-02-18 18:47 ` Arnd Bergmann
2014-02-18 18:47 ` Arnd Bergmann
2014-02-18 18:51 ` Will Deacon
2014-02-18 18:51 ` Will Deacon
2014-02-18 19:11 ` Arnd Bergmann
2014-02-18 19:11 ` Arnd Bergmann
2014-02-18 19:16 ` Will Deacon
2014-02-18 19:16 ` Will Deacon
2014-02-18 18:59 ` Jason Gunthorpe
2014-02-18 18:59 ` Jason Gunthorpe
2014-02-18 19:09 ` Will Deacon
2014-02-18 19:09 ` Will Deacon
2014-02-18 19:32 ` Arnd Bergmann
2014-02-18 19:32 ` Arnd Bergmann
2014-02-18 19:36 ` Will Deacon
2014-02-18 19:36 ` Will Deacon
2014-02-18 19:57 ` Will Deacon
2014-02-18 19:57 ` Will Deacon
2014-02-18 20:19 ` Arnd Bergmann
2014-02-18 20:19 ` Arnd Bergmann
2014-02-19 10:57 ` Will Deacon
2014-02-19 10:57 ` Will Deacon
2014-02-18 20:15 ` Arnd Bergmann
2014-02-18 20:15 ` Arnd Bergmann
2014-02-19 10:54 ` Will Deacon
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=20140218191023.GG2010@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.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.