Searched full:by (Results 1 – 25 of 3449) sorted by relevance
12345678910>>...138
| /Documentation/arch/arm64/ |
| D | elf_hwcaps.rst | 19 Userspace software can test for features by acquiring the AT_HWCAP or
32 Where software relies on a feature described by a hwcap, it should check
46 which are described by architected ID registers inaccessible to
53 Functionality implied by idreg.field == val.
58 indicate the absence of functionality implied by other values of
62 described by ID registers alone. These may be described without
70 Functionality implied by ID_AA64PFR0_EL1.FP == 0b0000.
73 Functionality implied by ID_AA64PFR0_EL1.AdvSIMD == 0b0000.
80 Functionality implied by ID_AA64ISAR0_EL1.AES == 0b0001.
83 Functionality implied by ID_AA64ISAR0_EL1.AES == 0b0010.
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | amlogic,axg-audio-clkc.yaml | 46 - description: slave bit clock N0 provided by external components
47 - description: slave bit clock N1 provided by external components
48 - description: slave bit clock N2 provided by external components
49 - description: slave bit clock N3 provided by external components
50 - description: slave bit clock N4 provided by external components
51 - description: slave bit clock N5 provided by external components
52 - description: slave bit clock N6 provided by external components
53 - description: slave bit clock N7 provided by external components
54 - description: slave bit clock N8 provided by external components
55 - description: slave bit clock N9 provided by external components
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-reserved.rst | 9 These formats are not defined by this specification, they are just
50 - 8 bit RGB format used by the BTTV driver.
55 - YUV format used by the gspca cpia1 driver.
66 - YUYV per line used by the gspca driver.
71 - YYUV per line used by the gspca driver.
76 - YUVY per line used by the gspca driver.
81 - Compressed GBRG Bayer format used by the gspca driver.
86 - Compressed BGGR Bayer format used by the gspca driver.
91 - Compressed BGGR Bayer format used by the gspca driver.
96 - JPEG compressed RGGB Bayer format used by the gspca driver.
[all …]
|
| D | pixfmt-v4l2.rst | 43 be calculated internally by the encoder itself, based on the OUTPUT
47 - The pixel format or type of compression, set by the application.
69 the value requested by the application, returning ``width`` times
70 bytes per pixel or a larger value required by the hardware. That
81 to the first plane and is divided by the same factor as the
92 - Size in bytes of the buffer to hold a complete image, set by the
95 number of bytes required by the codec to support the worst-case
111 by the driver for capture streams and by the application for
117 The driver indicates that colorspace conversion is supported by setting
130 must first ensure that the feature is supported by querying the
[all …]
|
| D | selection-api-configuration.rst | 31 areas that can be sampled is given by the ``V4L2_SEL_TGT_CROP_BOUNDS``
37 the area actually sampled, is given by the ``V4L2_SEL_TGT_CROP`` target.
43 Each capture device has a default source rectangle, given by the
53 the image size set by :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`.
55 The part of a buffer into which the image is inserted by the hardware is
56 controlled by the ``V4L2_SEL_TGT_COMPOSE`` target. The rectangle's
69 The part of a buffer that is modified by the hardware is given by
71 ``V4L2_SEL_TGT_COMPOSE`` plus all padding data modified by hardware
73 be changed by the hardware. The content of pixels that lie inside the
96 the area from which image date are processed by the hardware, is given
[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
59 allows the hardware to do performance scaling by itself, while in the passive
60 mode it responds to requests made by a generic ``CPUFreq`` governor implementing
83 For example, the ``powersave`` P-state selection algorithm provided by
87 There are two P-state selection algorithms provided by ``intel_pstate`` in the
[all …]
|
| D | intel_idle.rst | 30 first of which, referred to as a *hint*, can be used by the processor to
47 Each ``MWAIT`` hint value is interpreted by the processor as a license to
55 In order to create a list of available idle states required by the ``CPUIdle``
61 recognized by ``intel_idle`` and the latter are used if that is required for
63 recognized by ``intel_idle``) or if the processor model is not recognized.
65 tables with any processor model recognized by it; see
72 ``CPUIdle`` subsystem expects that the list of idle states supplied by the
73 driver will be suitable for all of the CPUs handled by it and ``intel_idle`` is
90 If the processor model at hand is recognized by ``intel_idle``, there is a
95 (depending on the processor model), all of the listed idle state are enabled by
[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/translations/zh_TW/process/ |
| D | submitting-patches.rst | 325 Signed-off-by: Random J Developer <random@developer.example.org>
328 將會自動完成。撤銷也應當包含“Signed-off-by”， ``git revert -s`` 會幫你搞定。
333 作者簽署之後的任何其他簽署（Signed-off-by:'s）均來自處理和傳遞補丁的人員，但
337 何時使用Acked-by:，Cc:，和Co-developed-by:
340 Signed-off-by: 標籤表示簽名者參與了補丁的開發，或者他/她在補丁的傳遞路徑中。
343 那麼他們可以要求在補丁的變更日誌中添加一個Acked-by:。
345 Acked-by: 通常由受影響代碼的維護者使用，當該維護者既沒有貢獻也沒有轉發補丁時。
347 Acked-by: 不像簽署那樣正式。這是一個記錄，確認人至少審閱了補丁，並表示接受。
348 因此，補丁合併有時會手動將Acker的“Yep，looks good to me”轉換爲 Acked-By:（但
351 Acked-by：不一定表示對整個補丁的確認。例如，如果一個補丁影響多個子系統，並且
[all …]
|
| /Documentation/translations/zh_CN/process/ |
| D | submitting-patches.rst | 324 Signed-off-by: Random J Developer <random@developer.example.org>
327 将会自动完成。撤销也应当包含“Signed-off-by”， ``git revert -s`` 会帮你搞定。
332 作者签署之后的任何其他签署（Signed-off-by:'s）均来自处理和传递补丁的人员，但
336 何时使用Acked-by:，Cc:，和Co-developed-by:
339 Signed-off-by: 标签表示签名者参与了补丁的开发，或者他/她在补丁的传递路径中。
342 那么他们可以要求在补丁的变更日志中添加一个Acked-by:。
344 Acked-by: 通常由受影响代码的维护者使用，当该维护者既没有贡献也没有转发补丁时。
346 Acked-by: 不像签署那样正式。这是一个记录，确认人至少审阅了补丁，并表示接受。
347 因此，补丁合并有时会手动将Acker的“Yep，looks good to me”转换为 Acked-By:（但
350 Acked-by：不一定表示对整个补丁的确认。例如，如果一个补丁影响多个子系统，并且
[all …]
|
| /Documentation/driver-api/pm/ |
| D | cpuidle.rst | 21 belongs to. That can be done by making the idle logical CPU stop fetching
23 depended on by it into an idle state in which they will draw less power.
49 operated on by them cannot depend on any hardware architecture or platform
52 The governor itself is represented by a struct cpuidle_governor object
58 with the ``CPUIdle`` core by calling :c:func:`cpuidle_register_governor()` with
81 (logical) CPU represented by the struct cpuidle_device object pointed
82 to by the ``dev`` argument. The struct cpuidle_driver object pointed
83 to by the ``drv`` argument represents the ``CPUIdle`` driver to be used
100 by the struct cpuidle_device object pointed to by the ``dev``
103 It is expected to reverse any changes made by the ``->enable()``
[all …]
|
| /Documentation/driver-api/media/ |
| 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 media_device
41 Allocation of the structure is handled by the media device driver, usually by
45 Drivers initialise media device instances by calling
47 registered by calling :c:func:`__media_device_register()` via the macro
48 ``media_device_register()`` and unregistered by calling
50 eventually cleaned up by calling :c:func:`media_device_cleanup()`.
59 Entities are represented by a struct media_entity
65 Drivers initialize entity pads by calling
68 Drivers register entities with a media device by calling
[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/ABI/testing/ |
| D | sysfs-secvar | 12 by the firmware.
17 Description: A string indicating which backend is in use by the firmware.
21 On powernv/OPAL, this value is provided by the OPAL firmware
24 On pseries/PLPKS, this is generated by the kernel based on the
34 representation. The data and size can be determined by reading
60 defined by the secure variable implementation. All data is in
68 Description: Config version as reported by the hypervisor in ASCII decimal
71 Currently only provided by PLPKS on the pseries platform.
84 Currently only provided by PLPKS on the pseries platform.
92 Currently only provided by PLPKS on the pseries platform.
[all …]
|
| /Documentation/mhi/ |
| D | mhi.rst | 12 MHI is a protocol developed by Qualcomm Innovation Center, Inc. It is used
13 by the host processors to control and communicate with modem devices over high
29 which are mapped to the host memory space by the peripheral buses like PCIe.
34 MHI BHI registers: BHI (Boot Host Interface) registers are used by the host
37 Channel Doorbell array: Channel Doorbell (DB) registers used by the host to
41 (DB) registers are used by the host to notify the device when new events are
44 Debug registers: A set of registers and counters used by the device to expose
50 All data structures used by MHI are in the host system memory. Using the
58 Transfer rings: Used by the host to schedule work items for a channel. The
64 Event rings: Used by the device to send completion and state transition messages
[all …]
|
| /Documentation/livepatch/ |
| D | system-state.rst | 17 done by the already installed livepatches.
31 The state of the system might get modified either by several livepatch callbacks
32 or by the newly used code. Also it must be possible to find changes done by
35 Each modified state is described by struct klp_state, see
51 is supported by the given livepatch.
90 has not been already modified by a livepatches that are being
94 been done by a livepatch that is being replaced.
100 done by livepatches that were being replaced.
108 System states are usually modified by livepatch callbacks. The expected
116 are already provided by previously installed livepatches.
[all …]
|
| /Documentation/virt/kvm/arm/ |
| D | vcpu-features.rst | 14 (``struct kvm_vcpu_init::features``). Features enabled by this interface are
16 documentation of the features controlled by the ioctl.
18 Otherwise, all CPU features supported by KVM are described by the architected
25 of architectural features supported by the CPU implementation. KVM initializes
26 the guest's ID registers to the maximum set of CPU features supported by the
30 KVM allows userspace to *opt-out* of certain CPU features described by the ID
31 registers by writing values to them via the ``KVM_SET_ONE_REG`` ioctl. The ID
39 outlined by the architecture in DDI0487J.a D19.1.3 'Principles of the ID
|
| D | pkvm.rst | 16 The major implementation change brought about by pKVM is that the hypervisor
28 The pKVM hypervisor is enabled by booting the host kernel at EL2 with
70 When pKVM is enabled, protected VMs can be created by specifying the
75 described by the ID register definitions in
78 capabilities advertised by ``KVM_CHECK_EXTENSION`` are limited accordingly,
82 Where not defined by the architecture, the registers of a protected vCPU
84 either by the ``KVM_SET_ONE_REG`` interface or by a call to PSCI ``CPU_ON``.
89 By default, memory pages mapped into a protected guest are inaccessible to the
90 host and any attempt by the host to access such a page will result in the
91 injection of an abort at EL1 by the hypervisor. For accesses originating from
|
| /Documentation/admin-guide/nfs/ |
| D | nfsd-admin-interfaces.rst | 5 Note that normally these interfaces are used only by the utilities in
8 nfsd is controlled mainly by pseudofiles under the "nfsd" filesystem,
11 The server is always started by the first write of a nonzero value to
14 Before doing that, NFSD can be told which sockets to listen on by
25 On startup, nfsd and lockd grace periods start. nfsd is shut down by a write of
29 or down by additional writes to nfsd/threads or by writes to
|
| /Documentation/devicetree/bindings/power/ |
| D | power-domain.yaml | 16 used for power gating of selected IP blocks for power saving by reduced
21 their PM domains provided by PM domain providers. A PM domain provider can be
22 represented by any node in the device tree and can provide one or more PM
23 domains. A consumer node can refer to the provider by a phandle and a set of
24 phandle arguments (so called PM domain specifiers) of length specified by the
49 performance, provided by a power domain provider. If the provider provides
50 a single power domain only or all the power domains provided by the
59 by device tree binding documentation of particular provider.
63 A phandle and PM domain specifier as defined by bindings of the power
64 controller specified by phandle. Some power domains might be powered
[all …]
|
| /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/virt/kvm/s390/ |
| D | s390-diag.rst | 11 Note that bits are numbered as by the usual s390 convention (most significant
18 DIAGNOSE calls by the guest cause a mandatory intercept. This implies
19 all supported DIAGNOSE calls need to be handled by either KVM or its
22 All DIAGNOSE calls supported by KVM use the RS-a format::
29 The second-operand address (obtained by the base/displacement calculation)
33 The supported DIAGNOSE function codes vary by the userspace used. For
53 Handled by userspace.
56 Handled by userspace.
59 Handled by userspace.
62 Handled by either userspace or KVM (ioeventfd case).
[all …]
|
| /Documentation/translations/ja_JP/ |
| D | SubmittingPatches | 3 This document is maintained by Keiichi KII <k-keiichi@bx.jp.nec.com>
330 Signed-off-by: Random J Developer <random@developer.example.org>
346 Signed-off-by とあなたがその末尾に追加する Signed-off-by の間に、修正を
352 Signed-off-by: Random J Developer <random@developer.example.org>
354 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
382 13) いつ Acked-by: と Cc: を使うのか
384 「 Signed-off-by: 」タグはその署名者がパッチの開発に関わっていたことやパッチ
388 る承認を記録し、示したいとします。その場合、その人を示すのに Acked-by: が使
389 えます。Acked-by: はパッチのチェンジログにも追加されます。
392 の伝播パスにいなかった時にも、メンテナは Acked-by: をしばしば利用します。
[all …]
|
| /Documentation/networking/ |
| D | netdev-features.rst | 22 one used internally by network core:
25 be changed (enabled or disabled) for a particular device by user's
30 for a device. This should be changed only by network core or in
34 by child VLAN devices (limits netdev->features set). This is currently
38 4. netdev->wanted_features set contains feature set requested by user.
39 This set is filtered by ndo_fix_features callback whenever it or
49 is calculated and filtered by calling ndo_fix_features callback
64 A driver that wants to trigger recalculation must do so by calling
66 from ndo_*_features callbacks. netdev->features should not be modified by
67 driver except by means of ndo_fix_features callback.
[all …]
|
| /Documentation/devicetree/bindings/access-controllers/ |
| D | access-controllers.yaml | 16 their responsibility (their domain) can be accesssed by which compartment. A
19 resources covered by the access controller.
22 controller provided by access-controllers property. In this case, the device
25 An access controller can be represented by any node in the device tree and
27 of the consumer device. A consumer node can refer to the provider by phandle
28 and a set of phandle arguments, specified by '#access-controller-cells'
33 controller. The capabilities of each access controller are defined by the
45 Can be any value as specified by device tree binding documentation
58 A list of access controller specifiers, as defined by the
|
12345678910>>...138