Home
last modified time | relevance | path

Searched +full:2 +full:x32 +full:- +full:bit (Results 1 – 15 of 15) sorted by relevance

/Documentation/process/
Dadding-syscalls.rst9 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`.
13 ------------------------
18 kernel, there are other possibilities -- choose what fits best for your
21 - If the operations involved can be made to look like a filesystem-like
26 - If the new functionality involves operations where the kernel notifies
30 - However, operations that don't map to
31 :manpage:`read(2)`/:manpage:`write(2)`-like operations
32 have to be implemented as :manpage:`ioctl(2)` requests, which can lead
35 - If you're just exposing runtime system information, a new node in sysfs
41 - If the operation is specific to a particular file or file descriptor, then
[all …]
/Documentation/translations/it_IT/process/
Dadding-syscalls.rst1 .. include:: ../disclaimer-ita.rst
3 :Original: :ref:`Documentation/process/adding-syscalls.rst <addsyscalls>`
14 :ref:`Documentation/translations/it_IT/process/submitting-patches.rst <it_submittingpatches>`.
18 ------------------------------------
23 ovvio, esistono altre possibilità - scegliete quella che meglio si adatta alle
26 - Se le operazioni coinvolte possono rassomigliare a quelle di un filesystem,
32 - Se la nuova funzionalità prevede operazioni dove il kernel notifica
36 - Tuttavia, le operazioni che non si sposano bene con operazioni tipo
37 :manpage:`read(2)`/:manpage:`write(2)` dovrebbero essere implementate
38 come chiamate :manpage:`ioctl(2)`, il che potrebbe portare ad un'API in
[all …]
/Documentation/translations/sp_SP/process/
Dadding-syscalls.rst1 .. include:: ../disclaimer-sp.rst
3 :Original: :ref:`Documentation/process/adding-syscalls.rst <addsyscalls>`
13 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>` que
17 -----------------------------------
22 tradicionales, existen otras posibilidades -- elija la que mejor se adecúe
25 - Si se puede hacer que la operación se parezca a un objeto filesystem,
31 - Si la nueva funcionalidad involucra operaciones donde el kernel
36 - Sin embargo, operaciones que no mapean a operaciones similares a
37 :manpage:`read(2)`/:manpage:`write(2)` tienen que ser implementadas
38 como solicitudes :manpage:`ioctl(2)`, las cuales pueden llevar a un
[all …]
/Documentation/ABI/testing/
Dsysfs-driver-zynqmp-fpga1 What: /sys/bus/platform/drivers/zynqmp_fpga_manager/firmware:zynqmp-firmware:pcap/status
7 of the FPGA device. Each bit position in the status value is
9 https://docs.xilinx.com/v/u/en-US/ug570-ultrascale-configuration
12 BIT(0) 0: No CRC error
15 BIT(1) 0: Decryptor security not set
18 BIT(2) 0: MMCMs/PLLs are not locked
21 BIT(3) 0: DCI not matched
24 BIT(4) 0: Start-up sequence has not finished
25 1: Start-up sequence has finished
27 BIT(5) 0: All I/Os are placed in High-Z state
[all …]
/Documentation/trace/
Duprobetracer.rst2 Uprobe-tracer: Uprobe-based Event Tracing
9 --------
13 Similar to the kprobe-event tracer, this doesn't need to be activated via
18 However unlike kprobe-event tracer, the uprobe event interface expects the
26 -------------------------
32 -:[GRP/][EVENT] : Clear uprobe or uretprobe event
49 +|-[u]OFFS(FETCHARG) : Fetch memory at FETCHARG +|- OFFS address.(\*2)(\*3)
54 (x8/x16/x32/x64), "string" and bitfield are supported.
57 (\*2) this is useful for fetching a field of data structures.
59 events can access only user-space memory.
[all …]
Dkprobetrace.rst2 Kprobe-based Event Tracing
8 --------
9 These events are similar to tracepoint-based events. Instead of tracepoints,
13 Unlike the tracepoint-based event, this can be added and removed
28 -------------------------
34 -:[GRP/][EVENT] : Clear a probe
50 @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol)
54 $retval : Fetch return value.(\*2)
56 +|-[u]OFFS(FETCHARG) : Fetch memory at FETCHARG +|- OFFS address.(\*3)(\*4)
61 (x8/x16/x32/x64), VFS layer common type(%pd/%pD), "char",
[all …]
Dfprobetrace.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Fprobe-based Event Tracing
10 --------
18 tracepoint argument, or the tracepoint without trace-event, which is
24 Synopsis of fprobe-events
25 -------------------------
47 @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol)
50 $argN : Fetch the Nth function argument. (N >= 1) (\*2)
53 +|-[u]OFFS(FETCHARG) : Fetch memory at FETCHARG +|- OFFS address.(\*4)(\*5)
58 (x8/x16/x32/x64), "char", "string", "ustring", "symbol", "symstr"
[all …]
Dhistogram.rst15 2. Histogram Trigger Command
33 numeric fields - on an event hit, the value(s) will be added to a
35 in place of an explicit value field - this is simply a count of
45 useful for providing more fine-grained summaries of event data.
69 numeric fields are displayed as base-10 integers. This can be
76 .sym-offset display an address as a symbol and offset
83 .graph display a bar-graph of a value
91 - only the 'hex' modifier can be used for values (because values
94 - the 'execname' modifier can only be used on a 'common_pid'. The
100 pid-specific comm fields in the event itself.
[all …]
/Documentation/devicetree/bindings/memory-controllers/
Dnvidia,tegra124-mc.yaml1 # SPDX-License-Identifier: (GPL-2.0)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/nvidia,tegra124-mc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jon Hunter <jonathanh@nvidia.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 Tegra124 SoC features a hybrid 2x32-bit / 1x64-bit memory controller.
22 const: nvidia,tegra124-mc
30 clock-names:
32 - const: mc
[all …]
/Documentation/userspace-api/media/v4l/
Dpixfmt-yuv-planar.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. planar-yuv:
12 - Semi-planar formats use two planes. The first plane is the luma plane and
16 - Fully planar formats use three planes to store the Y, Cb and Cr components
26 and applications that support the multi-planar API, described in
27 :ref:`planar-apis`. Unless explicitly documented as supporting non-contiguous
31 Semi-Planar YUV Formats
43 line stride. With horizontal subsampling by 2, the chroma line stride is equal
46 For non-contiguous formats, no constraints are enforced by the format on the
57 .. flat-table:: Overview of Semi-Planar YUV Formats
[all …]
Dsubdev-formats.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _v4l2-mbus-format:
14 .. flat-table:: struct v4l2_mbus_framefmt
15 :header-rows: 0
16 :stub-columns: 0
17 :widths: 1 1 2
19 * - __u32
20 - ``width``
21 - Image width in pixels.
22 * - __u32
[all …]
Dext-ctrls-codec-stateless.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _codec-stateless-controls:
18 .. _codec-stateless-control-id:
23 .. _v4l2-codec-stateless-h264:
43 .. flat-table:: struct v4l2_ctrl_h264_sps
44 :header-rows: 0
45 :stub-columns: 0
46 :widths: 1 1 2
48 * - __u8
49 - ``profile_idc``
[all …]
/Documentation/driver-api/media/drivers/ccs/
Dccs-regs.asc1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-3-Clause
2 # Copyright (C) 2019--2020 Intel Corporation
5 # - f field LSB MSB rflags
6 # - e enum value # after a field
7 # - e enum value [LSB MSB]
8 # - b bool bit
9 # - l arg name min max elsize [discontig...]
23 - e GRBG 0
24 - e RGGB 1
25 - e BGGR 2
[all …]
/Documentation/driver-api/
Dmtdnand.rst10 The generic NAND driver supports almost all NAND and AG-AND based chips
31 --------------------------
37 - [MTD Interface]
43 - [NAND Interface]
48 - [GENERIC]
53 - [DEFAULT]
65 -------------------------------
71 - [INTERN]
77 - [REPLACEABLE]
86 - [BOARDSPECIFIC]
[all …]
/Documentation/scsi/
Darcmsr_spec.rst11 ------------
13 - InitThread message and return code
15 2. Doorbell is used for RS-232 emulation
16 ----------------------------------------
35 ---------------------
46 4. RS-232 emulation
47 -------------------
52 1st uint32_t Data length (1--124)
53 Byte 4--127 Max 124 bytes of data
57 --------
[all …]