SUPERH platform development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 4/7] dmaengine: rcar-dmac: Add Renesas R-Car Gen2 DMA Controller (DMAC) driver
Date: Fri, 18 Jul 2014 13:06:48 +0000	[thread overview]
Message-ID: <3790931.EVz52zbfLN@avalon> (raw)
In-Reply-To: <1405455522-20676-5-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Hi Morimoto-san,

On Wednesday 16 July 2014 20:02:48 Kuninori Morimoto wrote:
> Hi Laurent again
> 
> I found bug/trouble
> 
> > +/*
> > -------------------------------------------------------------------------
> > ---- + * OF xlate and channel filter
> > + */
> > +
> > +static bool rcar_dmac_chan_filter(struct dma_chan *chan, void *arg)
> > +{
> > +	struct rcar_dmac *dmac = to_rcar_dmac(chan->device);
> > +	unsigned int id = (unsigned int)arg;
> > +
> > +	return !test_and_set_bit(id, dmac->modules);
> > +}
> 
> I got 2 troubles on this filter.
> 
> You know sound driver needs both "Audio DMAC" and "Audio DMAC peri peri"
> now, DMAC drivers are
>  - Audio DMAC           : rcar-dma
>  - Audio DMAC peri peri : rcar-audma (= shdma-base)
> 
> If I enabled both DMAC, this filter will be called
> with Audio DMAC peri peri side (= shdma-base) chan.
> This filter needs to check "chan" itself.
> (I used "chan->private" for checking as local hack.)
> This is 1st trouble.

Right. I'll fix that in the driver, but this is really hackish. The 
rcar_dmac_of_xlate() function, called by of_dma_request_slave_channel(), 
currently calls dma_request_channel() with a private filter function. This 
will iterate over all channels from all devices, even though we have a pointer 
to the struct dma_device at that time, and we know we want to allocate a 
channel from that particular dma_device.

Wouldn't it make more sense, to support OF platforms, to extend the dmaengine 
core with a function that requests a specific channel from a specific 
dma_device, without using a filter function ?

> 2nd trouble is chan/filter again :P
> Now, your [6/7] patch adds 2 SYS-DMAC on DTSI file.
> And, I need to add Audio DMAC / Audio DMAC peri peri entry
> So, total entrys are...
> 
> 	dmac0: dma-controller@e6700000 {
> 	..
> 	};
> 	dmac1: dma-controller@e6720000 {
> 	...
> 	};
> 	audma0: dma-contorller@ec700000 {
> 	...
> 	};
> 	audma1: dma-controller@ec720000 {
> 	...
> 	};
> 	audmapp: audio-dma-pp@0xec740000 {
> 	...
> 	};
> 
> But, this filter doesn't check DMAC itself.
> So, my driver requests "audma0's 0x01 ID", but,
> this filter accepts as "dmac0's 0x01 ID".

I'll fix that at the same time as the first problem.

> > +/* ----------------------------------------------------------------------
> > + * Probe and remove
> > + */
> > +
> > +static int rcar_dmac_chan_probe(struct rcar_dmac *dmac,
> > +				struct rcar_dmac_chan *rchan,
> > +				unsigned int index)
> > +{
> > +	struct platform_device *pdev = to_platform_device(dmac->dev);
> > +	struct dma_chan *chan = &rchan->chan;
> > +	char irqname[16];
> > +	int irq;
> > +	int ret;
> > +
> > +	rchan->index = index;
> > +	rchan->iomem = dmac->iomem + RCAR_DMAC_CHAN_OFFSET(index);
> > +	rchan->mid_rid = -EINVAL;
> > +
> > +	spin_lock_init(&rchan->lock);
> > +	mutex_init(&rchan->power_lock);
> > +
> > +	/* Request the channel interrupt. */
> > +	sprintf(irqname, "ch%u", index);
> > +	irq = platform_get_irq_byname(pdev, irqname);
> > +	if (irq < 0) {
> > +		dev_err(dmac->dev, "no IRQ specified for channel %u\n", index);
> > +		return -ENODEV;
> > +	}
> > +
> > +	sprintf(irqname, "DMAC channel %u", index);
> > +	ret = devm_request_threaded_irq(dmac->dev, irq, 
rcar_dmac_isr_channel,
> > +					rcar_dmac_isr_channel_thread, 0,
> > +					irqname, rchan);
> > +	if (ret) {
> > +		dev_err(dmac->dev, "failed to request IRQ %u (%d)\n", irq, ret);
> > +		return ret;
> > +	}
> 
> Here, you used "irqname" which exists on stack memory for
> devm_request_threaded_irq(). It breaks /proc/interrupt interrupt names.

I've noticed that too :-) I have already fixed the problem in my tree, the fix 
will be integrated in v2.

-- 
Regards,

Laurent Pinchart


      parent reply	other threads:[~2014-07-18 13:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 20:18 [PATCH 4/7] dmaengine: rcar-dmac: Add Renesas R-Car Gen2 DMA Controller (DMAC) driver Laurent Pinchart
2014-07-16  1:33 ` Kuninori Morimoto
2014-07-16  9:30 ` Laurent Pinchart
2014-07-17  0:59 ` Kuninori Morimoto
2014-07-17  1:08 ` Laurent Pinchart
2014-07-17  3:02 ` Kuninori Morimoto
2014-07-17  3:25 ` Kuninori Morimoto
2014-07-18 12:52 ` Laurent Pinchart
2014-07-18 13:06 ` Laurent Pinchart [this message]

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=3790931.EVz52zbfLN@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox