From: Stafford Horne <shorne@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Stafford Horne <shorne@gmail.com>,
Guo Ren <guoren@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Pierre Morel <pmorel@linux.ibm.com>,
linux-csky@vger.kernel.org
Subject: [PATCH v6 3/4] csky: PCI: Define ARCH_GENERIC_PCI_MMAP_RESOURCE
Date: Sat, 23 Jul 2022 06:49:43 +0900 [thread overview]
Message-ID: <20220722214944.831438-4-shorne@gmail.com> (raw)
In-Reply-To: <20220722214944.831438-1-shorne@gmail.com>
This looks to be something that was left out on accident on the csky
port. Add the definition of ARCH_GENERIC_PCI_MMAP_RESOURCE to keep it
inline with other ports. Adding ARCH_GENERIC_PCI_MMAP_RESOURCE enables
the definition of mordern pci_mmap_resource_range functions which is
generally what new ports should be using.
Acked-by: Guo Ren <guoren@kernel.org>
Signed-off-by: Stafford Horne <shorne@gmail.com>
---
arch/csky/include/asm/pci.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/csky/include/asm/pci.h b/arch/csky/include/asm/pci.h
index 5c02454ec724..875bc028f8f6 100644
--- a/arch/csky/include/asm/pci.h
+++ b/arch/csky/include/asm/pci.h
@@ -15,6 +15,8 @@
/* C-SKY shim does not initialize PCI bus */
#define pcibios_assign_all_busses() 1
+#define ARCH_GENERIC_PCI_MMAP_RESOURCE 1
+
#ifdef CONFIG_PCI
static inline int pci_proc_domain(struct pci_bus *bus)
{
--
2.36.1
next prev parent reply other threads:[~2022-07-22 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 21:49 [PATCH v6 0/4] Cleanups for asm-generic/pci.h Stafford Horne
2022-07-22 21:49 ` [PATCH v6 1/4] PCI: Remove pci_get_legacy_ide_irq and asm-generic/pci.h Stafford Horne
2022-07-22 23:38 ` Bjorn Helgaas
2022-07-22 23:51 ` Stafford Horne
2022-07-23 18:28 ` Rolf Eike Beer
2022-07-22 21:49 ` [PATCH v6 2/4] PCI: Move isa_dma_bridge_buggy out of dma.h Stafford Horne
2022-07-22 21:49 ` Stafford Horne [this message]
2022-07-22 21:49 ` [PATCH v6 4/4] asm-generic: Add new pci.h and use it Stafford Horne
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=20220722214944.831438-4-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmorel@linux.ibm.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