From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tony Lindgren <tony@atomide.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 15:36:08 -0800 [thread overview]
Message-ID: <87y6mbs4d3.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20091112210226.GD24837@atomide.com> (Tony Lindgren's message of "Thu\, 12 Nov 2009 13\:02\:26 -0800")
Tony Lindgren <tony@atomide.com> writes:
> * 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.
>
OK, will send refreshed version.
Kevin
prev parent reply other threads:[~2009-11-12 23:36 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
2009-11-12 23:36 ` Kevin Hilman [this message]
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=87y6mbs4d3.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=premi@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox