Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Paul Walmsley <paul@pwsan.com>
Subject: Re: [RFC/PATCH 8/7] ARM: OMAP: AM35xx: convert 3517 detection/flags to AM35xx
Date: Mon, 09 Jan 2012 15:06:15 -0800	[thread overview]
Message-ID: <87zkdwxyqg.fsf@ti.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A80752F2@DBDE01.ent.ti.com> (Vaibhav Hiremath's message of "Sun, 8 Jan 2012 07:02:03 +0000")

"Hiremath, Vaibhav" <hvaibhav@ti.com> writes:

>> -----Original Message-----
>> From: Hilman, Kevin
>> Sent: Saturday, January 07, 2012 12:24 AM
>> To: linux-omap@vger.kernel.org
>> Cc: Paul Walmsley; Hiremath, Vaibhav
>> Subject: [RFC/PATCH 8/7] ARM: OMAP: AM35xx: convert 3517 detection/flags
>> to AM35xx
>> 
>> Currently cpu_is_omap3517() actually detects any device in the AM35x
>> family (3517 and no-SGX version 3505.)  To make it more clear what is
>> being detected, convert the names from 3517 to AM35xx.
>> 
>> For the same reason, replace the CK_3517 flag used in the clock data
>> to CK_AM35XX.
>> 
>> Signed-off-by: Kevin Hilman <khilman@ti.com>
>> ---
>>  arch/arm/mach-omap2/clock3xxx_data.c          |    8 ++++----
>>  arch/arm/mach-omap2/hsmmc.c                   |    8 ++++----
>>  arch/arm/mach-omap2/id.c                      |    7 +++----
>>  arch/arm/mach-omap2/omap_hwmod_3xxx_data.c    |    2 +-
>>  arch/arm/mach-omap2/powerdomains3xxx_data.c   |    2 +-
>>  arch/arm/mach-omap2/usb-musb.c                |    2 +-
>>  arch/arm/mach-omap2/voltagedomains3xxx_data.c |    2 +-
>>  arch/arm/plat-omap/include/plat/clkdev_omap.h |    3 +--
>>  arch/arm/plat-omap/include/plat/cpu.h         |   15 +++++++--------
>>  9 files changed, 23 insertions(+), 26 deletions(-)
>> 
> Is this also right time to change Makefile and Kconfig files???
> Change in board/mach-types/Makefile/Kconfig files will bring
> consistency across...

Probably, yes.  Although Tony might thing that is too much churn.

Feel free to spin up a patch and I'll add it to this series and we'll
see what Tony thinks.

Kevin

  reply	other threads:[~2012-01-09 23:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05  1:16 [PATCH 0/7] ARM: OMAP: remove IP checks from SoC family detection Kevin Hilman
2012-01-05  1:16 ` [RFC/PATCH 1/7] ARM: OMAP: remove unused cpu_is macros that depend on specific IP checks Kevin Hilman
2012-01-05  1:16 ` [RFC/PATCH 2/7] ARM: OMAP3: clock data: replace 3503/3517 flag with AM35x flag for UART4 Kevin Hilman
2012-01-05  1:16 ` [RFC/PATCH 3/7] ARM: OMAP3: clock data: treat all AM35x devices the same Kevin Hilman
2012-01-05  9:48   ` Jean Pihet
2012-01-06  0:59     ` Kevin Hilman
2012-01-05 11:07   ` Hiremath, Vaibhav
2012-01-06  0:04     ` Kevin Hilman
2012-01-06  8:59       ` Hiremath, Vaibhav
2012-01-05  1:16 ` [RFC/PATCH 4/7] ARM: OMAP: AM35x: remove redunant cpu_is checks for AM3505 Kevin Hilman
2012-01-05 11:06   ` Hiremath, Vaibhav
2012-01-05  1:16 ` [RFC/PATCH 5/7] ARM: OMAP: clock: remove unused CK_3505 flag Kevin Hilman
2012-01-05 11:06   ` Hiremath, Vaibhav
2012-01-05  1:16 ` [RFC/PATCH 6/7] ARM: OMAP: remove unused cpu_is_omap3505() Kevin Hilman
2012-01-05  1:16 ` [RFC/PATCH 7/7] ARM: OMAP: remove unused cpu_is_omap3530() Kevin Hilman
2012-01-05 11:07   ` Hiremath, Vaibhav
2012-01-05 11:15 ` [PATCH 0/7] ARM: OMAP: remove IP checks from SoC family detection Hiremath, Vaibhav
2012-01-06 18:55   ` Kevin Hilman
2012-01-08  8:56     ` Hiremath, Vaibhav
2012-01-06 18:53 ` [RFC/PATCH 8/7] ARM: OMAP: AM35xx: convert 3517 detection/flags to AM35xx Kevin Hilman
2012-01-08  7:02   ` Hiremath, Vaibhav
2012-01-09 23:06     ` Kevin Hilman [this message]
2012-01-11 16:29       ` Hiremath, Vaibhav
2012-01-12  5:58       ` Hiremath, Vaibhav

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=87zkdwxyqg.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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