Home
last modified time | relevance | path

Searched refs:by (Results 1 – 25 of 4190) sorted by relevance

12345678910>>...168

/linux-6.1.9/Documentation/arm64/
Delf_hwcaps.rst19 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 …]
/linux-6.1.9/Documentation/translations/zh_CN/process/
Dsubmitting-patches.rst324 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 Singed-off-by: 标签表示签名者参与了补丁的开发，或者他/她在补丁的传递路径中。
342 那么他们可以要求在补丁的变更日志中添加一个Acked-by:。
344 Acked-by: 通常由受影响代码的维护者使用，当该维护者既没有贡献也没有转发补丁时。
346 Acked-by: 不像签署那样正式。这是一个记录，确认人至少审阅了补丁，并表示接受。
350 Acked-by：不一定表示对整个补丁的确认。例如，如果一个补丁影响多个子系统，并且
358 Co-developed-by: 声明补丁是由多个开发人员共同创建的；当几个人在一个补丁上工
[all …]
D5.Posting.rst125 - 一个或多个标记行，至少有一个由补丁作者的 Signed-off-by 签名。标记将在下面
163 - Signed-off-by: 这是一个开发人员的证明，证明他或她有权提交补丁以包含到内核
168 - Co-developed-by: 声明补丁是由多个开发人员共同创建的；当几个人在一个补丁上
170 Co-developed-by: 表示作者身份，所以每个共同开发人，必须紧跟在相关合作作者
171 的Signed-off-by之后。具体内容和示例见以下文件
174 - Acked-by: 表示另一个开发人员（通常是相关代码的维护人员）同意补丁适合包含
177 - Tested-by: 声明某人已经测试了补丁并确认它可以工作。
179 - Reviewed-by: 表示某开发人员已经审查了补丁的正确性；有关详细信息，请参阅
182 - Reported-by: 指定报告此补丁修复的问题的用户；此标记用于表示感谢。
/linux-6.1.9/Documentation/translations/zh_TW/process/
Dsubmitting-patches.rst344 Signed-off-by: Random J Developer <random@developer.example.org>
359 Signed-off-by: Random J Developer <random@developer.example.org>
361 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
385 12）何時使用Acked-by:，CC:，和Co-Developed by:
388 Singed-off-by: 標記表示簽名者參與了補丁的開發，或者他/她在補丁的傳遞路徑中。
391 那麼他們可以要求在補丁的變更日誌中添加一個 Acked-by:
393 Acked-by：通常由受影響代碼的維護者使用，當該維護者既沒有貢獻也沒有轉發補丁時。
395 Acked-by: 不像簽字人那樣正式。這是一個記錄，確認人至少審查了補丁，並表示接受。
399 Acked-by：不一定表示對整個補丁的確認。例如，如果一個補丁影響多個子系統，並且
407 Co-developed-by: 聲明補丁是由多個開發人員共同創建的；當幾個人在一個補丁上工
[all …]
D5.Posting.rst128 - 一個或多個標記行，至少有一個由補丁作者的 Signed-off-by 簽名。標記將在下面
166 - Signed-off-by: 這是一個開發人員的證明，證明他或她有權提交補丁以包含到內核
171 - Co-developed-by: 聲明補丁是由多個開發人員共同創建的；當幾個人在一個補丁上
173 Co-developed-by: 表示作者身份，所以每個共同開發人，必須緊跟在相關合作作者
174 的Signed-off-by之後。具體內容和示例見以下文件
177 - Acked-by: 表示另一個開發人員（通常是相關代碼的維護人員）同意補丁適合包含
180 - Tested-by: 聲明某人已經測試了補丁並確認它可以工作。
182 - Reviewed-by: 表示某開發人員已經審查了補丁的正確性；有關詳細信息，請參閱
185 - Reported-by: 指定報告此補丁修復的問題的用戶；此標記用於表示感謝。
/linux-6.1.9/Documentation/translations/ja_JP/
DSubmittingPatches3 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 …]
/linux-6.1.9/arch/arm/boot/dts/
Daxm5516-cpus.dtsi77 cpu-release-addr = <0>; // Fixed by the boot loader
85 cpu-release-addr = <0>; // Fixed by the boot loader
93 cpu-release-addr = <0>; // Fixed by the boot loader
101 cpu-release-addr = <0>; // Fixed by the boot loader
109 cpu-release-addr = <0>; // Fixed by the boot loader
117 cpu-release-addr = <0>; // Fixed by the boot loader
125 cpu-release-addr = <0>; // Fixed by the boot loader
133 cpu-release-addr = <0>; // Fixed by the boot loader
141 cpu-release-addr = <0>; // Fixed by the boot loader
149 cpu-release-addr = <0>; // Fixed by the boot loader
[all …]
Dexynos5420-cpus.dtsi15 * booting cluster (big or LITTLE) is chosen by IROM code by reading
65 #cooling-cells = <2>; /* min followed by max */
77 #cooling-cells = <2>; /* min followed by max */
89 #cooling-cells = <2>; /* min followed by max */
101 #cooling-cells = <2>; /* min followed by max */
113 #cooling-cells = <2>; /* min followed by max */
125 #cooling-cells = <2>; /* min followed by max */
137 #cooling-cells = <2>; /* min followed by max */
149 #cooling-cells = <2>; /* min followed by max */
/linux-6.1.9/arch/x86/crypto/
Daes_ctrby8_avx-x86_64.S113 .set by, \b define
124 .rept (by)
130 .rept (by)
138 .rept (by - 1)
155 add $by, counter
157 vpaddq (ddq_add_1 + 16 * (by - 1))(%rip), xcounter, xcounter
165 .rept (by - 1)
174 .rept by
189 .rept by
195 add $(16*by), p_in
[all …]
/linux-6.1.9/arch/arm/nwfpe/
Dsoftfloat-macros8 Written by John R. Hauser. This work was made possible in part by the
10 Street, Berkeley, California 94704. Funding was partially provided by the
14 overseen by Profs. Nelson Morgan and John Wawrzynek. More information
34 Shifts `a' right by the number of bits given in `count'. If any nonzero
36 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 nonzero
61 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 …]
/linux-6.1.9/Documentation/userspace-api/media/v4l/
Dpixfmt-reserved.rst9 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 …]
/linux-6.1.9/drivers/staging/media/atomisp/
Dnotes.txt9 Memory is allocated by the hmm code. hmm_alloc() returns an ISP virtual
11 the hmm code finds the backing hmm-buffer-object (hmm_bo) by looking
14 The actual processing pipeline is made by loading one or more programs,
16 different binaries. Binaries are picked by filling a ia_css_binary_descr
24 (it is enabled by default) only the preview binary is loaded.
35 a camera_mipi_info struct. This struct is allocated/managed by
37 are filled by the atomisp core itself, like e.g. the port number.
42 used by the atomisp code at all. It is returned to userspace by
45 Other members of camera_mipi_info which are set by some drivers are:
46 -metadata_width, metadata_height, metadata_effective_width, set by
[all …]
/linux-6.1.9/arch/m68k/fpsp040/
Dbinstr.S16 | bit 63. The fraction is multiplied by 10 using a mul by 2
17 | shift and a mul by 8 shift. The bits shifted out of the
28 | A3. Multiply the fraction in d2:d3 by 8 using bit-field
32 | A4. Multiply the fraction in d4:d5 by 2 using shifts. The msb
33 | will be collected by the carry.
51 | d2: upper 32-bits of fraction for mul by 8
52 | d3: lower 32-bits of fraction for mul by 8
53 | d4: upper 32-bits of fraction for mul by 2
54 | d5: lower 32-bits of fraction for mul by 2
87 | A3. Multiply d2:d3 by 8; extract msbs into d1.
[all …]
/linux-6.1.9/Documentation/driver-api/media/
Dmc-core.rst28 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 …]
/linux-6.1.9/tools/lib/traceevent/Documentation/
Dlibtraceevent-event_list.txt7 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 be
48 it is managed by the library.
51 In case of an error, NULL is returned. The returned array must be freed by
68 /* Failed to get the events, sorted by ID */
[all …]
/linux-6.1.9/drivers/char/mwave/
DREADME5 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.
/linux-6.1.9/Documentation/sound/soc/
Djack.rst11 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 …]
/linux-6.1.9/Documentation/admin-guide/pm/
Dintel_pstate.rst24 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 …]
/linux-6.1.9/Documentation/mhi/
Dmhi.rst12 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 …]
/linux-6.1.9/drivers/staging/greybus/Documentation/firmware/
Dfirmware-management10 All firmware packages on the Modules or Interfaces are managed by a special
11 Firmware Management Protocol. To support Firmware Management by the AP, the
61 be used by the user to identify the right character device for it. The class
76 The Character device (gb-fw-mgmt-0 in example) can be opened by the userspace
142 This ioctl shall be used by the user to get the version and firmware-tag of
144 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 currently
149 running Backend Interface Firmware identified by a firmware-tag. The user is
151 in this case. The 'major' and 'minor' fields are set by the kernel in
156 This ioctl shall be used by the user to load an Interface Firmware package on
[all …]
/linux-6.1.9/Documentation/virt/kvm/s390/
Ds390-diag.rst11 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 …]
/linux-6.1.9/Documentation/devicetree/bindings/power/
Dpower-domain.yaml16 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
50 Phandles to the OPP tables of power domains provided by a power domain
52 the power domains provided by the provider have identical OPP tables,
61 by device tree binding documentation of particular provider.
65 A phandle and PM domain specifier as defined by bindings of the power
66 controller specified by phandle. Some power domains might be powered
[all …]
/linux-6.1.9/Documentation/pcmcia/
Dlocking.rst62 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::
/linux-6.1.9/Documentation/livepatch/
Dsystem-state.rst17 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 …]
/linux-6.1.9/drivers/media/v4l2-core/
DKconfig18 This API is mostly used by camera interfaces in embedded platforms.
35 # Used by drivers that need tuner.ko
39 # Used by drivers that need v4l2-jpeg.ko
43 # Used by drivers that need v4l2-h264.ko
47 # Used by drivers that need v4l2-vp9.ko
51 # Used by drivers that need v4l2-mem2mem.ko
56 # Used by LED subsystem flash drivers
77 # Used by drivers that need Videobuf modules

12345678910>>...168