Home
last modified time | relevance | path

Searched full:can (Results 1 – 25 of 2795) sorted by relevance

12345678910>>...112

/Documentation/networking/
Dcan.rst8 The socketcan package is an implementation of CAN protocols
9 (Controller Area Network) for Linux. CAN is a networking technology
11 automotive fields. While there have been other CAN implementations
13 socket API, the Linux network stack and implements the CAN device
14 drivers as network interfaces. The CAN socket API has been designed
16 familiar with network programming, to easily learn how to use CAN
25 There have been CAN implementations for Linux before SocketCAN so the
27 implementations come as a device driver for some CAN hardware, they
31 receive raw CAN frames, directly to/from the controller hardware.
36 the CAN controller requires employment of another device driver and
[all …]
Diso15765-2.rst11 for diagnostic communication on CAN. It is widely used in the automotive
15 ISO-TP can be used both on CAN CC (aka Classical CAN) and CAN FD (CAN with
17 CAN network using SAE J1939 as data link layer (however, this is not a
38 Three different addressing formats can be employed:
40 * "normal" : each address is represented simply by a CAN ID.
42 * "extended": each address is represented by a CAN ID plus the first byte of
43 the CAN payload; both the CAN ID and the byte inside the payload shall be
46 * "mixed": each address is represented by a CAN ID plus the first byte of
47 the CAN payload; the CAN ID is different between two addresses, but the
53 When transmitting data using the ISO-TP protocol, the payload can either fit
[all …]
/Documentation/devicetree/bindings/net/can/
Drenesas,rcar-can.yaml4 $id: http://devicetree.org/schemas/net/can/renesas,rcar-can.yaml#
7 title: Renesas R-Car CAN Controller
17 - renesas,can-r8a7778 # R-Car M1-A
18 - renesas,can-r8a7779 # R-Car H1
19 - const: renesas,rcar-gen1-can # R-Car Gen1
23 - renesas,can-r8a7742 # RZ/G1H
24 - renesas,can-r8a7743 # RZ/G1M
25 - renesas,can-r8a7744 # RZ/G1N
26 - renesas,can-r8a7745 # RZ/G1E
27 - renesas,can-r8a77470 # RZ/G1C
[all …]
Dallwinner,sun4i-a10-can.yaml4 $id: http://devicetree.org/schemas/net/can/allwinner,sun4i-a10-can.yaml#
7 title: Allwinner A10 CAN Controller
14 - $ref: can-controller.yaml#
20 - const: allwinner,sun7i-a20-can
21 - const: allwinner,sun4i-a10-can
22 - const: allwinner,sun4i-a10-can
23 - const: allwinner,sun8i-r40-can
24 - const: allwinner,sun20i-d1-can
42 - allwinner,sun8i-r40-can
43 - allwinner,sun20i-d1-can
[all …]
Dxilinx,can.yaml4 $id: http://devicetree.org/schemas/net/can/xilinx,can.yaml#
8 Xilinx CAN and CANFD controller
16 - xlnx,zynq-can-1.0
17 - xlnx,axi-can-1.00.a
39 description: CAN Tx fifo depth (Zynq, Axi CAN).
43 description: CAN Rx fifo depth (Zynq, Axi CAN, CAN FD in sequential Rx mode)
47 description: CAN Tx mailbox buffer count (CAN FD)
54 description: CAN TX_OL, TX_TL and RX FIFOs have ECC support(AXI CAN)
66 - $ref: can-controller.yaml#
72 - xlnx,zynq-can-1.0
[all …]
Datmel-can.txt1 * AT91 CAN *
4 - compatible: Should be "atmel,at91sam9263-can", "atmel,at91sam9x5-can" or
5 "microchip,sam9x60-can"
6 - reg: Should contain CAN controller registers location and length
7 - interrupts: Should contain IRQ line for the CAN controller
11 can0: can@f000c000 {
12 compatible = "atmel,at91sam9x5-can";
Dst,stm32-bxcan.yaml4 $id: http://devicetree.org/schemas/net/can/st,stm32-bxcan.yaml#
9 description: STMicroelectronics BxCAN controller for CAN bus
15 - $ref: can-controller.yaml#
22 st,can-primary:
25 two CAN peripherals in dual CAN configuration. In that case they share
27 Not to be used if the peripheral is in single CAN configuration.
32 st,can-secondary:
35 has two CAN peripherals in dual CAN configuration. In that case they
37 Not to be used if the peripheral is in single CAN configuration.
70 secondary) in dual CAN peripheral configuration.
[all …]
Dcan-transceiver.yaml4 $id: http://devicetree.org/schemas/net/can/can-transceiver.yaml#
7 title: CAN transceiver
9 description: CAN transceiver generic properties bindings
17 description: a positive non 0 value that determines the max speed that CAN/CAN-FD can run.
Dmicrochip,mpfs-can.yaml4 $id: http://devicetree.org/schemas/net/can/microchip,mpfs-can.yaml#
8 Microchip PolarFire SoC (MPFS) can controller
14 - $ref: can-controller.yaml#
18 const: microchip,mpfs-can
29 - description: CAN bus clock
41 can@2010c000 {
42 compatible = "microchip,mpfs-can";
Dfsl,flexcan.yaml4 $id: http://devicetree.org/schemas/net/can/fsl,flexcan.yaml#
8 Flexcan CAN controller on Freescale's ARM and PowerPC system-on-a-chip (SOC).
14 - $ref: can-controller.yaml#
71 description: Regulator that powers the CAN transceiver.
81 can-transceiver:
82 $ref: can-transceiver.yaml#
92 req_gpr is the gpr register offset of CAN stop request.
93 req_bit is the bit offset of CAN stop request.
98 - description: The 'req_gpr' is the gpr register offset of CAN stop request.
100 - description: The 'req_bit' is the bit offset of CAN stop request.
[all …]
Dcan-controller.yaml4 $id: http://devicetree.org/schemas/net/can/can-controller.yaml#
7 title: CAN Controller Common Properties
14 pattern: "^can(@.*)?$"
17 description: GPIO pin to enable CAN bus termination.
21 description: The resistance value of the CAN bus termination resistor.
Dholt_hi311x.txt1 * Holt HI-311X stand-alone CAN controller device tree bindings
7 - clocks: The clock feeding the CAN controller.
8 - interrupts: Should contain IRQ line for the CAN controller.
11 - vdd-supply: Regulator that powers the CAN controller.
12 - xceiver-supply: Regulator that powers the CAN transceiver.
15 can0: can@1 {
Drenesas,rcar-canfd.yaml4 $id: http://devicetree.org/schemas/net/can/renesas,rcar-canfd.yaml#
7 title: Renesas R-Car CAN FD Controller
64 renesas,no-can-fd:
67 The controller can operate in either CAN FD only mode (default) or
68 Classical CAN only mode. The mode is global to all channels.
69 Specify this property to put the controller in Classical CAN only mode.
73 Reference to the CANFD clock. The CANFD clock is a div6 clock and can be
74 used by both CAN (if present) and CAN FD controllers at the same time.
86 child node. Each channel can be enabled/disabled individually.
109 - $ref: can-controller.yaml#
[all …]
/Documentation/userspace-api/media/rc/
Dlirc-get-features.rst41 .. _LIRC-CAN-REC-RAW:
47 .. _LIRC-CAN-REC-PULSE:
52 :ref:`LIRC_MODE_PULSE <lirc-mode-pulse>` can only be used for transmitting.
54 .. _LIRC-CAN-REC-MODE2:
64 .. _LIRC-CAN-REC-LIRCCODE:
70 .. _LIRC-CAN-REC-SCANCODE:
77 .. _LIRC-CAN-SET-SEND-CARRIER:
84 .. _LIRC-CAN-SET-SEND-DUTY-CYCLE:
91 .. _LIRC-CAN-SET-TRANSMITTER-MASK:
98 .. _LIRC-CAN-SET-REC-CARRIER:
[all …]
/Documentation/sound/cards/
Dpcmtest.rst6 The Virtual PCM Test Driver emulates a generic PCM device, and can be used for
8 the PCM middle layer. Additionally, it can be used for simulating hard to reproduce
11 What can this driver do?
14 At this moment the driver can do the following things:
23 Also, this driver can check the playback stream for containing the predefined pattern,
47 First of all, you may want to specify the pattern for data generation. You can do it
54 To set the pattern for the channel 0 you can execute the following command:
63 The pattern itself can be up to 4096 bytes long.
69 can be used for time delay/speedup simulations. The parameter has integer type, and
73 negative - faster. You can try it yourself by starting a recording in any
[all …]
/Documentation/networking/device_drivers/can/
Dcan327.rst17 working with CAN buses.
19 CAN adapters are expensive, few, and far between.
21 Let's use ELM327s as CAN adapters.
29 into full fledged (as far as possible) CAN interfaces.
31 Since the ELM327 was never meant to be a stand alone CAN controller,
52 The official data sheets can be found at ELM electronics' home page:
64 If you have kept this default configuration, the line discipline can
80 Once the ldisc is attached, the CAN interface starts out unconfigured.
85 sudo ip link set can0 type can bitrate 500000
92 After this, you can set out as usual with candump, cansniffer, etc.
[all …]
/Documentation/power/regulator/
Dconsumer.rst12 A consumer driver can get access to its supply regulator by calling ::
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::
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::
63 Finally, a regulator can be forcefully disabled in the case of an emergency::
76 voltage to match system operating points. e.g. CPUfreq drivers can scale
80 Consumers can control their supply voltage by calling::
87 NOTE: this can be called when the regulator is enabled or disabled. If called
92 The regulators configured voltage output can be found by calling::
[all …]
/Documentation/devicetree/bindings/regulator/
Dregulator.yaml128 hardware performs emergency shutdown. Zero can be passed to disable
130 limit setting can be omitted.
135 Zero can be passed to disable error detection and value '1' indicates
136 that detection should be enabled but limit setting can be omitted.
141 damaged. Recovery actions should be initiated. Zero can be passed to
143 be enabled but limit setting can be omitted.
147 hardware performs emergency shutdown. Zero can be passed to disable
149 limit setting can be omitted. Limit is given as microvolt offset from
155 Zero can be passed to disable error detection and value '1' indicates
156 that detection should be enabled but limit setting can be omitted. Limit
[all …]
/Documentation/core-api/
Dmaple_tree.rst17 entry in a cache-efficient manner. The tree can also be put into an RCU-safe
19 synchronize on a lock, which can be the default spinlock, or the user can set
28 The Maple Tree can store values between ``0`` and ``ULONG_MAX``. The Maple
31 entries then the users can convert the entries using xa_mk_value() and convert
33 value, then the user can convert the value when using the
36 The Maple Tree can also be configured to support searching for a gap of a given
57 ``0`` upwards or ``ULONG_MAX`` down. An allocation tree can be used by
60 You can then set entries using mtree_store() or mtree_store_range().
64 given index. You can use mtree_erase() to erase an entire range by only
69 currently ``NULL``, you can use mtree_insert_range() or mtree_insert() which
[all …]
/Documentation/networking/device_drivers/can/freescale/
Dflexcan.rst4 Flexcan CAN Controller driver
22 The RX FIFO mode uses a hardware FIFO with a depth of 6 CAN frames,
24 CAN frames. With the help of the bigger buffer, the mailbox mode
27 As reception of RTR frames is part of the CAN standard, all flexcan
30 With the "rx-rtr" private flag the ability to receive RTR frames can
37 The CAN controller can and will receive RTR frames.
50 The setting can only be changed if the interface is down::
/Documentation/admin-guide/mm/
Dzswap.rst11 for potentially reduced swap I/O. This trade-off can also result in a
17 * Desktop/laptop users with limited RAM capacities can mitigate the
19 * Overcommitted guests that share a common I/O resource can
23 * Users with SSDs as swap devices can extend the life of the device by
32 This setting can then be overridden by providing the kernel command line
34 Zswap can also be enabled and disabled at runtime using the sysfs interface.
62 but it can be overridden at boot time by setting the ``zpool`` attribute,
63 e.g. ``zswap.zpool=zbud``. It can also be changed at runtime using the sysfs
71 storage method, and it can achieve greater storage densities.
91 pool can occupy.
[all …]
/Documentation/driver-api/early-userspace/
Dearly_userspace_support.rst32 You can create a cpio archive that contains the early userspace image.
41 The kernel build process can also build an early userspace image from
47 CONFIG_INITRAMFS_SOURCE. Sources can be either directories or files -
52 directory, limited user and group ID translation can be performed.
53 INITRAMFS_ROOT_UID can be set to a user ID that needs to be mapped to
54 user root (0). INITRAMFS_ROOT_GID can be set to a group ID that needs
64 can create a 'root-image' directory and install all files into it.
66 special files can be listed in a 'root-files' file. Both 'root-image'
67 and 'root-files' can be listed in CONFIG_INITRAMFS_SOURCE and a complete
68 early userspace image can be built by an unprivileged user.
[all …]
/Documentation/networking/device_drivers/can/ctu/
Dctucanfd-driver.rst3 CTU CAN FD Driver
9 About CTU CAN FD IP Core
12 `CTU CAN FD <https://gitlab.fel.cvut.cz/canbus/ctucanfd_ip_core>`_
19 `Vivado integration <https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top>`_
30 The basic functional model of the CTU CAN FD peripheral has been
31 accepted into QEMU mainline. See QEMU `CAN emulation support <https://www.qemu.org/docs/master/syst…
32 for CAN FD buses, host connection and CTU CAN FD core emulation. The development
33 version of emulation support can be cloned from ctu-canfd branch of QEMU local
40 SocketCAN is a standard common interface for CAN devices in the Linux
43 described in `Linux SocketCAN <https://www.kernel.org/doc/html/latest/networking/can.html>`_.
[all …]
/Documentation/bpf/
Dprog_lsm.rst15 The example shows an eBPF program that can be attached to the ``file_mprotect``
20 Other LSM hooks which can be instrumented can be found in
25 They can simply declare the structures in the eBPF program and only specify
43 This can be further simplified (if one has access to the BTF information at
50 .. note:: ``path-to-btf-vmlinux`` can be ``/sys/kernel/btf/vmlinux`` if the
54 The ``vmlinux.h`` can then simply be included in the BPF programs without
57 The eBPF programs can be declared using the``BPF_PROG``
98 eBPF programs can be loaded with the :manpage:`bpf(2)` syscall's
108 This can be simplified by using a skeleton header generated by ``bpftool``:
114 and the program can be loaded by including ``my_prog.skel.h`` and using
[all …]
/Documentation/gpu/amdgpu/display/
Ddisplay-contributing.rst10 This page summarizes some of the issues you can help with; keep in mind that
19 Users can report issues associated with AMD GPUs at:
24 filter issues. If you can reproduce any problem, you could help by adding more
32 `IGT`_ provides many integration tests that can be run on your GPU. We always
36 your hardware. Keep in mind that this failure can be an IGT problem or a kernel
57 Linux has a User-mode Linux (UML) feature, and the kernel can be compiled to
58 the **um** architecture. Compiling for **um** can bring multiple advantages
72 bug. Ftrace provides a filter mechanism that can be useful when the developer
73 has some hunch of which part of the code can cause the issue; for this reason,
75 filter. Additionally, prefixes can improve stack trace readability.
[all …]

12345678910>>...112