/linux/drivers/net/can/ |
A D | kvaser_pciefd.c | 788 can->echo_idx = (can->echo_idx + 1) % can->can.echo_skb_max; in kvaser_pciefd_start_xmit() 817 can->can.echo_skb[can->echo_idx]) in kvaser_pciefd_start_xmit() 835 bt = &can->can.bittiming; in kvaser_pciefd_set_bittiming() 1010 pcie->can[i] = can; in kvaser_pciefd_setup_can_ctrls() 1329 can = pcie->can[ch_id]; in kvaser_pciefd_handle_error_packet() 1408 can = pcie->can[ch_id]; in kvaser_pciefd_handle_status_packet() 1468 can = pcie->can[ch_id]; in kvaser_pciefd_handle_eack_packet() 1532 can = pcie->can[ch_id]; in kvaser_pciefd_handle_ack_packet() 1574 can = pcie->can[ch_id]; in kvaser_pciefd_handle_eflush_packet() 1776 can = pcie->can[i]; in kvaser_pciefd_teardown_can_ctrls() [all …]
|
A D | Kconfig | 44 slcand) can be found in the can-utils at the linux-can project, see 45 https://github.com/linux-can/can-utils for details. 48 can be changed by the 'maxdev=xx' module option. This driver can 169 This driver can access CAN bus. 171 source "drivers/net/can/c_can/Kconfig" 172 source "drivers/net/can/cc770/Kconfig" 174 source "drivers/net/can/m_can/Kconfig" 175 source "drivers/net/can/mscan/Kconfig" 177 source "drivers/net/can/rcar/Kconfig" 180 source "drivers/net/can/spi/Kconfig" [all …]
|
/linux/Documentation/devicetree/bindings/net/can/ |
A D | renesas,rcar-can.yaml | 4 $id: http://devicetree.org/schemas/net/can/renesas,rcar-can.yaml# 23 - renesas,can-r8a7742 # RZ/G1H 24 - renesas,can-r8a7743 # RZ/G1M 25 - renesas,can-r8a7744 # RZ/G1N 26 - renesas,can-r8a7745 # RZ/G1E 70 renesas,can-clock-select: 100 - $ref: can-controller.yaml# 107 const: renesas,rcar-gen1-can 116 const: renesas,rcar-gen3-can 130 can0: can@e6e80000 { [all …]
|
A D | allwinner,sun4i-a10-can.yaml | 4 $id: http://devicetree.org/schemas/net/can/allwinner,sun4i-a10-can.yaml# 17 - const: allwinner,sun7i-a20-can 18 - const: allwinner,sun4i-a10-can 19 - const: allwinner,sun4i-a10-can 43 can0: can@1c2bc00 { 44 compatible = "allwinner,sun7i-a20-can", 45 "allwinner,sun4i-a10-can";
|
A D | atmel-can.txt | 4 - compatible: Should be "atmel,at91sam9263-can", "atmel,at91sam9x5-can" or 5 "microchip,sam9x60-can" 11 can0: can@f000c000 { 12 compatible = "atmel,at91sam9x5-can";
|
/linux/net/can/ |
A D | proc.c | 318 dev_rcv_lists = net->can.rx_alldev_list; in can_rcvlist_proc_show() 435 if (!net->can.proc_dir) { in can_init_proc() 470 if (!net->can.proc_dir) in can_remove_proc() 473 if (net->can.pde_stats) in can_remove_proc() 476 if (net->can.pde_reset_stats) in can_remove_proc() 479 if (net->can.pde_rcvlist_err) in can_remove_proc() 482 if (net->can.pde_rcvlist_all) in can_remove_proc() 485 if (net->can.pde_rcvlist_fil) in can_remove_proc() 488 if (net->can.pde_rcvlist_inv) in can_remove_proc() 491 if (net->can.pde_rcvlist_eff) in can_remove_proc() [all …]
|
A D | Makefile | 6 obj-$(CONFIG_CAN) += can.o 7 can-y := af_can.o 8 can-$(CONFIG_PROC_FS) += proc.o 10 obj-$(CONFIG_CAN_RAW) += can-raw.o 11 can-raw-y := raw.o 13 obj-$(CONFIG_CAN_BCM) += can-bcm.o 14 can-bcm-y := bcm.o 16 obj-$(CONFIG_CAN_GW) += can-gw.o 17 can-gw-y := gw.o 21 obj-$(CONFIG_CAN_ISOTP) += can-isotp.o [all …]
|
A D | af_can.c | 310 return net->can.rx_alldev_list; in can_dev_rcv_lists_find() 796 net->can.rx_alldev_list = in can_pernet_init() 798 if (!net->can.rx_alldev_list) in can_pernet_init() 800 net->can.pkg_stats = kzalloc(sizeof(*net->can.pkg_stats), GFP_KERNEL); in can_pernet_init() 801 if (!net->can.pkg_stats) in can_pernet_init() 803 net->can.rcv_lists_stats = kzalloc(sizeof(*net->can.rcv_lists_stats), GFP_KERNEL); in can_pernet_init() 804 if (!net->can.rcv_lists_stats) in can_pernet_init() 822 kfree(net->can.pkg_stats); in can_pernet_init() 824 kfree(net->can.rx_alldev_list); in can_pernet_init() 837 kfree(net->can.rx_alldev_list); in can_pernet_exit() [all …]
|
/linux/drivers/net/can/dev/ |
A D | Makefile | 3 obj-$(CONFIG_CAN_DEV) += can-dev.o 4 can-dev-y += bittiming.o 5 can-dev-y += dev.o 6 can-dev-y += length.o 7 can-dev-y += netlink.o 8 can-dev-y += rx-offload.o 9 can-dev-y += skb.o 11 can-dev-$(CONFIG_CAN_LEDS) += led.o
|
/linux/drivers/hwmon/pmbus/ |
A D | Kconfig | 12 This driver can also be built as a module. If so, the module will 27 This driver can also be built as a module. If so, the module will 38 This driver can also be built as a module. If so, the module will 48 This driver can also be built as a module. If so, the module will 57 This driver can also be built as a module. If so, the module will 66 This driver can also be built as a module. If so, the module will 76 This driver can also be built as a module. If so, the module will 86 This driver can also be built as a module. If so, the module will 95 This driver can also be built as a module. If so, the module will 104 This driver can also be built as a module. If so, the module will [all …]
|
/linux/drivers/net/can/ifi_canfd/ |
A D | ifi_canfd.c | 395 priv->can.can_stats.bus_error++; in ifi_canfd_handle_lec_err() 467 priv->can.can_stats.error_warning++; in ifi_canfd_handle_state_change() 468 priv->can.state = CAN_STATE_ERROR_ACTIVE; in ifi_canfd_handle_state_change() 472 priv->can.can_stats.error_warning++; in ifi_canfd_handle_state_change() 477 priv->can.can_stats.error_passive++; in ifi_canfd_handle_state_change() 482 priv->can.state = CAN_STATE_BUS_OFF; in ifi_canfd_handle_state_change() 484 priv->can.can_stats.bus_off++; in ifi_canfd_handle_state_change() 767 priv->can.state = CAN_STATE_ERROR_ACTIVE; in ifi_canfd_start() 800 priv->can.state = CAN_STATE_STOPPED; in ifi_canfd_stop() 984 priv->can.state = CAN_STATE_STOPPED; in ifi_canfd_plat_probe() [all …]
|
/linux/Documentation/power/regulator/ |
A D | consumer.rst | 12 A consumer driver can get access to its supply regulator by calling :: 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:: 80 Consumers can control their supply voltage by calling:: 92 The regulators configured voltage output can be found by calling:: 111 Consumers can control their supply current limit by calling:: 124 A regulators current limit can be found by calling:: 141 Regulator operating mode can be changed indirectly or directly. 182 Consumers can register interest in regulator events by calling:: [all …]
|
/linux/drivers/net/can/peak_canfd/ |
A D | peak_canfd.c | 99 priv->can.state = CAN_STATE_ERROR_ACTIVE; in pucan_set_normal_mode() 111 priv->can.state = CAN_STATE_ERROR_ACTIVE; in pucan_set_listen_only_mode() 124 priv->can.ctrlmode & in pucan_set_timing_slow() 365 priv->can.state = CAN_STATE_BUS_OFF; in pucan_handle_status() 366 priv->can.can_stats.bus_off++; in pucan_handle_status() 373 priv->can.state = CAN_STATE_ERROR_PASSIVE; in pucan_handle_status() 374 priv->can.can_stats.error_passive++; in pucan_handle_status() 386 priv->can.state = CAN_STATE_ERROR_WARNING; in pucan_handle_status() 387 priv->can.can_stats.error_warning++; in pucan_handle_status() 731 if (priv->can.ctrlmode & CAN_CTRLMODE_FD) in peak_canfd_start_xmit() [all …]
|
/linux/Documentation/devicetree/bindings/sound/ |
A D | renesas,rsnd.txt | 27 Multi-SSI : 6ch case, you can use stereo x 3 SSI 28 TDM-SSI : 6ch case, you can use TDM 44 You can use below. 45 ${LINUX}/arch/arm/boot/dts/r8a7790.dts can be good example. 68 you can use this mode on Playback / Capture 72 you can use this mode on Playback 185 But you can't use it if SSI was PIO mode. 226 You can use DMA without SSIU. 235 Each SSI can share WS pin. It is based on platform. 244 You can use Multi-SSI. [all …]
|
/linux/drivers/hwmon/ |
A D | Kconfig | 13 can include temperature sensors, voltage sensors, fan speed 23 This support can also be built as a module. If so, the module 53 This driver can also be built as a module. If so, the module 67 This driver can also be built as a module. If so, the module 77 This driver can also be built as a module. If so, the module 87 This driver can also be built as a module. If so, the module 97 This driver can also be built as a module. If so, the module 108 This driver can also be built as a module. If so, the module 119 This driver can also be built as a module. If so, the module 130 This driver can also be built as a module. If so, the module [all …]
|
/linux/drivers/accessibility/speakup/ |
A D | Kconfig | 10 kernel, it can speak everything on the text console from 14 can subscribe to. 22 that can be used with a plain text terminal. 24 Speakup can either be built in or compiled as a module 28 the synthesizer drivers below can only be built as 38 the module can be loaded. See the decpc choice below 79 You can say y to build it into the kernel, or m to 139 PC synthesizer. You can say y to build it into the 150 PC synthesizer. You can say y to build it into the 160 LT synthesizer. You can say y to build it into the [all …]
|
/linux/drivers/net/can/sja1000/ |
A D | sja1000.c | 127 priv->can.state = CAN_STATE_STOPPED; in set_reset_mode() 150 priv->can.state = CAN_STATE_ERROR_ACTIVE; in set_normal_mode() 209 if (priv->can.state != CAN_STATE_STOPPED) in sja1000_start() 297 fi = can_get_cc_dlc(cf, priv->can.ctrlmode); in sja1000_start_xmit() 323 if (priv->can.ctrlmode & CAN_CTRLMODE_ONE_SHOT) in sja1000_start_xmit() 326 if (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK) in sja1000_start_xmit() 395 enum can_state state = priv->can.state; in sja1000_err() 433 priv->can.can_stats.bus_error++; in sja1000_err() 475 priv->can.can_stats.arbitration_lost++; in sja1000_err() 480 if (state != priv->can.state) { in sja1000_err() [all …]
|
/linux/drivers/net/can/usb/ |
A D | mcba_usb.c | 68 bool can; member 188 ctx->can = true; in mcba_usb_get_free_ctx() 191 ctx->can = false; in mcba_usb_get_free_ctx() 234 if (ctx->can) { in mcba_usb_write_bulk_callback() 519 priv->can.state = CAN_STATE_BUS_OFF; in mcba_usb_process_ka_can() 523 priv->can.state = CAN_STATE_ERROR_PASSIVE; in mcba_usb_process_ka_can() 709 priv->can.state = CAN_STATE_ERROR_ACTIVE; in mcba_usb_open() 735 priv->can.state = CAN_STATE_STOPPED; in mcba_usb_close() 834 priv->can.state = CAN_STATE_STOPPED; in mcba_usb_probe() 837 priv->can.bitrate_const = mcba_bitrate; in mcba_usb_probe() [all …]
|
/linux/Documentation/ABI/testing/ |
A D | sysfs-class-firmware-attributes | 28 A file that can be read to obtain the current 37 A file that can be read to obtain the default 45 A file that can be read to obtain 52 A file that can be read to obtain the possible 59 A file that can be read to obtain the lower 63 A file that can be read to obtain the upper 73 A file that can be read to obtain the maximum 77 A file that can be read to obtain the minimum 90 modifier rules can be in following format:: 170 A file that can be read to obtain the [all …]
|
/linux/drivers/rtc/ |
A D | Kconfig | 129 can be accessed as /dev/rtc, which is a name 151 RTC test driver. It's a software RTC which can be 158 This driver can also be built as a module. If so, the module 172 This driver can also be built as a module. If so, the module 182 This driver can also be built as a module. If so, the module 192 This driver can also be built as a module. If so, the module 202 This driver can also be built as a module. If so, the module 213 This driver can also be built as a module. If so, the module 1357 LS1088A, LS208xA, we can use FTM as the wakeup source. 1397 This driver can also be built as a module, if so, module [all …]
|
/linux/Documentation/bpf/ |
A D | bpf_lsm.rst | 15 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 114 and the program can be loaded by including ``my_prog.skel.h`` and using 127 One can also use the helpers generated in ``my_prog.skel.h`` i.e. [all …]
|
/linux/net/netfilter/ipset/ |
A D | Kconfig | 9 ipset(8). You can use the sets in netfilter via the "set" match 22 You can define here default value of the maximum number 25 The value can be overridden by the 'max_sets' module 33 can store IPv4 addresses (or network addresse) from a range. 51 can store TCP/UDP port numbers from a range. 70 can store IPv4/IPv6 address and mark pairs. 79 can store IPv4/IPv6 address and protocol/port pairs. 88 one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6 117 one can store MAC (ethernet address) elements in a set. 153 one can store IPv4/IPv6 network address/prefix and [all …]
|
/linux/drivers/block/paride/ |
A D | Transition-notes | 2 If ps_tq is scheduled, ps_tq_active is 1. ps_tq_int() can be called 5 under ps_spinlock. There are three places where that can happen: 7 Consider the sequnce of these events. A can not be preceded by 9 ps_spinlock. C is always preceded by B, since we can't reach it 11 IOW, the sequence is A?(BA|BC|B)*. OTOH, number of B can not exceed 16 since at any time number of B can not exceed the number of these 17 moments which, in turn, can not exceed the number of A and C. 68 d) ps_tq_int() can enter the area only when the thread is holding 77 f) pi_wake_up() can enter the area only when the thread is holding 125 We can remove the check for ps_continuation being NULL for the same [all …]
|
/linux/fs/nls/ |
A D | Kconfig | 43 The Microsoft FAT file system family can deal with filenames in 55 The Microsoft FAT file system family can deal with filenames in 67 The Microsoft FAT file system family can deal with filenames in 80 The Microsoft FAT file system family can deal with filenames in 459 The Apple HFS file system family can deal with filenames in 474 The Apple HFS file system family can deal with filenames in 488 The Apple HFS file system family can deal with filenames in 502 The Apple HFS file system family can deal with filenames in 516 The Apple HFS file system family can deal with filenames in 530 The Apple HFS file system family can deal with filenames in [all …]
|
/linux/Documentation/userspace-api/accelerators/ |
A D | ocxl.rst | 11 device can also host its own memory, that can be accessed from the 25 implementing the DL and TL can start sharing memory. 55 device. So the host can discover AFUs by querying the config space. 61 enumeration. Commands like 'lspci' can therefore be used to see what 64 The configuration space defines the AFU(s) that can be found on the 65 physical adapter, such as its name, how many memory contexts it can 89 64-bit object handle, that can be passed to the AFU. 101 Char devices can be found in /dev/ocxl/ and are named as: 106 <location> is added by the driver and can help distinguish devices 140 the AFU can access its memory. [all …]
|