From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 10/10] dmaengine: qcom_hidma: add MSI support for interrupts
Date: Thu, 4 Aug 2016 18:16:41 +0530 [thread overview]
Message-ID: <20160804124641.GE9681@localhost> (raw)
In-Reply-To: <e6560c8b-e18e-9e32-5b51-c1c12d8551ce@codeaurora.org>
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
next prev parent reply other threads:[~2016-08-04 12:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 18:39 [PATCH 00/10] dmaengine: qcom_hidma: add MSI interrupt support Sinan Kaya
2016-07-18 18:39 ` [PATCH 01/10] Documentation: DT: qcom_hidma: update binding for MSI Sinan Kaya
2016-07-19 10:37 ` Mark Rutland
2016-07-19 12:42 ` Sinan Kaya
2016-07-18 18:39 ` [PATCH 02/10] Documentation: DT: qcom_hidma: correct spelling mistakes Sinan Kaya
2016-07-20 1:16 ` Rob Herring
2016-07-18 18:39 ` [PATCH 03/10] of: irq: make of_msi_configure accessible from modules Sinan Kaya
2016-07-18 21:24 ` Rob Herring
2016-07-19 21:40 ` Sinan Kaya
2016-07-18 18:39 ` [PATCH 04/10] dmaending: qcom_hidma: configure DMA and MSI for OF Sinan Kaya
2016-07-24 6:33 ` Vinod Koul
2016-07-24 14:40 ` Sinan Kaya
2016-07-18 18:39 ` [PATCH 05/10] dmaengine: qcom_hidma: make pending_tre_count atomic Sinan Kaya
2016-07-18 18:39 ` [PATCH 06/10] dmaengine: qcom_hidma: make error and success path common Sinan Kaya
2016-07-18 18:39 ` [PATCH 07/10] dmaengine: qcom_hidma: eliminate processed variables Sinan Kaya
2016-07-18 18:39 ` [PATCH 08/10] dmaengine: qcom_hidma: bring out interrupt cause Sinan Kaya
2016-07-18 18:39 ` [PATCH 09/10] dmaengine: qcom_hidma: add a common API to setup the interrupt Sinan Kaya
2016-07-18 18:39 ` [PATCH 10/10] dmaengine: qcom_hidma: add MSI support for interrupts Sinan Kaya
2016-07-24 6:42 ` Vinod Koul
2016-07-24 14:38 ` Sinan Kaya
2016-08-04 12:46 ` Vinod Koul [this message]
2016-08-04 13:59 ` Sinan Kaya
2016-08-08 8:14 ` Vinod Koul
2016-08-08 11:48 ` okaya at codeaurora.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160804124641.GE9681@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).