1 files changed, 219 insertions, 60 deletions

diff --git a/arch/mn10300/Kconfig b/arch/mn10300/Kconfig
index 7c2a2f7f8dc1..365766a3d536 100644
--- a/arch/mn10300/Kconfig
+++ b/arch/mn10300/Kconfig
@@ -9,8 +9,19 @@ config MN10300
         def_bool y
         select HAVE_OPROFILE
 
-config AM33
-        def_bool y
+config AM33_2
+        def_bool n
+
+config AM33_3
+        def_bool n
+
+config AM34_2
+        def_bool n
+        select MN10300_HAS_ATOMIC_OPS_UNIT
+        select MN10300_HAS_CACHE_SNOOP
+
+config ERRATUM_NEED_TO_RELOAD_MMUCTR
+        def_bool y if AM33_3 || AM34_2
 
 config MMU
         def_bool y
@@ -37,7 +48,7 @@ config GENERIC_CALIBRATE_DELAY
         def_bool y
 
 config GENERIC_CMOS_UPDATE
-        def_bool y
+        def_bool n
 
 config GENERIC_FIND_NEXT_BIT
         def_bool y
@@ -45,6 +56,27 @@ config GENERIC_FIND_NEXT_BIT
 config GENERIC_HWEIGHT
         def_bool y
 
+config GENERIC_TIME
+        def_bool y
+
+config GENERIC_CLOCKEVENTS
+        def_bool y
+
+config GENERIC_CLOCKEVENTS_BUILD
+        def_bool y
+        depends on GENERIC_CLOCKEVENTS
+
+config GENERIC_CLOCKEVENTS_BROADCAST
+        bool
+
+config CEVT_MN10300
+       def_bool y
+       depends on GENERIC_CLOCKEVENTS
+
+config CSRC_MN10300
+       def_bool y
+       depends on GENERIC_TIME
+
 config GENERIC_BUG
         def_bool y
 
@@ -61,18 +93,14 @@ config GENERIC_HARDIRQS
 config HOTPLUG_CPU
         def_bool n
 
-config HZ
-        int
-        default 1000
-
-mainmenu "Matsushita MN10300/AM33 Kernel Configuration"
+mainmenu "Panasonic MN10300/AM33 Kernel Configuration"
 
 source "init/Kconfig"
 
 source "kernel/Kconfig.freezer"
 
 
-menu "Matsushita MN10300 system setup"
+menu "Panasonic MN10300 system setup"
 
 choice
         prompt "Unit type"
@@ -87,6 +115,10 @@ config MN10300_UNIT_ASB2303
 config MN10300_UNIT_ASB2305
         bool "ASB2305"
 
+config MN10300_UNIT_ASB2364
+        bool "ASB2364"
+        select SMSC911X_ARCH_HOOKS if SMSC911X
+
 endchoice
 
 choice
@@ -99,57 +131,51 @@ choice
 config MN10300_PROC_MN103E010
         bool "MN103E010"
         depends on MN10300_UNIT_ASB2303 || MN10300_UNIT_ASB2305
+        select AM33_2
+        select MN10300_PROC_HAS_TTYSM0
+        select MN10300_PROC_HAS_TTYSM1
+        select MN10300_PROC_HAS_TTYSM2
+
+config MN10300_PROC_MN2WS0050
+        bool "MN2WS0050"
+        depends on MN10300_UNIT_ASB2364
+        select AM34_2
         select MN10300_PROC_HAS_TTYSM0
         select MN10300_PROC_HAS_TTYSM1
         select MN10300_PROC_HAS_TTYSM2
 
 endchoice
 
-choice
-        prompt "Processor core support"
-        default MN10300_CPU_AM33V2
+config MN10300_HAS_ATOMIC_OPS_UNIT
+        def_bool n
         help
-          This option specifies the processor core for which the kernel will be
-          compiled. It affects the instruction set used.
-
-config MN10300_CPU_AM33V2
-        bool "AM33v2"
-
-endchoice
+          This should be enabled if the processor has an atomic ops unit
+          capable of doing LL/SC equivalent operations.
 
 config FPU
         bool "FPU present"
         default y
-        depends on MN10300_PROC_MN103E010
+        depends on MN10300_PROC_MN103E010 || MN10300_PROC_MN2WS0050
 
-choice
-        prompt "CPU Caching mode"
-        default MN10300_CACHE_WBACK
+config LAZY_SAVE_FPU
+        bool "Save FPU state lazily"
+        default y
+        depends on FPU && !SMP
         help
-          This option determines the caching mode for the kernel.
-
-          Write-Back caching mode involves the all reads and writes causing
-          the affected cacheline to be read into the cache first before being
-          operated upon. Memory is not then updated by a write until the cache
-          is filled and a cacheline needs to be displaced from the cache to
-          make room. Only at that point is it written back.
-
-          Write-Through caching only fetches cachelines from memory on a
-          read. Writes always get written directly to memory. If the affected
-          cacheline is also in cache, it will be updated too.
-
-          The final option is to turn of caching entirely.
+          Enable this to be lazy in the saving of the FPU state to the owning
+          task's thread struct.  This is useful if most tasks on the system
+          don't use the FPU as only those tasks that use it will pass it
+          between them, and the state needn't be saved for a task that isn't
+          using it.
 
-config MN10300_CACHE_WBACK
-        bool "Write-Back"
+          This can't be so easily used on SMP as the process that owns the FPU
+          state on a CPU may be currently running on another CPU, so for the
+          moment, it is disabled.
 
-config MN10300_CACHE_WTHRU
-        bool "Write-Through"
+source "arch/mn10300/mm/Kconfig.cache"
 
-config MN10300_CACHE_DISABLED
-        bool "Disabled"
-
-endchoice
+config MN10300_TLB_USE_PIDR
+        def_bool y
 
 menu "Memory layout options"
 
@@ -170,24 +196,55 @@ config KERNEL_TEXT_ADDRESS
 
 config KERNEL_ZIMAGE_BASE_ADDRESS
         hex "Base address of compressed vmlinux image"
-        default "0x90700000"
+        default "0x50700000"
 
+config BOOT_STACK_OFFSET
+        hex
+        default "0xF00" if SMP
+        default "0xFF0" if !SMP
+
+config BOOT_STACK_SIZE
+        hex
+        depends on SMP
+        default "0x100"
 endmenu
 
-config PREEMPT
-        bool "Preemptible Kernel"
-        help
-          This option reduces the latency of the kernel when reacting to
-          real-time or interactive events by allowing a low priority process to
-          be preempted even if it is in kernel mode executing a system call.
-          This allows applications to run more reliably even when the system is
-          under load.
+config SMP
+        bool "Symmetric multi-processing support"
+        default y
+        depends on MN10300_PROC_MN2WS0038 || MN10300_PROC_MN2WS0050
+        ---help---
+          This enables support for systems with more than one CPU. If you have
+          a system with only one CPU, like most personal computers, say N. If
+          you have a system with more than one CPU, say Y.
+
+          If you say N here, the kernel will run on single and multiprocessor
+          machines, but will use only one CPU of a multiprocessor machine. If
+          you say Y here, the kernel will run on many, but not all,
+          singleprocessor machines. On a singleprocessor machine, the kernel
+          will run faster if you say N here.
 
-          Say Y here if you are building a kernel for a desktop, embedded
-          or real-time system.  Say N if you are unsure.
+          See also <file:Documentation/i386/IO-APIC.txt>,
+          <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
+          <http://www.tldp.org/docs.html#howto>.
+
+          If you don't know what to do here, say N.
+
+config NR_CPUS
+        int
+        depends on SMP
+        default "2"
+
+config USE_GENERIC_SMP_HELPERS
+        bool
+        depends on SMP
+        default y
+
+source "kernel/Kconfig.preempt"
 
 config MN10300_CURRENT_IN_E2
         bool "Hold current task address in E2 register"
+        depends on !SMP
         default y
         help
           This option removes the E2/R2 register from the set available to gcc
@@ -209,12 +266,15 @@ config MN10300_USING_JTAG
           suppresses the use of certain hardware debugging features, such as
           single-stepping, which are taken over completely by the JTAG unit.
 
+source "kernel/Kconfig.hz"
+source "kernel/time/Kconfig"
+
 config MN10300_RTC
         bool "Using MN10300 RTC"
-        depends on MN10300_PROC_MN103E010
+        depends on MN10300_PROC_MN103E010 || MN10300_PROC_MN2WS0050
+        select GENERIC_CMOS_UPDATE
         default n
         help
-
           This option enables support for the RTC, thus enabling time to be
           tracked, even when system is powered down. This is available on-chip
           on the MN103E010.
@@ -306,14 +366,23 @@ config MN10300_TTYSM1
 
 choice
         prompt "Select the timer to supply the clock for SIF1"
-        default MN10300_TTYSM0_TIMER9
+        default MN10300_TTYSM1_TIMER12 \
+                if !(AM33_2 || AM33_3)
+        default MN10300_TTYSM1_TIMER9 \
+                if AM33_2 || AM33_3
         depends on MN10300_TTYSM1
 
+config MN10300_TTYSM1_TIMER12
+        bool "Use timer 12 (16-bit)"
+        depends on !(AM33_2 || AM33_3)
+
 config MN10300_TTYSM1_TIMER9
         bool "Use timer 9 (16-bit)"
+        depends on AM33_2 || AM33_3
 
 config MN10300_TTYSM1_TIMER3
         bool "Use timer 3 (8-bit)"
+        depends on AM33_2 || AM33_3
 
 endchoice
 
@@ -328,17 +397,107 @@ config MN10300_TTYSM2
 
 choice
         prompt "Select the timer to supply the clock for SIF2"
-        default MN10300_TTYSM0_TIMER10
+        default MN10300_TTYSM2_TIMER3 \
+                if !(AM33_2 || AM33_3)
+        default MN10300_TTYSM2_TIMER10 \
+                if AM33_2 || AM33_3
         depends on MN10300_TTYSM2
 
+config MN10300_TTYSM2_TIMER9
+        bool "Use timer 9 (16-bit)"
+        depends on !(AM33_2 || AM33_3)
+
+config MN10300_TTYSM2_TIMER1
+        bool "Use timer 1 (8-bit)"
+        depends on !(AM33_2 || AM33_3)
+
+config MN10300_TTYSM2_TIMER3
+        bool "Use timer 3 (8-bit)"
+        depends on !(AM33_2 || AM33_3)
+
 config MN10300_TTYSM2_TIMER10
         bool "Use timer 10 (16-bit)"
+        depends on AM33_2 || AM33_3
 
 endchoice
 
 config MN10300_TTYSM2_CTS
         bool "Enable the use of the CTS line /dev/ttySM2"
-        depends on MN10300_TTYSM2
+        depends on MN10300_TTYSM2 && AM33_2
+
+endmenu
+
+menu "Interrupt request priority options"
+
+comment "[!] NOTE: A lower number/level indicates a higher priority (0 is highest, 6 is lowest)"
+
+comment "____Non-maskable interrupt levels____"
+comment "The following must be set to a higher priority than local_irq_disable() and on-chip serial"
+
+config GDBSTUB_IRQ_LEVEL
+        int "GDBSTUB interrupt priority"
+        depends on GDBSTUB
+        range 0 1 if LINUX_CLI_LEVEL = 2
+        range 0 2 if LINUX_CLI_LEVEL = 3
+        range 0 3 if LINUX_CLI_LEVEL = 4
+        range 0 4 if LINUX_CLI_LEVEL = 5
+        range 0 5 if LINUX_CLI_LEVEL = 6
+        default 0
+
+comment "The following must be set to a higher priority than local_irq_disable()"
+
+config MN10300_SERIAL_IRQ_LEVEL
+        int "MN10300 on-chip serial interrupt priority"
+        depends on MN10300_TTYSM
+        range 1 1 if LINUX_CLI_LEVEL = 2
+        range 1 2 if LINUX_CLI_LEVEL = 3
+        range 1 3 if LINUX_CLI_LEVEL = 4
+        range 1 4 if LINUX_CLI_LEVEL = 5
+        range 1 5 if LINUX_CLI_LEVEL = 6
+        default 1
+
+comment "-"
+comment "____Maskable interrupt levels____"
+
+config LINUX_CLI_LEVEL
+        int "The highest interrupt priority excluded by local_irq_disable() (2-6)"
+        range 2 6
+        default 2
+        help
+          local_irq_disable() doesn't actually disable maskable interrupts -
+          what it does is restrict the levels of interrupt which are permitted
+          (a lower level indicates a higher priority) by lowering the value in
+          EPSW.IM from 7.  Any interrupt is permitted for which the level is
+          lower than EPSW.IM.
+
+          Certain interrupts, such as GDBSTUB and virtual MN10300 on-chip
+          serial DMA interrupts are allowed to interrupt normal disabled
+          sections.
+
+comment "The following must be set to a equal to or lower priority than LINUX_CLI_LEVEL"
+
+config TIMER_IRQ_LEVEL
+        int "Kernel timer interrupt priority"
+        range LINUX_CLI_LEVEL 6
+        default 4
+
+config PCI_IRQ_LEVEL
+        int "PCI interrupt priority"
+        depends on PCI
+        range LINUX_CLI_LEVEL 6
+        default 5
+
+config ETHERNET_IRQ_LEVEL
+        int "Ethernet interrupt priority"
+        depends on SMC91X || SMC911X || SMSC911X
+        range LINUX_CLI_LEVEL 6
+        default 6
+
+config EXT_SERIAL_IRQ_LEVEL
+        int "External serial port interrupt priority"
+        depends on SERIAL_8250
+        range LINUX_CLI_LEVEL 6
+        default 6
 
 endmenu