All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Liviu.Dudau@arm.com" <Liviu.Dudau@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	nofooter <nofooter@xilinx.com>,
	"thomas.petazzoni@free-electrons.com" 
	<thomas.petazzoni@free-electrons.com>
Subject: Re: Purpose of pci_remap_iospace
Date: Wed, 13 Jul 2016 16:42:12 +0100	[thread overview]
Message-ID: <20160713154212.GN8609@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <27194299.uDJcp1GxUD@wuerfel>

On Wed, Jul 13, 2016 at 05:28:47PM +0200, Arnd Bergmann wrote:
> On Wednesday, July 13, 2016 3:16:21 PM CEST Bharat Kumar Gogada wrote:
> > 
> > > This has neither the PCI memory nor the I/O resource, it looks like you never
> > > call pci_add_resource_offset() to start with, or maybe it fails for some
> > > reason.
> > 
> > I see that above API is used in ARM drivers, do we need to do it in ARM64 also ?
> > 
> 
> Yes, all architectures need it.

of_pci_get_host_bridge_resources() calls it for him.

Liviu

> 
> 	Arnd
> 

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯

  reply	other threads:[~2016-07-13 15:42 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12  6:57 Purpose of pci_remap_iospace Bharat Kumar Gogada
2016-07-12  6:57 ` Bharat Kumar Gogada
2016-07-12  8:31 ` Arnd Bergmann
2016-07-12  8:31   ` Arnd Bergmann
2016-07-12  8:40   ` Bharat Kumar Gogada
2016-07-12  8:40     ` Bharat Kumar Gogada
2016-07-13  8:11   ` Bharat Kumar Gogada
2016-07-13  8:11     ` Bharat Kumar Gogada
2016-07-13  8:30     ` Arnd Bergmann
2016-07-13  8:30       ` Arnd Bergmann
2016-07-13 12:30       ` Bharat Kumar Gogada
2016-07-13 12:30         ` Bharat Kumar Gogada
2016-07-13 13:28         ` Arnd Bergmann
2016-07-13 13:28           ` Arnd Bergmann
2016-07-13 15:16           ` Bharat Kumar Gogada
2016-07-13 15:16             ` Bharat Kumar Gogada
2016-07-13 15:28             ` Arnd Bergmann
2016-07-13 15:28               ` Arnd Bergmann
2016-07-13 15:42               ` Liviu.Dudau [this message]
2016-07-13 15:42                 ` Liviu.Dudau
2016-07-13 16:13             ` Lorenzo Pieralisi
2016-07-13 16:13               ` Lorenzo Pieralisi
2016-07-13 13:46         ` Lorenzo Pieralisi
2016-07-13 13:46           ` Lorenzo Pieralisi
2016-07-14  6:03           ` Bharat Kumar Gogada
2016-07-14  6:03             ` Bharat Kumar Gogada
2016-07-14 13:32           ` Bharat Kumar Gogada
2016-07-14 13:32             ` Bharat Kumar Gogada
2016-07-14 14:56             ` Lorenzo Pieralisi
2016-07-14 14:56               ` Lorenzo Pieralisi
2016-07-14 15:05               ` Bharat Kumar Gogada
2016-07-14 15:05                 ` Bharat Kumar Gogada
2016-07-14 15:20                 ` Lorenzo Pieralisi
2016-07-14 15:20                   ` Lorenzo Pieralisi
2016-07-14 15:12               ` Arnd Bergmann
2016-07-14 15:12                 ` Arnd Bergmann
2016-07-14 15:27                 ` Lorenzo Pieralisi
2016-07-14 15:27                   ` Lorenzo Pieralisi
2016-07-15  5:21               ` Bharat Kumar Gogada
2016-07-15  5:21                 ` Bharat Kumar Gogada
2016-07-15  6:55                 ` Arnd Bergmann
2016-07-15  6:55                   ` Arnd Bergmann
2016-07-15  6:55                   ` Arnd Bergmann
2016-07-13 13:24     ` Liviu.Dudau
2016-07-13 13:24       ` 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=20160713154212.GN8609@e106497-lin.cambridge.arm.com \
    --to=liviu.dudau@arm.com \
    --cc=arnd@arndb.de \
    --cc=bharat.kumar.gogada@xilinx.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=nofooter@xilinx.com \
    --cc=thomas.petazzoni@free-electrons.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.