Searched full:by (Results 1 – 25 of 3216) sorted by relevance
12345678910>>...129
| /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/userspace-api/media/v4l/ |
| D | pixfmt-reserved.rst | 9 These formats are not defined by this specification, they are just
46 - 8 bit RGB format used by the BTTV driver.
51 - YUV 4:2:0 format used by the IVTV driver.
59 - YUV format used by the gspca cpia1 driver.
70 - YUYV per line used by the gspca driver.
75 - YYUV per line used by the gspca driver.
80 - YUVY per line used by the gspca driver.
85 - Compressed GBRG Bayer format used by the gspca driver.
90 - Compressed BGGR Bayer format used by the gspca driver.
95 - Compressed BGGR 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/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 register media device instances by calling
47 and unregistered by calling :c:func:`media_device_unregister()`.
52 Entities are represented by a struct 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/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 preformance 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 | cpufreq.rst | 22 can be retired by the CPU over a unit of time, but also the higher the clock
24 time (or the more power is drawn) by the CPU in the given P-state. Therefore
26 that can be executed over a unit of time) and the power drawn by the CPU.
43 repeatedly on a regular basis. The activity by which this happens is referred
51 The Linux kernel supports CPU performance scaling by means of the ``CPUFreq``
66 by scaling governors.
69 driver. That design is based on the observation that the information used by
77 based on information provided by the hardware itself, for example through
82 algorithms. That is done by the |intel_pstate| scaling driver.
88 In some cases the hardware interface for P-state control is shared by multiple
[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``
60 recognized by ``intel_idle`` and the latter are used if that is required for
62 recognized by ``intel_idle``) or if the processor model is not recognized.
64 tables with any processor model recognized by it; see
71 ``CPUIdle`` subsystem expects that the list of idle states supplied by the
72 driver will be suitable for all of the CPUs handled by it and ``intel_idle`` is
89 If the processor model at hand is recognized by ``intel_idle``, there is a
94 (depending on the processor model), all of the listed idle state are enabled 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/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/devicetree/bindings/power/ |
| D | power-domain.yaml | 16 used for power gating of selected IP blocks for power saving by reduced leakage
20 their PM domains provided by PM domain providers. A PM domain provider can be
21 represented by any node in the device tree and can provide one or more PM
22 domains. A consumer node can refer to the provider by a phandle and a set of
23 phandle arguments (so called PM domain specifiers) of length specified by the
46 Phandles to the OPP tables of power domains provided by a power domain
48 the power domains provided by the provider have identical OPP tables,
57 by device tree binding documentation of particular provider.
61 A phandle and PM domain specifier as defined by bindings of the power
62 controller specified by phandle. Some power domains might be powered
[all …]
|
| /Documentation/virt/kvm/ |
| 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/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/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/process/ |
| D | submitting-patches.rst | 94 If the patch fixes a logged bug entry, refer to that bug entry by
159 change that can be verified by reviewers. Each patch should be justifiable
244 toward the stable maintainers by putting a line like this::
272 - Non-portable code replaced by portable code (even in arch-specific,
274 - Any fix by the author/maintainer of the file (ie. patch monkey
287 For this reason, all patches should be submitted by e-mail "inline". The
372 By making a contribution to this project, I certify that:
374 (a) The contribution was created in whole or in part by me and I
382 by me, under the same open source license (unless I am
386 (c) The contribution was provided directly to me by some other
[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/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/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/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::
91 Writing the character sequence '*' followed by a newline to
100 <obsoleted by the LED class API now exported by the driver>
102 remote as indicated by the LED lights on the device. If no
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-aggregator.rst | 14 devices. Access control to these devices is provided by standard UNIX file
18 The GPIO Aggregator provides access control for a set of one or more GPIOs, by
25 Aggregated GPIO controllers are instantiated and destroyed by writing to
32 controller by writing a string describing the GPIOs to
49 GPIO offset ranges denoted by dashes.
51 Example: Instantiate a new GPIO aggregator by aggregating GPIO
61 controller after use by writing its device name to the
80 Binding a device to the GPIO Aggregator is performed either by modifying the
81 gpio-aggregator driver, or by writing to the "driver_override" file in Sysfs.
94 it can be bound to the GPIO Aggregator by either:
|
| /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 …]
|
12345678910>>...129