From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Kumar Gala <galak@codeaurora.org>,
Rob Herring <robherring2@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: [PATCH 1/2] pci: Add IORESOURCE_BIT entry for PCIe ECAM resources.
Date: Sat, 31 May 2014 01:36:40 +0100 [thread overview]
Message-ID: <1401496601-31983-2-git-send-email-Liviu.Dudau@arm.com> (raw)
In-Reply-To: <1401496601-31983-1-git-send-email-Liviu.Dudau@arm.com>
We would like to be able to describe PCIe ECAM resources as
IORESOURCE_MEM blocks while distinguish them from standard
memory resources. Add an IORESOURCE_BIT entry for this case.
Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
---
include/linux/ioport.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/ioport.h b/include/linux/ioport.h
index 5e3a906..9672533 100644
--- a/include/linux/ioport.h
+++ b/include/linux/ioport.h
@@ -103,6 +103,7 @@ struct resource {
/* PCI control bits. Shares IORESOURCE_BITS with above PCI ROM. */
#define IORESOURCE_PCI_FIXED (1<<4) /* Do not move resource */
+#define IORESOURCE_PCI_ECFG (1<<5) /* ECAM config resource */
/* helpers to define resources */
--
1.9.2
WARNING: multiple messages have this Message-ID (diff)
From: Liviu.Dudau@arm.com (Liviu Dudau)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] pci: Add IORESOURCE_BIT entry for PCIe ECAM resources.
Date: Sat, 31 May 2014 01:36:40 +0100 [thread overview]
Message-ID: <1401496601-31983-2-git-send-email-Liviu.Dudau@arm.com> (raw)
In-Reply-To: <1401496601-31983-1-git-send-email-Liviu.Dudau@arm.com>
We would like to be able to describe PCIe ECAM resources as
IORESOURCE_MEM blocks while distinguish them from standard
memory resources. Add an IORESOURCE_BIT entry for this case.
Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
---
include/linux/ioport.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/ioport.h b/include/linux/ioport.h
index 5e3a906..9672533 100644
--- a/include/linux/ioport.h
+++ b/include/linux/ioport.h
@@ -103,6 +103,7 @@ struct resource {
/* PCI control bits. Shares IORESOURCE_BITS with above PCI ROM. */
#define IORESOURCE_PCI_FIXED (1<<4) /* Do not move resource */
+#define IORESOURCE_PCI_ECFG (1<<5) /* ECAM config resource */
/* helpers to define resources */
--
1.9.2
next prev parent reply other threads:[~2014-05-31 0:36 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 16:03 [PATCH] of: treat PCI config space as IORESOURCE_MEM type Kumar Gala
2014-05-29 16:03 ` Kumar Gala
2014-05-29 20:44 ` Rob Herring
2014-05-29 20:44 ` Rob Herring
2014-05-29 20:44 ` Rob Herring
2014-05-29 20:51 ` Kumar Gala
2014-05-29 20:51 ` Kumar Gala
2014-05-29 20:51 ` Kumar Gala
2014-05-29 21:50 ` Rob Herring
2014-05-29 21:50 ` Rob Herring
2014-05-29 21:50 ` Rob Herring
2014-05-30 0:56 ` Liviu Dudau
2014-05-30 0:56 ` Liviu Dudau
2014-05-30 0:56 ` Liviu Dudau
[not found] ` <20140530005602.GE1677-hOhETlTuV5niMG9XS5x8Mg@public.gmane.org>
2014-05-30 1:29 ` Bjorn Helgaas
2014-05-30 1:29 ` Bjorn Helgaas
2014-05-30 1:29 ` Bjorn Helgaas
2014-05-30 1:29 ` Bjorn Helgaas
2014-05-30 1:41 ` Liviu Dudau
2014-05-30 1:41 ` Liviu Dudau
2014-05-30 1:41 ` Liviu Dudau
2014-05-30 20:37 ` Jason Gunthorpe
2014-05-30 20:37 ` Jason Gunthorpe
2014-05-30 20:37 ` Jason Gunthorpe
2014-05-30 20:44 ` Kumar Gala
2014-05-30 20:44 ` Kumar Gala
2014-05-30 20:44 ` Kumar Gala
2014-05-30 20:45 ` Kumar Gala
2014-05-30 20:45 ` Kumar Gala
2014-05-30 20:45 ` Kumar Gala
2014-05-30 23:11 ` Liviu Dudau
2014-05-30 23:11 ` Liviu Dudau
2014-05-30 23:11 ` Liviu Dudau
2014-05-30 23:16 ` Bjorn Helgaas
2014-05-30 23:16 ` Bjorn Helgaas
2014-05-30 23:16 ` Bjorn Helgaas
2014-05-30 23:30 ` Liviu Dudau
2014-05-30 23:30 ` Liviu Dudau
2014-05-30 23:30 ` Liviu Dudau
2014-05-31 0:36 ` Liviu Dudau
2014-05-31 0:36 ` Liviu Dudau
2014-05-31 0:36 ` Liviu Dudau
2014-05-31 0:36 ` Liviu Dudau [this message]
2014-05-31 0:36 ` [PATCH 1/2] pci: Add IORESOURCE_BIT entry for PCIe ECAM resources Liviu Dudau
2014-05-31 0:36 ` Liviu Dudau
2014-05-31 18:41 ` Arnd Bergmann
2014-05-31 18:41 ` Arnd Bergmann
2014-05-31 18:41 ` Arnd Bergmann
2014-06-01 11:26 ` Liviu Dudau
2014-06-01 11:26 ` Liviu Dudau
2014-06-01 11:26 ` Liviu Dudau
2014-06-02 15:09 ` Grant Likely
2014-06-02 15:09 ` Grant Likely
2014-06-02 15:09 ` Grant Likely
2014-06-02 15:40 ` Kumar Gala
2014-06-02 15:40 ` Kumar Gala
2014-06-02 15:40 ` Kumar Gala
2014-06-02 16:23 ` Grant Likely
2014-06-02 16:23 ` Grant Likely
2014-06-02 16:23 ` Grant Likely
2014-06-02 16:23 ` Grant Likely
2014-06-02 18:09 ` Kumar Gala
2014-06-02 18:09 ` Kumar Gala
2014-06-02 18:09 ` Kumar Gala
2014-06-02 19:15 ` Arnd Bergmann
2014-06-02 19:15 ` Arnd Bergmann
2014-06-02 19:15 ` Arnd Bergmann
2014-06-02 20:43 ` Kumar Gala
2014-06-02 20:43 ` Kumar Gala
2014-06-02 20:43 ` Kumar Gala
2014-06-02 20:44 ` Arnd Bergmann
2014-06-02 20:44 ` Arnd Bergmann
2014-06-02 20:44 ` Arnd Bergmann
2014-06-03 8:44 ` Grant Likely
2014-06-03 8:44 ` Grant Likely
2014-06-03 8:44 ` Grant Likely
2014-06-03 8:44 ` Grant Likely
2014-06-03 9:21 ` Arnd Bergmann
2014-06-03 9:21 ` Arnd Bergmann
2014-06-03 9:21 ` Arnd Bergmann
2014-06-03 11:38 ` Grant Likely
2014-06-03 11:38 ` Grant Likely
2014-06-03 11:38 ` Grant Likely
2014-05-31 0:36 ` [PATCH 2/2] of: treat PCI config space as IORESOURCE_MEM type with special flags Liviu Dudau
2014-05-31 0:36 ` Liviu Dudau
2014-05-31 0:36 ` 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=1401496601-31983-2-git-send-email-Liviu.Dudau@arm.com \
--to=liviu.dudau@arm.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.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.