[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 8 Aug 2016 13:44:15 +0530
From: Vinod Koul <vinod.koul@...el.com>
To: Sinan Kaya <okaya@...eaurora.org>
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 Thu, Aug 04, 2016 at 09:59:43AM -0400, Sinan Kaya wrote:
> 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.
Hmmm, wasn't the who get_property stuff supposed to make properties work on
both ACPi & DT. I am not sure though about the current state of affairs on
that.
--
~Vinod
Powered by blists - more mailing lists