On 10/11/2014 04:37 PM, Arnd Bergmann wrote:
On Friday 10 October 2014 20:04:57 Santosh Shilimkar wrote:
On 10/10/14 5:37 PM, Murali Karicheri wrote:
Based on this, dma configuration parameters get set for the device which
is probed through DT.
As PCI devices are attached to the PCI bus
On 10/11/2014 04:37 PM, Arnd Bergmann wrote:
On Friday 10 October 2014 20:04:57 Santosh Shilimkar wrote:
On 10/10/14 5:37 PM, Murali Karicheri wrote:
Based on this, dma configuration parameters get set for the device which
is probed through DT.
As PCI devices are attached to the PCI bus
On Friday 10 October 2014 20:04:57 Santosh Shilimkar wrote:
> On 10/10/14 5:37 PM, Murali Karicheri wrote:
> > Based on this, dma configuration parameters get set for the device which
> > is probed through DT.
> >
> > As PCI devices are attached to the PCI bus during scan, and we don't
> > have DT
On Friday 10 October 2014 20:04:57 Santosh Shilimkar wrote:
On 10/10/14 5:37 PM, Murali Karicheri wrote:
Based on this, dma configuration parameters get set for the device which
is probed through DT.
As PCI devices are attached to the PCI bus during scan, and we don't
have DT nodes, we
On 10/10/14 5:37 PM, Murali Karicheri wrote:
On 10/10/2014 02:22 PM, Arnd Bergmann wrote:
On Friday 10 October 2014 11:15:37 Murali Karicheri wrote:
@@ -54,6 +55,8 @@ static void __init keystone_init(void)
keystone_pm_runtime_init();
if (platform_nb.notifier_call)
On 10/10/2014 02:22 PM, Arnd Bergmann wrote:
On Friday 10 October 2014 11:15:37 Murali Karicheri wrote:
@@ -54,6 +55,8 @@ static void __init keystone_init(void)
keystone_pm_runtime_init();
if (platform_nb.notifier_call)
bus_register_notifier(_bus_type,_nb);
+
On Friday 10 October 2014 11:15:37 Murali Karicheri wrote:
> @@ -54,6 +55,8 @@ static void __init keystone_init(void)
> keystone_pm_runtime_init();
> if (platform_nb.notifier_call)
> bus_register_notifier(_bus_type, _nb);
> + if (platform_nb.notifier_call)
> +
On 10/10/2014 11:42 AM, Russell King - ARM Linux wrote:
On Fri, Oct 10, 2014 at 11:29:03AM -0400, Santosh Shilimkar wrote:
On 10/10/14 11:15 AM, Murali Karicheri wrote:
When PCI device driver such as that for e1000e tries to set dma mask
using dma_set_mask_and_coherent(), it fails because
On 10/10/14 11:42 AM, Russell King - ARM Linux wrote:
On Fri, Oct 10, 2014 at 11:29:03AM -0400, Santosh Shilimkar wrote:
On 10/10/14 11:15 AM, Murali Karicheri wrote:
When PCI device driver such as that for e1000e tries to set dma mask
using dma_set_mask_and_coherent(), it fails because
On Fri, Oct 10, 2014 at 11:29:03AM -0400, Santosh Shilimkar wrote:
>
>
> On 10/10/14 11:15 AM, Murali Karicheri wrote:
>> When PCI device driver such as that for e1000e tries to set dma mask
>> using dma_set_mask_and_coherent(), it fails because the dma_pfn_offset
>> is incorrect on a Keystone
On 10/10/14 11:15 AM, Murali Karicheri wrote:
When PCI device driver such as that for e1000e tries to set dma mask
using dma_set_mask_and_coherent(), it fails because the dma_pfn_offset
is incorrect on a Keystone SoC. This patch fix this by adding a bus
notifier to set this correctly for PCI
When PCI device driver such as that for e1000e tries to set dma mask
using dma_set_mask_and_coherent(), it fails because the dma_pfn_offset
is incorrect on a Keystone SoC. This patch fix this by adding a bus
notifier to set this correctly for PCI devices.
Signed-off-by: Murali Karicheri
---
When PCI device driver such as that for e1000e tries to set dma mask
using dma_set_mask_and_coherent(), it fails because the dma_pfn_offset
is incorrect on a Keystone SoC. This patch fix this by adding a bus
notifier to set this correctly for PCI devices.
Signed-off-by: Murali Karicheri
On 10/10/14 11:15 AM, Murali Karicheri wrote:
When PCI device driver such as that for e1000e tries to set dma mask
using dma_set_mask_and_coherent(), it fails because the dma_pfn_offset
is incorrect on a Keystone SoC. This patch fix this by adding a bus
notifier to set this correctly for PCI
On Fri, Oct 10, 2014 at 11:29:03AM -0400, Santosh Shilimkar wrote:
On 10/10/14 11:15 AM, Murali Karicheri wrote:
When PCI device driver such as that for e1000e tries to set dma mask
using dma_set_mask_and_coherent(), it fails because the dma_pfn_offset
is incorrect on a Keystone SoC. This
On 10/10/14 11:42 AM, Russell King - ARM Linux wrote:
On Fri, Oct 10, 2014 at 11:29:03AM -0400, Santosh Shilimkar wrote:
On 10/10/14 11:15 AM, Murali Karicheri wrote:
When PCI device driver such as that for e1000e tries to set dma mask
using dma_set_mask_and_coherent(), it fails because
On 10/10/2014 11:42 AM, Russell King - ARM Linux wrote:
On Fri, Oct 10, 2014 at 11:29:03AM -0400, Santosh Shilimkar wrote:
On 10/10/14 11:15 AM, Murali Karicheri wrote:
When PCI device driver such as that for e1000e tries to set dma mask
using dma_set_mask_and_coherent(), it fails because
On Friday 10 October 2014 11:15:37 Murali Karicheri wrote:
@@ -54,6 +55,8 @@ static void __init keystone_init(void)
keystone_pm_runtime_init();
if (platform_nb.notifier_call)
bus_register_notifier(platform_bus_type, platform_nb);
+ if
On 10/10/2014 02:22 PM, Arnd Bergmann wrote:
On Friday 10 October 2014 11:15:37 Murali Karicheri wrote:
@@ -54,6 +55,8 @@ static void __init keystone_init(void)
keystone_pm_runtime_init();
if (platform_nb.notifier_call)
On 10/10/14 5:37 PM, Murali Karicheri wrote:
On 10/10/2014 02:22 PM, Arnd Bergmann wrote:
On Friday 10 October 2014 11:15:37 Murali Karicheri wrote:
@@ -54,6 +55,8 @@ static void __init keystone_init(void)
keystone_pm_runtime_init();
if (platform_nb.notifier_call)
20 matches
Mail list logo
