From: Tony Lindgren <tony@atomide.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: khilman@deeprootsystems.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/4] ARM: OMAP4+: PM: Consolidate OMAP4 PM code to re-use it for OMAP5
Date: Tue, 9 Apr 2013 09:55:03 -0700 [thread overview]
Message-ID: <20130409165503.GM10155@atomide.com> (raw)
In-Reply-To: <5163B19E.30105@ti.com>
* Santosh Shilimkar <santosh.shilimkar@ti.com> [130408 23:16]:
> >
> As I said, the IP has been there from OMAP2XX days. Here the case that
> IP version is very similar between OMAP4, OMAP5. DRA(next SOC) and its
> derivatives. Hence can share most of the code. I thought this was good
> enough reason considering at least 4 family of SOC's can make use
> of the code.
Well at least that might be enough of a reasoning to rename it as
it is somewhat futureproof.
> It has nothing to do with SMP etc specifically and rather the similarity
> between the PM infrastructure on the mentioned SOCs.
>
> Let me know if you can suggested better name than what I chose ?
Not really except something like pm-iprevXXX.[chS] where the rev is
the first revision that it works with?
But then again if it's touching registers all over the place directly,
that naming does not make much sense either :)
Regards,
Tony
next prev parent reply other threads:[~2013-04-09 16:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 12:58 [PATCH v3 0/4] ARM: OMAP4+: PM: Consolidate code for re-use on OMAP5 Santosh Shilimkar
2013-04-05 12:59 ` [PATCH v3 1/4] ARM: OMAP4+: PM: Consolidate MPU subsystem PM code for re-use Santosh Shilimkar
2013-04-05 13:19 ` Felipe Balbi
2013-04-05 13:35 ` Nishanth Menon
2013-04-05 13:39 ` Santosh Shilimkar
2013-04-05 14:04 ` Felipe Balbi
2013-04-05 14:18 ` Nishanth Menon
2013-04-05 14:29 ` Felipe Balbi
2013-04-05 13:37 ` Santosh Shilimkar
2013-04-05 12:59 ` [PATCH v3 2/4] ARM: OMAP4+: PM: Consolidate OMAP4 PM code to re-use it for OMAP5 Santosh Shilimkar
2013-04-05 13:21 ` Felipe Balbi
2013-04-05 13:35 ` Santosh Shilimkar
2013-04-05 21:34 ` Tony Lindgren
2013-04-08 10:48 ` Santosh Shilimkar
2013-04-08 16:42 ` Tony Lindgren
2013-04-09 6:13 ` Santosh Shilimkar
2013-04-09 16:55 ` Tony Lindgren [this message]
2013-04-10 6:17 ` Santosh Shilimkar
2013-04-05 12:59 ` [PATCH v3 3/4] ARM: OMAP4+: Make secondary_startup function name more consistent Santosh Shilimkar
2013-04-05 12:59 ` [PATCH v3 4/4] ARM: OMAP4+: CPUidle: Consolidate idle driver for OMAP5 support Santosh Shilimkar
2013-04-05 21:29 ` Kevin Hilman
2013-04-05 23:42 ` [PATCH v3 0/4] ARM: OMAP4+: PM: Consolidate code for re-use on OMAP5 Kevin Hilman
2013-04-08 11:03 ` 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=20130409165503.GM10155@atomide.com \
--to=tony@atomide.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@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;
as well as URLs for NNTP newsgroup(s).