From: "Luck, Tony" <tony.luck@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jchandra@broadcom.com, Sinan Kaya <okaya@codeaurora.org>,
Tomasz Nowicki <tn@semihalf.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Boris Brezillon <boris.brezillon@bootlin.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: how to fix acpi_pci_root_remap_iospace?
Date: Thu, 16 Aug 2018 16:26:40 -0700 [thread overview]
Message-ID: <20180816232639.GA25889@agluck-desk> (raw)
In-Reply-To: <CAK8P3a2vAMzL22ds=kM1WRZgATzOrAz_y8Yk6edqJTVRJJFydw@mail.gmail.com>
On Thu, Aug 16, 2018 at 11:10:33PM +0200, Arnd Bergmann wrote:
> Another way would be to add
>
> #include <asm-generic/io.h>
> +#undef PCI_IOBASE
>
> in your asm/io.h. This is about as ugly as the your version, but
> it would be local to ia64 ;-)
Third way ...
Is "0" actually the right value for PCI_IOBASE for some platform?
#ifndef PCI_IOBASE
#define PCI_IOBASE ((void __iomem *)0)
#endif
Or is this just here to make sure that:
static inline u8 inb(unsigned long addr)
{
u8 val;
__io_pbr();
val = __raw_readb(PCI_IOBASE + addr);
__io_par();
return val;
}
etc. Do not throw errors?
Should we really just enclose all of inb, inw, inl, ...
inside of:
#ifdef PCI_IOBASE
... all those static functions that use PCI_IOBASE ...
#endif
-Tony
next prev parent reply other threads:[~2018-08-16 23:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 20:45 how to fix acpi_pci_root_remap_iospace? Luck, Tony
2018-08-16 21:10 ` Arnd Bergmann
2018-08-16 23:26 ` Luck, Tony [this message]
2018-08-17 8:47 ` Arnd Bergmann
2018-08-17 8:55 ` Boris Brezillon
2018-08-17 15:56 ` Luck, Tony
2018-08-17 16:20 ` Boris Brezillon
2018-08-17 19:01 ` Arnd Bergmann
2018-08-20 16:31 ` [PATCH] ia64: Fix kernel BUG at lib/ioremap.c:72! Tony Luck
2018-08-20 19:23 ` Linus Torvalds
2018-08-17 11:24 ` how to fix acpi_pci_root_remap_iospace? Lorenzo Pieralisi
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=20180816232639.GA25889@agluck-desk \
--to=tony.luck@intel.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=boris.brezillon@bootlin.com \
--cc=jchandra@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=miquel.raynal@bootlin.com \
--cc=okaya@codeaurora.org \
--cc=tn@semihalf.com \
/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).