From: martin@neutronstar.dyndns.org (martin at neutronstar.dyndns.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: omap3evm: Add support for an MT9M032 based camera board.
Date: Sun, 18 Sep 2011 22:10:22 +0200 [thread overview]
Message-ID: <1316376623.565262.7548@localhost> (raw)
In-Reply-To: <1316291069.1610.23.camel@Joe-Laptop>
On Sat, Sep 17, 2011 at 01:24:29PM -0700, Joe Perches wrote:
> On Sat, 2011-09-17 at 11:34 +0200, Martin Hostettler wrote:
> > Adds board support for an MT9M032 based camera to omap3evm.
>
> All of the logging messages could be
> prefixed by the printk subsystem if you
> add #define pr_fmt before any #include
Ah, i didn't really knew about that feature yet. I really have to keep
that in mind when grepping for error messages in the future.
But i don't think it would help much, as i now reducted the total number
of pr_err calls to 2 in this patch.
Thanks for the idea anyway.
- Martin Hostettler
>
> > diff --git a/arch/arm/mach-omap2/board-omap3evm-camera.c b/arch/arm/mach-omap2/board-omap3evm-camera.c
> []
> #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> []
> > +static int omap3evm_set_mux(enum omap3evmdc_mux mux_id)
> []
> > + switch (mux_id) {
> []
> > + default:
> > + pr_err("omap3evm-camera: Invalid mux id #%d\n", mux_id);
>
> pr_err("Invalid mux id #%d\n", mux_id);
> []
> > +static int __init camera_init(void)
> []
> > + if (gpio_request(nCAM_VD_SEL, "nCAM_VD_SEL") < 0) {
> > + pr_err("omap3evm-camera: Failed to get GPIO nCAM_VD_SEL(%d)\n",
> > + nCAM_VD_SEL);
>
> pr_err("Failed to get GPIO nCAM_VD_SEL(%d)\n",
> nCAM_VD_SEL);
> etc.
>
next prev parent reply other threads:[~2011-09-18 20:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 9:34 [PATCH v2] arm: omap3evm: Add support for an MT9M032 based camera board Martin Hostettler
2011-09-17 20:24 ` Joe Perches
2011-09-18 20:10 ` martin at neutronstar.dyndns.org [this message]
2011-09-17 22:00 ` Sylwester Nawrocki
2011-09-17 22:08 ` Laurent Pinchart
2011-09-18 20:13 ` martin at neutronstar.dyndns.org
2011-09-18 21:58 ` Laurent Pinchart
2011-09-19 6:07 ` Hiremath, Vaibhav
2011-09-19 19:24 ` martin at neutronstar.dyndns.org
2011-09-19 19:59 ` Hiremath, Vaibhav
2011-09-19 6:10 ` martin at neutronstar.dyndns.org
2011-09-19 8:01 ` Laurent Pinchart
2011-09-19 19:17 ` Guennadi Liakhovetski
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=1316376623.565262.7548@localhost \
--to=martin@neutronstar.dyndns.org \
--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).