From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Varadarajan, Charulatha" <charu@ti.com>
Cc: linux-omap@vger.kernel.org, tony@atomide.com,
linux-arm-kernel@lists.infradead.org, b-cousson@ti.com,
balbi@ti.com
Subject: Re: [PATCH v1] OMAP: GPIO: Correct IP version message during boot
Date: Thu, 16 Dec 2010 08:49:32 -0800 [thread overview]
Message-ID: <8739pxhdcz.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1292508586-21651-1-git-send-email-charu@ti.com> (Charulatha Varadarajan's message of "Thu, 16 Dec 2010 19:39:46 +0530")
"Varadarajan, Charulatha" <charu@ti.com> writes:
> With the commit 9a748053f5f58a77cd71864f1d7b804175b0e47d whose subject is
> "OMAP: GPIO: Make omap_gpio_show_rev bank specific" (see [1]),
> the IP version information for all the banks are shown during bootup,
> but it does not show the bank number.
>
> Use dev_info instead of printk in omap_gpio_show_rev() so that the
> bank id is displayed along with the IP version
>
> [1] http://www.spinics.net/lists/arm-kernel/msg105872.html
A related question, the commit above also changed the GPIO revision
display from one-time to once per bank. Do we need to know the GPIO HW
revision for each bank, or can we assume it's the same for all banks?
Kevin
> Signed-off-by: Varadarajan, Charulatha <charu@ti.com>
> Acked-by: Felipe Balbi <balbi@ti.com>
> ---
> arch/arm/plat-omap/gpio.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/plat-omap/gpio.c b/arch/arm/plat-omap/gpio.c
> index 8d493b9..47aeaeb 100644
> --- a/arch/arm/plat-omap/gpio.c
> +++ b/arch/arm/plat-omap/gpio.c
> @@ -1554,7 +1554,7 @@ static void __init omap_gpio_show_rev(struct gpio_bank *bank)
> else
> return;
>
> - printk(KERN_INFO "OMAP GPIO hardware version %d.%d\n",
> + dev_info(bank->dev, "hardware version %d.%d\n",
> (rev >> 4) & 0x0f, rev & 0x0f);
> }
WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] OMAP: GPIO: Correct IP version message during boot
Date: Thu, 16 Dec 2010 08:49:32 -0800 [thread overview]
Message-ID: <8739pxhdcz.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1292508586-21651-1-git-send-email-charu@ti.com> (Charulatha Varadarajan's message of "Thu, 16 Dec 2010 19:39:46 +0530")
"Varadarajan, Charulatha" <charu@ti.com> writes:
> With the commit 9a748053f5f58a77cd71864f1d7b804175b0e47d whose subject is
> "OMAP: GPIO: Make omap_gpio_show_rev bank specific" (see [1]),
> the IP version information for all the banks are shown during bootup,
> but it does not show the bank number.
>
> Use dev_info instead of printk in omap_gpio_show_rev() so that the
> bank id is displayed along with the IP version
>
> [1] http://www.spinics.net/lists/arm-kernel/msg105872.html
A related question, the commit above also changed the GPIO revision
display from one-time to once per bank. Do we need to know the GPIO HW
revision for each bank, or can we assume it's the same for all banks?
Kevin
> Signed-off-by: Varadarajan, Charulatha <charu@ti.com>
> Acked-by: Felipe Balbi <balbi@ti.com>
> ---
> arch/arm/plat-omap/gpio.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/plat-omap/gpio.c b/arch/arm/plat-omap/gpio.c
> index 8d493b9..47aeaeb 100644
> --- a/arch/arm/plat-omap/gpio.c
> +++ b/arch/arm/plat-omap/gpio.c
> @@ -1554,7 +1554,7 @@ static void __init omap_gpio_show_rev(struct gpio_bank *bank)
> else
> return;
>
> - printk(KERN_INFO "OMAP GPIO hardware version %d.%d\n",
> + dev_info(bank->dev, "hardware version %d.%d\n",
> (rev >> 4) & 0x0f, rev & 0x0f);
> }
next prev parent reply other threads:[~2010-12-16 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 14:09 [PATCH v1] OMAP: GPIO: Correct IP version message during boot Varadarajan, Charulatha
2010-12-16 14:09 ` Varadarajan, Charulatha
2010-12-16 16:49 ` Kevin Hilman [this message]
2010-12-16 16:49 ` Kevin Hilman
2010-12-17 14:15 ` Varadarajan, Charulatha
2010-12-17 14:15 ` Varadarajan, Charulatha
2010-12-20 23:49 ` Kevin Hilman
2010-12-20 23:49 ` Kevin Hilman
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=8739pxhdcz.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=charu@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.