From: Murali Karicheri <m-karicheri2@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: bhelgaas@google.com, linux-arm-kernel@lists.infradead.org,
joro@8bytes.org, grant.likely@linaro.org, robh+dt@kernel.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
will.deacon@arm.com, linux@arm.linux.org.uk
Subject: Re: [PATCH v3 0/4] PCI: get DMA configuration from parent device
Date: Thu, 8 Jan 2015 17:46:31 -0500 [thread overview]
Message-ID: <54AF08C7.2010100@ti.com> (raw)
In-Reply-To: <2785994.gTZ9chGdKf@wuerfel>
On 01/08/2015 05:27 PM, Arnd Bergmann wrote:
> On Thursday 08 January 2015 09:56:39 Arnd Bergmann wrote:
>> There is another interesting case, which is a USB host controller or
>> something similar behind a PCI bus. These are quite common and also
>> need to be handled in some form. Let's do just PCI first for now, but
>> be aware that this will come next. Should we assume that the ID that
>> is required for a device is either known from the device node, or
>> that it comes from a PCI device? That means for the USB case, we will
>> likely need to have some custom logic. There seems to be an implicit
>> assumption all over the kernel that all devices have the same IOMMU
>> instance, but we can't really rely on that here.
>>
>
> Update: I've checked the USB implementation and we are lucky because
> these interactions are all done by the USB host controller, and a
> USB device is not itself DMA capable. We don't have to do anything
> for USB.
Ok Thanks.
Murali
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Murali Karicheri
Linux Kernel, Texas Instruments
WARNING: multiple messages have this Message-ID (diff)
From: Murali Karicheri <m-karicheri2@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <bhelgaas@google.com>, <linux-arm-kernel@lists.infradead.org>,
<joro@8bytes.org>, <grant.likely@linaro.org>,
<robh+dt@kernel.org>, <iommu@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <will.deacon@arm.com>,
<linux@arm.linux.org.uk>
Subject: Re: [PATCH v3 0/4] PCI: get DMA configuration from parent device
Date: Thu, 8 Jan 2015 17:46:31 -0500 [thread overview]
Message-ID: <54AF08C7.2010100@ti.com> (raw)
In-Reply-To: <2785994.gTZ9chGdKf@wuerfel>
On 01/08/2015 05:27 PM, Arnd Bergmann wrote:
> On Thursday 08 January 2015 09:56:39 Arnd Bergmann wrote:
>> There is another interesting case, which is a USB host controller or
>> something similar behind a PCI bus. These are quite common and also
>> need to be handled in some form. Let's do just PCI first for now, but
>> be aware that this will come next. Should we assume that the ID that
>> is required for a device is either known from the device node, or
>> that it comes from a PCI device? That means for the USB case, we will
>> likely need to have some custom logic. There seems to be an implicit
>> assumption all over the kernel that all devices have the same IOMMU
>> instance, but we can't really rely on that here.
>>
>
> Update: I've checked the USB implementation and we are lucky because
> these interactions are all done by the USB host controller, and a
> USB device is not itself DMA capable. We don't have to do anything
> for USB.
Ok Thanks.
Murali
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Murali Karicheri
Linux Kernel, Texas Instruments
WARNING: multiple messages have this Message-ID (diff)
From: m-karicheri2@ti.com (Murali Karicheri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] PCI: get DMA configuration from parent device
Date: Thu, 8 Jan 2015 17:46:31 -0500 [thread overview]
Message-ID: <54AF08C7.2010100@ti.com> (raw)
In-Reply-To: <2785994.gTZ9chGdKf@wuerfel>
On 01/08/2015 05:27 PM, Arnd Bergmann wrote:
> On Thursday 08 January 2015 09:56:39 Arnd Bergmann wrote:
>> There is another interesting case, which is a USB host controller or
>> something similar behind a PCI bus. These are quite common and also
>> need to be handled in some form. Let's do just PCI first for now, but
>> be aware that this will come next. Should we assume that the ID that
>> is required for a device is either known from the device node, or
>> that it comes from a PCI device? That means for the USB case, we will
>> likely need to have some custom logic. There seems to be an implicit
>> assumption all over the kernel that all devices have the same IOMMU
>> instance, but we can't really rely on that here.
>>
>
> Update: I've checked the USB implementation and we are lucky because
> these interactions are all done by the USB host controller, and a
> USB device is not itself DMA capable. We don't have to do anything
> for USB.
Ok Thanks.
Murali
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Murali Karicheri
Linux Kernel, Texas Instruments
next prev parent reply other threads:[~2015-01-08 22:46 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 18:49 [PATCH v3 0/4] PCI: get DMA configuration from parent device Murali Karicheri
2015-01-07 18:49 ` Murali Karicheri
2015-01-07 18:49 ` Murali Karicheri
2015-01-07 18:49 ` [PATCH v3 2/4] of: move of_dma_configure() to device,c to help re-use Murali Karicheri
2015-01-07 18:49 ` [PATCH v3 2/4] of: move of_dma_configure() to device, c " Murali Karicheri
2015-01-07 18:49 ` [PATCH v3 2/4] of: move of_dma_configure() to device,c " Murali Karicheri
2015-01-07 23:37 ` Rob Herring
2015-01-07 23:37 ` [PATCH v3 2/4] of: move of_dma_configure() to device, c " Rob Herring
[not found] ` <CAL_Jsq+pKeXuGnZV_NYHn6iZgeOs404OPhcUb0FJs=-7j2P1Ug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-08 8:40 ` Arnd Bergmann
2015-01-08 8:40 ` Arnd Bergmann
2015-01-08 8:40 ` [PATCH v3 2/4] of: move of_dma_configure() to device,c " Arnd Bergmann
2015-01-08 19:26 ` Murali Karicheri
2015-01-08 19:26 ` Murali Karicheri
2015-01-08 22:24 ` Arnd Bergmann
2015-01-08 22:24 ` [PATCH v3 2/4] of: move of_dma_configure() to device, c " Arnd Bergmann
2015-01-08 23:44 ` [PATCH v3 2/4] of: move of_dma_configure() to device,c " Murali Karicheri
2015-01-08 23:44 ` Murali Karicheri
2015-01-08 23:44 ` Murali Karicheri
[not found] ` <54AF165F.7070909-l0cyMroinI0@public.gmane.org>
2015-01-09 0:05 ` Arnd Bergmann
2015-01-09 0:05 ` [PATCH v3 2/4] of: move of_dma_configure() to device, c " Arnd Bergmann
2015-01-09 0:05 ` [PATCH v3 2/4] of: move of_dma_configure() to device,c " Arnd Bergmann
2015-01-09 15:34 ` Rob Herring
2015-01-09 15:34 ` [PATCH v3 2/4] of: move of_dma_configure() to device, c " Rob Herring
2015-01-09 15:34 ` [PATCH v3 2/4] of: move of_dma_configure() to device,c " Rob Herring
2015-01-23 18:19 ` Murali Karicheri
2015-01-23 18:19 ` Murali Karicheri
2015-01-23 18:35 ` Rob Herring
2015-01-23 18:35 ` [PATCH v3 2/4] of: move of_dma_configure() to device, c " Rob Herring
2015-01-07 18:49 ` [PATCH v3 3/4] of/pci: add of_pci_dma_configure() update dma configuration Murali Karicheri
2015-01-07 18:49 ` Murali Karicheri
2015-01-07 18:49 ` Murali Karicheri
2015-01-08 16:06 ` Will Deacon
2015-01-08 16:06 ` Will Deacon
2015-01-08 19:52 ` Murali Karicheri
2015-01-08 19:52 ` Murali Karicheri
[not found] ` <54AEDFED.8060008-l0cyMroinI0@public.gmane.org>
2015-01-08 22:25 ` Arnd Bergmann
2015-01-08 22:25 ` Arnd Bergmann
2015-01-08 22:25 ` Arnd Bergmann
2015-01-08 22:46 ` Murali Karicheri
2015-01-08 22:46 ` Murali Karicheri
2015-01-08 22:46 ` Murali Karicheri
2015-01-09 11:32 ` Will Deacon
2015-01-09 11:32 ` Will Deacon
2015-01-07 18:49 ` [PATCH v3 4/4] PCI: update dma configuration from DT Murali Karicheri
2015-01-07 18:49 ` Murali Karicheri
2015-01-07 18:49 ` Murali Karicheri
2015-01-07 21:18 ` [PATCH v3 0/4] PCI: get DMA configuration from parent device Arnd Bergmann
2015-01-07 21:18 ` Arnd Bergmann
2015-01-07 23:04 ` Murali Karicheri
2015-01-07 23:04 ` Murali Karicheri
2015-01-07 23:04 ` Murali Karicheri
[not found] ` <54ADBB89.8070503-l0cyMroinI0@public.gmane.org>
2015-01-08 8:56 ` Arnd Bergmann
2015-01-08 8:56 ` Arnd Bergmann
2015-01-08 8:56 ` Arnd Bergmann
2015-01-08 15:54 ` Will Deacon
2015-01-08 15:54 ` Will Deacon
2015-01-08 15:54 ` Will Deacon
2015-01-08 22:27 ` Arnd Bergmann
2015-01-08 22:27 ` Arnd Bergmann
2015-01-08 22:46 ` Murali Karicheri [this message]
2015-01-08 22:46 ` Murali Karicheri
2015-01-08 22:46 ` Murali Karicheri
[not found] ` <1420656594-8908-1-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2015-01-07 18:49 ` [PATCH v3 1/4] of: iommu: add ptr to OF node arg to of_iommu_configure() Murali Karicheri
2015-01-07 18:49 ` Murali Karicheri
2015-01-07 18:49 ` Murali Karicheri
[not found] ` <1420656594-8908-2-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2015-01-07 23:30 ` Rob Herring
2015-01-07 23:30 ` Rob Herring
2015-01-07 23:30 ` Rob Herring
2015-01-08 18:29 ` Murali Karicheri
2015-01-08 18:29 ` Murali Karicheri
2015-01-07 23:05 ` [PATCH v3 0/4] PCI: get DMA configuration from parent device Murali Karicheri
2015-01-07 23:05 ` Murali Karicheri
2015-01-07 23:05 ` Murali Karicheri
[not found] ` <54ADBBCF.8020206-l0cyMroinI0@public.gmane.org>
2015-01-07 23:08 ` Bjorn Helgaas
2015-01-07 23:08 ` Bjorn Helgaas
2015-01-07 23:08 ` Bjorn Helgaas
[not found] ` <CAErSpo46UAn9ckbzrgzAoQbu2D=oyOOL_rO24NWEg_iDLSuCLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-08 15:52 ` Murali Karicheri
2015-01-08 15:52 ` Murali Karicheri
2015-01-08 15:52 ` Murali Karicheri
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=54AF08C7.2010100@ti.com \
--to=m-karicheri2@ti.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.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.