menu "GCOV-based kernel profiling" config GCOV_KERNEL bool "Enable gcov-based kernel profiling" depends on DEBUG_FS select CONSTRUCTORS if !UML default n ---help--- This option enables gcov-based code profiling (e.g. for code coverage measurements). If unsure, say N. Additionally specify CONFIG_GCOV_PROFILE_ALL=y to get profiling data for the entire kernel. To enable profiling for specific files or directories, add a line similar to the following to the respective Makefile: For a single file (e.g. main.o): GCOV_PROFILE_main.o := y For all files in one directory: GCOV_PROFILE := y To exclude files from being profiled even when CONFIG_GCOV_PROFILE_ALL is specified, use: GCOV_PROFILE_main.o := n and: GCOV_PROFILE := n Note that the debugfs filesystem has to be mounted to access profiling data. config ARCH_HAS_GCOV_PROFILE_ALL def_bool n config GCOV_PROFILE_ALL bool "Profile entire Kernel" depends on !COMPILE_TEST depends on GCOV_KERNEL depends on ARCH_HAS_GCOV_PROFILE_ALL default n ---help--- This options activates profiling for the entire kernel. If unsure, say N. Note that a kernel compiled with profiling flags will be significantly larger and run slower. Also be sure to exclude files from profiling which are not linked to the kernel image to prevent linker errors. choice prompt "Specify GCOV format" depends on GCOV_KERNEL default GCOV_FORMAT_AUTODETECT ---help--- The gcov format is usually determined by the GCC version, but there are exceptions where format changes are integrated in lower-version GCCs. In such a case use this option to adjust the format used in the kernel accordingly. If unsure, choose "Autodetect". config GCOV_FORMAT_AUTODETECT bool "Autodetect" ---help--- Select this option to use the format that corresponds to your GCC version. config GCOV_FORMAT_3_4 bool "GCC 3.4 format" ---help--- Select this option to use the format defined by GCC 3.4. config GCOV_FORMAT_4_7 bool "GCC 4.7 format" ---help--- Select this option to use the format defined by GCC 4.7. endchoice endmenu 96ab1010fd6b057eee18496'>diff
path: root/include/dt-bindings/gpio
diff options
context:
space:
mode:
authorCharles Keepax <ckeepax@opensource.wolfsonmicro.com>2016-11-10 10:45:18 +0000
committerMark Brown <broonie@kernel.org>2016-11-10 17:28:32 +0000
commit85b037442e3f0e84296ab1010fd6b057eee18496 (patch)
treeb745f3f22cbd45af2039a004eb3f21d530afdc8b /include/dt-bindings/gpio
parent1001354ca34179f3db924eb66672442a173147dc (diff)
regulators: helpers: Fix handling of bypass_val_on in get_bypass_regmap
The handling of bypass_val_on that was added in regulator_get_bypass_regmap is done unconditionally however several drivers don't define a value for bypass_val_on. This results in those drivers reporting bypass being enabled when it is not. In regulator_set_bypass_regmap we use bypass_mask if bypass_val_on is zero. This patch adds similar handling in regulator_get_bypass_regmap. Fixes: commit dd1a571daee7 ("regulator: helpers: Ensure bypass register field matches ON value") Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'include/dt-bindings/gpio')