From: Murali Karicheri <m-karicheri2@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
<linux-pci@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Krzysztof Halasa <khalasa@piap.pl>,
Phil Edworthy <phil.edworthy@renesas.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Jingoo Han <jg1.han@samsung.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Russell King <linux@arm.linux.org.uk>,
Mohit Kumar <mohit.kumar@st.com>
Subject: Re: [PATCH v3 0/2] arm: pcibios: remove pci_sys_data domain
Date: Fri, 19 Dec 2014 10:22:44 -0500 [thread overview]
Message-ID: <549442C4.1030302@ti.com> (raw)
In-Reply-To: <14802556.IUBqXXJ43p@wuerfel>
On 12/18/2014 06:25 PM, Arnd Bergmann wrote:
> On Thursday 18 December 2014 18:12:58 Murali Karicheri wrote:
>>
>> I am assuming this is transparent to the user drivers of designware core
>> such as pci-keystone as CONFIG_PCI_DOMAINS_GENERIC is enabled by default
>> by ARM. Is this true ?
>
> One difference is that you can now specify the domain number in DT,
> but if you don't do that, it should behave exactly as befor.
>
> Arnd
Arnd,
Great! Thanks.
--
Murali Karicheri
Linux Kernel, Texas Instruments
next prev parent reply other threads:[~2014-12-19 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 11:29 [PATCH v3 0/2] arm: pcibios: remove pci_sys_data domain Lorenzo Pieralisi
2014-11-21 11:29 ` [PATCH v3 1/2] arm: cns3xxx: pci: remove artificial dependency on " Lorenzo Pieralisi
2014-11-21 11:29 ` [PATCH v3 2/2] arm: pcibios: move to generic PCI domains Lorenzo Pieralisi
2014-12-16 0:18 ` Jason Gunthorpe
2014-12-15 23:52 ` [PATCH v3 0/2] arm: pcibios: remove pci_sys_data domain Bjorn Helgaas
2014-12-15 23:56 ` Bjorn Helgaas
2014-12-16 0:08 ` Russell King - ARM Linux
2014-12-16 0:35 ` Bjorn Helgaas
2014-12-18 23:12 ` Murali Karicheri
2014-12-18 23:25 ` Arnd Bergmann
2014-12-19 15:22 ` Murali Karicheri [this message]
2014-12-19 9:19 ` Lorenzo Pieralisi
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=549442C4.1030302@ti.com \
--to=m-karicheri2@ti.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=jg1.han@samsung.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=khalasa@piap.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=mohit.kumar@st.com \
--cc=phil.edworthy@renesas.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;
as well as URLs for NNTP newsgroup(s).