From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Nishanth Menon <nm@ti.com>, "Premi, Sanjeev" <premi@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: FEATURES prints
Date: Thu, 12 Nov 2009 13:02:26 -0800 [thread overview]
Message-ID: <20091112210226.GD24837@atomide.com> (raw)
In-Reply-To: <87ws2zge60.fsf@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [091013 15:01]:
> Nishanth Menon <nm@ti.com> writes:
>
> > Folks,
> >
> > With the addition of FEATURES in l-o, the following prints:
> > - l2cache : Y
> > - iva : Y
> > - sgx : Y
> > - neon : Y
> > - isp : Y
> >
> > comes up on SDP3430 -> now that we will introduce half a dozen
> > features here and there, we will soon clutter this up. we should
> > introduce a sysfs entry + remove the above noise..
> >
>
> Like Nishanth, I don't like the multi-line noise here. The patch
> below results in a single line output like this instead
>
> OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp )
>
> Not sure why we need to dump features that are not there, but if that
> s considered important, maybe prefixing each feature with a '+' or '-'
> would still allow this to be collapsed into a single line.
>
> Even with this, I think adding the display of these features into an
> OMAP-specific section of /proc/cpuinfo would be even better.
>
> Comments?
I like. Looks like this patch needs to be refreshed.
Tony
> Kevin
>
>
> commit 24f7422bad970cea2ed71d71e3994eeed70f175f
> Author: Kevin Hilman <khilman@deeprootsystems.com>
> Date: Tue Oct 13 14:42:00 2009 -0700
>
> OMAP3: collapse chip feature prints to single line
>
> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
>
> diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
> index 71d5568..b90fcf1 100644
> --- a/arch/arm/mach-omap2/id.c
> +++ b/arch/arm/mach-omap2/id.c
> @@ -249,11 +249,8 @@ void __init omap3_check_revision(void)
> }
>
> #define OMAP3_SHOW_FEATURE(feat) \
> - if (omap3_has_ ##feat()) { \
> - pr_info (" - "#feat" : Y"); \
> - } else { \
> - pr_info (" - "#feat" : N"); \
> - }
> + if (omap3_has_ ##feat()) \
> + printk (#feat" "); \
>
> void __init omap3_cpuinfo(void)
> {
> @@ -307,13 +304,14 @@ void __init omap3_cpuinfo(void)
> /*
> * Print verbose information
> */
> - pr_info("OMAP%s ES%s\n", cpu_name, cpu_rev);
> + pr_info("OMAP%s ES%s (", cpu_name, cpu_rev);
>
> OMAP3_SHOW_FEATURE(l2cache);
> OMAP3_SHOW_FEATURE(iva);
> OMAP3_SHOW_FEATURE(sgx);
> OMAP3_SHOW_FEATURE(neon);
> OMAP3_SHOW_FEATURE(isp);
> + printk(")\n");
> }
>
> /*
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" 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:[~2009-11-12 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 19:13 FEATURES prints Nishanth Menon
2009-10-09 10:46 ` Premi, Sanjeev
2009-10-09 14:15 ` Nishanth Menon
2009-10-09 14:51 ` Premi, Sanjeev
2009-10-13 21:46 ` Kevin Hilman
2009-10-13 21:56 ` Premi, Sanjeev
2009-10-14 4:24 ` Shilimkar, Santosh
2009-10-14 4:48 ` Kevin Hilman
2009-11-12 21:02 ` Tony Lindgren [this message]
2009-11-12 23:36 ` 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=20091112210226.GD24837@atomide.com \
--to=tony@atomide.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=premi@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox