Searched full:can (Results 1 – 25 of 2893) sorted by relevance
12345678910>>...116
| /Documentation/devicetree/bindings/net/can/ |
| D | rcar_can.txt | 1 Renesas R-Car CAN controller Device Tree Bindings
5 - compatible: "renesas,can-r8a7743" if CAN controller is a part of R8A7743 SoC.
6 "renesas,can-r8a7744" if CAN controller is a part of R8A7744 SoC.
7 "renesas,can-r8a7745" if CAN controller is a part of R8A7745 SoC.
8 "renesas,can-r8a77470" if CAN controller is a part of R8A77470 SoC.
9 "renesas,can-r8a774a1" if CAN controller is a part of R8A774A1 SoC.
10 "renesas,can-r8a774c0" if CAN controller is a part of R8A774C0 SoC.
11 "renesas,can-r8a7778" if CAN controller is a part of R8A7778 SoC.
12 "renesas,can-r8a7779" if CAN controller is a part of R8A7779 SoC.
13 "renesas,can-r8a7790" if CAN controller is a part of R8A7790 SoC.
[all …]
|
| D | xilinx_can.txt | 1 Xilinx Axi CAN/Zynq CANPS controller Device Tree Bindings
6 - "xlnx,zynq-can-1.0" for Zynq CAN controllers
7 - "xlnx,axi-can-1.00.a" for Axi CAN controllers
8 - "xlnx,canfd-1.0" for CAN FD controllers
9 - "xlnx,canfd-2.0" for CAN FD 2.0 controllers
16 - "can_clk", "s_axi_aclk" (For AXI CAN and CAN FD).
19 - tx-fifo-depth : Can Tx fifo depth (Zynq, Axi CAN).
20 - rx-fifo-depth : Can Rx fifo depth (Zynq, Axi CAN, CAN FD in
22 - tx-mailbox-count : Can Tx mailbox buffer count (CAN FD).
23 - rx-mailbox-count : Can Rx mailbox buffer count (CAN FD in mailbox Rx
[all …]
|
| D | can-transceiver.txt | 1 Generic CAN transceiver Device Tree binding
4 CAN transceiver typically limits the max speed in standard CAN and CAN FD
7 the "can-transceiver" node can be used.
11 speed that CAN/CAN-FD can run. Any other value
16 Based on Texas Instrument's TCAN1042HGV CAN Transceiver
20 can-transceiver {
|
| D | atmel-can.txt | 1 * AT91 CAN *
4 - compatible: Should be "atmel,at91sam9263-can" or "atmel,at91sam9x5-can"
5 - reg: Should contain CAN controller registers location and length
6 - interrupts: Should contain IRQ line for the CAN controller
10 can0: can@f000c000 {
11 compatible = "atmel,at91sam9x5-can";
|
| D | fsl-flexcan.txt | 1 Flexcan CAN controller on Freescale's ARM and PowerPC system-on-a-chip (SOC).
19 - xceiver-supply: Regulator that powers the CAN transceiver
30 req_gpr is the gpr register offset of CAN stop request.
31 req_bit is the bit offset of CAN stop request.
32 ack_gpr is the gpr register offset of CAN stop acknowledge.
33 ack_bit is the bit offset of CAN stop acknowledge.
35 - fsl,clk-source: Select the clock source to the CAN Protocol Engine (PE).
42 - wakeup-source: enable CAN remote wakeup
46 can@1c000 {
|
| D | microchip,mcp251x.txt | 1 * Microchip MCP251X stand-alone CAN controller device tree bindings
9 - clocks: The clock feeding the CAN controller.
10 - interrupts: Should contain IRQ line for the CAN controller.
13 - vdd-supply: Regulator that powers the CAN controller.
14 - xceiver-supply: Regulator that powers the CAN transceiver.
17 can0: can@1 {
|
| D | holt_hi311x.txt | 1 * 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 {
|
| D | sun4i_can.txt | 1 Allwinner A10/A20 CAN controller Device Tree Bindings
5 - compatible: "allwinner,sun4i-a10-can"
6 - reg: physical base address and size of the Allwinner A10/A20 CAN register map.
17 allwinner,function = "can";
22 can0: can@1c2bc00 {
23 compatible = "allwinner,sun4i-a10-can";
32 can0: can@1c2bc00 {
|
| D | m_can.txt | 14 and CAN clock.
19 Multiple M_CAN instances can share the same Message
47 - can-transceiver : Can-transceiver subnode describing maximum speed
48 that can be used for CAN/CAN-FD modes. See
49 Documentation/devicetree/bindings/net/can/can-transceiver.txt
53 m_can1: can@20e8000 {
72 can-transceiver {
|
| D | rcar_canfd.txt | 1 Renesas R-Car CAN FD controller Device Tree Bindings
21 - reg: physical base address and size of the R-Car CAN FD register map.
36 In the denoted SoCs, canfd clock is a div6 clock and can be used by both CAN
37 and CAN FD controller at the same time. It needs to be scaled to maximum
45 The controller can operate in either CAN FD only mode (default) or
46 Classical CAN only mode. The mode is global to both the channels. In order to
48 - renesas,no-can-fd: puts the controller in Classical CAN only mode.
55 canfd: can@e66c0000 {
81 E.g. below enables Channel 1 alone in the board in Classical CAN only mode.
86 renesas,no-can-fd;
|
| D | mpc5xxx-mscan.txt | 1 CAN Device Tree Bindings
9 In addition to the required compatible-, reg- and interrupt-properties, you can
20 In addition to the required compatible-, reg- and interrupt-properties, you can
27 If this property is not present, an optimal CAN
33 clock divider can be specified. By default, a
39 can@1300 {
46 can@1380 {
|
| /Documentation/networking/ |
| D | can.rst | 8 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 …]
|
| D | batman-adv.rst | 13 affected by any changes within the network. You can run almost any protocol
17 to a minimum. It does not depend on any (other) network driver, and can be used
30 batman-adv can operate. The batman-adv soft-interface can be created using the
46 The same can also be done using the batctl interface subcommand::
57 which can be modified using batctl. Detailed information about this can be found
60 For instance, you can check the current originator interval (value
75 Information about the current state can be accessed via the batadv generic
89 The "bat0" interface can be used like any other regular interface. It needs an
90 IP address which can be either statically configured or dynamically (by using
110 log. Depending on your operating system distribution this can be read in one of
[all …]
|
| /Documentation/media/uapi/rc/ |
| D | lirc-get-features.rst | 48 .. _LIRC-CAN-REC-RAW:
54 .. _LIRC-CAN-REC-PULSE:
59 :ref:`LIRC_MODE_PULSE <lirc-mode-pulse>` can only be used for transmitting.
61 .. _LIRC-CAN-REC-MODE2:
71 .. _LIRC-CAN-REC-LIRCCODE:
77 .. _LIRC-CAN-REC-SCANCODE:
84 .. _LIRC-CAN-SET-SEND-CARRIER:
91 .. _LIRC-CAN-SET-SEND-DUTY-CYCLE:
98 .. _LIRC-CAN-SET-TRANSMITTER-MASK:
105 .. _LIRC-CAN-SET-REC-CARRIER:
[all …]
|
| /Documentation/power/regulator/ |
| D | consumer.rst | 12 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/process/ |
| D | 7.AdvancedTopics.rst | 8 number of topics which can be helpful for developers wanting to become a
23 Managing patches with git can make life much easier for the developer,
46 heads, etc. It can all be a little intimidating at the outset, but the
49 Using git to generate patches for submission by email can be a good
53 will, of course, need a server that can be pulled from. Setting up such a
57 developers can get an account on kernel.org, but those are not easy to come
61 of development can be separated into a separate "topic branch" and
69 Git provides some powerful tools which can allow you to rewrite your
71 say, or which has some other sort of obvious bug) can be fixed in place or
72 made to disappear from the history entirely. A patch series can be
[all …]
|
| /Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 32 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/scsi/ |
| D | scsi.txt | 7 It can also be found at:
12 The scsi support in the linux kernel can be modularized in a number of
17 support. Without it you can do nothing with any of the other scsi drivers.
18 The scsi core support can be a module (scsi_mod.o), or it can be built into
25 The individual upper and lower level drivers can be loaded in any order
29 level drivers to support the various assorted devices which can be
30 controlled. You can for example load the tape driver to use the tape drive,
38 Adaptec. Almost all lower level drivers can be built either as modules or
|
| /Documentation/vm/ |
| D | zswap.rst | 13 for potentially reduced swap I/O. This trade-off can also result in a
25 * Desktop/laptop users with limited RAM capacities can mitigate the
27 * Overcommitted guests that share a common I/O resource can
31 * Users with SSDs as swap devices can extend the life of the device by
38 Zswap is disabled by default but can be enabled at boot time by setting
40 can also be enabled and disabled at runtime using the sysfs interface.
67 of type zbud is created, but it can be selected at boot time by
68 setting the ``zpool`` attribute, e.g. ``zswap.zpool=zbud``. It can
76 storage method, and it can achieve greater storage densities. However,
78 cannot evict the oldest page, it can only reject new pages.
[all …]
|
| /Documentation/media/uapi/mediactl/ |
| D | request-api.rst | 1 .. This file is dual-licensed: you can use it either under the terms
6 .. a) This file is free software; you can redistribute it and/or
39 While the initial use-case was V4L2, it can be extended to other subsystems
78 Standard V4L2 ioctls can then receive a request file descriptor to express the
88 Once the configuration and buffers of the request are specified, it can be
94 For :ref:`memory-to-memory devices <mem2mem>` you can use requests only for
112 Controls can still be set without a request and are applied immediately,
117 Setting the same control through a request and also directly can lead to
120 User-space can :ref:`poll() <request-func-poll>` a request file descriptor in
125 dequeue its buffers: buffers that are available halfway through a request can
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-powercap | 17 controlled. A <control type> can contain multiple power zones.
32 A power zone is a single or a collection of devices, which can
45 power zone for a whole CPU package, each CPU core in it can
61 If the counter can not be reset, then this attribute is
91 Each power zone can define one or more constraints. Each
92 constraint can have an optional name. Here "X" can have values
102 Here "X" can have values from 0 to max integer.
111 Here "X" can have values from 0 to max integer.
120 Here "X" can have values from 0 to max integer.
128 Here "X" can have values from 0 to max integer.
[all …]
|
| /Documentation/hid/ |
| D | hid-sensor.rst | 16 and also the individual data fields. Each sensor can have variable number of
18 example a part of report descriptor can look like::
47 for different sensors. For example an accelerometer can send X,Y and Z data, whereas
48 an ambient light sensor can send illumination data.
65 function will be called. So an accelerometer processing driver can register
68 The core driver provides a set of APIs which can be used by the processing
76 the report and get the indexes of the fields and also can get events. This driver
77 can use IIO interface to use the standard ABI defined for a type of sensor.
85 Each processing driver can use this structure to set some callbacks.
89 int (*send_event)(..): One complete event is received which can have
[all …]
|
| /Documentation/core-api/ |
| D | debug-objects.rst | 22 can be compiled in with a minimal runtime impact and enabled on demand
31 the object type. Optional functions can and should be provided to fixup
32 detected problems so the kernel can continue to work and the debug
33 information can be retrieved from a live system instead of hard core
74 whether the object can be initialized. Initializing is not allowed for
77 structure if provided by the caller. The fixup function can correct the
79 can deactivate an active object in order to prevent damage to the
97 whether the object can be initialized. Initializing is not allowed for
100 structure if provided by the caller. The fixup function can correct the
102 can deactivate an active object in order to prevent damage to the
[all …]
|
| D | idr.rst | 27 You can call :c:func:`idr_alloc` to allocate an unused ID. Look up
31 If you need to change the pointer associated with an ID, you can call
42 If you need to allocate IDs sequentially, you can use
46 To perform an action on all pointers used by the IDR, you can
49 :c:func:`idr_for_each_entry_continue` to continue an iteration. You can
52 When you have finished using an IDR, you can call :c:func:`idr_destroy`
57 You can use :c:func:`idr_is_empty` to find out whether there are any
61 you may need to pass a restrictive set of GFP flags, which can lead
63 you can call :c:func:`idr_preload` before taking the lock, and then
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | st,stm32-adc.txt | 4 It has several multiplexed input channels. Conversions can be performed
7 Conversions can be launched in software or using hardware triggers.
12 Each STM32 ADC block can have up to 3 ADC instances.
16 - regular conversion can be done in sequence, running in background
32 - clocks: Core can use up to two clocks, depending on part used:
50 - booster-supply: Phandle to the embedded booster regulator that can be used
52 - vdd-supply: Phandle to the vdd input voltage. It can be used to supply ADC
54 - st,syscfg: Phandle to system configuration controller. It can be used to
73 It can have up to 16 channels on stm32f4 or 20 channels on stm32h7, numbered
76 Depending on part used, some channels can be configured as differential
[all …]
|
12345678910>>...116