[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160804124641.GE9681@localhost>
Date: Thu, 4 Aug 2016 18:16:41 +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 Sun, Jul 24, 2016 at 10:38:11AM -0400, Sinan Kaya wrote:
> >> + if (rc)
> >> + dev_warn(&pdev->dev,
> >> + "failed to request MSI irq, falling back to wired IRQ\n");
> >> + return rc;
> >> +#else
> >> + return -EINVAL;
> >
> > -EINVAL doesnt sound apt here..
>
> What should I use? -ENOENT ?
that sounds okay or EIO
> >> + return false;
> >> +
> >> + ret = strcmp(of_compat, "qcom,hidma-1.1");
> >> + } else {
> >> + ret = strcmp(acpi_device_hid(adev), "QCOM8062");
> >
> > Okay if you ahve a device ID then why do we need new binding? This device as
> > you said implies the support for MSI interrupts.
>
>
> 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 ?
--
~Vinod
Powered by blists - more mailing lists