From: Shardar Mohammed <smohammed@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
"vinod.koul@intel.com" <vinod.koul@intel.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"gnurou@gmail.com" <gnurou@gmail.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>
Subject: RE: [PATCH v2] dmaengine: tegra-apb: proper default init of channel slave_id
Date: Fri, 22 Apr 2016 13:58:03 +0000 [thread overview]
Message-ID: <f683ecd6d18e46b0a33090dfca27f919@bgmail102.nvidia.com> (raw)
In-Reply-To: <20160422133551.GP9047@ulmo.ba.sec>
> On Fri, Apr 22, 2016 at 06:14:53PM +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>
> >
> > ---
> > - Instead of initializing the slave id to -1 define macros for
> > max slave id and invalid slave id and do the checks accordingly.
> > ---
> > drivers/dma/tegra20-apb-dma.c | 13 +++++++++++--
> > 1 file changed, 11 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/dma/tegra20-apb-dma.c
> > b/drivers/dma/tegra20-apb-dma.c index 3871f29..2957e26 100644
> > --- a/drivers/dma/tegra20-apb-dma.c
> > +++ b/drivers/dma/tegra20-apb-dma.c
> > @@ -114,6 +114,9 @@
> > /* Channel base address offset from APBDMA base address */
> > #define TEGRA_APBDMA_CHANNEL_BASE_ADD_OFFSET 0x1000
> >
> > +#define TEGRA_APBDMA_SLAVE_ID_MAX 31
> > +#define TEGRA_APBDMA_SLAVE_ID_INVALID
> (TEGRA_APBDMA_SLAVE_ID_MAX + 1)
> > +
> > struct tegra_dma;
> >
> > /*
> > @@ -353,7 +356,7 @@ static int tegra_dma_slave_config(struct dma_chan
> *dc,
> > }
> >
> > memcpy(&tdc->dma_sconfig, sconfig, sizeof(*sconfig));
> > - if (!tdc->slave_id)
> > + if (tdc->slave_id == TEGRA_APBDMA_SLAVE_ID_INVALID)
> > tdc->slave_id = sconfig->slave_id;
> > tdc->config_init = true;
> > return 0;
> > @@ -1236,7 +1239,7 @@ static void
> tegra_dma_free_chan_resources(struct dma_chan *dc)
> > }
> > pm_runtime_put(tdma->dev);
> >
> > - tdc->slave_id = 0;
> > + tdc->slave_id = TEGRA_APBDMA_SLAVE_ID_INVALID;
> > }
> >
> > static struct dma_chan *tegra_dma_of_xlate(struct of_phandle_args
> > *dma_spec, @@ -1253,6 +1256,11 @@ static struct dma_chan
> *tegra_dma_of_xlate(struct of_phandle_args *dma_spec,
> > tdc = to_tegra_dma_chan(chan);
> > tdc->slave_id = dma_spec->args[0];
> >
> > + if (tdc->slave_id > TEGRA_APBDMA_SLAVE_ID_MAX) {
> > + dev_err(tdc2dev(tdc), "Invalid slave id\n");
> > + return NULL;
> > + }
>
> Should this check happen before the channel is requested? As it is, you're
> setting up the private data of the channel with a slave_id and error out after
> that. As I understand the channel would already have its ID set to the invalid
> ID, but without going too deep into the DMA engine core code it looks as
> though once requested, the channel needs to be released again (which the
> invalid ID handling code here doesn't).
[Shardar] Thanks will correct this.
>
> Thierry
>
> * Unknown Key
> * 0x7F3EB3A1
next prev parent reply other threads:[~2016-04-22 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 12:44 [PATCH v2] dmaengine: tegra-apb: proper default init of channel slave_id Shardar Shariff Md
2016-04-22 13:33 ` Jon Hunter
2016-04-22 13:56 ` Shardar Mohammed
2016-04-22 14:40 ` Jon Hunter
2016-04-22 13:35 ` Thierry Reding
2016-04-22 13:58 ` Shardar Mohammed [this message]
2016-04-22 13:43 ` Jon Hunter
2016-04-22 13:57 ` Shardar Mohammed
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=f683ecd6d18e46b0a33090dfca27f919@bgmail102.nvidia.com \
--to=smohammed@nvidia.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=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--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