From: "Cousson, Benoit" <b-cousson@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 2/2] omap4: mux: Remove duplicate mux modes
Date: Mon, 14 Mar 2011 18:22:18 +0100 [thread overview]
Message-ID: <4D7E4ECA.5010200@ti.com> (raw)
In-Reply-To: <20110314165922.GA7258@atomide.com>
On 3/14/2011 5:59 PM, Tony Lindgren wrote:
> * Cousson, Benoit<b-cousson@ti.com> [110314 01:39]:
>> Hi Tony,
>>
>> On 3/11/2011 9:34 PM, Tony Lindgren wrote:
>>> Remove duplicate mux modes to make the binary smaller:
>>>
>>> text data bss dec hex filename
>>> 9378 24472 0 33850 843a mux44xx.o
>>> 9378 19104 0 28482 6f42 mux44xx.o
>>>
>>> Cc: Benoit Cousson<b-cousson@ti.com>
>>> Signed-off-by: Tony Lindgren<tony@atomide.com>
>>> ---
>>> arch/arm/mach-omap2/mux44xx.c | 282 +----------------------------------------
>>> 1 files changed, 6 insertions(+), 276 deletions(-)
>>>
>>> diff --git a/arch/arm/mach-omap2/mux44xx.c b/arch/arm/mach-omap2/mux44xx.c
>>> index c322e7b..9a66445 100644
>>> --- a/arch/arm/mach-omap2/mux44xx.c
>>> +++ b/arch/arm/mach-omap2/mux44xx.c
>>> @@ -755,25 +755,9 @@ static struct omap_ball __initdata omap4_core_cbl_ball[] = {
>>> #endif
>>>
>>> /*
>>> - * Superset of all mux modes for omap4 ES2.0
>>> + * Signals different on ES2.0 compared to superset
>>
>> I didn't do it originally due to the huge amount of differences
>> between the two versions and the impact at runtime it will imply to
>> fix the modified entries at boot time. It might still be interesting
>> to measure it.
>
> A quick test shows the difference is 0.007324218 - 0.007202148 seconds.. :)
Whaoo, 122us, that chip is really fast :-)
>> Since ES1 is no longer used on any board except the early one, that
>> you probably still have :-), it might be better to consider ES2 as
>> the superset and then store ES1 diff as the subset. It will avoid
>> any performance impact for the latest devices.
>
> Well the performance impact is minimal in this case. But from cutting
> down the size point of view that makes sense as then we could later on
> optionally compile out OMAP_PACKAGE_CBL.
>
> Sounds like that's a separate incremental patch on top of this one
> though.
OK, I'll try to make that for 2.6.40.
Benoit
prev parent reply other threads:[~2011-03-14 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 20:34 [PATCH 0/2] omap2+: Few mux patches Tony Lindgren
2011-03-11 20:34 ` [PATCH 1/2] omap2+: mux: Fix compile when CONFIG_OMAP_MUX is not selected Tony Lindgren
2011-03-11 20:34 ` [PATCH 2/2] omap4: mux: Remove duplicate mux modes Tony Lindgren
2011-03-14 8:41 ` Cousson, Benoit
2011-03-14 16:59 ` Tony Lindgren
2011-03-14 17:22 ` Cousson, Benoit [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=4D7E4ECA.5010200@ti.com \
--to=b-cousson@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 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).