OMAP3: Common mechanism to identify cpu revision
Subsystems (5)
PATCH 1/1 OMAP3: Common mechanism to identify cpu revision
There are multiple mechanisms to identify the cpu revisions. Most common is use of omap_rev(). This, however, does a absolute comparison of omap_revision - which includes CPU id, CPU rev and CPU class. This comparison fails for OMAP35x processors.
This patch defines generic functions that use only the CPU rev bits in omap_revision to identify the revision information.
Usage will change from (for example):
if (omap_rev() > OMAP3430_REV_ES2_0) to: if (cpu_is_omap34xx() && omap_rev_gt_2_0())
Specific check for cpu_is_xxx() will not be needed for files specific to silicon e.g. pm34xx.c, clock34xx.c, etc.
--- arch/arm/mach-omap2/clock34xx.c | 4 +- arch/arm/mach-omap2/control.c | 6 ++-- arch/arm/mach-omap2/pm34xx.c | 17 +++++----- arch/arm/plat-omap/include/mach/cpu.h | 55 +++++++++++++++++++++++++++++++++ 4 files changed, 69 insertions(+), 13 deletions(-)
arch/arm/mach-omap2/clock34xx.c +2 -2
@@ -815,7 +815,7 @@ static int omap3_dpll4_set_rate(struct clk *clk, unsigned long rate)* on 3430ES1 prevents us from changing DPLL multipliers or dividers * on DPLL4. */ -if (omap_rev () ==OMAP3430_REV_ES1_0 ) { +if (omap_rev_is_1_0 ()) {printk (KERN_ERR "clock: DPLL4 cannot change rate due to " "silicon 'Limitation 2.5' on 3430ES1.\n" );return -EINVAL ;
@@ -1157,7 +1157,7 @@ int __init omap2_clk_init(void)* Update this if there are further clock changes between ES2 * and production parts */ -if (omap_rev () ==OMAP3430_REV_ES1_0 ) { +if (omap_rev_is_1_0 ()) {/* No 3430ES1-only rates exist, so no RATE_IN_3430ES1 */ cpu_clkflg |=CK_3430ES1 ; }else {
arch/arm/mach-omap2/control.c +3 -3
@@ -209,8 +209,8 @@ void omap3_save_scratchpad_contents(void)/* Populate the Scratchpad contents */ scratchpad_contents.boot_config_ptr =0x0 ; -if (omap_rev () !=OMAP3430_REV_ES3_0 && -omap_rev () !=OMAP3430_REV_ES3_1 ) +if (cpu_is_omap34xx () + && !omap_rev_is_3_0 () && !omap_rev_is_3_1 ()) scratchpad_contents.public_restore_ptr =virt_to_phys (get_restore_pointer ());else
@@ -271,7 +271,7 @@ void omap3_save_scratchpad_contents(void)* of AUTO_CNT = 1 prior to any transition to OFF mode. */ if ((omap_type () !=OMAP2_DEVICE_TYPE_GP ) - && (omap_rev () >=OMAP3430_REV_ES3_0 )) + &&cpu_is_omap34xx () &&omap_rev_ge_3_0 ()) sdrc_block_contents.power = (sdrc_read_reg (SDRC_POWER ) & ~(SDRC_POWER_AUTOCOUNT_MASK | SDRC_POWER_CLKCTRL_MASK)) |
arch/arm/mach-omap2/pm34xx.c +9 -8
@@ -28,6 +28,7 @@#include <linux/clk.h> #include <linux/usb/musb.h> +#include <mach/cpu.h> #include <mach/sram.h> #include <mach/prcm.h> #include <mach/clockdomain.h>
@@ -108,7 +109,7 @@ static void omap3_enable_io_chain(void) {int timeout =0 ; -if (omap_rev () >=OMAP3430_REV_ES3_1 ) { +if (omap_rev_ge_3_1 ()) {prm_set_mod_reg_bits (OMAP3430_EN_IO_CHAIN ,WKUP_MOD ,PM_WKEN );/* Do a readback to assure write has been done */ prm_read_mod_reg (WKUP_MOD ,PM_WKEN );
@@ -129,7 +130,7 @@ static void omap3_enable_io_chain(void)static void omap3_disable_io_chain (void ) { -if (omap_rev () >=OMAP3430_REV_ES3_1 ) +if (omap_rev_ge_3_1 ())prm_clear_mod_reg_bits (OMAP3430_EN_IO_CHAIN ,WKUP_MOD ,PM_WKEN ); }
@@ -248,7 +249,7 @@ static int _prcm_int_handle_wakeup(void) c =prcm_clear_mod_irqs (WKUP_MOD ,1 ); c +=prcm_clear_mod_irqs (CORE_MOD ,1 ); c +=prcm_clear_mod_irqs (OMAP3430_PER_MOD ,1 ); -if (omap_rev () >OMAP3430_REV_ES1_0 ) { +if (omap_rev_gt_1_0 ()) { c +=prcm_clear_mod_irqs (CORE_MOD ,3 ); c +=prcm_clear_mod_irqs (OMAP3430ES2_USBHOST_MOD ,1 ); }
@@ -432,7 +433,7 @@ void omap_sram_idle(void)* of AUTO_CNT = 1 enabled. This takes care of errata 1.142. * Hence store/restore the SDRC_POWER register here. */ -if (omap_rev () >=OMAP3430_REV_ES3_0 && +if (omap_rev_ge_3_0 () &&omap_type () !=OMAP2_DEVICE_TYPE_GP && core_next_state ==PWRDM_POWER_OFF ) sdrc_pwr =sdrc_read_reg (SDRC_POWER );
@@ -449,7 +450,7 @@ void omap_sram_idle(void)cpu_init ();/* Restore normal SDRC POWER settings */ -if (omap_rev () >=OMAP3430_REV_ES3_0 && +if (omap_rev_ge_3_0 () &&omap_type () !=OMAP2_DEVICE_TYPE_GP && core_next_state ==PWRDM_POWER_OFF )sdrc_write_reg (sdrc_pwr,SDRC_POWER );
@@ -784,7 +785,7 @@ static void __init prcm_setup_regs(void)prm_write_mod_reg (0 ,OMAP3430_NEON_MOD ,PM_WKDEP );prm_write_mod_reg (0 ,OMAP3430_CAM_MOD ,PM_WKDEP );prm_write_mod_reg (0 ,OMAP3430_PER_MOD ,PM_WKDEP ); -if (omap_rev () >OMAP3430_REV_ES1_0 ) { +if (omap_rev_gt_1_0 ()) {prm_write_mod_reg (0 ,OMAP3430ES2_SGX_MOD ,PM_WKDEP );prm_write_mod_reg (0 ,OMAP3430ES2_USBHOST_MOD ,PM_WKDEP ); }else
@@ -835,7 +836,7 @@ static void __init prcm_setup_regs(void)OMAP3430_AUTO_DES1 , CORE_MOD, CM_AUTOIDLE2); -if (omap_rev () >OMAP3430_REV_ES1_0 ) { +if (omap_rev_gt_1_0 ()) { cm_write_mod_reg( OMAP3430_AUTO_MAD2D | OMAP3430ES2_AUTO_USBTLL,
@@ -883,7 +884,7 @@ static void __init prcm_setup_regs(void)OMAP3430_PER_MOD , CM_AUTOIDLE); -if (omap_rev () >OMAP3430_REV_ES1_0 ) { +if (omap_rev_gt_1_0 ()) { cm_write_mod_reg( OMAP3430ES2_AUTO_USBHOST, OMAP3430ES2_USBHOST_MOD,
arch/arm/plat-omap/include/mach/cpu.h +55 -0
61 lines not on this page · raw message
Signature · 1 line
1.6.2.2
Quoted 11 lines · Sanjeev Premi
There are multiple mechanisms to identify the cpu revisions. Most common is use of
omap_rev(). This, however, does a absolute comparison ofomap_revision- which includes CPU id, CPU rev and CPU class. This comparison fails for OMAP35x processors.This patch defines generic functions that use only the CPU rev bits in
omap_revisionto identify the revision information.Usage will change from (for example):
Quoted 8 lines
if (omap_rev() > OMAP3430_REV_ES2_0) to: if (cpu_is_omap34xx() && omap_rev_gt_2_0())Specific check for
cpu_is_xxx()will not be needed for files specific to silicon e.g.pm34xx.c,clock34xx.c, etc.Signed-off-by Sanjeev Premi <[email protected]>
Looks mostly good, some minor comments/questions below...
Quoted 45 lines
--- arch/arm/mach-omap2/clock34xx.c | 4 +- arch/arm/mach-omap2/control.c | 6 ++-- arch/arm/mach-omap2/pm34xx.c | 17 +++++----- arch/arm/plat-omap/include/mach/cpu.h | 55 +++++++++++++++++++++++++++++++++ 4 files changed, 69 insertions(+), 13 deletions(-)arch/arm/mach-omap2/clock34xx.c +2
-2@@ -815,7 +815,7 @@ static int omap3_dpll4_set_rate(struct clk *clk, unsigned long rate)* on 3430ES1 prevents us from changing DPLL multipliers or dividers * on DPLL4. */ -if (omap_rev () ==OMAP3430_REV_ES1_0 ) { +if (omap_rev_is_1_0 ()) {printk (KERN_ERR "clock: DPLL4 cannot change rate due to " "silicon 'Limitation 2.5' on 3430ES1.\n" );return -EINVAL ;@@ -1157,7 +1157,7 @@ int __init omap2_clk_init(void)* Update this if there are further clock changes between ES2 * and production parts */ -if (omap_rev () ==OMAP3430_REV_ES1_0 ) { +if (omap_rev_is_1_0 ()) {/* No 3430ES1-only rates exist, so no RATE_IN_3430ES1 */ cpu_clkflg |=CK_3430ES1 ; }else {arch/arm/mach-omap2/control.c +2
-2@@ -209,8 +209,8 @@ void omap3_save_scratchpad_contents(void)/* Populate the Scratchpad contents */ scratchpad_contents.boot_config_ptr =0x0 ; -if (omap_rev () !=OMAP3430_REV_ES3_0 && -omap_rev () !=OMAP3430_REV_ES3_1 ) +if (cpu_is_omap34xx () + && !omap_rev_is_3_0 () && !omap_rev_is_3_1 ()) scratchpad_contents.public_restore_ptr =virt_to_phys (get_restore_pointer ());else
arch/arm/mach-omap2/control.c void omap3_save_scratchpad_contents(void) · line 274
Quoted 5 lines
arch/arm/mach-omap2/control.c +1
-1@@ -271,7 +271,7 @@ void omap3_save_scratchpad_contents(void)* of AUTO_CNT = 1 prior to any transition to OFF mode. */ if ((omap_type () !=OMAP2_DEVICE_TYPE_GP ) - && (omap_rev () >=OMAP3430_REV_ES3_0 )) + &&cpu_is_omap34xx () &&omap_rev_ge_3_0 ())
I don't think the cpu_is_... is needed here because of the OMAP3 specific function.
Quoted 92 lines
arch/arm/mach-omap2/control.c +0
-0sdrc_block_contents.power = (sdrc_read_reg (SDRC_POWER ) & ~(SDRC_POWER_AUTOCOUNT_MASK | SDRC_POWER_CLKCTRL_MASK)) |arch/arm/mach-omap2/pm34xx.c +9
-8@@ -28,6 +28,7 @@#include <linux/clk.h> #include <linux/usb/musb.h> +#include <mach/cpu.h> #include <mach/sram.h> #include <mach/prcm.h> #include <mach/clockdomain.h> @@ -108,7 +109,7 @@ static void omap3_enable_io_chain(void) {int timeout =0 ; -if (omap_rev () >=OMAP3430_REV_ES3_1 ) { +if (omap_rev_ge_3_1 ()) {prm_set_mod_reg_bits (OMAP3430_EN_IO_CHAIN ,WKUP_MOD ,PM_WKEN );/* Do a readback to assure write has been done */ prm_read_mod_reg (WKUP_MOD ,PM_WKEN );@@ -129,7 +130,7 @@ static void omap3_enable_io_chain(void)static void omap3_disable_io_chain (void ) { -if (omap_rev () >=OMAP3430_REV_ES3_1 ) +if (omap_rev_ge_3_1 ())prm_clear_mod_reg_bits (OMAP3430_EN_IO_CHAIN ,WKUP_MOD ,PM_WKEN ); }@@ -248,7 +249,7 @@ static int _prcm_int_handle_wakeup(void) c =prcm_clear_mod_irqs (WKUP_MOD ,1 ); c +=prcm_clear_mod_irqs (CORE_MOD ,1 ); c +=prcm_clear_mod_irqs (OMAP3430_PER_MOD ,1 ); -if (omap_rev () >OMAP3430_REV_ES1_0 ) { +if (omap_rev_gt_1_0 ()) { c +=prcm_clear_mod_irqs (CORE_MOD ,3 ); c +=prcm_clear_mod_irqs (OMAP3430ES2_USBHOST_MOD ,1 ); }@@ -432,7 +433,7 @@ void omap_sram_idle(void)* of AUTO_CNT = 1 enabled. This takes care of errata 1.142. * Hence store/restore the SDRC_POWER register here. */ -if (omap_rev () >=OMAP3430_REV_ES3_0 && +if (omap_rev_ge_3_0 () &&omap_type () !=OMAP2_DEVICE_TYPE_GP && core_next_state ==PWRDM_POWER_OFF ) sdrc_pwr =sdrc_read_reg (SDRC_POWER );@@ -449,7 +450,7 @@ void omap_sram_idle(void)cpu_init ();/* Restore normal SDRC POWER settings */ -if (omap_rev () >=OMAP3430_REV_ES3_0 && +if (omap_rev_ge_3_0 () &&omap_type () !=OMAP2_DEVICE_TYPE_GP && core_next_state ==PWRDM_POWER_OFF )sdrc_write_reg (sdrc_pwr,SDRC_POWER );@@ -784,7 +785,7 @@ static void __init prcm_setup_regs(void)prm_write_mod_reg (0 ,OMAP3430_NEON_MOD ,PM_WKDEP );prm_write_mod_reg (0 ,OMAP3430_CAM_MOD ,PM_WKDEP );prm_write_mod_reg (0 ,OMAP3430_PER_MOD ,PM_WKDEP ); -if (omap_rev () >OMAP3430_REV_ES1_0 ) { +if (omap_rev_gt_1_0 ()) {prm_write_mod_reg (0 ,OMAP3430ES2_SGX_MOD ,PM_WKDEP );prm_write_mod_reg (0 ,OMAP3430ES2_USBHOST_MOD ,PM_WKDEP ); }else @@ -835,7 +836,7 @@ static void __init prcm_setup_regs(void)OMAP3430_AUTO_DES1 , CORE_MOD, CM_AUTOIDLE2); -if (omap_rev () >OMAP3430_REV_ES1_0 ) { +if (omap_rev_gt_1_0 ()) { cm_write_mod_reg( OMAP3430_AUTO_MAD2D | OMAP3430ES2_AUTO_USBTLL,@@ -883,7 +884,7 @@ static void __init prcm_setup_regs(void)OMAP3430_PER_MOD , CM_AUTOIDLE); -if (omap_rev () >OMAP3430_REV_ES1_0 ) { +if (omap_rev_gt_1_0 ()) { cm_write_mod_reg( OMAP3430ES2_AUTO_USBHOST, OMAP3430ES2_USBHOST_MOD,arch/arm/plat-omap/include/mach/cpu.h +0
-0
arch/arm/plat-omap/include/mach/cpu.h IS_OMAP_TYPE(3517, 0x3517) · line 462
Quoted 10 lines
arch/arm/plat-omap/include/mach/cpu.h +7
-0@@ -453,6 +453,61 @@ IS_OMAP_TYPE(3517, 0x3517)#define omap35xx_rev_mask () (omap_rev() & 0x0000F000)/* +* Silicon revisions +*/ +#define OMAP_ES_1_0 0x00 +#define OMAP_ES_2_0 0x10 +#define OMAP_ES_2_1 0x20 +#define OMAP_ES_3_0 0x30 +#define OMAP_ES_3_1 0x40
Hmm, are these the same values on OMAP2? and OMAP4?
arch/arm/plat-omap/include/mach/cpu.h IS_OMAP_TYPE(3517, 0x3517) · line 468
Quoted 5 lines
arch/arm/plat-omap/include/mach/cpu.h +5
-0+#define OMAP_REV_MASK 0x0000ff00 +#define OMAP_REV_BITS ((omap_rev() & OMAP_REV_MASK) >> 8) + +#define OMAP_REV_IS (revid) \ +static inline u8 omap_rev_is_ ##revid (void) \
Minor nit, but these should return bool.
Quoted 35 lines
arch/arm/plat-omap/include/mach/cpu.h +35
-0+{ \ + return (OMAP_REV_BITS == OMAP_ES_ ##revid) ? 1 : 0; \ +} + +#define OMAP_REV_LT (revid) \ +static inline u8 omap_rev_lt_ ##revid (void) \ +{ \ + return (OMAP_REV_BITS < OMAP_ES_ ##revid) ? 1 : 0; \ +} + +#define OMAP_REV_LE (revid) \ +static inline u8 omap_rev_le_ ##revid (void) \ +{ \ + return (OMAP_REV_BITS <= OMAP_ES_ ##revid) ? 1 : 0; \ +} + +#define OMAP_REV_GT (revid) \ +static inline u8 omap_rev_gt_ ##revid (void) \ +{ \ + return (OMAP_REV_BITS > OMAP_ES_ ##revid) ? 1 : 0; \ +} + +#define OMAP_REV_GE (revid) \ +static inline u8 omap_rev_ge_ ##revid (void) \ +{ \ + return (OMAP_REV_BITS >= OMAP_ES_ ##revid) ? 1 : 0; \ +} + +#define OMAP_REV_FUNCTIONS (revid) \ + OMAP_REV_IS(revid) \ + OMAP_REV_LT(revid) \ + OMAP_REV_LE(revid) \ + OMAP_REV_GT(revid) \ + OMAP_REV_GE(revid) +
arch/arm/plat-omap/include/mach/cpu.h IS_OMAP_TYPE(3517, 0x3517) · line 513
Quoted 10 lines
arch/arm/plat-omap/include/mach/cpu.h +7
-0+OMAP_REV_FUNCTIONS(1_0) +OMAP_REV_FUNCTIONS(2_0) +OMAP_REV_FUNCTIONS(2_1) +OMAP_REV_FUNCTIONS(3_0) +OMAP_REV_FUNCTIONS(3_1) + +/* * omap_chip bits * * CHIP_IS_OMAP{2420,2430,3430} indicate that a particular structure is
Kevin
Quoted 25 lines
-----Original Message-----
From: Kevin Hilman [mailto:[email protected]]
Sent: Wednesday, September 30, 2009 7:32 PM
To: Premi, Sanjeev
Cc: [email protected]
Subject: Re: [PATCH 1/1] OMAP3: Common mechanism to identify cpu revisionQuoted 15 lines · Sanjeev Premi
There are multiple mechanisms to identify the cpu revisions. Most common is use of
omap_rev(). This, however, does a absolute comparison ofomap_revision- which includes CPU id, CPU rev and CPU class. This comparison fails for OMAP35x processors.This patch defines generic functions that use only the CPU rev bits in
omap_revisionto identify the revision information.Usage will change from (for example):
if (omap_rev() > OMAP3430_REV_ES2_0) to: if (cpu_is_omap34xx() && omap_rev_gt_2_0())
Quoted 7 lines
Quoted 4 lines
Specific check for
cpu_is_xxx()will not be needed for files specific to silicon e.g.pm34xx.c,clock34xx.c, etc.Signed-off-by Sanjeev Premi <[email protected]>Looks mostly good, some minor comments/questions below...
[snip]--[snip]
Quoted 3 lines
I don't think the
cpu_is_... is needed here because of the OMAP3 specific function.
[sp] Yes. This can be removed.
Quoted 11 lines
arch/arm/plat-omap/include/mach/cpu.h IS_OMAP_TYPE(3517, 0x3517) · line 462
Quoted 8 lines
/*
+ * Silicon revisions
+ */arch/arm/plat-omap/include/mach/cpu.h +5
-0+#define OMAP_ES_1_0 0x00 +#define OMAP_ES_2_0 0x10 +#define OMAP_ES_2_1 0x20 +#define OMAP_ES_3_0 0x30 +#define OMAP_ES_3_1 0x40Hmm, are these the same values on OMAP2? and OMAP4?
[sp] Based on the values defined for OMAP2420 and OMA2430, these definitions are applicable. There aren't as many Revisions though.
Not sure if it will hold good for OMAP4..
Do you think, we make these definitions silicon specific now?
Quoted 9 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+#define OMAP_REV_MASK 0x0000ff00 +#define OMAP_REV_BITS ((omap_rev() &
OMAP_REV_MASK) >> 8)arch/arm/plat-omap/include/mach/cpu.h IS_OMAP_TYPE(3517, 0x3517)
Quoted 3 lines
arch/arm/plat-omap/include/mach/cpu.h +3
-0+ +#define OMAP_REV_IS (revid) \ +static inline u8 omap_rev_is_ ##revid (void)\Minor nit, but these should return bool.
[sp] I will update.
Quoted 8 lines
arch/arm/plat-omap/include/mach/cpu.h IS_OMAP_TYPE(3517, 0x3517)
Quoted 7 lines
arch/arm/plat-omap/include/mach/cpu.h +6
-0+{ \ + return (OMAP_REV_BITS == OMAP_ES_ ##revid) ? 1 : 0; \ +} + +#define OMAP_REV_LT (revid) \ +static inline u8 omap_rev_lt_ ##revid (void)\
[snip]--[snip]
Quoted 4 lines
Kevin
Quoted 74 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Premi, Sanjeev
Sent: Monday, October 05, 2009 7:18 PM
To: Kevin Hilman
Cc: [email protected]
Subject: RE: [PATCH 1/1] OMAP3: Common mechanism to identify cpu revisionQuoted 25 lines
-----Original Message-----
From: Kevin Hilman [mailto:[email protected]]
Sent: Wednesday, September 30, 2009 7:32 PM
To: Premi, Sanjeev
Cc: [email protected]
Subject: Re: [PATCH 1/1] OMAP3: Common mechanism to identify cpu revisionQuoted 15 lines · Sanjeev Premi
There are multiple mechanisms to identify the cpu revisions. Most common is use of
omap_rev(). This, however, does a absolute comparison ofomap_revision- which includes CPU id, CPU rev and CPU class. This comparison fails for OMAP35x processors.This patch defines generic functions that use only the CPU rev bits in
omap_revisionto identify the revision information.Usage will change from (for example):
if (omap_rev() > OMAP3430_REV_ES2_0) to: if (cpu_is_omap34xx() && omap_rev_gt_2_0())Quoted 7 lines
Quoted 4 lines
Specific check for
cpu_is_xxx()will not be needed for files specific to silicon e.g.pm34xx.c,clock34xx.c, etc.Signed-off-by Sanjeev Premi <[email protected]>Looks mostly good, some minor comments/questions below...
[snip]--[snip]
Quoted 3 lines
I don't think the
cpu_is_... is needed here because of the OMAP3 specific function.[sp] Yes. This can be removed.
Quoted 11 lines
arch/arm/plat-omap/include/mach/cpu.h IS_OMAP_TYPE(3517, 0x3517) · line 462
Quoted 8 lines
/*
+ * Silicon revisions
+ */arch/arm/plat-omap/include/mach/cpu.h +5
-0+#define OMAP_ES_1_0 0x00 +#define OMAP_ES_2_0 0x10 +#define OMAP_ES_2_1 0x20 +#define OMAP_ES_3_0 0x30 +#define OMAP_ES_3_1 0x40Hmm, are these the same values on OMAP2? and OMAP4?
[sp] Based on the values defined for OMAP2420 and OMA2430, these definitions are applicable. There aren't as many Revisions though.
Not sure if it will hold good for OMAP4..
Do you think, we make these definitions silicon specific now?
Quoted 5 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+#define OMAP_REV_MASK 0x0000ff00 +#define OMAP_REV_BITS ((omap_rev() &
OMAP_REV_MASK) >> 8)Review
Quoted 2 lines
(quoted diff) +2
-0+ +#define OMAP_REV_IS(revid)\
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
+static inline u8
omap_rev_is_##revid (void)\Minor nit, but these should return bool.
[sp] I will update.
Kevin, Tony,
The original patch was created against the pm branch.
While re-submitting, should I split in two - one against master and delta for pm branch?
Best regards,
Sanjeev
Quoted 23 lines
Quoted 3 lines
Quoted 3 lines
+{
\Quoted 4 lines
arch/arm/plat-omap/include/mach/cpu.h IS_OMAP_TYPE(3517, 0x3517)
Quoted 4 lines
arch/arm/plat-omap/include/mach/cpu.h +4
-0+ return (OMAP_REV_BITS == OMAP_ES_ ##revid) ? 1 : 0; \ +} + +#define OMAP_REV_LT (revid)\Quoted 2 lines
Quoted 1 line
+static inline u8
omap_rev_lt_##revid (void)\[snip]--[snip]
Quoted 4 lines
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 59 lines · Sanjeev
Quoted 59 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Premi, Sanjeev
Sent: Monday, October 05, 2009 7:18 PM
To: Kevin Hilman
Cc: [email protected]
Subject: RE: [PATCH 1/1] OMAP3: Common mechanism to identify cpu revisionQuoted 25 lines
-----Original Message-----
From: Kevin Hilman [mailto:[email protected]]
Sent: Wednesday, September 30, 2009 7:32 PM
To: Premi, Sanjeev
Cc: [email protected]
Subject: Re: [PATCH 1/1] OMAP3: Common mechanism to identify cpu revisionQuoted 15 lines · Sanjeev Premi
There are multiple mechanisms to identify the cpu revisions. Most common is use of
omap_rev(). This, however, does a absolute comparison ofomap_revision- which includes CPU id, CPU rev and CPU class. This comparison fails for OMAP35x processors.This patch defines generic functions that use only the CPU rev bits in
omap_revisionto identify the revision information.Usage will change from (for example):
if (omap_rev() > OMAP3430_REV_ES2_0) to: if (cpu_is_omap34xx() && omap_rev_gt_2_0())Quoted 7 lines
Quoted 4 lines
Specific check for
cpu_is_xxx()will not be needed for files specific to silicon e.g.pm34xx.c,clock34xx.c, etc.Signed-off-by Sanjeev Premi <[email protected]>Looks mostly good, some minor comments/questions below...
[snip]--[snip]
Quoted 3 lines
I don't think the
cpu_is_... is needed here because of the OMAP3 specific function.[sp] Yes. This can be removed.
Quoted 11 lines
arch/arm/plat-omap/include/mach/cpu.h IS_OMAP_TYPE(3517, 0x3517) · line 462
Quoted 8 lines
/*
+ * Silicon revisions
+ */arch/arm/plat-omap/include/mach/cpu.h +5
-0+#define OMAP_ES_1_0 0x00 +#define OMAP_ES_2_0 0x10 +#define OMAP_ES_2_1 0x20 +#define OMAP_ES_3_0 0x30 +#define OMAP_ES_3_1 0x40Hmm, are these the same values on OMAP2? and OMAP4?
Quoted 8 lines
Quoted 8 lines
[sp] Based on the values defined for OMAP2420 and OMA2430, these definitions are applicable. There aren't as many Revisions though.
Not sure if it will hold good for OMAP4..
Do you think, we make these definitions silicon specific now?
Not necessarily, for OMAP4, we can use OMAP4_ prefix. But you should add a comment that these are valid for OMAP2/3.
Quoted 11 lines
Quoted 11 lines
Quoted 5 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+#define OMAP_REV_MASK 0x0000ff00 +#define OMAP_REV_BITS ((omap_rev() &
OMAP_REV_MASK) >> 8)Review
Quoted 2 lines
(quoted diff) +2
-0+ +#define OMAP_REV_IS(revid)\Quoted 4 lines
Quoted 1 line
+static inline u8
omap_rev_is_##revid (void)\Minor nit, but these should return bool.
Quoted 8 lines
Quoted 1 line
[sp] I will update.
Kevin, Tony,
The original patch was created against the pm branch.
While re-submitting, should I split in two - one against master and delta for pm branch?
Yes. The main part of this should go into l-o master.
Kevin
Quoted 26 lines
Best regards,
SanjeevQuoted 23 lines
Quoted 3 lines
Quoted 3 lines
+{
\Quoted 4 lines
arch/arm/plat-omap/include/mach/cpu.h IS_OMAP_TYPE(3517, 0x3517)
Quoted 4 lines
arch/arm/plat-omap/include/mach/cpu.h +4
-0+ return (OMAP_REV_BITS == OMAP_ES_ ##revid) ? 1 : 0; \ +} + +#define OMAP_REV_LT (revid)\Quoted 2 lines
Quoted 1 line
+static inline u8
omap_rev_lt_##revid (void)\[snip]--[snip]
Quoted 4 lines
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html