Searched refs:by (Results 1 – 25 of 4592) sorted by relevance
12345678910>>...184
17 Userspace software can test for features by acquiring the AT_HWCAP or30 Where software relies on a feature described by a hwcap, it should check44 which are described by architected ID registers inaccessible to51 Functionality implied by idreg.field == val.56 indicate the absence of functionality implied by other values of60 described by ID registers alone. These may be described without68 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 …]
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: 不像签字人那样正式。这是一个记录，确认人至少审查了补丁，并表示接受。422 Acked-by：不一定表示对整个补丁的确认。例如，如果一个补丁影响多个子系统，并且430 Co-developed-by: 声明补丁是由多个开发人员共同创建的；当几个人在一个补丁上工[all …]
119 - 一个或多个标记行，至少有一个由补丁作者的：signed-off-by 签名。签名将在下面157 - Signed-off-by: 这是一个开发人员的证明，他或她有权提交补丁以包含到内核中。162 - Co-developed-by: 声明补丁是由多个开发人员共同创建的；当几个人在一个补丁上164 Co-developed-by: 表示作者身份，所以每个共同开发人, 必须紧跟在相关合作作者168 - Acked-by: 表示另一个开发人员（通常是相关代码的维护人员）同意补丁适合包含171 - Tested-by: 声明指定的人已经测试了补丁并发现它可以工作。173 - Reviewed-by: 指定的开发人员已经审查了补丁的正确性；有关详细信息，请参阅176 - Reported-by: 指定报告此补丁修复的问题的用户；此标记用于提供感谢。
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 …]
77 cpu-release-addr = <0>; // Fixed by the boot loader85 cpu-release-addr = <0>; // Fixed by the boot loader93 cpu-release-addr = <0>; // Fixed by the boot loader101 cpu-release-addr = <0>; // Fixed by the boot loader109 cpu-release-addr = <0>; // Fixed by the boot loader117 cpu-release-addr = <0>; // Fixed by the boot loader125 cpu-release-addr = <0>; // Fixed by the boot loader133 cpu-release-addr = <0>; // Fixed by the boot loader141 cpu-release-addr = <0>; // Fixed by the boot loader149 cpu-release-addr = <0>; // Fixed by the boot loader[all …]
15 * booting cluster (big or LITTLE) is chosen by IROM code by reading33 #cooling-cells = <2>; /* min followed by max */45 #cooling-cells = <2>; /* min followed by max */57 #cooling-cells = <2>; /* min followed by max */69 #cooling-cells = <2>; /* min followed by max */81 #cooling-cells = <2>; /* min followed by max */93 #cooling-cells = <2>; /* min followed by max */105 #cooling-cells = <2>; /* min followed by max */117 #cooling-cells = <2>; /* min followed by max */
14 * booting cluster (big or LITTLE) is chosen by IROM code by reading32 #cooling-cells = <2>; /* min followed by max */44 #cooling-cells = <2>; /* min followed by max */56 #cooling-cells = <2>; /* min followed by max */68 #cooling-cells = <2>; /* min followed by max */80 #cooling-cells = <2>; /* min followed by max */92 #cooling-cells = <2>; /* min followed by max */104 #cooling-cells = <2>; /* min followed by max */116 #cooling-cells = <2>; /* min followed by max */
156 .set by, \b define167 .rept (by - 1)183 club DDQ_DATA, by191 .rept (by - 1)200 .rept by215 .rept by221 add $(16*by), p_in232 .rept by246 .rept by266 .rept by[all …]
8 Written by John R. Hauser. This work was made possible in part by the10 Street, Berkeley, California 94704. Funding was partially provided by the14 overseen by Profs. Nelson Morgan and John Wawrzynek. More information34 Shifts `a' right by the number of bits given in `count'. If any nonzero36 the result by setting the least significant bit to 1. The value of `count'39 The result is stored in the location pointed to by `zPtr'.59 Shifts `a' right by the number of bits given in `count'. If any nonzero61 the result by setting the least significant bit to 1. The value of `count'64 The result is stored in the location pointed to by `zPtr'.87 Shifts the 128-bit value formed by concatenating `a0' and `a1' right by 64[all …]
3 .. Version 1.1 or any later version published by the Free Software16 These formats are not defined by this specification, they are just53 - 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 …]
3 .. Version 1.1 or any later version published by the Free Software35 set by the driver. When the image consists of variable length36 compressed data this is the number of bytes required by the54 - Reserved for future extensions. Should be zeroed by drivers and102 - Flags set by the application or driver, see :ref:`format-flags`.107 This information supplements the ``colorspace`` and must be set by108 the driver for capture streams and by the application for output113 This information supplements the ``colorspace`` and must be set by114 the driver for capture streams and by the application for output120 This information supplements the ``colorspace`` and must be set by[all …]
3 .. Version 1.1 or any later version published by the Free Software38 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 the60 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 is63 controlled by the ``V4L2_SEL_TGT_COMPOSE`` target. The rectangle's76 The part of a buffer that is modified by the hardware is given by78 ``V4L2_SEL_TGT_COMPOSE`` plus all padding data modified by hardware80 be changed by the hardware. The content of pixels that lie inside the[all …]
16 | bit 63. The fraction is multiplied by 10 using a mul by 217 | shift and a mul by 8 shift. The bits shifted out of the28 | A3. Multiply the fraction in d2:d3 by 8 using bit-field32 | A4. Multiply the fraction in d4:d5 by 2 using shifts. The msb33 | will be collected by the carry.51 | d2: upper 32-bits of fraction for mul by 852 | d3: lower 32-bits of fraction for mul by 853 | d4: upper 32-bits of fraction for mul by 254 | d5: lower 32-bits of fraction for mul by 287 | A3. Multiply d2:d3 by 8; extract msbs into d1.[all …]
7 Get list of events, sorted by given criteria.28 sorted by the _sort_type_ criteria. The last element of the array is NULL.29 The returned memory must not be freed, it is managed by the library.34 _TEP_EVENT_SORT_ID_ - sort by the event ID.35 _TEP_EVENT_SORT_NAME_ - sort by the event (name, system, id) triplet.36 _TEP_EVENT_SORT_SYSTEM_ - sort by the event (system, name, id) triplet.41 must be freed by the caller. Note that the content of the array must not be48 it is managed by the library.51 In case of an error, NULL is returned. The returned array must be freed by68 /* Failed to get the events, sorted by ID */[all …]
28 other entities. Data (not restricted to video) produced by an entity39 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 by45 Drivers register media device instances by calling47 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 calling61 Drivers register entities with a media device by calling63 and unregistered by calling69 Interfaces are represented by a[all …]
5 are not saved by the BIOS and so do not persist after unload and reload.18 If the dsp irq has not been setup and stored in bios by the 20 irq used by the dsp to be configured.23 If the dsp io range has not been setup and stored in bios by the 25 io range used by the dsp to be configured.28 If the mwave's uart irq has not been setup and stored in bios by the 30 irq used by the mwave uart to be configured.33 If the uart io range has not been setup and stored in bios by the 35 io range used by the mwave uart to be configured.
11 to be present on a single jack but handled by separate bits of18 This is done by splitting the jacks up into three things working19 together: the jack itself represented by a struct snd_soc_jack, sets of33 user space. The jack itself is completely passive, it is set up by the34 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 these43 which are updated automatically. They are created by the machine driver52 Actual jack detection is done by code which is able to monitor some53 input to the system and update a jack by calling snd_soc_jack_report(),[all …]
8 Note that bits are numbered as by the usual s390 convention (most significant15 DIAGNOSE calls by the guest cause a mandatory intercept. This implies16 all supported DIAGNOSE calls need to be handled by either KVM or its19 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. For50 Handled by userspace.53 Handled by userspace.56 Handled by userspace.59 Handled by either userspace or KVM (ioeventfd case).[all …]
10 All firmware packages on the Modules or Interfaces are managed by a special11 Firmware Management Protocol. To support Firmware Management by the AP, the61 be used by the user to identify the right character device for it. The class76 The Character device (gb-fw-mgmt-0 in example) can be opened by the userspace142 This ioctl shall be used by the user to get the version and firmware-tag of144 fw_mgmt_ioc_get_fw' are filled by the kernel.148 This ioctl shall be used by the user to get the version of a currently149 running Backend Interface Firmware identified by a firmware-tag. The user is151 in this case. The 'major' and 'minor' fields are set by the kernel in156 This ioctl shall be used by the user to load an Interface Firmware package on[all …]
10 Should be selected by any drivers that do in-kernel push16 Provides the generic IIO DMA buffer infrastructure that can be used by19 Should be selected by drivers that want to use the generic DMA buffer27 DMAengine framework. This can be used by converter drivers with a DMA port28 connected to an external DMA controller which is supported by the31 Should be selected by drivers that want to use this functionality.38 are handled by hardware.40 Should be selected by drivers that want to use the generic Hw consumer
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::
24 For the processors supported by ``intel_pstate``, the P-state concept is broader26 LinuxCon Europe 2015 presentation by Kristen Accardi [1]_ for more28 by ``intel_pstate`` internally follows the hardware specification (for details31 frequencies are involved in the user space interface exposed by it, so36 that. Some functionality of the core is limited by that.38 Since the hardware P-state selection interface used by ``intel_pstate`` is79 For example, the ``powersave`` P-state selection algorithm provided by83 There are two P-state selection algorithms provided by ``intel_pstate`` in the88 Which of the P-state selection algorithms is used by default depends on the90 Namely, if that option is set, the ``performance`` algorithm will be used by[all …]
17 This option is not user-selectable but automagically handled by33 This option is not user-selectable but automagically handled by39 This option is not user-selectable but automagically handled by47 This option is not user-selectable but automagically handled by57 This option is not user-selectable but automagically handled by74 This option is not user-selectable but automagically handled by90 This option is not user-selectable but automagically handled by109 This option is not user-selectable but automagically handled by124 This option is not user-selectable but automagically handled by139 This option is not user-selectable but automagically handled by[all …]
30 capability to large number of user-space processes by introducing socket-like55 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 is72 The handler for this request assumes that message buffer specified by73 a caller includes the reserved space for a packet header required by78 handler will wait for new message until timeout specified by a caller80 defined by MAX_SCHEDULE_TIMEOUT.86 The ioctl command codes and corresponding data structures intended for use by92 This device driver uses standard interfaces defined by kernel RapidIO subsystem93 and therefore it can be used with any mport device driver registered by RapidIO[all …]
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 with39 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 …]
