From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] davinci: Add MityDSP-L138/MityARM-1808 SOM support
Date: Fri, 16 Jul 2010 16:49:27 -0700 [thread overview]
Message-ID: <1279324167.4526.85.camel@Joe-Laptop.home> (raw)
In-Reply-To: <E1OZlTF-0006NW-1I@wanda>
On Fri, 2010-07-16 at 10:00 -0400, Michael Williamson wrote:
> +static __init void mityomapl138_setup_lcd(void)
> +{
[]
> + pr_warning("mityomapl138_init: unknown LCD type : %s\n",
> + peripheral_config.LCDConfig.PanelName);
I think you'd be better off actually using the actual
function name rather than the caller name
pr_warning("%s: unknown LCD type: %s\n",
__func__, peripheral_config.LCDConfig.PanelName);
[]
> + if (ret) {
> + pr_warning("mityomapl138_init: lcd pinmux failed : "
> + "%d\n", ret);
pr_warning("%s: lcd pinmux failed : %d\n",
__func__, ret);
> + pr_warning("mityomapl138_init: no LCD device enabled\n");
etc.
> +static __init void mityomapl138_init(void)
> +{
> + int ret;
> +
> + pr_info("mityomapl138_init...\n");
> +
> + ret = pmic_tps65023_init();
> + if (ret)
> + pr_warning("mityomapl138_init: TPS65023 PMIC init failed: %d\n",
> + ret);
pr_warning("%s: TPS65023 PMIC init failed: %d\n",
__func__, ret);
etc.
> +
> + ret = da8xx_register_edma();
> + if (ret)
> + pr_warning("mityomapl138_init: edma registration failed: %d\n",
> + ret);
> +
> + ret = da8xx_register_i2c(0, &mityomap_i2c_0_pdata);
> + if (ret)
> + pr_warning("mityomapl138_init: i2c0 registration failed: %d\n",
> + ret);
> +
> + ret = da8xx_register_watchdog();
> + if (ret)
> + pr_warning("mityomapl138_init: watchdog registration failed: "
> + "%d\n", ret);
> +
next prev parent reply other threads:[~2010-07-16 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 14:00 [PATCH] davinci: Add MityDSP-L138/MityARM-1808 SOM support Michael Williamson
2010-07-16 23:49 ` Joe Perches [this message]
2010-07-18 17:29 ` Mike Williamson
2010-07-19 6:35 ` Nori, Sekhar
2010-07-19 11:43 ` Michael Williamson
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=1279324167.4526.85.camel@Joe-Laptop.home \
--to=joe@perches.com \
--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