All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	arnd@arndb.de, linux-arch@vger.kernel.org
Cc: mingo@kernel.org, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com, linux-s390@vger.kernel.org,
	bp@suse.de, linux@roeck-us.net, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, rostedt@goodmis.org,
	"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit
Date: Fri, 28 Aug 2015 19:13:08 -0700	[thread overview]
Message-ID: <55E11534.2050508@infradead.org> (raw)
In-Reply-To: <1440807447-584-1-git-send-email-mcgrof@do-not-panic.com>

On 08/28/15 17:17, Luis R. Rodriguez wrote:
> 
>  arch/s390/Kconfig                 |  8 +++++
>  arch/s390/include/asm/io.h        | 11 -------
>  arch/s390/include/asm/pci.h       |  2 --
>  arch/s390/include/asm/pci_iomap.h | 33 +++++++++++++++++++++
>  arch/s390/pci/pci.c               |  2 ++
>  include/asm-generic/io.h          | 12 --------
>  include/asm-generic/iomap.h       | 10 -------
>  include/asm-generic/pci_iomap.h   | 62 +++++++++++++++++++++++++++++++++++----
>  lib/Kconfig                       |  1 +
>  lib/pci_iomap.c                   |  5 ++++
>  10 files changed, 105 insertions(+), 41 deletions(-)
>  create mode 100644 arch/s390/include/asm/pci_iomap.h
> 
> diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
> index 1d57000b1b24..1217b7db4265 100644
> --- a/arch/s390/Kconfig
> +++ b/arch/s390/Kconfig
> @@ -614,6 +614,14 @@ endif	# PCI
>  config PCI_DOMAINS
>  	def_bool PCI
>  
> +config ARCH_PCI_NON_DISJUNCTIVE
> +	def_bool PCI
> +	help
> +	  On the S390 architecture PCI BAR spaces are not disjunctive, as such

	are not disjoint?  may be overlapping?

> +	  the PCI bar is required on a series of otherwise asm generic PCI
> +	  routines, as such S390 requires itw own implemention for these

	                                  its own implementation

> +	  routines.
> +
>  config HAS_IOMEM
>  	def_bool PCI
>  


-- 
~Randy

  reply	other threads:[~2015-08-29  2:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-29  0:17 [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit Luis R. Rodriguez
2015-08-29  2:13 ` Randy Dunlap [this message]
2015-10-02 23:17   ` Luis R. Rodriguez
2015-10-04  0:14     ` Randy Dunlap
2015-10-05 16:58       ` Luis R. Rodriguez
2015-08-29 15:25 ` Christoph Hellwig
2015-09-03  1:45   ` Luis R. Rodriguez
2015-08-30 19:30 ` Arnd Bergmann
2015-09-03  1:44   ` Luis R. Rodriguez
2015-09-03  1:47     ` Luis R. Rodriguez
2015-09-08  9:54       ` Luis R. Rodriguez
2015-09-08 13:42     ` Arnd Bergmann
2015-09-11  8:14       ` Martin Schwidefsky
2015-10-03  0:04         ` Luis R. Rodriguez
2015-10-02 23:53       ` Luis R. Rodriguez
2015-10-04 19:02         ` Arnd Bergmann
2015-10-05 17:09           ` Luis R. Rodriguez
2015-10-06 11:15             ` Martin Schwidefsky

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=55E11534.2050508@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bp@suse.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mcgrof@do-not-panic.com \
    --cc=mcgrof@suse.com \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=schwidefsky@de.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 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.