sh: oprofile: Fix up the SH7750 performance counter name.

Rather than varying this on a subtype level, we use the counter type as a
generic identifier. This simplifies logic in the userspace tools where no
fundamental difference exists across the various subtypes.

Signed-off-by: Paul Mundt <lethal@linux-sh.org>

diff --git a/arch/sh/oprofile/op_model_sh7750.c b/arch/sh/oprofile/op_model_sh7750.c
index 6b9a98e07004a09f30e34d4335e26aa62e788328..008b3b03750aa94f78f44a601f5de0f2a5af5aea 100644 (file)
--- a/arch/sh/oprofile/op_model_sh7750.c
+++ b/arch/sh/oprofile/op_model_sh7750.c
@@ -255,10 +255,9 @@ int __init oprofile_arch_init(struct oprofile_operations *ops)
                return -ENODEV;
 
        ops = &sh7750_perf_counter_ops;
-       ops->cpu_type = (char *)get_cpu_subtype(&current_cpu_data);
+       ops->cpu_type = "sh/sh7750";
 
-       printk(KERN_INFO "oprofile: using SH-4 (%s) performance monitoring.\n",
-              sh7750_perf_counter_ops.cpu_type);
+       printk(KERN_INFO "oprofile: using SH-4 performance monitoring.\n");
 
        /* Clear the counters */
        ctrl_outw(ctrl_inw(PMCR1) | PMCR_PMCLR, PMCR1);
@@ -270,4 +269,3 @@ int __init oprofile_arch_init(struct oprofile_operations *ops)
 void oprofile_arch_exit(void)
 {
 }
-