From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Sricharan R <r.sricharan@ti.com>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
rnayak@ti.com, tony@atomide.com, marc.zyngier@arm.com,
mark.rutland@arm.com
Subject: Re: [PATCH] ARM: OMAP5/DRA7: realtime_counter: Configure CNTFRQ register
Date: Wed, 18 Sep 2013 09:45:13 -0400 [thread overview]
Message-ID: <5239AE69.6040600@ti.com> (raw)
In-Reply-To: <5239AE35.8030406@ti.com>
On Wednesday 18 September 2013 09:44 AM, Nishanth Menon wrote:
> On 09/18/2013 08:31 AM, Santosh Shilimkar wrote:
>> On Wednesday 18 September 2013 07:23 AM, Sricharan R wrote:
> [...]
> 4, 0, 0, 0, 0, 0);
>>>
>>> /*
>>> + * Configure the CNTFRQ register for the secondary cpu's which
>>> + * indicates the frequency of the cpu local timers.
>>> + */
>>> + if (soc_is_omap54xx() || soc_is_dra7xx())
>> CNTFREQ programming was not supported on OMAP5 ES1.0 and that was one
>> of the reason this parameter came into picture. So you need to skip
>> the ES1.0 here.
>>
> Even though ES1.0 is present in id.c, we have 0 support for ES1.0.
>
> ES1.0 was more or less a test chip, no production devices were
> manufactured with it, no public boards (including uevms) are available
> to purchase with ES1.0. Further, inside TI, all ES1.0 samples and
> boards have been scrapped and replaced with ES2.0 platforms.
>
> In short, no users and dead code in kernel tree. I dont see why we
> cant just cleanup OMAP5 ES1.0 entirely from kernel tree?
>
Yes...There is no reason to keep broken ES1.0 support. Patch please ;-)
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP5/DRA7: realtime_counter: Configure CNTFRQ register
Date: Wed, 18 Sep 2013 09:45:13 -0400 [thread overview]
Message-ID: <5239AE69.6040600@ti.com> (raw)
In-Reply-To: <5239AE35.8030406@ti.com>
On Wednesday 18 September 2013 09:44 AM, Nishanth Menon wrote:
> On 09/18/2013 08:31 AM, Santosh Shilimkar wrote:
>> On Wednesday 18 September 2013 07:23 AM, Sricharan R wrote:
> [...]
> 4, 0, 0, 0, 0, 0);
>>>
>>> /*
>>> + * Configure the CNTFRQ register for the secondary cpu's which
>>> + * indicates the frequency of the cpu local timers.
>>> + */
>>> + if (soc_is_omap54xx() || soc_is_dra7xx())
>> CNTFREQ programming was not supported on OMAP5 ES1.0 and that was one
>> of the reason this parameter came into picture. So you need to skip
>> the ES1.0 here.
>>
> Even though ES1.0 is present in id.c, we have 0 support for ES1.0.
>
> ES1.0 was more or less a test chip, no production devices were
> manufactured with it, no public boards (including uevms) are available
> to purchase with ES1.0. Further, inside TI, all ES1.0 samples and
> boards have been scrapped and replaced with ES2.0 platforms.
>
> In short, no users and dead code in kernel tree. I dont see why we
> cant just cleanup OMAP5 ES1.0 entirely from kernel tree?
>
Yes...There is no reason to keep broken ES1.0 support. Patch please ;-)
Regards,
Santosh
next prev parent reply other threads:[~2013-09-18 13:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 11:23 [PATCH] ARM: OMAP5/DRA7: realtime_counter: Configure CNTFRQ register Sricharan R
2013-09-18 11:23 ` Sricharan R
2013-09-18 13:00 ` Nishanth Menon
2013-09-18 13:00 ` Nishanth Menon
2013-09-18 13:31 ` Santosh Shilimkar
2013-09-18 13:31 ` Santosh Shilimkar
2013-09-18 13:44 ` Sricharan R
2013-09-18 13:44 ` Sricharan R
2013-09-18 13:49 ` Santosh Shilimkar
2013-09-18 13:49 ` Santosh Shilimkar
2013-09-18 13:51 ` Sricharan R
2013-09-18 13:51 ` Sricharan R
2013-09-18 13:44 ` Nishanth Menon
2013-09-18 13:44 ` Nishanth Menon
2013-09-18 13:45 ` Santosh Shilimkar [this message]
2013-09-18 13:45 ` Santosh Shilimkar
2013-09-18 14:05 ` [PATCH] ARM: OMAP5: id: Remove ES1.0 support Nishanth Menon
2013-09-18 14:05 ` Nishanth Menon
2013-09-18 14:07 ` Santosh Shilimkar
2013-09-18 14:07 ` Santosh Shilimkar
2013-10-08 21:31 ` Tony Lindgren
2013-10-08 21:31 ` Tony Lindgren
2013-10-08 21:34 ` Santosh Shilimkar
2013-10-08 21:34 ` Santosh Shilimkar
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=5239AE69.6040600@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=r.sricharan@ti.com \
--cc=rnayak@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 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.