From: Vinod Koul <vinod.koul@intel.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: dmaengine@vger.kernel.org, timur@codeaurora.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: qcom_hidma: allow ACPI/DT parameters to be overridden
Date: Mon, 26 Jun 2017 08:28:07 +0530 [thread overview]
Message-ID: <20170626025805.GW19154@localhost> (raw)
In-Reply-To: <1498157962-27962-1-git-send-email-okaya@codeaurora.org>
On Thu, Jun 22, 2017 at 02:59:22PM -0400, Sinan Kaya wrote:
> Parameters like maximum read/write request size and the maximum
> number of active transactions are currently configured in DT/ACPI.
>
> This patch allows a user to override these to fine tune performance
> for their application.
Applied, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: qcom_hidma: allow ACPI/DT parameters to be overridden
Date: Mon, 26 Jun 2017 08:28:07 +0530 [thread overview]
Message-ID: <20170626025805.GW19154@localhost> (raw)
In-Reply-To: <1498157962-27962-1-git-send-email-okaya@codeaurora.org>
On Thu, Jun 22, 2017 at 02:59:22PM -0400, Sinan Kaya wrote:
> Parameters like maximum read/write request size and the maximum
> number of active transactions are currently configured in DT/ACPI.
>
> This patch allows a user to override these to fine tune performance
> for their application.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2017-06-26 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 18:59 [PATCH] dmaengine: qcom_hidma: allow ACPI/DT parameters to be overridden Sinan Kaya
2017-06-22 18:59 ` Sinan Kaya
2017-06-26 2:58 ` Vinod Koul [this message]
2017-06-26 2:58 ` Vinod Koul
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=20170626025805.GW19154@localhost \
--to=vinod.koul@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=timur@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.