Searched full:targets (Results 1 – 25 of 124) sorted by relevance
12345
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-targets.rst | 4 Selection targets
8 .. _sel-targets-capture:
14 Cropping and composing targets
16 Targets used by a cropping, composing and scaling process
20 See :ref:`v4l2-selection-targets` for more information.
|
| D | selection-api-configuration.rst | 26 See figure :ref:`sel-targets-capture` for examples of the selection
27 targets available for a video capture device. It is recommended to
28 configure the cropping targets before to the composing targets.
49 The composing targets refer to a memory buffer. The limits of composing
82 For output devices targets and ioctls are used similarly to the video
85 buffer. It is recommended to configure the composing targets before to
86 the cropping targets.
88 The cropping targets refer to the memory buffer that contains an image
135 ``V4L2_SEL_TGT_COMPOSE`` targets. If these are not equal then the
|
| D | v4l2-selection-targets.rst | 3 .. _v4l2-selection-targets:
6 Selection targets
9 The precise meaning of the selection targets may be dependent on which
13 .. _v4l2-selection-targets-table:
|
| D | vidioc-subdev-g-selection.rst | 54 Types of selection targets
57 There are two types of selection targets: actual and bounds. The actual
58 targets are the targets which configure the hardware. The BOUNDS target
64 To discover which targets are supported, the user can perform
68 Selection targets and flags are documented in
|
| D | selection-api.rst | 13 selection-api-targets.rst
|
| D | selections-common.rst | 22 v4l2-selection-targets
|
| D | vidioc-g-selection.rst | 46 additional targets. The ``flags`` and ``reserved`` fields of struct
64 targets. The struct :c:type:`v4l2_rect` ``r`` rectangle need
115 Selection targets and flags are documented in
|
| /Documentation/networking/ |
| D | nfc.rst | 16 - Polling for targets;
27 PF_NFC. The NFC_SOCKPROTO_RAW performs raw communication with NFC targets.
62 * start_poll - setup the device to poll for targets
64 * activate_target - select and initialize one of the targets found
80 * NFC_CMD_START_POLL - setup a specific device to polling for targets
82 * NFC_CMD_GET_TARGET - dump the list of targets found by a specific device
86 * NFC_EVENT_TARGETS_FOUND - reports START_POLL results when 1 or more targets
89 The user must call START_POLL to poll for NFC targets, passing the desired NFC
95 If the polling operation finds one or more targets, the event TARGETS_FOUND is
97 all targets found by such device. Each reply message has target attributes with
[all …]
|
| D | netconsole.rst | 102 remote logging targets to be dynamically added, removed, or have their
116 Note that newly created targets have default parameter values (as mentioned
142 disabled targets (i.e. if "enabled" is 0).
157 Netconsole targets defined at boot time (or module load time) with the
160 these targets by creating configfs directories with the matching name.
162 Let's suppose you have two netconsole targets defined at boot time::
166 You can modify these targets in runtime by creating the following targets::
|
| /Documentation/arch/powerpc/ |
| D | bootwrapper.rst | 7 PowerPC image targets compresses and wraps the kernel image (vmlinux) with
13 Makefile in that directory has targets for all the available image types.
24 Currently, the following image format targets exist:
100 Two special targets called 'zImage' and 'zImage.initrd' also exist. These
101 targets build all the default images as selected by the kernel configuration.
103 (arch/powerpc/boot/Makefile) by adding targets to the $image-y variable. Look
104 at the Makefile to see which default image targets are available.
|
| /Documentation/dev-tools/ |
| D | kselftest.rst | 82 You can use the "TARGETS" variable on the make command line to specify
87 $ make -C tools/testing/selftests TARGETS=ptrace run_tests
91 $ make TARGETS="size timers" kselftest
95 $ make O=/tmp/kselftest TARGETS="size timers" kselftest
99 $ export KBUILD_OUTPUT=/tmp/kselftest; make TARGETS="size timers" kselftest
102 line to specify one or more targets to exclude from the TARGETS list.
115 $ make TARGETS="breakpoints size timers" SKIP_TARGETS=size kselftest
118 possible targets.
213 $ make -C tools/testing/selftests gen_tar TARGETS="size" FORMAT=.xz
298 * Add new test name in TARGETS in selftests/Makefile::
[all …]
|
| D | ubsan.rst | 60 and to exclude all targets in one directory use::
64 When disabled for all targets, specific files can be enabled using::
|
| /Documentation/i2c/ |
| D | summary.rst | 37 :alt: Simple I2C bus with one controller and 3 targets
41 A **controller** chip is a node that starts communications with targets. In the
52 While targets are usually separate external chips, Linux can also act as a
62 the I2C controller, and drivers for your I2C targets. Usually one driver for
|
| /Documentation/admin-guide/hw-vuln/ |
| D | cross-thread-rsb.rst | 13 address prediction entries with safe targets when context switching to the idle
51 change. This behavior may result in return targets from one SMT thread being
55 could lead to information disclosure if the return targets used do not come
70 targets by performing a sequence of CALL instructions.
|
| /Documentation/admin-guide/mm/ |
| D | numaperf.rst | 42 memory targets.
44 To aid applications matching memory targets with their initiators, the
46 relationship for the access class "0" memory initiators and targets::
48 # symlinks -v /sys/devices/system/node/nodeX/access0/targets/
49 relative: /sys/devices/system/node/nodeX/access0/targets/nodeY -> ../../nodeY
54 A memory initiator may have multiple memory targets in the same access
|
| /Documentation/scsi/ |
| D | aic79xx.rst | 273 :Definition: Global tag depth for all targets on all busses.
283 per controller basis. Both controllers and targets
301 - specifies a tag depth of 8 for targets 4 and 5
303 - specifies a tag depth of 32 for targets 1,2,7-15
305 All other targets retain the default depth.
313 - specifies a tag depth of 32 for targets 0 and 2
315 All other targets retain the default depth.
334 - enables read streaming for targets 0 and 6.
335 - disables read streaming for targets 1-5,7-15.
337 All other targets retain the default read
[all …]
|
| /Documentation/userspace-api/media/ |
| D | Makefile | 13 TARGETS := $(addprefix $(BUILDDIR)/, $(FILES)) macro
52 all: $(IMGDOT) $(BUILDDIR) ${TARGETS}
61 -rm -f $(DOTTGT) $(IMGTGT) ${TARGETS} 2>/dev/null
|
| /Documentation/admin-guide/device-mapper/ |
| D | persistent-data.rst | 8 The more-sophisticated device-mapper targets require complex metadata
10 different targets were rolling their own data structures, for example:
22 targets. It's currently used by the thin-provisioning target and an
|
| /Documentation/devicetree/bindings/ |
| D | Makefile | 66 targets += .dt-binding.checked .yamllint.checked
74 targets += $(patsubst $(obj)/%,%, $(CHK_DT_EXAMPLES))
75 targets += $(patsubst $(obj)/%.dtb,%.dts, $(CHK_DT_EXAMPLES))
|
| /Documentation/kbuild/ |
| D | makefiles.rst | 34 any built-in or modular targets.
276 Non-builtin vmlinux targets - extra-y
279 extra-y specifies targets which are needed for building vmlinux,
294 $(extra-y) should only contain targets needed for vmlinux.
299 If you intend to build targets unconditionally, always-y (explained
305 always-y specifies targets which are literally always built when
508 Any target that utilizes if_changed must be listed in $(targets),
514 automatically adds it to $(targets). Otherwise, the target must be
515 explicitly added to $(targets).
517 Assignments to $(targets) are without $(obj)/ prefix. if_changed may be
[all …]
|
| /Documentation/translations/zh_TW/admin-guide/mm/damon/ |
| D | usage.rst | 51 # echo 1 > kdamonds/0/contexts/0/targets/nr_targets
52 # echo $(pidof <workload>) > kdamonds/0/contexts/0/targets/0/pid_target
69 │ │ │ │ │ targets/nr_targets
138 ``targets``, 和 ``schemes``)。
160 contexts/<N>/targets/
166 targets/<N>/
174 targets/<N>/regions
|
| /Documentation/translations/zh_CN/admin-guide/mm/damon/ |
| D | usage.rst | 51 # echo 1 > kdamonds/0/contexts/0/targets/nr_targets
52 # echo $(pidof <workload>) > kdamonds/0/contexts/0/targets/0/pid_target
69 │ │ │ │ │ targets/nr_targets
138 ``targets``, 和 ``schemes``)。
160 contexts/<N>/targets/
166 targets/<N>/
174 targets/<N>/regions
|
| /Documentation/devicetree/bindings/misc/ |
| D | pvpanic-mmio.txt | 3 QEMU's emulation / virtualization targets provide the following PVPANIC
|
| /Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 52 # echo 1 > kdamonds/0/contexts/0/targets/nr_targets
53 # echo $(pidof <workload>) > kdamonds/0/contexts/0/targets/0/pid_target
74 │ │ │ │ │ :ref:`targets <sysfs_targets>`/nr_targets
183 and three directories (``monitoring_attrs``, ``targets``, and ``schemes``)
224 contexts/<N>/targets/
233 targets/<N>/
245 targets/<N>/regions
426 the list of the DAMON context's monitoring targets list to ``target_idx`` file.
653 monitoring targets. Users can set the targets by writing relevant id values of
654 the targets to, and get the ids of the current targets by reading from the
[all …]
|
| /Documentation/driver-api/ |
| D | pwrseq.rst | 37 to the power sequencer. Via the dependency system, multiple targets may
66 (units) and define their dependencies. They can then expose named targets that
|
12345