From: Vinod Koul <vinod.koul@intel.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Padmavathi Venna <padma.v@samsung.com>,
linux-samsung-soc@vger.kernel.org,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
padma.kvr@gmail.com, sbkim73@samsung.com,
"Mark Brown (broonie@opensource.wolfsonmicro.com)"
<broonie@opensource.wolfsonmicro.com>,
kgene.kim@samsung.com, Arnd Bergmann <arnd@arndb.de>,
Grant Likely <grant.likely@secretlab.ca>,
jon-hunter@ti.com, boojin.kim@samsung.com
Subject: Re: [PATCH V2] DMA: PL330: Add check if device tree compatible
Date: Mon, 1 Apr 2013 23:51:51 +0530 [thread overview]
Message-ID: <20130401182151.GH10326@intel.com> (raw)
In-Reply-To: <CAL_Jsq+3bJDiA=rXS=WY3BGuRh5X+nyxxosrqtSD9fx-asbCKQ@mail.gmail.com>
On Mon, Apr 01, 2013 at 08:13:31AM -0500, Rob Herring wrote:
> On Thu, Mar 21, 2013 at 4:39 AM, Vinod Koul <vinod.koul@intel.com> wrote:
> > On Tue, Mar 05, 2013 at 02:55:31PM +0530, Padmavathi Venna wrote:
> >> This patch register the dma controller with generic dma helpers only
> >> in DT case. This also adds some extra error handling in the driver.
> >>
> >> Signed-off-by: Padmavathi Venna <padma.v@samsung.com>
> >> Reported-by: Sachin Kamat <sachin.kamat@linaro.org>
>
> What's the status on this? It is needed for 3.9 to fix pl330 on highbank.
Well the status is that submitter has been rude. I had few questions and
comments on this patch and they are yet to be addressed.
--
~Vinod
>
> Rob
>
> >> ---
> >>
> >> Based on Vinod Koul next branch.
> >>
> >> Changes since V1:
> >> - return silently when of_dma_controller_register fails, as
> >> suggested by Arnd.
> >>
> >> drivers/dma/pl330.c | 38 +++++++++++++++++++++++++++-----------
> >> 1 files changed, 27 insertions(+), 11 deletions(-)
> >>
> >> diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
> >> index 7181531..5dbc594 100644
> >> --- a/drivers/dma/pl330.c
> >> +++ b/drivers/dma/pl330.c
> >> @@ -2882,7 +2882,7 @@ pl330_probe(struct amba_device *adev, const struct amba_id *id)
> >> {
> >> struct dma_pl330_platdata *pdat;
> >> struct dma_pl330_dmac *pdmac;
> >> - struct dma_pl330_chan *pch;
> >> + struct dma_pl330_chan *pch, *_p;
> >> struct pl330_info *pi;
> >> struct dma_device *pd;
> >> struct resource *res;
> >> @@ -2984,7 +2984,16 @@ pl330_probe(struct amba_device *adev, const struct amba_id *id)
> >> ret = dma_async_device_register(pd);
> >> if (ret) {
> >> dev_err(&adev->dev, "unable to register DMAC\n");
> >> - goto probe_err2;
> >> + goto probe_err3;
> >> + }
> >> +
> >> + if (adev->dev.of_node) {
> >> + ret = of_dma_controller_register(adev->dev.of_node,
> >> + of_dma_pl330_xlate, pdmac);
> >> + if (ret) {
> >> + dev_err(&adev->dev,
> >> + "unable to register DMA to the generic DT DMA helpers\n");
> > Indent?
> >> + }
> >> }
> >>
> >> dev_info(&adev->dev,
> >> @@ -2995,16 +3004,21 @@ pl330_probe(struct amba_device *adev, const struct amba_id *id)
> >> pi->pcfg.data_bus_width / 8, pi->pcfg.num_chan,
> >> pi->pcfg.num_peri, pi->pcfg.num_events);
> >>
> >> - ret = of_dma_controller_register(adev->dev.of_node,
> >> - of_dma_pl330_xlate, pdmac);
> >> - if (ret) {
> >> - dev_err(&adev->dev,
> >> - "unable to register DMA to the generic DT DMA helpers\n");
> >> - goto probe_err2;
> >> - }
> >> -
> >> return 0;
> >> +probe_err3:
> >> + amba_set_drvdata(adev, NULL);
> >>
> >> + /* Idle the DMAC */
> >> + list_for_each_entry_safe(pch, _p, &pdmac->ddma.channels,
> >> + chan.device_node) {
> >> +
> >> + /* Remove the channel */
> >> + list_del(&pch->chan.device_node);
> >> +
> >> + /* Flush the channel */
> >> + pl330_control(&pch->chan, DMA_TERMINATE_ALL, 0);
> >> + pl330_free_chan_resources(&pch->chan);
> > free_chan for error handling in probe?
> >
> >> + }
> >> probe_err2:
> >> pl330_del(pi);
> >> probe_err1:
> >> @@ -3023,8 +3037,10 @@ static int pl330_remove(struct amba_device *adev)
> >> if (!pdmac)
> >> return 0;
> >>
> >> - of_dma_controller_free(adev->dev.of_node);
> >> + if (adev->dev.of_node)
> >> + of_dma_controller_free(adev->dev.of_node);
> >>
> >> + dma_async_device_unregister(&pdmac->ddma);
> >> amba_set_drvdata(adev, NULL);
> >>
> >> /* Idle the DMAC */
> >> --
> >> 1.7.4.4
> >>
next prev parent reply other threads:[~2013-04-01 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 9:25 [PATCH] dma: of-dma: return error when 'dma-cells' not found Padmavathi Venna
2013-03-05 9:25 ` [PATCH V2] DMA: PL330: Add check if device tree compatible Padmavathi Venna
2013-03-13 5:36 ` Padma Venkat
2013-03-21 9:39 ` Vinod Koul
2013-04-01 13:13 ` Rob Herring
2013-04-01 18:21 ` Vinod Koul [this message]
2013-04-02 2:58 ` Padma Venkat
2013-03-05 9:43 ` [PATCH] dma: of-dma: return error when 'dma-cells' not found Rob Herring
2013-03-05 10:04 ` Padma Venkat
[not found] ` <5135BE58.4040105-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-03-05 10:15 ` Arnd Bergmann
2013-03-05 14:56 ` Rob Herring
2013-03-05 19:48 ` Arnd Bergmann
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=20130401182151.GH10326@intel.com \
--to=vinod.koul@intel.com \
--cc=arnd@arndb.de \
--cc=boojin.kim@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jon-hunter@ti.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=padma.kvr@gmail.com \
--cc=padma.v@samsung.com \
--cc=robherring2@gmail.com \
--cc=sbkim73@samsung.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;
as well as URLs for NNTP newsgroup(s).