Pull power management and ACPI updates from Rafael Wysocki:
"This time the total number of ACPI commits is slightly greater than
the number of cpufreq commits, but Viresh Kumar (who works on cpufreq)
remains the most active patch submitter.
To me, the most significant change is the addition of offline/online
device operations to the driver core (with the Greg's blessing) and
the related modifications of the ACPI core hotplug code. Next are the
freezer updates from Colin Cross that should make the freezing of
tasks a bit less heavy weight.
We also have a couple of regression fixes, a number of fixes for
issues that have not been identified as regressions, two new drivers
and a bunch of cleanups all over.
Highlights:
- Hotplug changes to support graceful hot-removal failures.
It sometimes is necessary to fail device hot-removal operations
gracefully if they cannot be carried out completely. For example,
if memory from a memory module being hot-removed has been allocated
for the kernel's own use and cannot be moved elsewhere, it's
desirable to fail the hot-removal operation in a graceful way
rather than to crash the kernel, but currenty a success or a kernel
crash are the only possible outcomes of an attempted memory
hot-removal. Needless to say, that is not a very attractive
alternative and it had to be addressed.
However, in order to make it work for memory, I first had to make
it work for CPUs and for this purpose I needed to modify the ACPI
processor driver. It's been split into two parts, a resident one
handling the low-level initialization/cleanup and a modular one
playing the actual driver's role (but it binds to the CPU system
device objects rather than to the ACPI device objects representing
processors). That's been sort of like a live brain surgery on a
patient who's riding a bike.
So this is a little scary, but since we found and fixed a couple of
regressions it caused to happen during the early linux-next testing
(a month ago), nobody has complained.
As a bonus we remove some duplicated ACPI hotplug code, because the
ACPI-based CPU hotplug is now going to use the common ACPI hotplug
code.
- Lighter weight freezing of tasks.
These changes from Colin Cross and Mandeep Singh Baines are
targeted at making the freezing of tasks a bit less heavy weight
operation. They reduce the number of tasks woken up every time
during the freezing, by using the observation that the freezer
simply doesn't need to wake up some of them and wait for them all
to call refrigerator(). The time needed for the freezer to decide
to report a failure is reduced too.
Also reintroduced is the check causing a lockdep warining to
trigger when try_to_freeze() is called with locks held (which is
generally unsafe and shouldn't happen).
- cpufreq updates
First off, a commit from Srivatsa S Bhat fixes a resume regression
introduced during the 3.10 cycle causing some cpufreq sysfs
attributes to return wrong values to user space after resume. The
fix is kind of fresh, but also it's pretty obvious once Srivatsa
has identified the root cause.
Second, we have a new freqdomain_cpus sysfs attribute for the
acpi-cpufreq driver to provide information previously available via
related_cpus. From Lan Tianyu.
Finally, we fix a number of issues, mostly related to the
CPUFREQ_POSTCHANGE notifier and cpufreq Kconfig options and clean
up some code. The majority of changes from Viresh Kumar with bits
from Jacob Shin, Heiko Stübner, Xiaoguang Chen, Ezequiel Garcia,
Arnd Bergmann, and Tang Yuantian.
- ACPICA update
A usual bunch of updates from the ACPICA upstream.
During the 3.4 cycle we introduced support for ACPI 5 extended
sleep registers, but they are only supposed to be used if the
HW-reduced mode bit is set in the FADT flags and the code attempted
to use them without checking that bit. That caused suspend/resume
regressions to happen on some systems. Fix from Lv Zheng causes
those registers to be used only if the HW-reduced mode bit is set.
Apart from this some other ACPICA bugs are fixed and code cleanups
are made by Bob Moore, Tomasz Nowicki, Lv Zheng, Chao Guan, and
Zhang Rui.
- cpuidle updates
New driver for Xilinx Zynq processors is added by Michal Simek.
Multidriver support simplification, addition of some missing
kerneldoc comments and Kconfig-related fixes come from Daniel
Lezcano.
- ACPI power management updates
Changes to make suspend/resume work correctly in Xen guests from
Konrad Rzeszutek Wilk, sparse warning fix from Fengguang Wu and
cleanups and fixes of the ACPI device power state selection
routine.
- ACPI documentation updates
Some previously missing pieces of ACPI documentation are added by
Lv Zheng and Aaron Lu (hopefully, that will help people to
uderstand how the ACPI subsystem works) and one outdated doc is
updated by Hanjun Guo.
- Assorted ACPI updates
We finally nailed down the IA-64 issue that was the reason for
reverting commit 9f29ab11dd ("ACPI / scan: do not match drivers
against objects having scan handlers"), so we can fix it and move
the ACPI scan handler check added to the ACPI video driver back to
the core.
A mechanism for adding CMOS RTC address space handlers is
introduced by Lan Tianyu to allow some EC-related breakage to be
fixed on some systems.
A spec-compliant implementation of acpi_os_get_timer() is added by
Mika Westerberg.
The evaluation of _STA is added to do_acpi_find_child() to avoid
situations in which a pointer to a disabled device object is
returned instead of an enabled one with the same _ADR value. From
Jeff Wu.
Intel BayTrail PCH (Platform Controller Hub) support is added to
the ACPI driver for Intel Low-Power Subsystems (LPSS) and that
driver is modified to work around a couple of known BIOS issues.
Changes from Mika Westerberg and Heikki Krogerus.
The EC driver is fixed by Vasiliy Kulikov to use get_user() and
put_user() instead of dereferencing user space pointers blindly.
Code cleanups are made by Bjorn Helgaas, Nicholas Mazzuca and Toshi
Kani.
- Assorted power management updates
The "runtime idle" helper routine is changed to take the return
values of the callbacks executed by it into account and to call
rpm_suspend() if they return 0, which allows us to reduce the
overall code bloat a bit (by dropping some code that's not
necessary any more after that modification).
The runtime PM documentation is updated by Alan Stern (to reflect
the "runtime idle" behavior change).
New trace points for PM QoS are added by Sahara
(<keun-o.park@windriver.com>).
PM QoS documentation is updated by Lan Tianyu.
Code cleanups are made and minor issues are addressed by Bernie
Thompson, Bjorn Helgaas, Julius Werner, and Shuah Khan.
- devfreq updates
New driver for the Exynos5-bus device from Abhilash Kesavan.
Minor cleanups, fixes and MAINTAINERS update from MyungJoo Ham,
Abhilash Kesavan, Paul Bolle, Rajagopal Venkat, and Wei Yongjun.
- OMAP power management updates
Adaptive Voltage Scaling (AVS) SmartReflex voltage control driver
updates from Andrii Tseglytskyi and Nishanth Menon."
* tag 'pm+acpi-3.11-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (162 commits)
cpufreq: Fix cpufreq regression after suspend/resume
ACPI / PM: Fix possible NULL pointer deref in acpi_pm_device_sleep_state()
PM / Sleep: Warn about system time after resume with pm_trace
cpufreq: don't leave stale policy pointer in cdbs->cur_policy
acpi-cpufreq: Add new sysfs attribute freqdomain_cpus
cpufreq: make sure frequency transitions are serialized
ACPI: implement acpi_os_get_timer() according the spec
ACPI / EC: Add HP Folio 13 to ec_dmi_table in order to skip DSDT scan
ACPI: Add CMOS RTC Operation Region handler support
ACPI / processor: Drop unused variable from processor_perflib.c
cpufreq: tegra: call CPUFREQ_POSTCHANGE notfier in error cases
cpufreq: s3c64xx: call CPUFREQ_POSTCHANGE notfier in error cases
cpufreq: omap: call CPUFREQ_POSTCHANGE notfier in error cases
cpufreq: imx6q: call CPUFREQ_POSTCHANGE notfier in error cases
cpufreq: exynos: call CPUFREQ_POSTCHANGE notfier in error cases
cpufreq: dbx500: call CPUFREQ_POSTCHANGE notfier in error cases
cpufreq: davinci: call CPUFREQ_POSTCHANGE notfier in error cases
cpufreq: arm-big-little: call CPUFREQ_POSTCHANGE notfier in error cases
cpufreq: powernow-k8: call CPUFREQ_POSTCHANGE notfier in error cases
cpufreq: pcc: call CPUFREQ_POSTCHANGE notfier in error cases
...
653 lines
16 KiB
Plaintext
653 lines
16 KiB
Plaintext
config MMU
|
|
bool
|
|
default y
|
|
|
|
config ZONE_DMA
|
|
bool
|
|
default y
|
|
|
|
config RWSEM_GENERIC_SPINLOCK
|
|
bool
|
|
default y
|
|
|
|
config RWSEM_XCHGADD_ALGORITHM
|
|
bool
|
|
|
|
config ARCH_HAS_ILOG2_U32
|
|
bool
|
|
default n
|
|
|
|
config ARCH_HAS_ILOG2_U64
|
|
bool
|
|
default n
|
|
|
|
config GENERIC_HWEIGHT
|
|
bool
|
|
default y
|
|
|
|
config GENERIC_CALIBRATE_DELAY
|
|
bool
|
|
default y
|
|
|
|
config NO_IOPORT
|
|
def_bool y
|
|
|
|
config FORCE_MAX_ZONEORDER
|
|
int
|
|
default 6
|
|
|
|
config CRIS
|
|
bool
|
|
default y
|
|
select HAVE_IDE
|
|
select GENERIC_ATOMIC64
|
|
select HAVE_GENERIC_HARDIRQS
|
|
select HAVE_UID16
|
|
select VIRT_TO_BUS
|
|
select ARCH_WANT_IPC_PARSE_VERSION
|
|
select GENERIC_IRQ_SHOW
|
|
select GENERIC_IOMAP
|
|
select GENERIC_SMP_IDLE_THREAD if ETRAX_ARCH_V32
|
|
select GENERIC_CMOS_UPDATE
|
|
select MODULES_USE_ELF_RELA
|
|
select CLONE_BACKWARDS2
|
|
select OLD_SIGSUSPEND
|
|
select OLD_SIGACTION
|
|
|
|
config HZ
|
|
int
|
|
default 100
|
|
|
|
source "init/Kconfig"
|
|
|
|
source "kernel/Kconfig.freezer"
|
|
|
|
menu "General setup"
|
|
|
|
source "fs/Kconfig.binfmt"
|
|
|
|
config ETRAX_CMDLINE
|
|
string "Kernel command line"
|
|
default "root=/dev/mtdblock3"
|
|
help
|
|
Pass additional commands to the kernel.
|
|
|
|
config ETRAX_WATCHDOG
|
|
bool "Enable ETRAX watchdog"
|
|
help
|
|
Enable the built-in watchdog timer support on ETRAX based embedded
|
|
network computers.
|
|
|
|
config ETRAX_WATCHDOG_NICE_DOGGY
|
|
bool "Disable watchdog during Oops printouts"
|
|
depends on ETRAX_WATCHDOG
|
|
help
|
|
By enabling this you make sure that the watchdog does not bite while
|
|
printing oopses. Recommended for development systems but not for
|
|
production releases.
|
|
|
|
config ETRAX_FAST_TIMER
|
|
bool "Enable ETRAX fast timer API"
|
|
help
|
|
This options enables the API to a fast timer implementation using
|
|
timer1 to get sub jiffie resolution timers (primarily one-shot
|
|
timers).
|
|
This is needed if CONFIG_ETRAX_SERIAL_FAST_TIMER is enabled.
|
|
|
|
config ETRAX_KMALLOCED_MODULES
|
|
bool "Enable module allocation with kmalloc"
|
|
help
|
|
Enable module allocation with kmalloc instead of vmalloc.
|
|
|
|
config OOM_REBOOT
|
|
bool "Enable reboot at out of memory"
|
|
|
|
source "kernel/Kconfig.preempt"
|
|
|
|
source mm/Kconfig
|
|
|
|
endmenu
|
|
|
|
menu "Hardware setup"
|
|
|
|
choice
|
|
prompt "Processor type"
|
|
default ETRAX100LX
|
|
|
|
config ETRAX100LX
|
|
bool "ETRAX-100LX-v1"
|
|
select ARCH_USES_GETTIMEOFFSET
|
|
help
|
|
Support version 1 of the ETRAX 100LX.
|
|
|
|
config ETRAX100LX_V2
|
|
bool "ETRAX-100LX-v2"
|
|
select ARCH_USES_GETTIMEOFFSET
|
|
help
|
|
Support version 2 of the ETRAX 100LX.
|
|
|
|
config SVINTO_SIM
|
|
bool "ETRAX-100LX-for-xsim-simulator"
|
|
select ARCH_USES_GETTIMEOFFSET
|
|
help
|
|
Support the xsim ETRAX Simulator.
|
|
|
|
config ETRAXFS
|
|
bool "ETRAX-FS-V32"
|
|
select CPU_FREQ_TABLE if CPU_FREQ
|
|
help
|
|
Support CRIS V32.
|
|
|
|
config CRIS_MACH_ARTPEC3
|
|
bool "ARTPEC-3"
|
|
select CPU_FREQ_TABLE if CPU_FREQ
|
|
help
|
|
Support Axis ARTPEC-3.
|
|
|
|
endchoice
|
|
|
|
config ETRAX_ARCH_V10
|
|
bool
|
|
default y if ETRAX100LX || ETRAX100LX_V2
|
|
default n if !(ETRAX100LX || ETRAX100LX_V2)
|
|
|
|
config ETRAX_ARCH_V32
|
|
bool
|
|
default y if (ETRAXFS || CRIS_MACH_ARTPEC3)
|
|
default n if !(ETRAXFS || CRIS_MACH_ARTPEC3)
|
|
|
|
config ETRAX_DRAM_SIZE
|
|
int "DRAM size (dec, in MB)"
|
|
default "8"
|
|
help
|
|
Size of DRAM (decimal in MB) typically 2, 8 or 16.
|
|
|
|
config ETRAX_VMEM_SIZE
|
|
int "Video memory size (dec, in MB)"
|
|
depends on ETRAX_ARCH_V32 && !ETRAXFS
|
|
default 8 if !ETRAXFS
|
|
help
|
|
Size of Video accessible memory (decimal, in MB).
|
|
|
|
config ETRAX_FLASH_BUSWIDTH
|
|
int "Buswidth of NOR flash in bytes"
|
|
default "2"
|
|
help
|
|
Width in bytes of the NOR Flash bus (1, 2 or 4). Is usually 2.
|
|
|
|
config ETRAX_NANDFLASH_BUSWIDTH
|
|
int "Buswidth of NAND flash in bytes"
|
|
default "1"
|
|
help
|
|
Width in bytes of the NAND flash (1 or 2).
|
|
|
|
config ETRAX_FLASH1_SIZE
|
|
int "FLASH1 size (dec, in MB. 0 = Unknown)"
|
|
default "0"
|
|
|
|
choice
|
|
prompt "Product debug-port"
|
|
default ETRAX_DEBUG_PORT0
|
|
|
|
config ETRAX_DEBUG_PORT0
|
|
bool "Serial-0"
|
|
help
|
|
Choose a serial port for the ETRAX debug console. Default to
|
|
port 0.
|
|
|
|
config ETRAX_DEBUG_PORT1
|
|
bool "Serial-1"
|
|
help
|
|
Use serial port 1 for the console.
|
|
|
|
config ETRAX_DEBUG_PORT2
|
|
bool "Serial-2"
|
|
help
|
|
Use serial port 2 for the console.
|
|
|
|
config ETRAX_DEBUG_PORT3
|
|
bool "Serial-3"
|
|
help
|
|
Use serial port 3 for the console.
|
|
|
|
config ETRAX_DEBUG_PORT_NULL
|
|
bool "disabled"
|
|
help
|
|
Disable serial-port debugging.
|
|
|
|
endchoice
|
|
|
|
choice
|
|
prompt "Kernel GDB port"
|
|
depends on ETRAX_KGDB
|
|
default ETRAX_KGDB_PORT0
|
|
help
|
|
Choose a serial port for kernel debugging. NOTE: This port should
|
|
not be enabled under Drivers for built-in interfaces (as it has its
|
|
own initialization code) and should not be the same as the debug port.
|
|
|
|
config ETRAX_KGDB_PORT0
|
|
bool "Serial-0"
|
|
help
|
|
Use serial port 0 for kernel debugging.
|
|
|
|
config ETRAX_KGDB_PORT1
|
|
bool "Serial-1"
|
|
help
|
|
Use serial port 1 for kernel debugging.
|
|
|
|
config ETRAX_KGDB_PORT2
|
|
bool "Serial-2"
|
|
help
|
|
Use serial port 2 for kernel debugging.
|
|
|
|
config ETRAX_KGDB_PORT3
|
|
bool "Serial-3"
|
|
help
|
|
Use serial port 3 for kernel debugging.
|
|
|
|
endchoice
|
|
|
|
source arch/cris/arch-v10/Kconfig
|
|
source arch/cris/arch-v32/Kconfig
|
|
|
|
endmenu
|
|
|
|
source "net/Kconfig"
|
|
|
|
# bring in ETRAX built-in drivers
|
|
menu "Drivers for built-in interfaces"
|
|
source arch/cris/arch-v10/drivers/Kconfig
|
|
source arch/cris/arch-v32/drivers/Kconfig
|
|
|
|
config ETRAX_AXISFLASHMAP
|
|
bool "Axis flash-map support"
|
|
select MTD
|
|
select MTD_CFI
|
|
select MTD_CFI_AMDSTD
|
|
select MTD_JEDECPROBE if ETRAX_ARCH_V32
|
|
select MTD_BLOCK
|
|
select MTD_COMPLEX_MAPPINGS
|
|
help
|
|
This option enables MTD mapping of flash devices. Needed to use
|
|
flash memories. If unsure, say Y.
|
|
|
|
config ETRAX_RTC
|
|
bool "Real Time Clock support"
|
|
depends on ETRAX_I2C
|
|
help
|
|
Enables drivers for the Real-Time Clock battery-backed chips on
|
|
some products. The kernel reads the time when booting, and
|
|
the date can be set using ioctl(fd, RTC_SET_TIME, &rt) with rt a
|
|
rtc_time struct (see <file:arch/cris/include/asm/rtc.h>) on the
|
|
/dev/rtc device. You can check the time with cat /proc/rtc, but
|
|
normal time reading should be done using libc function time and
|
|
friends.
|
|
|
|
choice
|
|
prompt "RTC chip"
|
|
depends on ETRAX_RTC
|
|
default ETRAX_DS1302
|
|
|
|
config ETRAX_DS1302
|
|
depends on ETRAX_ARCH_V10
|
|
bool "DS1302"
|
|
help
|
|
Enables the driver for the DS1302 Real-Time Clock battery-backed
|
|
chip on some products.
|
|
|
|
config ETRAX_PCF8563
|
|
bool "PCF8563"
|
|
help
|
|
Enables the driver for the PCF8563 Real-Time Clock battery-backed
|
|
chip on some products.
|
|
|
|
endchoice
|
|
|
|
config ETRAX_SYNCHRONOUS_SERIAL
|
|
bool "Synchronous serial-port support"
|
|
help
|
|
Select this to enable the synchronous serial port driver.
|
|
|
|
config ETRAX_SYNCHRONOUS_SERIAL_PORT0
|
|
bool "Synchronous serial port 0 enabled"
|
|
depends on ETRAX_SYNCHRONOUS_SERIAL
|
|
help
|
|
Enabled synchronous serial port 0.
|
|
|
|
config ETRAX_SYNCHRONOUS_SERIAL0_DMA
|
|
bool "Enable DMA on synchronous serial port 0."
|
|
depends on ETRAX_SYNCHRONOUS_SERIAL_PORT0
|
|
help
|
|
A synchronous serial port can run in manual or DMA mode.
|
|
Selecting this option will make it run in DMA mode.
|
|
|
|
config ETRAX_SYNCHRONOUS_SERIAL_PORT1
|
|
bool "Synchronous serial port 1 enabled"
|
|
depends on ETRAX_SYNCHRONOUS_SERIAL && (ETRAXFS || ETRAX_ARCH_V10)
|
|
help
|
|
Enabled synchronous serial port 1.
|
|
|
|
config ETRAX_SYNCHRONOUS_SERIAL1_DMA
|
|
bool "Enable DMA on synchronous serial port 1."
|
|
depends on ETRAX_SYNCHRONOUS_SERIAL_PORT1
|
|
help
|
|
A synchronous serial port can run in manual or DMA mode.
|
|
Selecting this option will make it run in DMA mode.
|
|
|
|
choice
|
|
prompt "Network LED behavior"
|
|
depends on ETRAX_ETHERNET
|
|
default ETRAX_NETWORK_LED_ON_WHEN_ACTIVITY
|
|
|
|
config ETRAX_NETWORK_LED_ON_WHEN_LINK
|
|
bool "LED_on_when_link"
|
|
help
|
|
Selecting LED_on_when_link will light the LED when there is a
|
|
connection and will flash off when there is activity.
|
|
|
|
Selecting LED_on_when_activity will light the LED only when
|
|
there is activity.
|
|
|
|
This setting will also affect the behaviour of other activity LEDs
|
|
e.g. Bluetooth.
|
|
|
|
config ETRAX_NETWORK_LED_ON_WHEN_ACTIVITY
|
|
bool "LED_on_when_activity"
|
|
help
|
|
Selecting LED_on_when_link will light the LED when there is a
|
|
connection and will flash off when there is activity.
|
|
|
|
Selecting LED_on_when_activity will light the LED only when
|
|
there is activity.
|
|
|
|
This setting will also affect the behaviour of other activity LEDs
|
|
e.g. Bluetooth.
|
|
|
|
endchoice
|
|
|
|
choice
|
|
prompt "Ser0 DMA out channel"
|
|
depends on ETRAX_SERIAL_PORT0
|
|
default ETRAX_SERIAL_PORT0_DMA6_OUT if ETRAX_ARCH_V32
|
|
default ETRAX_SERIAL_PORT0_NO_DMA_OUT if ETRAX_ARCH_V10
|
|
|
|
config ETRAX_SERIAL_PORT0_NO_DMA_OUT
|
|
bool "Ser0 uses no DMA for output"
|
|
help
|
|
Do not use DMA for ser0 output.
|
|
|
|
config ETRAX_SERIAL_PORT0_DMA6_OUT
|
|
bool "Ser0 uses DMA6 for output"
|
|
depends on ETRAXFS
|
|
help
|
|
Enables the DMA6 output channel for ser0 (ttyS0).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when transmitting data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
config ETRAX_SERIAL_PORT0_DMA0_OUT
|
|
bool "Ser0 uses DMA0 for output"
|
|
depends on CRIS_MACH_ARTPEC3
|
|
help
|
|
Enables the DMA0 output channel for ser0 (ttyS0).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when transmitting data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
endchoice
|
|
|
|
choice
|
|
prompt "Ser0 DMA in channel "
|
|
depends on ETRAX_SERIAL_PORT0
|
|
default ETRAX_SERIAL_PORT0_NO_DMA_IN if ETRAX_ARCH_V32
|
|
default ETRAX_SERIAL_PORT0_DMA7_IN if ETRAX_ARCH_V10
|
|
help
|
|
What DMA channel to use for ser0.
|
|
|
|
config ETRAX_SERIAL_PORT0_NO_DMA_IN
|
|
bool "Ser0 uses no DMA for input"
|
|
help
|
|
Do not use DMA for ser0 input.
|
|
|
|
config ETRAX_SERIAL_PORT0_DMA7_IN
|
|
bool "Ser0 uses DMA7 for input"
|
|
depends on ETRAXFS
|
|
help
|
|
Enables the DMA7 input channel for ser0 (ttyS0).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when receiving data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
config ETRAX_SERIAL_PORT0_DMA1_IN
|
|
bool "Ser0 uses DMA1 for input"
|
|
depends on CRIS_MACH_ARTPEC3
|
|
help
|
|
Enables the DMA1 input channel for ser0 (ttyS0).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when receiving data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
endchoice
|
|
|
|
choice
|
|
prompt "Ser1 DMA in channel "
|
|
depends on ETRAX_SERIAL_PORT1
|
|
default ETRAX_SERIAL_PORT1_NO_DMA_IN if ETRAX_ARCH_V32
|
|
default ETRAX_SERIAL_PORT1_DMA9_IN if ETRAX_ARCH_V10
|
|
help
|
|
What DMA channel to use for ser1.
|
|
|
|
config ETRAX_SERIAL_PORT1_NO_DMA_IN
|
|
bool "Ser1 uses no DMA for input"
|
|
help
|
|
Do not use DMA for ser1 input.
|
|
|
|
config ETRAX_SERIAL_PORT1_DMA5_IN
|
|
bool "Ser1 uses DMA5 for input"
|
|
depends on ETRAX_ARCH_V32
|
|
help
|
|
Enables the DMA5 input channel for ser1 (ttyS1).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when receiving data.
|
|
Normally you want this on, unless you use the DMA channel for
|
|
something else.
|
|
|
|
config ETRAX_SERIAL_PORT1_DMA9_IN
|
|
depends on ETRAX_ARCH_V10
|
|
bool "Ser1 uses DMA9 for input"
|
|
|
|
endchoice
|
|
|
|
|
|
choice
|
|
prompt "Ser1 DMA out channel"
|
|
depends on ETRAX_SERIAL_PORT1
|
|
default ETRAX_SERIAL_PORT1_NO_DMA_OUT if ETRAX_ARCH_V32
|
|
default ETRAX_SERIAL_PORT1_DMA8_OUT if ETRAX_ARCH_V10
|
|
help
|
|
What DMA channel to use for ser1.
|
|
|
|
config ETRAX_SERIAL_PORT1_NO_DMA_OUT
|
|
bool "Ser1 uses no DMA for output"
|
|
help
|
|
Do not use DMA for ser1 output.
|
|
|
|
config ETRAX_SERIAL_PORT1_DMA8_OUT
|
|
depends on ETRAX_ARCH_V10
|
|
bool "Ser1 uses DMA8 for output"
|
|
|
|
config ETRAX_SERIAL_PORT1_DMA4_OUT
|
|
depends on ETRAX_ARCH_V32
|
|
bool "Ser1 uses DMA4 for output"
|
|
help
|
|
Enables the DMA4 output channel for ser1 (ttyS1).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when transmitting data.
|
|
Normally you want this on, unless you use the DMA channel for
|
|
something else.
|
|
|
|
endchoice
|
|
|
|
choice
|
|
prompt "Ser2 DMA out channel"
|
|
depends on ETRAX_SERIAL_PORT2
|
|
default ETRAX_SERIAL_PORT2_NO_DMA_OUT if ETRAX_ARCH_V32
|
|
default ETRAX_SERIAL_PORT2_DMA2_OUT if ETRAX_ARCH_V10
|
|
|
|
config ETRAX_SERIAL_PORT2_NO_DMA_OUT
|
|
bool "Ser2 uses no DMA for output"
|
|
help
|
|
Do not use DMA for ser2 output.
|
|
|
|
config ETRAX_SERIAL_PORT2_DMA2_OUT
|
|
bool "Ser2 uses DMA2 for output"
|
|
depends on ETRAXFS || ETRAX_ARCH_V10
|
|
help
|
|
Enables the DMA2 output channel for ser2 (ttyS2).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when transmitting data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
config ETRAX_SERIAL_PORT2_DMA6_OUT
|
|
bool "Ser2 uses DMA6 for output"
|
|
depends on CRIS_MACH_ARTPEC3
|
|
help
|
|
Enables the DMA6 output channel for ser2 (ttyS2).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when transmitting data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
endchoice
|
|
|
|
choice
|
|
prompt "Ser2 DMA in channel"
|
|
depends on ETRAX_SERIAL_PORT2
|
|
default ETRAX_SERIAL_PORT2_NO_DMA_IN if ETRAX_ARCH_V32
|
|
default ETRAX_SERIAL_PORT2_DMA3_IN if ETRAX_ARCH_V10
|
|
help
|
|
What DMA channel to use for ser2.
|
|
|
|
config ETRAX_SERIAL_PORT2_NO_DMA_IN
|
|
bool "Ser2 uses no DMA for input"
|
|
help
|
|
Do not use DMA for ser2 input.
|
|
|
|
config ETRAX_SERIAL_PORT2_DMA3_IN
|
|
bool "Ser2 uses DMA3 for input"
|
|
depends on ETRAXFS || ETRAX_ARCH_V10
|
|
help
|
|
Enables the DMA3 input channel for ser2 (ttyS2).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when receiving data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
config ETRAX_SERIAL_PORT2_DMA7_IN
|
|
bool "Ser2 uses DMA7 for input"
|
|
depends on CRIS_MACH_ARTPEC3
|
|
help
|
|
Enables the DMA7 input channel for ser2 (ttyS2).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when receiving data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
endchoice
|
|
|
|
choice
|
|
prompt "Ser3 DMA in channel"
|
|
depends on ETRAX_SERIAL_PORT3
|
|
default ETRAX_SERIAL_PORT3_NO_DMA_IN if ETRAX_ARCH_V32
|
|
default ETRAX_SERIAL_PORT3_DMA5_IN if ETRAX_ARCH_V10
|
|
help
|
|
What DMA channel to use for ser3.
|
|
|
|
config ETRAX_SERIAL_PORT3_NO_DMA_IN
|
|
bool "Ser3 uses no DMA for input"
|
|
help
|
|
Do not use DMA for ser3 input.
|
|
|
|
config ETRAX_SERIAL_PORT3_DMA5_IN
|
|
depends on ETRAX_ARCH_V10
|
|
bool "DMA 5"
|
|
|
|
config ETRAX_SERIAL_PORT3_DMA9_IN
|
|
bool "Ser3 uses DMA9 for input"
|
|
depends on ETRAXFS
|
|
help
|
|
Enables the DMA9 input channel for ser3 (ttyS3).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when receiving data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
config ETRAX_SERIAL_PORT3_DMA3_IN
|
|
bool "Ser3 uses DMA3 for input"
|
|
depends on CRIS_MACH_ARTPEC3
|
|
help
|
|
Enables the DMA3 input channel for ser3 (ttyS3).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when receiving data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
endchoice
|
|
|
|
choice
|
|
prompt "Ser3 DMA out channel"
|
|
depends on ETRAX_SERIAL_PORT3
|
|
default ETRAX_SERIAL_PORT3_NO_DMA_OUT if ETRAX_ARCH_V32
|
|
default ETRAX_SERIAL_PORT3_DMA4_OUT if ETRAX_ARCH_V10
|
|
|
|
config ETRAX_SERIAL_PORT3_NO_DMA_OUT
|
|
bool "Ser3 uses no DMA for output"
|
|
help
|
|
Do not use DMA for ser3 output.
|
|
|
|
config ETRAX_SERIAL_PORT3_DMA4_OUT
|
|
depends on ETRAX_ARCH_V10
|
|
bool "DMA 4"
|
|
|
|
config ETRAX_SERIAL_PORT3_DMA8_OUT
|
|
bool "Ser3 uses DMA8 for output"
|
|
depends on ETRAXFS
|
|
help
|
|
Enables the DMA8 output channel for ser3 (ttyS3).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when transmitting data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
config ETRAX_SERIAL_PORT3_DMA2_OUT
|
|
bool "Ser3 uses DMA2 for output"
|
|
depends on CRIS_MACH_ARTPEC3
|
|
help
|
|
Enables the DMA2 output channel for ser3 (ttyS3).
|
|
If you do not enable DMA, an interrupt for each character will be
|
|
used when transmitting data.
|
|
Normally you want to use DMA, unless you use the DMA channel for
|
|
something else.
|
|
|
|
endchoice
|
|
|
|
endmenu
|
|
|
|
source "drivers/Kconfig"
|
|
|
|
source "fs/Kconfig"
|
|
|
|
source "arch/cris/Kconfig.debug"
|
|
|
|
source "security/Kconfig"
|
|
|
|
source "crypto/Kconfig"
|
|
|
|
source "lib/Kconfig"
|