From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 1/3] MTD : add the common code for GPMI-NFC controller driver
Date: Wed, 29 Jun 2011 12:33:37 +0200 [thread overview]
Message-ID: <20110629103337.GF1992@pengutronix.de> (raw)
In-Reply-To: <20110629100658.GE1992@pengutronix.de>
> > +static int __devinit acquire_interrupt(struct gpmi_nfc_data *this,
> > + const char *resource_name,
> > + irq_handler_t interrupt_handler, int *lno, int *hno)
> > +{
> > + struct platform_device *pdev = this->pdev;
> > + struct resource *r;
> > + int err;
> > +
> > + r = platform_get_resource_byname(pdev, IORESOURCE_IRQ, resource_name);
> > + if (!r) {
> > + pr_info("Can't get resource for %s\n", resource_name);
> > + return -ENXIO;
> > + }
> > +
> > + BUG_ON(r->start != r->end);
> > + err = request_irq(r->start, interrupt_handler, 0, resource_name, this);
> > + if (err) {
> > + pr_info("Can't own %s\n", resource_name);
> > + return err;
> > + }
> > +
> > + *lno = r->start;
> > + *hno = r->end;
> > + return 0;
> > +}
>
> This will not work if max_chip_count > 1, because the irq is already
> taken. (Also, I am not convinced of the resource handling, but I need to
Doh, I wrote that below the wrong codepath. This is another irq here.
Still, the problem exists: When a second channel GPMI channel is
requested, dmaengine will return -EBUSY, because the DMAIRQ is already
taken.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110629/c51e4f00/attachment-0001.sig>
next prev parent reply other threads:[~2011-06-29 10:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 8:24 [PATCH v7 0/3] add the GPMI controller driver for IMX23/IMX28 Huang Shijie
2011-06-29 8:24 ` Huang Shijie
2011-06-29 8:24 ` [PATCH v7 1/3] MTD : add the common code for GPMI-NFC controller driver Huang Shijie
2011-06-29 10:06 ` Wolfram Sang
2011-06-29 10:33 ` Wolfram Sang [this message]
2011-06-29 10:46 ` Huang Shijie
2011-06-29 12:29 ` Wolfram Sang
2011-06-29 12:42 ` Russell King - ARM Linux
2011-06-29 12:49 ` Wolfram Sang
2011-06-29 14:00 ` Shawn Guo
2011-06-29 14:15 ` Wolfram Sang
2011-06-29 14:37 ` Shawn Guo
2011-06-30 4:46 ` Wolfram Sang
2011-06-30 5:28 ` Shawn Guo
2011-06-30 8:06 ` [PATCH] dmaengine: mxs-dma: skip request_irq for NO_IRQ Shawn Guo
2011-07-07 0:15 ` Shawn Guo
2011-07-07 2:06 ` Vinod Koul
2011-07-07 3:24 ` Shawn Guo
2011-07-07 3:23 ` Huang Shijie
2011-07-13 23:31 ` Koul, Vinod
2011-06-29 12:38 ` [PATCH v7 1/3] MTD : add the common code for GPMI-NFC controller driver Russell King - ARM Linux
2011-06-30 1:50 ` Huang Shijie
2011-06-30 10:27 ` Wolfram Sang
2011-06-30 17:04 ` Wolfram Sang
2011-07-01 5:41 ` Artem Bityutskiy
2011-07-01 6:47 ` Huang Shijie
2011-06-29 8:24 ` [PATCH v7 2/3] MTD : add support for imx23 and imx28 Huang Shijie
2011-06-29 8:24 ` [PATCH v7 3/3] MTD : add GPMI-NFC driver in the config and Makefile Huang Shijie
2011-06-30 10:40 ` [PATCH v7 0/3] add the GPMI controller driver for IMX23/IMX28 Wolfram Sang
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=20110629103337.GF1992@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).