[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56BBA80E.6090205@amd.com>
Date: Thu, 11 Feb 2016 04:13:50 +0700
From: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>
To: Arnd Bergmann <arnd@...db.de>
CC: <robh+dt@...nel.org>, <pawel.moll@....com>, <mark.rutland@....com>,
<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <arm@...nel.org>,
<brijeshkumar.singh@....com>, <thomas.lendacky@....com>,
<leo.duran@....com>
Subject: Re: [PATCH V2 03/12] dtb: amd: Fix DMA ranges in device tree
Hi Arnd,
On 2/9/16 21:57, Arnd Bergmann wrote:
> On Monday 08 February 2016 11:59:08 Suravee Suthikulpanit wrote:
>> From: Suravee Suthikulpanit <suravee.suthikulpanit@....com>
>>
>> Fix DMA ranges of smb0 and pcie0 nodes in AMD Seattle SOC.
>>
>> Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@....com>
>>
>
> This could use a changelog text to explain why it's broken and how the
> fix works.
>
> Arnd
>
So, I have not experience the breakage. However, IIUC, the GICv2m MSI
frame is also considered DMA-able. So, I think it should be included in
the dma-range specified here. Please let me know if my assumption is
incorrect. Otherwise, I will include more description in the commit log
in my next rev.
Thanks,
Suravee
Powered by blists - more mailing lists