Searched full:by (Results 1 – 25 of 2871) sorted by relevance
12345678910>>...115
| /Documentation/arm64/ |
| D | elf_hwcaps.rst | 17 Userspace software can test for features by acquiring the AT_HWCAP or
30 Where software relies on a feature described by a hwcap, it should check
44 which are described by architected ID registers inaccessible to
51 Functionality implied by idreg.field == val.
56 indicate the absence of functionality implied by other values of
60 described by ID registers alone. These may be described without
68 Functionality implied by ID_AA64PFR0_EL1.FP == 0b0000.
71 Functionality implied by ID_AA64PFR0_EL1.AdvSIMD == 0b0000.
78 Functionality implied by ID_AA64ISAR0_EL1.AES == 0b0001.
81 Functionality implied by ID_AA64ISAR0_EL1.AES == 0b0010.
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | pixfmt-reserved.rst | 3 .. Version 1.1 or any later version published by the Free Software
16 These formats are not defined by this specification, they are just
53 - 8 bit RGB format used by the BTTV driver.
58 - YUV 4:2:0 format used by the IVTV driver,
67 - YUV format used by the gspca cpia1 driver.
78 - YUYV per line used by the gspca driver.
83 - YYUV per line used by the gspca driver.
88 - YUVY per line used by the gspca driver.
93 - Compressed GBRG Bayer format used by the gspca driver.
98 - Compressed BGGR Bayer format used by the gspca driver.
[all …]
|
| D | pixfmt-v4l2.rst | 3 .. Version 1.1 or any later version published by the Free Software
49 - The pixel format or type of compression, set by the application.
71 the value requested by the application, returning ``width`` times
72 bytes per pixel or a larger value required by the hardware. That
83 to the first plane and is divided by the same factor as the
94 - Size in bytes of the buffer to hold a complete image, set by the
97 number of bytes required by the codec to support the worst-case
113 by the driver for capture streams and by the application for
125 must first ensure that the feature is supported by querying the
143 - Flags set by the application or driver, see :ref:`format-flags`.
[all …]
|
| D | selection-api-configuration.rst | 3 .. Version 1.1 or any later version published by the Free Software
38 areas that can be sampled is given by the ``V4L2_SEL_TGT_CROP_BOUNDS``
44 the area actually sampled, is given by the ``V4L2_SEL_TGT_CROP`` target.
50 Each capture device has a default source rectangle, given by the
60 the image size set by :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`.
62 The part of a buffer into which the image is inserted by the hardware is
63 controlled by the ``V4L2_SEL_TGT_COMPOSE`` target. The rectangle's
76 The part of a buffer that is modified by the hardware is given by
78 ``V4L2_SEL_TGT_COMPOSE`` plus all padding data modified by hardware
80 be changed by the hardware. The content of pixels that lie inside the
[all …]
|
| D | pixfmt-v4l2-mplane.rst | 3 .. Version 1.1 or any later version published by the Free Software
35 set by the driver. When the image consists of variable length
36 compressed data this is the number of bytes required by the
54 - Reserved for future extensions. Should be zeroed by drivers and
102 - Flags set by the application or driver, see :ref:`format-flags`.
107 This information supplements the ``colorspace`` and must be set by
108 the driver for capture streams and by the application for output
113 This information supplements the ``colorspace`` and must be set by
114 the driver for capture streams and by the application for output
120 This information supplements the ``colorspace`` and must be set by
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 24 For the processors supported by ``intel_pstate``, the P-state concept is broader
26 LinuxCon Europe 2015 presentation by Kristen Accardi [1]_ for more
28 by ``intel_pstate`` internally follows the hardware specification (for details
31 frequencies are involved in the user space interface exposed by it, so
36 that. Some functionality of the core is limited by that.
38 Since the hardware P-state selection interface used by ``intel_pstate`` is
79 For example, the ``powersave`` P-state selection algorithm provided by
83 There are two P-state selection algorithms provided by ``intel_pstate`` in the
88 Which of the P-state selection algorithms is used by default depends on the
90 Namely, if that option is set, the ``performance`` algorithm will be used by
[all …]
|
| D | cpufreq.rst | 23 can be retired by the CPU over a unit of time, but also the higher the clock
25 time (or the more power is drawn) by the CPU in the given P-state. Therefore
27 that can be executed over a unit of time) and the power drawn by the CPU.
44 repeatedly on a regular basis. The activity by which this happens is referred
52 The Linux kernel supports CPU performance scaling by means of the ``CPUFreq``
67 by scaling governors.
70 driver. That design is based on the observation that the information used by
78 based on information provided by the hardware itself, for example through
83 algorithms. That is done by the |intel_pstate| scaling driver.
89 In some cases the hardware interface for P-state control is shared by multiple
[all …]
|
| /Documentation/media/kapi/ |
| D | mc-core.rst | 28 other entities. Data (not restricted to video) produced by an entity
39 A media device is represented by a struct :c:type:`media_device`
41 Allocation of the structure is handled by the media device driver, usually by
45 Drivers register media device instances by calling
47 and unregistered by calling :c:func:`media_device_unregister()`.
52 Entities are represented by a struct :c:type:`media_entity`
58 Drivers initialize entity pads by calling
61 Drivers register entities with a media device by calling
63 and unregistered by calling
69 Interfaces are represented by a
[all …]
|
| D | rc-core.rst | 29 system to support the infrared protocol used by the emitter.
31 The infrared transmission is done by blinking a infrared emitter using a
32 carrier. The carrier can be switched on or off by the IR transmitter
44 given remote controller), followed by 8 bits of code. A bit "1" is modulated
45 with 560µs *PULSE* followed by 1690µs *SPACE* and a bit "0" is modulated
46 with 560µs *PULSE* followed by 560µs *SPACE*.
55 receivers are identified by ``RC_DRIVER_IR_RAW``, as defined by
59 by ``RC_DRIVER_SCANCODE``.
68 When the RC core receives events produced by ``RC_DRIVER_IR_RAW`` IR
70 corresponding scan code. The protocols supported by the RC core are
[all …]
|
| /Documentation/sound/soc/ |
| D | jack.rst | 11 to be present on a single jack but handled by separate bits of
18 This is done by splitting the jacks up into three things working
19 together: the jack itself represented by a struct snd_soc_jack, sets of
33 user space. The jack itself is completely passive, it is set up by the
34 machine driver and updated by jack detection methods.
36 Jacks are created by the machine driver calling snd_soc_jack_new().
42 bits supported by the jack. Each snd_soc_jack has zero or more of these
43 which are updated automatically. They are created by the machine driver
52 Actual jack detection is done by code which is able to monitor some
53 input to the system and update a jack by calling snd_soc_jack_report(),
[all …]
|
| /Documentation/driver-api/pm/ |
| D | cpuidle.rst | 26 belongs to. That can be done by making the idle logical CPU stop fetching
28 depended on by it into an idle state in which they will draw less power.
54 operated on by them cannot depend on any hardware architecture or platform
57 The governor itself is represented by a |struct cpuidle_governor| object
63 with the ``CPUIdle`` core by calling :c:func:`cpuidle_register_governor()` with
87 (logical) CPU represented by the |struct cpuidle_device| object pointed
88 to by the ``dev`` argument. The |struct cpuidle_driver| object pointed
89 to by the ``drv`` argument represents the ``CPUIdle`` driver to be used
106 by the |struct cpuidle_device| object pointed to by the ``dev``
109 It is expected to reverse any changes made by the ``->enable()``
[all …]
|
| /Documentation/virt/kvm/ |
| D | s390-diag.txt | 8 Note that bits are numbered as by the usual s390 convention (most significant
15 DIAGNOSE calls by the guest cause a mandatory intercept. This implies
16 all supported DIAGNOSE calls need to be handled by either KVM or its
19 All DIAGNOSE calls supported by KVM use the RS-a format:
26 The second-operand address (obtained by the base/displacement calculation)
30 The supported DIAGNOSE function codes vary by the userspace used. For
50 Handled by userspace.
53 Handled by userspace.
56 Handled by userspace.
59 Handled by either userspace or KVM (ioeventfd case).
[all …]
|
| /Documentation/networking/ |
| D | netdev-features.txt | 19 one used internally by network core:
22 be changed (enabled or disabled) for a particular device by user's
27 for a device. This should be changed only by network core or in
31 by child VLAN devices (limits netdev->features set). This is currently
35 4. netdev->wanted_features set contains feature set requested by user.
36 This set is filtered by ndo_fix_features callback whenever it or
46 is calculated and filtered by calling ndo_fix_features callback
61 A driver that wants to trigger recalculation must do so by calling
63 from ndo_*_features callbacks. netdev->features should not be modified by
64 driver except by means of ndo_fix_features callback.
[all …]
|
| D | lapb-module.txt | 7 The LAPB module will be a separately compiled module for use by any parts of
9 defines the interfaces to, and the services provided by this module. The
74 be unacknowledged by the remote end, the value of the window is between 1
89 MLP operation is the same as SLP operation except that the addresses used by
107 generated by the device driver to allow for the unique identification of the
108 instance of the LAPB link. It is returned by the LAPB module in all of the
109 callbacks, and is used by the device driver in all calls to the LAPB module.
175 is successful then the skbuff is owned by the LAPB module and may not be
176 used by the device driver again. The valid return values are:
188 is owned by the LAPB module and may not be used by the device driver again.
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | nfsd-admin-interfaces.txt | 4 Note that normally these interfaces are used only by the utilities in
7 nfsd is controlled mainly by pseudofiles under the "nfsd" filesystem,
10 The server is always started by the first write of a nonzero value to
13 Before doing that, NFSD can be told which sockets to listen on by
26 nfsd is shut down by a write of 0 to nfsd/threads. All locks and state
30 or down by additional writes to nfsd/threads or by writes to
|
| /Documentation/driver-api/rapidio/ |
| D | rio_cm.rst | 30 capability to large number of user-space processes by introducing socket-like
55 with channel ID assigned automatically or as requested by a caller.
64 channel. If wait timeout for this request is specified by a caller it is
72 The handler for this request assumes that message buffer specified by
73 a caller includes the reserved space for a packet header required by
78 handler will wait for new message until timeout specified by a caller
80 defined by MAX_SCHEDULE_TIMEOUT.
86 The ioctl command codes and corresponding data structures intended for use by
92 This device driver uses standard interfaces defined by kernel RapidIO subsystem
93 and therefore it can be used with any mport device driver registered by RapidIO
[all …]
|
| /Documentation/translations/zh_CN/process/ |
| D | submitting-patches.rst | 367 Signed-off-by: Random J Developer <random@developer.example.org>
382 Signed-off-by: Random J Developer <random@developer.example.org>
384 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
408 12）何时使用Acked-by:，CC:，和Co-Developed by:
411 Singed-off-by: 标记表示签名者参与了补丁的开发，或者他/她在补丁的传递路径中。
414 那么他们可以要求在补丁的变更日志中添加一个 Acked-by:
416 Acked-by：通常由受影响代码的维护者使用，当该维护者既没有贡献也没有转发补丁时。
418 Acked-by: 不像签字人那样正式。这是一个记录，确认人至少审查了补丁，并表示接受。
419 因此，补丁合并有时会手动将Acker的“Yep，looks good to me”转换为 Acked-By：（但
422 Acked-by：不一定表示对整个补丁的确认。例如，如果一个补丁影响多个子系统，并且
[all …]
|
| /Documentation/filesystems/ |
| D | vfs.rst | 30 calls. The pathname argument that is passed to them is used by the VFS
40 and then loading the inode. This is done by looking up the inode.
51 written back to disc. A single inode can be pointed to by multiple
55 the parent directory inode. This method is installed by the specific
72 this is another switch performed by the VFS. The file structure is
76 is done by using the userspace file descriptor to grab the appropriate
98 specific filesystem. New vfsmount referring to the tree returned by
156 describes the filesystem, partly initialized by the specific
169 The mount() method must return the root dentry of the tree requested by
196 mount a filesystem that is not backed by a device
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-wacom | 27 <obsoleted by the LED class API now exported by the driver>
37 <obsoleted by the LED class API now exported by the driver>
46 <obsoleted by the LED class API now exported by the driver>
56 <obsoleted by the LED class API now exported by the driver>
82 be summarized by converting 76543210 into GECA6420.
89 Writing the character sequence '*' followed by a newline to
98 <obsoleted by the LED class API now exported by the driver>
100 remote as indicated by the LED lights on the device. If no
|
| D | sysfs-driver-ppi | 7 Presence Interface). Only if TPM is supported by BIOS, this
8 folder makes sense. The folder path can be got by command
22 This attribute shows the version of the PPI supported by the
60 operation to be executed in the pre-OS environment by the BIOS
61 for the requests defined by TCG, i.e. requests from 1 to 22.
63 This attribute is only supported by PPI version 1.2+.
71 operation to be executed in the pre-OS environment by the BIOS
74 is also only supported by PPI version 1.2+.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 5 Written by Paul Menage <menage@google.com> based on
14 Modified by Paul Jackson <pj@sgi.com>
16 Modified by Christoph Lameter <cl@linux.com>
30 2.3 Mounting hierarchies by name
54 facilities provided by cgroups to treat groups of tasks in
69 User-level code may create and destroy cgroups by name in an
111 As an example of a scenario (originally proposed by vatsa@in.ibm.com)
141 (by putting those resource subsystems in different hierarchies),
182 can be determined by following pointers through the
194 - You can list all the tasks (by PID) attached to any cgroup.
[all …]
|
| /Documentation/power/regulator/ |
| D | consumer.rst | 12 A consumer driver can get access to its supply regulator by calling ::
17 then finds the correct regulator by consulting a machine specific lookup table.
25 Consumers can be supplied by more than one regulator e.g. codec consumer with
39 A consumer can enable its power supply by calling::
46 previously enabled by bootloader or kernel board initialization code.
48 A consumer can determine if a regulator is enabled by calling::
55 A consumer can disable its supply when no longer needed by calling::
80 Consumers can control their supply voltage by calling::
92 The regulators configured voltage output can be found by calling::
111 Consumers can control their supply current limit by calling::
[all …]
|
| /Documentation/process/ |
| D | submitting-patches.rst | 48 If you must generate your patches by hand, use ``diff -up`` or ``diff -uprN``
49 to create patches. Git generates patches in this form by default; if
53 generated by :manpage:`diff(1)`. When creating your patch, make sure to
54 create it in "unified diff" format, as supplied by the ``-u`` argument
83 ``dontdiff`` is a list of files which are generated by the kernel during
93 :ref:`split_changes`. This will facilitate review by other kernel developers,
156 If the patch fixes a logged bug entry, refer to that bug entry by
216 change that can be verified by reviewers. Each patch should be justifiable
300 toward the stable maintainers by putting a line like this::
333 - Non-portable code replaced by portable code (even in arch-specific,
[all …]
|
| /Documentation/pcmcia/ |
| D | locking.rst | 62 protected by pcmcia_socket_list_rwsem;
67 The resource_ops and their data are protected by ops_mutex.
72 - by pcmcia_socket_list_rwsem::
76 - by thread_lock::
80 - by skt_mutex::
87 - by ops_mutex::
116 - by pcmcia_socket->ops_mutex::
128 - by the PCMCIA driver::
|
| /Documentation/translations/ja_JP/ |
| D | SubmittingPatches | 3 This document is maintained by Keiichi KII <k-keiichi@bx.jp.nec.com>
336 Signed-off-by: Random J Developer <random@developer.example.org>
352 Signed-off-by とあなたがその末尾に追加する Signed-off-by の間に、修正を
358 Signed-off-by: Random J Developer <random@developer.example.org>
360 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
388 13) いつ Acked-by: と Cc: を使うのか
390 「 Signed-off-by: 」タグはその署名者がパッチの開発に関わっていたことやパッチ
394 る承認を記録し、示したいとします。その場合、その人を示すのに Acked-by: が使
395 えます。Acked-by: はパッチのチェンジログにも追加されます。
398 の伝播パスにいなかった時にも、メンテナは Acked-by: をしばしば利用します。
[all …]
|
12345678910>>...115