From: Thierry Reding <thierry.reding@gmail.com>
To: Shardar Shariff Md <smohammed@nvidia.com>
Cc: ldewangan@nvidia.com, vinod.koul@intel.com,
dan.j.williams@intel.com, swarren@wwwdotorg.org,
gnurou@gmail.com, dmaengine@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
jonathanh@nvidia.com
Subject: Re: [PATCH v3] dmaengine: tegra-apb: proper default init of channel slave_id
Date: Fri, 22 Apr 2016 16:37:00 +0200 [thread overview]
Message-ID: <20160422143700.GA7068@ulmo.ba.sec> (raw)
In-Reply-To: <1461334479-27985-1-git-send-email-smohammed@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
On Fri, Apr 22, 2016 at 07:44:39PM +0530, Shardar Shariff Md wrote:
> Initialize default channel slave_id(req_sel) to invalid id
> (i.e max supported slave id + 1) to avoid overwriting of slave_id
> during tegra_dma_slave_config() with client data if slave_id
> is not initialized through DT
>
> Signed-off-by: Shardar Shariff Md <smohammed@nvidia.com>
>
> ---
> Changes from v1:
> - Instead of initializing the slave id to -1 define macros for
> max slave id and invalid slave id and do the checks accordingly.
>
> Changes from v2:
> - Check slave id boundary before dma channel is allocated to
> avoid channel leakage.
> ---
> drivers/dma/tegra20-apb-dma.c | 18 +++++++++++++++---
> 1 file changed, 15 insertions(+), 3 deletions(-)
Looks good to me, though I'm not a DMA engine export, so I'll only
offer:
Acked-by: Thierry Reding <treding@nvidia.com>
Perhaps Jon would be comfortable enough to give a Reviewed-by?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-22 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 14:14 [PATCH v3] dmaengine: tegra-apb: proper default init of channel slave_id Shardar Shariff Md
2016-04-22 14:37 ` Thierry Reding [this message]
2016-04-22 14:43 ` Jon Hunter
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=20160422143700.GA7068@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=smohammed@nvidia.com \
--cc=swarren@wwwdotorg.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