| /kernel/linux/linux-4.19/tools/build/Documentation/ |
| D | Build.txt | 1 Build Framework
4 The perf build framework was adopted from the kernel build system, hence the
7 Basically the user provides set of 'Build' files that list objects and
8 directories to nest for specific target to be build.
10 Unlike the kernel we don't have a single build object 'obj-y' list that where
11 we setup source objects, but we support more. This allows one 'Build' file to
12 carry a sources list for multiple build objects.
15 Build framework makefiles
18 The build framework consists of 2 Makefiles:
20 Build.include
[all …]
|
| /kernel/linux/linux-5.10/tools/build/Documentation/ |
| D | Build.txt | 1 Build Framework
4 The perf build framework was adopted from the kernel build system, hence the
7 Basically the user provides set of 'Build' files that list objects and
8 directories to nest for specific target to be build.
10 Unlike the kernel we don't have a single build object 'obj-y' list that where
11 we setup source objects, but we support more. This allows one 'Build' file to
12 carry a sources list for multiple build objects.
15 Build framework makefiles
18 The build framework consists of 2 Makefiles:
20 Build.include
[all …]
|
| /kernel/linux/linux-5.10/samples/ |
| D | Kconfig | 5 You can build and test sample kernel code here.
14 tristate "Build trace_events examples -- loadable modules only"
17 This build trace event example modules.
20 tristate "Build trace_printk module - tests various trace_printk formats"
27 tristate "Build register_ftrace_direct() example"
35 tristate "Build sample module for kernel access to Ftrace instancess"
42 tristate "Build kobject examples"
44 This config option will allow you to build a number of
51 tristate "Build kprobes examples -- loadable modules only"
54 This build several kprobes example modules.
[all …]
|
| /kernel/linux/linux-4.19/samples/ |
| D | Kconfig | 5 You can build and test sample kernel code here.
10 tristate "Build trace_events examples -- loadable modules only"
13 This build trace event example modules.
16 tristate "Build trace_printk module - tests various trace_printk formats"
23 tristate "Build kobject examples -- loadable modules only"
26 This config option will allow you to build a number of
33 tristate "Build kprobes examples -- loadable modules only"
36 This build several kprobes example modules.
39 tristate "Build kretprobes example -- loadable modules only"
44 tristate "Build kernel hardware breakpoint examples -- loadable module only"
[all …]
|
| /kernel/linux/linux-5.10/drivers/block/paride/ |
| D | Kconfig | 17 connected through a parallel port. If you chose to build PARIDE
18 support into your kernel, you may answer Y here to build in the
19 parallel port IDE driver, otherwise you should answer M to build
33 connected through a parallel port. If you chose to build PARIDE
34 support into your kernel, you may answer Y here to build in the
36 build it as a loadable module. The module will be called pcd. You
49 connected through a parallel port. If you chose to build PARIDE
50 support into your kernel, you may answer Y here to build in the
52 to build it as a loadable module. The module will be called pf.
63 connected through a parallel port. If you chose to build PARIDE
[all …]
|
| /kernel/linux/linux-4.19/drivers/block/paride/ |
| D | Kconfig | 17 connected through a parallel port. If you chose to build PARIDE
18 support into your kernel, you may answer Y here to build in the
19 parallel port IDE driver, otherwise you should answer M to build
33 connected through a parallel port. If you chose to build PARIDE
34 support into your kernel, you may answer Y here to build in the
36 build it as a loadable module. The module will be called pcd. You
49 connected through a parallel port. If you chose to build PARIDE
50 support into your kernel, you may answer Y here to build in the
52 to build it as a loadable module. The module will be called pf.
63 connected through a parallel port. If you chose to build PARIDE
[all …]
|
| /kernel/linux/linux-5.10/tools/build/feature/ |
| D | Makefile | 85 BUILD = $(__BUILD) > $(@:.bin=.make.output) 2>&1 macro
93 …$(BUILD) -fstack-protector-all -O2 -D_FORTIFY_SOURCE=2 -ldw -lelf -lnuma -lelf -I/usr/include/slan…
96 $(BUILD)
99 $(BUILD) -D_GNU_SOURCE -lpthread
102 $(BUILD) -lpthread
105 $(BUILD) -fstack-protector-all
108 $(BUILD) -O2 -D_FORTIFY_SOURCE=2
111 $(BUILD)
114 $(BUILD) -lcap
117 $(BUILD) -lelf
[all …]
|
| /kernel/linux/linux-4.19/tools/build/feature/ |
| D | Makefile | 71 BUILD = $(__BUILD) > $(@:.bin=.make.output) 2>&1 macro
79 …$(BUILD) -fstack-protector-all -O2 -D_FORTIFY_SOURCE=2 -ldw -lelf -lnuma -lelf -laudit -I/usr/incl…
82 $(BUILD)
85 $(BUILD) -D_GNU_SOURCE -lpthread
88 $(BUILD) -lpthread
91 $(BUILD) -fstack-protector-all
94 $(BUILD) -O2 -D_FORTIFY_SOURCE=2
97 $(BUILD)
100 $(BUILD) -lelf
103 $(BUILD)
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/Documentation/ |
| D | Build.txt | 2 1) perf build
4 The perf build process consists of several separated building blocks,
11 Several makefiles govern the perf build:
18 main makefile that triggers build of all perf objects including
21 - tools/build/Makefile.build
22 main makefile of the build framework
24 - tools/build/Build.include
25 build framework generic definitions
27 - Build makefiles
28 makefiles that defines build objects
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | Build.txt | 2 1) perf build
4 The perf build process consists of several separated building blocks,
11 Several makefiles govern the perf build:
18 main makefile that triggers build of all perf objects including
21 - tools/build/Makefile.build
22 main makefile of the build framework
24 - tools/build/Build.include
25 build framework generic definitions
27 - Build makefiles
28 makefiles that defines build objects
[all …]
|
| /kernel/linux/linux-5.10/drivers/accessibility/speakup/ |
| D | Kconfig | 54 synthesizer. You can say y to build it into the kernel,
55 or m to build it as a module. See the configuration
63 synthesizer. You can say y to build it into the kernel,
64 or m to build it as a module. See the configuration
71 synthesizer. You can say y to build it into the kernel,
72 or m to build it as a module. See the configuration
79 You can say y to build it into the kernel, or m to
80 build it as a module. See the configuration help on the
87 synthesizer. You can say y to build it into the kernel,
88 or m to build it as a module. See the configuration
[all …]
|
| /kernel/linux/linux-4.19/drivers/staging/speakup/ |
| D | Kconfig | 48 synthesizer. You can say y to build it into the kernel,
49 or m to build it as a module. See the configuration
57 synthesizer. You can say y to build it into the kernel,
58 or m to build it as a module. See the configuration
65 synthesizer. You can say y to build it into the kernel,
66 or m to build it as a module. See the configuration
73 You can say y to build it into the kernel, or m to
74 build it as a module. See the configuration help on the
81 synthesizer. You can say y to build it into the kernel,
82 or m to build it as a module. See the configuration
[all …]
|
| /kernel/linux/patches/ |
| D | README.md | 6 - [Build](#section19369206113115)
17 During the build process, you can merge the driver code based on the chip platform and build the ke…
23 ├── build
24 │ ├── BUILD.gn # GN file of the build framework
25 │ ├── kernel.mk # Kernel build file
26 │ └── ohos.build # Kernel build component file
59 …nel version. For details, see the method in **kernel.mk** in the **kernel/linux/build** repository.
69 …es for the patches of the chip component in **kernel.mk** in the **kernel/linux/build** repository.
76 3. Modify the **config** file to build.
78 …h and naming rules of the chip component in **kernel.mk** in the **kernel/linux/build** repository.
[all …]
|
| /kernel/linux/linux-4.19/drivers/iio/accel/ |
| D | Kconfig | 14 Say Y here to build support for Analog Devices adis16201 dual-axis
26 Say Y here to build support for Analog Devices adis16209 dual-axis digital inclinometer
42 Say Y here if you want to build support for the Analog Devices
56 Say Y here if you want to build support for the Analog Devices
69 Say Y here if you want to build a driver for the Bosch BMA180 or
95 Say yes here to build support for the following Bosch accelerometers:
114 Say yes here to build support for the MiraMEMS DA280 3-axis 14-bit
124 Say yes here to build support for the MiraMEMS DA311 3-axis 12-bit
135 Say yes here to build support for the Domintech low-g tri-axial
148 Choosing M will build the driver as a module. If so, the module
[all …]
|
| /kernel/linux/linux-5.10/drivers/clk/rockchip/ |
| D | Kconfig | 16 Build the driver for PX30 Clock Driver.
22 Build the driver for RV110x Clock Driver.
28 Build the driver for RK3036 Clock Driver.
34 Build the driver for RK312x Clock Driver.
40 Build the driver for RK3188 Clock Driver.
46 Build the driver for RK322x Clock Driver.
53 Build the driver for RK3288 Clock Driver.
59 Build the driver for RK3308 Clock Driver.
65 Build the driver for RK3328 Clock Driver.
71 Build the driver for RK3368 Clock Driver.
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/accel/ |
| D | Kconfig | 15 Say Y here to build support for Analog Devices adis16201 dual-axis
27 Say Y here to build support for Analog Devices adis16209 dual-axis digital inclinometer
43 Say Y here if you want to build support for the Analog Devices
57 Say Y here if you want to build support for the Analog Devices
97 Say Y here if you want to build a driver for the Bosch BMA023, BMA150
121 Say Y here if you want to build a driver for the Bosch BMA400
145 Say yes here to build support for the following Bosch accelerometers:
164 Say yes here to build support for the MiraMEMS DA280 3-axis 14-bit
174 Say yes here to build support for the MiraMEMS DA311 3-axis 12-bit
185 Say yes here to build support for the Domintech low-g tri-axial
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/adc/ |
| D | Kconfig | 29 Say yes here to build support for Analog Devices AD7091R-5 ADC.
36 Say yes here to build support for Analog Devices AD7124-4 and AD7124-8
47 Say yes here to build support for Analog Devices AD7190,
61 Say yes here to build support for Analog Devices AD7265 and AD7266
71 Say yes here to build support for Analog Devices AD7291
81 Say yes here to build support for Analog Devices AD7292
93 Say yes here to build support for Analog Devices AD7298
105 Say yes here to build support for the following SPI analog to
125 Say yes here to build parallel interface support for Analog Devices:
136 Say yes here to build spi interface support for Analog Devices:
[all …]
|
| /kernel/linux/linux-4.19/drivers/iio/dac/ |
| D | Kconfig | 12 Say yes here to build support for Analog Devices AD5024, AD5025, AD5044,
26 Say yes here to build support for Analog Devices AD5360, AD5361,
39 Say yes here to build support for Analog Devices AD5380, AD5381,
50 Say yes here to build support for Analog Devices AD5421 loop-powered
60 Say yes here to build support for Analog Devices AD5300, AD5301, AD5310,
73 Say yes here to build support for Analog Devices AD5415, AD5426, AD5429,
88 Say yes here to build support for Analog Devices AD5592R
100 Say yes here to build support for Analog Devices AD5593R
110 Say yes here to build support for Analog Devices AD5504, AD5501,
120 Say yes here to build support for Analog Devices AD5624R, AD5644R and
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/dac/ |
| D | Kconfig | 13 Say yes here to build support for Analog Devices AD5024, AD5025, AD5044,
27 Say yes here to build support for Analog Devices AD5360, AD5361,
40 Say yes here to build support for Analog Devices AD5380, AD5381,
51 Say yes here to build support for Analog Devices AD5421 loop-powered
61 Say yes here to build support for Analog Devices AD5300, AD5301, AD5310,
74 Say yes here to build support for Analog Devices AD5415, AD5426, AD5429,
89 Say yes here to build support for Analog Devices AD5592R
101 Say yes here to build support for Analog Devices AD5593R
111 Say yes here to build support for Analog Devices AD5504, AD5501,
121 Say yes here to build support for Analog Devices AD5624R, AD5644R and
[all …]
|
| /kernel/linux/build/ |
| D | README.md | 7 - [Build](#section19369206113115)
18 During the build process, you can merge the driver code based on the chip platform and build the ke…
44 …nel version. For details, see the method in **kernel.mk** in the **kernel/linux/build** repository.
54 …es for the patches of the chip component in **kernel.mk** in the **kernel/linux/build** repository.
61 3. Modify the **config** file to build.
63 …h and naming rules of the chip component in **kernel.mk** in the **kernel/linux/build** repository.
72 …Harmony project build process, patches are installed after **kernel/linux/linux-\*\.\*** is copied…
77 ## Build<a name="section19369206113115"></a>
81 Perform a full build for the project to generate the **uImage** kernel image.
84 ./build.sh --product-name Hi3516DV300 # Build the Hi3516D V300 image.
[all …]
|
| /kernel/linux/linux-4.19/drivers/iio/adc/ |
| D | Kconfig | 20 Say yes here to build support for Analog Devices AD7265 and AD7266
30 Say yes here to build support for Analog Devices AD7291
42 Say yes here to build support for Analog Devices AD7298
54 Say yes here to build support for Analog Devices AD7273, AD7274, AD7276,
67 Say yes here to build support for Analog Devices AD7766, AD7766-1,
78 Say yes here to build support for Analog Devices AD7787, AD7788, AD7789,
89 Say yes here to build support for Analog Devices AD7785, AD7792, AD7793,
101 Say yes here to build support for Analog Devices
113 Say yes here to build support for Analog Devices
125 Say yes here to build support for Analog Devices:
[all …]
|
| /kernel/linux/linux-4.19/tools/testing/selftests/ |
| D | Makefile | 58 # Makefile to avoid test build failures when test
59 # Makefile doesn't have explicit build rules.
69 BUILD := $(O) macro
70 ifndef BUILD
71 BUILD := $(KBUILD_OUTPUT) macro
73 ifndef BUILD
74 BUILD := $(shell pwd) macro
83 export BUILD
86 BUILD_TARGET=$$BUILD/$$TARGET; \
93 BUILD_TARGET=$$BUILD/$$TARGET; \
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/light/ |
| D | Kconfig | 17 Say Y here if you want to build a driver for the ACPI0008
40 Say Y here if you want to build a driver for the Analog Devices
50 Say Y here if you want to build a driver for the Dyna Image AL3010
60 Say Y here if you want to build a driver for the Dyna Image AL3320A
70 Say Y here if you want to build a driver for the Avago APDS9300
83 Say Y here to build I2C interface support for the Avago
108 Say Y here to build support for the ROHM BH1710, BH1715, BH1721,
118 Say Y here to build support for the ROHM BH1780GLI ambient
150 Say Y here if you want to build a driver for Capella CM3323
160 Say Y here if you want to build a driver for Capella CM3605
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/pressure/ |
| D | Kconfig | 13 Say yes here to build support for the Honeywell ABP pressure
26 Say yes here to build support for Bosch Sensortec BMP180 and BMP280
50 Say yes here to build support for the Barometer sensor when
62 Say yes here to build support for the All Sensors DLH series
86 Say yes here to build support for the HID SENSOR
97 Say yes here to build support for Hope RF HP03 pressure and
108 Say yes here to build support for InvenSense ICP-101xx barometric
122 Say yes here to build support for the Freescale MPL115A2
133 Say yes here to build support for the Freescale MPL115A1
145 Say yes here to build support for the Freescale MPL3115A2
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/ |
| D | Makefile | 92 # implicit rules to sub-test Makefiles which avoids build failures in test
93 # Makefile that don't have explicit build rules.
107 BUILD := $(O)/kselftest macro
110 BUILD := $(KBUILD_OUTPUT)/kselftest macro
112 BUILD := $(shell pwd) macro
122 export BUILD
124 # build and run gpio when output directory is the src dir.
150 # Local build cases: "make kselftest", "make -C" - headers are installed
156 $(MAKE) --no-builtin-rules INSTALL_HDR_PATH=$$BUILD/usr \
163 BUILD_TARGET=$$BUILD/$$TARGET; \
[all …]
|