[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <497ddb6c-0233-657f-72c6-b844b798ff11@codeaurora.org>
Date: Thu, 4 Aug 2016 09:59:43 -0400
From: Sinan Kaya <okaya@...eaurora.org>
To: Vinod Koul <vinod.koul@...el.com>
Cc: "dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
"timur@...eaurora.org" <timur@...eaurora.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"cov@...eaurora.org" <cov@...eaurora.org>,
"jcm@...hat.com" <jcm@...hat.com>,
"eric.auger@...aro.org" <eric.auger@...aro.org>,
"agross@...eaurora.org" <agross@...eaurora.org>,
"arnd@...db.de" <arnd@...db.de>,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"Williams, Dan J" <dan.j.williams@...el.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 10/10] dmaengine: qcom_hidma: add MSI support for
interrupts
On 8/4/2016 8:46 AM, Vinod Koul wrote:
>> > Yes, I do have a new device ID for platforms with MSI capability.
>> >
>> > Which new binding are you referring to?
> If you have "QCOM8062" why do you need DT to tell hidma-1.1 ?
Unfortunately, DT cannot do a binding with the ACPI names. Similarly, ACPI
cannot do a binding with the DT name.
The structure of binding name is also subject to different kind of rules
for DT and ACPI.
This driver supports both device tree and ACPI. That's why, two different
names are required.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
Powered by blists - more mailing lists