public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: dmaengine@vger.kernel.org, timur@codeaurora.org,
	devicetree@vger.kernel.org, cov@codeaurora.org,
	vinod.koul@intel.com, jcm@redhat.com, shankerd@codeaurora.org,
	vikrams@codeaurora.org, marc.zyngier@arm.com,
	mark.rutland@arm.com, eric.auger@linaro.org,
	agross@codeaurora.org, arnd@arndb.de,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Pawel Moll <pawel.moll@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] dma: qcom_hidma: read the channel id from HW
Date: Fri, 18 Mar 2016 15:06:17 -0500	[thread overview]
Message-ID: <20160318200617.GA28108@rob-hp-laptop> (raw)
In-Reply-To: <1457732994-11175-5-git-send-email-okaya@codeaurora.org>

On Fri, Mar 11, 2016 at 04:49:54PM -0500, Sinan Kaya wrote:
> Removing the flexibility to choose the event channel as there is no real
> use case right now. We have been using the values in ACPI that match the HW
> defaults. OS is reading the event-channel from the HW register now.
> 
> Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
> ---
>  .../devicetree/bindings/dma/qcom_hidma_mgmt.txt    |  3 --

Acked-by: Rob Herring <robh@kernel.org>

>  drivers/dma/qcom/hidma.c                           | 39 +---------------------
>  2 files changed, 1 insertion(+), 41 deletions(-)

  reply	other threads:[~2016-03-18 20:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 21:49 [PATCH V15 0/4] dma: add Qualcomm Technologies HIDMA driver Sinan Kaya
2016-03-11 21:49 ` [PATCH V15 1/4] dma: qcom_hidma: implement lower level hardware interface Sinan Kaya
2016-03-11 21:49 ` [PATCH V15 2/4] dma: qcom_hidma: add debugfs hooks Sinan Kaya
2016-03-11 21:49 ` [PATCH V15 3/4] dma: qcom_hidma: add support for object hierarchy Sinan Kaya
2016-03-11 21:49 ` [PATCH 4/4] dma: qcom_hidma: read the channel id from HW Sinan Kaya
2016-03-18 20:06   ` Rob Herring [this message]
     [not found] ` <1457732994-11175-1-git-send-email-okaya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-03-20  9:39   ` [PATCH V15 0/4] dma: add Qualcomm Technologies HIDMA driver Vinod Koul
2016-03-20 13:30     ` okaya
2016-03-27 13:11     ` okaya-sgV2jX0FEOL9JmXXK+q4OQ

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=20160318200617.GA28108@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=agross@codeaurora.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd@arndb.de \
    --cc=cov@codeaurora.org \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=eric.auger@linaro.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jcm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=okaya@codeaurora.org \
    --cc=pawel.moll@arm.com \
    --cc=shankerd@codeaurora.org \
    --cc=timur@codeaurora.org \
    --cc=vikrams@codeaurora.org \
    --cc=vinod.koul@intel.com \
    /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