All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linaro-kernel@lists.linaro.org
Cc: Liviu Dudau <Liviu.Dudau@arm.com>,
	linux-pci <linux-pci@vger.kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Will Deacon <Will.Deacon@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/3] Fix ioport_map() for !CONFIG_GENERIC_IOMAP cases.
Date: Thu, 27 Feb 2014 15:09:28 +0100	[thread overview]
Message-ID: <5331963.VjH27eqhpK@wuerfel> (raw)
In-Reply-To: <1393506599-11561-2-git-send-email-Liviu.Dudau@arm.com>

On Thursday 27 February 2014 13:09:57 Liviu Dudau wrote:
> The inline version of ioport_map() that gets used when !CONFIG_GENERIC_IOMAP
> is wrong. It returns a mapped (i.e. virtual) address that can start from
> zero and completely ignores the PCI_IOBASE and IO_SPACE_LIMIT that most
> architectures that use !CONFIG_GENERIC_MAP define.
> 
> Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> 
> 

Acked-by: Arnd Bergmann <arnd@arndb.de>

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] Fix ioport_map() for !CONFIG_GENERIC_IOMAP cases.
Date: Thu, 27 Feb 2014 15:09:28 +0100	[thread overview]
Message-ID: <5331963.VjH27eqhpK@wuerfel> (raw)
In-Reply-To: <1393506599-11561-2-git-send-email-Liviu.Dudau@arm.com>

On Thursday 27 February 2014 13:09:57 Liviu Dudau wrote:
> The inline version of ioport_map() that gets used when !CONFIG_GENERIC_IOMAP
> is wrong. It returns a mapped (i.e. virtual) address that can start from
> zero and completely ignores the PCI_IOBASE and IO_SPACE_LIMIT that most
> architectures that use !CONFIG_GENERIC_MAP define.
> 
> Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> 
> 

Acked-by: Arnd Bergmann <arnd@arndb.de>

  reply	other threads:[~2014-02-27 14:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 13:09 [PATCH v2 0/3] [RFC] Add support for PCI in AArch64 Liviu Dudau
2014-02-27 13:09 ` Liviu Dudau
2014-02-27 13:09 ` [PATCH v2 1/3] Fix ioport_map() for !CONFIG_GENERIC_IOMAP cases Liviu Dudau
2014-02-27 13:09   ` Liviu Dudau
2014-02-27 14:09   ` Arnd Bergmann [this message]
2014-02-27 14:09     ` Arnd Bergmann
2014-02-27 13:09 ` [PATCH v2 2/3] arm64: Extend the PCI I/O space to 16MB Liviu Dudau
2014-02-27 13:09   ` Liviu Dudau
2014-02-28 15:27   ` Catalin Marinas
2014-02-28 15:27     ` Catalin Marinas
2014-02-28 15:27     ` Catalin Marinas
2014-02-27 13:09 ` [PATCH v2 3/3] arm64: Add architecture support for PCI Liviu Dudau
2014-02-27 13:09   ` Liviu Dudau
2014-02-27 13:35   ` Andrew Murray
2014-02-27 13:35     ` Andrew Murray
2014-02-27 13:35     ` Andrew Murray
2014-02-27 13:41     ` Liviu Dudau
2014-02-27 16:06   ` Arnd Bergmann
2014-02-27 16:06     ` Arnd Bergmann
2014-02-27 16:06     ` Arnd Bergmann
2014-02-27 16:48     ` Liviu Dudau
2014-02-27 16:48       ` Liviu Dudau
2014-02-27 16:48       ` Liviu Dudau

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=5331963.VjH27eqhpK@wuerfel \
    --to=arnd@arndb.de \
    --cc=Catalin.Marinas@arm.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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.