On Wed, Mar 29, 2017 at 11:12 PM, Robin Murphy wrote:
> On 29/03/17 06:46, Oza Oza wrote:
>> On Wed, Mar 29, 2017 at 10:23 AM, Oza Oza wrote:
>>> On Wed, Mar 29, 2017 at 12:27 AM, Robin Murphy wrote:
For PCI masters not
On Thu, Mar 30, 2017 at 8:51 AM, Oza Oza wrote:
> On Wed, Mar 29, 2017 at 11:12 PM, Robin Murphy wrote:
>> On 29/03/17 06:46, Oza Oza wrote:
>>> On Wed, Mar 29, 2017 at 10:23 AM, Oza Oza wrote:
On Wed, Mar 29, 2017 at 12:27
On Wed, Mar 29, 2017 at 11:12 PM, Robin Murphy wrote:
> On 29/03/17 06:46, Oza Oza wrote:
>> On Wed, Mar 29, 2017 at 10:23 AM, Oza Oza wrote:
>>> On Wed, Mar 29, 2017 at 12:27 AM, Robin Murphy wrote:
For PCI masters not
On 29/03/17 06:46, Oza Oza wrote:
> On Wed, Mar 29, 2017 at 10:23 AM, Oza Oza wrote:
>> On Wed, Mar 29, 2017 at 12:27 AM, Robin Murphy wrote:
>>> For PCI masters not represented in DT, we pass the OF node of their
>>> associated host bridge to
On Wed, Mar 29, 2017 at 10:23 AM, Oza Oza wrote:
> On Wed, Mar 29, 2017 at 12:27 AM, Robin Murphy wrote:
>> For PCI masters not represented in DT, we pass the OF node of their
>> associated host bridge to of_dma_configure(), such that they can inherit
On Wed, Mar 29, 2017 at 12:27 AM, Robin Murphy wrote:
> For PCI masters not represented in DT, we pass the OF node of their
> associated host bridge to of_dma_configure(), such that they can inherit
> the appropriate DMA configuration from whatever is described there.
>
For PCI masters not represented in DT, we pass the OF node of their
associated host bridge to of_dma_configure(), such that they can inherit
the appropriate DMA configuration from whatever is described there.
Unfortunately, whilst this has worked for the "dma-coherent" property,
it turns out to