From: Wolfram Sang <w.sang@pengutronix.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] mpc52xx/serial: fix error paths in probe function
Date: Thu, 27 Nov 2008 21:30:48 +0100 [thread overview]
Message-ID: <20081127203048.GA18994@pengutronix.de> (raw)
In-Reply-To: <9e4733910811270840w23214c91o4f8a141c245cb663@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
On Thu, Nov 27, 2008 at 11:40:55AM -0500, Jon Smirl wrote:
> > + if (port->irq == NO_IRQ) {
> > + dev_err(&op->dev, "Could not get irq\n");
> > + return -ENODEV;
> > + }
>
> Doesn't NO_IRQ imply polling, not an error?
See below, I just copied the original behaviour. Having another look at
mpc52xx_uart_setup, I don't see any polling option there, so I think it
is correct to do this.
>
> >
> > dev_dbg(&op->dev, "mpc52xx-psc uart at %p, irq=%x, freq=%i\n",
> > (void *)port->mapbase, port->irq, port->uartclk);
> >
> > - if ((port->irq == NO_IRQ) || !port->mapbase) {
> > - printk(KERN_ERR "Could not allocate resources for PSC\n");
> > - return -EINVAL;
> > - }
(Originaly dropout for NO_IRQ)
Regards,
Wolfram
--
Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-27 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 15:33 [PATCH] mpc52xx/serial: fix error paths in probe function Wolfram Sang
2008-11-27 16:40 ` Jon Smirl
2008-11-27 20:30 ` Wolfram Sang [this message]
2008-12-19 15:32 ` [PATCH V2] " 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=20081127203048.GA18994@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=jonsmirl@gmail.com \
--cc=linuxppc-dev@ozlabs.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).