From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752127AbcHHIGk (ORCPT ); Mon, 8 Aug 2016 04:06:40 -0400 Received: from mga03.intel.com ([134.134.136.65]:32720 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751158AbcHHIGi (ORCPT ); Mon, 8 Aug 2016 04:06:38 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,489,1464678000"; d="scan'208";a="1010302142" Date: Mon, 8 Aug 2016 13:44:15 +0530 From: Vinod Koul To: Sinan Kaya Cc: "dmaengine@vger.kernel.org" , "timur@codeaurora.org" , "devicetree@vger.kernel.org" , "cov@codeaurora.org" , "jcm@redhat.com" , "eric.auger@linaro.org" , "agross@codeaurora.org" , "arnd@arndb.de" , "linux-arm-msm@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "Williams, Dan J" , Andy Shevchenko , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 10/10] dmaengine: qcom_hidma: add MSI support for interrupts Message-ID: <20160808081415.GV9681@localhost> References: <1468867177-15007-1-git-send-email-okaya@codeaurora.org> <1468867177-15007-11-git-send-email-okaya@codeaurora.org> <20160724064256.GA9681@localhost> <20160804124641.GE9681@localhost> <497ddb6c-0233-657f-72c6-b844b798ff11@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <497ddb6c-0233-657f-72c6-b844b798ff11@codeaurora.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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