From: Alberto Panizzo <maramaopercheseimorto@gmail.com>
To: "Lothar Waßmann" <LW@KARO-electronics.de>
Cc: linux-input <linux-input@vger.kernel.org>,
H Hartley Sweeten <hartleys@visionengravers.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sascha linux-arm <s.hauer@pengutronix.de>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3] input: MXC: add mxc-keypad driver to support the Keypad Port present in the mxc application processors family.
Date: Wed, 27 Jan 2010 15:39:53 +0100 [thread overview]
Message-ID: <1264603193.2463.75.camel@realization> (raw)
In-Reply-To: <19296.12024.559688.606548@ipc1.ka-ro>
On mer, 2010-01-27 at 13:18 +0100, Lothar Waßmann wrote:
> Hi,
>
> Alberto Panizzo writes:
> > > > + irq = platform_get_irq(pdev, 0);
> > > > + if (irq < 0) {
> > > > + dev_err(&pdev->dev, "failed to get keypad irq\n");
> > > > + return -ENXIO;
> > > > + }
> > > >
> > > This should be -ENODEV.
> > >
> > Lot of reference keyboard driver use -ENXIO..
> > May should be better: return irq ?
> >
> Yes, of course. If a function returns an error code that should be
> promoted to the caller instead of inventing a new error code.
>
>
> Lothar Waßmann
But, errno.h say:
#define ENXIO 6 // Device not configured
#define ENODEV 19 // Operation not supported by device
And looking at the code of platform_get* these functions return only what
it is written in the platform_device data.
So the only way these functions fails is a not configured platform_device
with IRQ and I/O memory.
Maybe the error outputs are wrong. What about these:
if (pdata == NULL) {
dev_err(&pdev->dev, "no platform data defined\n");
return -ENXIO;
}
irq = platform_get_irq(pdev, 0);
if (irq < 0) {
dev_err(&pdev->dev, "no irq defined in platform data\n");
return -ENXIO;
}
res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
if (res == NULL) {
dev_err(&pdev->dev, "no I/O memory defined in platform data\n");
return -ENXIO;
}
res = request_mem_region(res->start, resource_size(res), pdev->name);
if (res == NULL) {
dev_err(&pdev->dev, "failed to request I/O memory\n");
return -EBUSY;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-27 14:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 9:55 [PATCH v3] input: MXC: add mxc-keypad driver to support the Keypad Port present in the mxc application processors family Alberto Panizzo
2010-01-27 10:33 ` Lothar Waßmann
2010-01-27 10:45 ` Uwe Kleine-König
2010-01-27 12:17 ` Alberto Panizzo
2010-01-27 12:14 ` Alberto Panizzo
2010-01-27 12:18 ` Lothar Waßmann
2010-01-27 14:39 ` Alberto Panizzo [this message]
2010-01-27 14:52 ` Lothar Waßmann
2010-01-27 15:29 ` Alberto Panizzo
2010-01-27 17:03 ` Lothar Waßmann
2010-01-27 17:32 ` Dmitry Torokhov
2010-01-27 17:42 ` Alberto Panizzo
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=1264603193.2463.75.camel@realization \
--to=maramaopercheseimorto@gmail.com \
--cc=LW@KARO-electronics.de \
--cc=dmitry.torokhov@gmail.com \
--cc=hartleys@visionengravers.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).