| /linux/Documentation/translations/zh_TW/process/ |
| H A 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: 不像簽署那樣正式。這是一個記錄，確認人至少審閱了補丁，並表示接受。
351 Acked-by：不一定表示對整個補丁的確認。例如，如果一個補丁影響多個子系統，並且
359 Co-developed-by: 聲明補丁是由多個開發人員共同創建的；當幾個人在一個補丁上工
[all …]
|
| /linux/Documentation/translations/zh_CN/process/ |
| H A D | submitting-patches.rst | 321 Signed-off-by: Random J Developer <random@developer.example.org>
324 将会自动完成。撤销也应当包含“Signed-off-by”， ``git revert -s`` 会帮你搞定。
329 作者签署之后的任何其他签署（Signed-off-by:'s）均来自处理和传递补丁的人员，但
333 何时使用Acked-by:，Cc:，和Co-developed-by:
336 Signed-off-by: 标签表示签名者参与了补丁的开发，或者他/她在补丁的传递路径中。
339 那么他们可以要求在补丁的变更日志中添加一个Acked-by:。
341 Acked-by: 通常由受影响代码的维护者使用，当该维护者既没有贡献也没有转发补丁时。
343 Acked-by: 不像签署那样正式。这是一个记录，确认人至少审阅了补丁，并表示接受。
347 Acked-by：不一定表示对整个补丁的确认。例如，如果一个补丁影响多个子系统，并且
355 Co-developed-by: 声明补丁是由多个开发人员共同创建的；当几个人在一个补丁上工
[all …]
|
| /linux/Documentation/translations/ja_JP/ |
| H A D | SubmittingPatches | 3 This document is maintained by Keiichi KII <k-keiichi@bx.jp.nec.com>
349 Signed-off-by: Random J Developer <random@developer.example.org>
365 Signed-off-by とあなたがその末尾に追加する Signed-off-by の間に、修正を
371 Signed-off-by: Random J Developer <random@developer.example.org>
373 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>
401 13) いつ Acked-by: と Cc: を使うのか
403 「 Signed-off-by: 」タグはその署名者がパッチの開発に関わっていたことやパッチ
407 る承認を記録し、示したいとします。その場合、その人を示すのに Acked-by: が使
408 えます。Acked-by: はパッチのチェンジログにも追加されます。
411 の伝播パスにいなかった時にも、メンテナは Acked-by: をしばしば利用します。
[all …]
|
| /linux/arch/arm/boot/dts/intel/axm/ |
| H A D | axm5516-cpus.dtsi | 77 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 …]
|
| /linux/arch/arm/nwfpe/ |
| H A D | softfloat-macros | 8 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/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-reserved.rst | 10 These formats are not defined by this specification, they are just
51 - 8 bit RGB format used by the BTTV driver.
56 - YUV format used by the gspca cpia1 driver.
67 - YUYV per line used by the gspca driver.
72 - YYUV per line used by the gspca driver.
77 - YUVY per line used by the gspca driver.
82 - Compressed GBRG Bayer format used by the gspca driver.
87 - Compressed BGGR Bayer format used by the gspca driver.
92 - Compressed BGGR Bayer format used by the gspca driver.
97 - JPEG compressed RGGB Bayer format used by the gspca driver.
[all …]
|
| H A D | pixfmt-v4l2.rst | 44 be calculated internally by the encoder itself, based on the OUTPUT
48 - The pixel format or type of compression, set by the application.
70 the value requested by the application, returning ``width`` times
71 bytes per pixel or a larger value required by the hardware. That
82 to the first plane and is divided by the same factor as the
93 - Size in bytes of the buffer to hold a complete image, set by the
96 number of bytes required by the codec to support the worst-case
112 by the driver for capture streams and by the application for
118 The driver indicates that colorspace conversion is supported by setting
131 must first ensure that the feature is supported by querying the
[all …]
|
| H A D | selection-api-configuration.rst | 32 areas that can be sampled is given by the ``V4L2_SEL_TGT_CROP_BOUNDS``
38 the area actually sampled, is given by the ``V4L2_SEL_TGT_CROP`` target.
44 Each capture device has a default source rectangle, given by the
54 the image size set by :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`.
56 The part of a buffer into which the image is inserted by the hardware is
57 controlled by the ``V4L2_SEL_TGT_COMPOSE`` target. The rectangle's
70 The part of a buffer that is modified by the hardware is given by
72 ``V4L2_SEL_TGT_COMPOSE`` plus all padding data modified by hardware
74 be changed by the hardware. The content of pixels that lie inside the
97 the area from which image date are processed by the hardware, is given
[all …]
|
| /linux/arch/m68k/fpsp040/ |
| H A D | binstr.S | 16 | 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/drivers/staging/media/atomisp/ |
| H A D | notes.txt | 9 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.
39 Other members of camera_mipi_info which are set by some drivers are:
40 -metadata_width, metadata_height, metadata_effective_width, set by
41 the ov5693 driver (and used by the atomisp core)
[all …]
|
| /linux/Documentation/driver-api/media/ |
| H A 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 …]
|
| /linux/tools/testing/selftests/sgx/ |
| H A D | test_encl_bootstrap.S | 13 .fill 1, 8, 0 # STATE (set by CPU)
16 .fill 1, 4, 0 # CSSA (set by CPU)
19 .fill 1, 8, 0 # AEP (set by EENTER and ERESUME)
27 .fill 1, 8, 0 # STATE (set by CPU)
30 .fill 1, 4, 0 # CSSA (set by CPU)
33 .fill 1, 8, 0 # AEP (set by EENTER and ERESUME)
45 # TCS #2. First make it relative by substracting __encl_base and
63 # simplify the code by not initializing ABI registers on entry or
67 # Prepare EEXIT target by popping the address of the instruction after
|
| /linux/Documentation/sound/soc/ |
| H A 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 …]
|
| /linux/Documentation/mhi/ |
| H A 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 …]
|
| /linux/drivers/staging/greybus/Documentation/firmware/ |
| H A D | firmware-management | 10 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/Documentation/virt/kvm/arm/ |
| H A 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
|
| /linux/Documentation/livepatch/ |
| H A 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 …]
|
| /linux/Documentation/driver-api/pm/ |
| H A 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 …]
|
| /linux/arch/arm/boot/dts/samsung/ |
| H A D | exynos5420-cpus.dtsi | 15 * 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 */
|
| H A D | exynos5422-cpus.dtsi | 14 * booting cluster (big or LITTLE) is chosen by IROM code by reading
64 #cooling-cells = <2>; /* min followed by max */
77 #cooling-cells = <2>; /* min followed by max */
90 #cooling-cells = <2>; /* min followed by max */
103 #cooling-cells = <2>; /* min followed by max */
116 #cooling-cells = <2>; /* min followed by max */
129 #cooling-cells = <2>; /* min followed by max */
142 #cooling-cells = <2>; /* min followed by max */
155 #cooling-cells = <2>; /* min followed by max */
|
| /linux/Documentation/pcmcia/ |
| H A 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::
|
| /linux/Documentation/driver-api/rapidio/ |
| H A 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 …]
|
| /linux/drivers/iio/buffer/ |
| H A D | Kconfig | 10 Should be selected by any drivers that do in-kernel push
16 Provides the generic IIO DMA buffer infrastructure that can be used by
19 Should be selected by drivers that want to use the generic DMA buffer
27 DMAEngine framework. This can be used by converter drivers with a DMA port
28 connected to an external DMA controller which is supported by the
31 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
|
| /linux/tools/testing/selftests/arm64/fp/ |
| H A D | README | 20 The test runs until killed by the user.
30 Terminated by signal 15, no error, iterations=9467, signals=1014
33 Terminated by signal 15, no error, iterations=9448, signals=1028
36 Terminated by signal 15, no error, iterations=9436, signals=1039
39 Terminated by signal 15, no error, iterations=9421, signals=1039
42 Terminated by signal 15, no error, iterations=9403, signals=1039
45 Terminated by signal 15, no error, iterations=9385, signals=1036
48 Terminated by signal 15, no error, iterations=9376, signals=1039
51 Terminated by signal 15, no error, iterations=9361, signals=1039
54 Terminated by signal 15, no error, iterations=9350, signals=1039
|
| /linux/Documentation/ABI/testing/ |
| H A 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
|