From: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>
To: Murali Karicheri <m-karicheri2-l0cyMroinI0@public.gmane.org>
Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
"linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Will Deacon <Will.Deacon-5wv7dgnIgG8@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Bjorn Helgaas <bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v6 0/7] PCI: get DMA configuration from parent device
Date: Fri, 6 Feb 2015 15:15:42 +0000 [thread overview]
Message-ID: <20150206151542.GD23190@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1423173179-10227-1-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
On Thu, Feb 05, 2015 at 09:52:52PM +0000, Murali Karicheri wrote:
> This patch add an important capability to PCI driver on Keystone. I hope to
> have this merged to the upstream branch so that it is available for v3.20.
It's very late for 3.20 and the code hasn't been in linux-next at all
(but it's not me who's merging this code), unless you can squeeze it in
as a bug-fix.
But the good part is that there is more time to fix the dma mask setting
as well ;).
> PCI devices on Keystone doesn't have correct dma_pfn_offset set. This patch
> add capability to set the dma configuration such as dma-mask, dma_pfn_offset,
> and dma ops etc using the information from DT. The prior RFCs and discussions
> are available at [1] and [2] below.
For the series, you can add:
Reviewed-by: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>
next prev parent reply other threads:[~2015-02-06 15:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 21:52 [PATCH v6 0/7] PCI: get DMA configuration from parent device Murali Karicheri
[not found] ` <1423173179-10227-1-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2015-02-05 21:52 ` [PATCH v6 1/7] of: iommu: add ptr to OF node arg to of_iommu_configure() Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 2/7] of: move of_dma_configure() to device.c to help re-use Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 3/7] of: fix size when dma-range is not used Murali Karicheri
2015-02-06 14:38 ` Catalin Marinas
2015-02-06 14:54 ` Murali Karicheri
2015-02-06 15:12 ` Catalin Marinas
2015-02-06 20:26 ` Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 4/7] PCI: add helper functions pci_get[put]_host_bridge_device() Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 5/7] of/pci: add of_pci_dma_configure() update dma configuration Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 6/7] PCI: update dma configuration from DT Murali Karicheri
[not found] ` <1423173179-10227-7-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2015-02-25 1:53 ` Bjorn Helgaas
[not found] ` <20150225015317.GO6220-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2015-02-25 16:03 ` Murali Karicheri
2015-02-25 16:09 ` Arnd Bergmann
2015-02-25 20:45 ` Murali Karicheri
2015-02-05 21:52 ` [PATCH v6 7/7] arm: dma-mapping: limit iommu mapping size Murali Karicheri
2015-02-05 21:59 ` [PATCH v6 0/7] PCI: get DMA configuration from parent device Murali Karicheri
2015-02-06 15:15 ` Catalin Marinas [this message]
2015-02-06 15:28 ` Murali Karicheri
2015-02-06 17:53 ` Bjorn Helgaas
[not found] ` <CAErSpo6GOXHeKKfU8s5jCS3+Mui=HupZd=jpkLEyWAE94Ory5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-06 18:36 ` Murali Karicheri
2015-02-11 16:54 ` Murali Karicheri
[not found] ` <54DB8960.9010707-l0cyMroinI0@public.gmane.org>
2015-02-11 16:58 ` Murali Karicheri
2015-02-23 22:08 ` Murali Karicheri
[not found] ` <54EBA4D0.1060705-l0cyMroinI0@public.gmane.org>
2015-02-23 22:15 ` Bjorn Helgaas
[not found] ` <CAErSpo6fWjibM-Lm54ESBpgMUi8w2q6YVzNAK5rHvR4+ydq6ZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-23 22:44 ` Murali Karicheri
2015-02-09 5:48 ` Will Deacon
2015-02-09 5:23 ` Suravee Suthikulpanit
[not found] ` <54D84456.8050509-5C7GfCeVMHo@public.gmane.org>
2015-02-09 17:26 ` Murali Karicheri
2015-02-25 22:20 ` Bjorn Helgaas
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=20150206151542.GD23190@e104818-lin.cambridge.arm.com \
--to=catalin.marinas-5wv7dgnigg8@public.gmane.org \
--cc=Will.Deacon-5wv7dgnIgG8@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=m-karicheri2-l0cyMroinI0@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 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).