| /linux-6.15/drivers/net/can/ |
| H A D | kvaser_pciefd.c | 868 bt = &can->can.bittiming; in kvaser_pciefd_set_bittiming() 917 if (!can->can.restart_ms) in kvaser_pciefd_set_mode() 1032 pcie->can[i] = can; in kvaser_pciefd_setup_can_ctrls() 1256 old_state = can->can.state; in kvaser_pciefd_change_state() 1274 can->can.restart_ms) { in kvaser_pciefd_change_state() 1321 old_state = can->can.state; in kvaser_pciefd_rx_error_frame() 1368 can = pcie->can[ch_id]; in kvaser_pciefd_handle_error_packet() 1428 can = pcie->can[ch_id]; in kvaser_pciefd_handle_status_packet() 1509 can = pcie->can[ch_id]; in kvaser_pciefd_handle_ack_packet() 1557 can = pcie->can[ch_id]; in kvaser_pciefd_handle_eflush_packet() [all …]
|
| H A D | Kconfig | 21 can-dev. 62 can-dev module. 82 can-dev module. 187 slcand) can be found in the can-utils at the linux-can project, see 188 https://github.com/linux-can/can-utils for details. 219 source "drivers/net/can/c_can/Kconfig" 220 source "drivers/net/can/cc770/Kconfig" 222 source "drivers/net/can/esd/Kconfig" 227 source "drivers/net/can/rcar/Kconfig" 231 source "drivers/net/can/spi/Kconfig" [all …]
|
| /linux-6.15/Documentation/devicetree/bindings/net/can/ |
| H 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 …]
|
| H A D | allwinner,sun4i-a10-can.yaml | 4 $id: http://devicetree.org/schemas/net/can/allwinner,sun4i-a10-can.yaml# 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 62 can0: can@1c2bc00 { [all …]
|
| H A D | microchip,mpfs-can.yaml | 4 $id: http://devicetree.org/schemas/net/can/microchip,mpfs-can.yaml# 8 Microchip PolarFire SoC (MPFS) can controller 14 - $ref: can-controller.yaml# 20 - const: microchip,pic64gx-can 21 - const: microchip,mpfs-can 22 - const: microchip,mpfs-can 45 can@2010c000 { 46 compatible = "microchip,mpfs-can";
|
| H A D | atmel,at91sam9263-can.yaml | 4 $id: http://devicetree.org/schemas/net/can/atmel,at91sam9263-can.yaml# 13 - $ref: can-controller.yaml# 19 - atmel,at91sam9263-can 20 - atmel,at91sam9x5-can 23 - microchip,sam9x60-can 24 - const: atmel,at91sam9x5-can 52 can@f000c000 { 53 compatible = "atmel,at91sam9263-can";
|
| H A D | xilinx,can.yaml | 4 $id: http://devicetree.org/schemas/net/can/xilinx,can.yaml# 16 - xlnx,zynq-can-1.0 17 - xlnx,axi-can-1.00.a 66 - $ref: can-controller.yaml# 72 - xlnx,zynq-can-1.0 89 - xlnx,axi-can-1.00.a 123 can@e0008000 { 124 compatible = "xlnx,zynq-can-1.0"; 135 can@40000000 { 148 can@40000000 { [all …]
|
| /linux-6.15/net/can/ |
| H A D | proc.c | 326 dev_rcv_lists = net->can.rx_alldev_list; in can_rcvlist_proc_show() 443 if (!net->can.proc_dir) { in can_init_proc() 478 if (!net->can.proc_dir) in can_remove_proc() 481 if (net->can.pde_stats) in can_remove_proc() 484 if (net->can.pde_reset_stats) in can_remove_proc() 487 if (net->can.pde_rcvlist_err) in can_remove_proc() 490 if (net->can.pde_rcvlist_all) in can_remove_proc() 493 if (net->can.pde_rcvlist_fil) in can_remove_proc() 496 if (net->can.pde_rcvlist_inv) in can_remove_proc() 499 if (net->can.pde_rcvlist_eff) in can_remove_proc() [all …]
|
| H 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 …]
|
| H A D | af_can.c | 312 return net->can.rx_alldev_list; in can_dev_rcv_lists_find() 790 net->can.rx_alldev_list = in can_pernet_init() 792 if (!net->can.rx_alldev_list) in can_pernet_init() 794 net->can.pkg_stats = kzalloc(sizeof(*net->can.pkg_stats), GFP_KERNEL); in can_pernet_init() 795 if (!net->can.pkg_stats) in can_pernet_init() 797 net->can.rcv_lists_stats = kzalloc(sizeof(*net->can.rcv_lists_stats), GFP_KERNEL); in can_pernet_init() 798 if (!net->can.rcv_lists_stats) in can_pernet_init() 816 kfree(net->can.pkg_stats); in can_pernet_init() 818 kfree(net->can.rx_alldev_list); in can_pernet_init() 831 kfree(net->can.rx_alldev_list); in can_pernet_exit() [all …]
|
| /linux-6.15/drivers/net/can/dev/ |
| H A D | Makefile | 3 obj-$(CONFIG_CAN_DEV) += can-dev.o 5 can-dev-y += skb.o 7 can-dev-$(CONFIG_CAN_CALC_BITTIMING) += calc_bittiming.o 8 can-dev-$(CONFIG_CAN_NETLINK) += bittiming.o 9 can-dev-$(CONFIG_CAN_NETLINK) += dev.o 10 can-dev-$(CONFIG_CAN_NETLINK) += length.o 11 can-dev-$(CONFIG_CAN_NETLINK) += netlink.o 12 can-dev-$(CONFIG_CAN_RX_OFFLOAD) += rx-offload.o
|
| /linux-6.15/Documentation/sound/cards/ |
| H A D | pcmtest.rst | 6 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. 73 negative - faster. You can try it yourself by starting a recording in any 87 For example, you can make all 'hw_params' PCM callback calls return EBUSY error by [all …]
|
| /linux-6.15/Documentation/power/regulator/ |
| H 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-6.15/drivers/net/can/ifi_canfd/ |
| H A D | ifi_canfd.c | 392 priv->can.can_stats.bus_error++; in ifi_canfd_handle_lec_err() 483 priv->can.can_stats.error_warning++; in ifi_canfd_handle_state_change() 484 priv->can.state = CAN_STATE_ERROR_ACTIVE; in ifi_canfd_handle_state_change() 488 priv->can.can_stats.error_warning++; in ifi_canfd_handle_state_change() 493 priv->can.can_stats.error_passive++; in ifi_canfd_handle_state_change() 498 priv->can.state = CAN_STATE_BUS_OFF; in ifi_canfd_handle_state_change() 500 priv->can.can_stats.bus_off++; in ifi_canfd_handle_state_change() 780 priv->can.state = CAN_STATE_ERROR_ACTIVE; in ifi_canfd_start() 813 priv->can.state = CAN_STATE_STOPPED; in ifi_canfd_stop() 999 priv->can.state = CAN_STATE_STOPPED; in ifi_canfd_plat_probe() [all …]
|
| /linux-6.15/drivers/hwmon/pmbus/ |
| H 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 36 This driver can also be built as a module. If so, the module will 47 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 67 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 85 This driver can also be built as a module. If so, the module will 94 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 [all …]
|
| /linux-6.15/drivers/net/can/peak_canfd/ |
| H A D | peak_canfd.c | 100 priv->can.state = CAN_STATE_ERROR_ACTIVE; in pucan_set_normal_mode() 112 priv->can.state = CAN_STATE_ERROR_ACTIVE; in pucan_set_listen_only_mode() 125 priv->can.ctrlmode & in pucan_set_timing_slow() 366 priv->can.state = CAN_STATE_BUS_OFF; in pucan_handle_status() 367 priv->can.can_stats.bus_off++; in pucan_handle_status() 374 priv->can.state = CAN_STATE_ERROR_PASSIVE; in pucan_handle_status() 375 priv->can.can_stats.error_passive++; in pucan_handle_status() 387 priv->can.state = CAN_STATE_ERROR_WARNING; in pucan_handle_status() 388 priv->can.can_stats.error_warning++; in pucan_handle_status() 728 if (priv->can.ctrlmode & CAN_CTRLMODE_FD) in peak_canfd_start_xmit() [all …]
|
| /linux-6.15/Documentation/devicetree/bindings/sound/ |
| H 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-6.15/drivers/accessibility/speakup/ |
| H 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 80 You can say y to build it into the kernel, or m to 140 PC synthesizer. You can say y to build it into the 151 PC synthesizer. You can say y to build it into the 161 LT synthesizer. You can say y to build it into the [all …]
|
| /linux-6.15/drivers/net/can/sja1000/ |
| H 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() 210 if (priv->can.state != CAN_STATE_STOPPED) in sja1000_start() 299 fi = can_get_cc_dlc(cf, priv->can.ctrlmode); in sja1000_start_xmit() 325 if (priv->can.ctrlmode & CAN_CTRLMODE_ONE_SHOT) in sja1000_start_xmit() 328 if (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK) in sja1000_start_xmit() 412 enum can_state state = priv->can.state; in sja1000_err() 463 priv->can.can_stats.bus_error++; in sja1000_err() 510 priv->can.can_stats.arbitration_lost++; in sja1000_err() 517 if (state != priv->can.state) { in sja1000_err() [all …]
|
| /linux-6.15/drivers/net/can/usb/ |
| H A D | mcba_usb.c | 67 bool can; member 189 ctx->can = true; in mcba_usb_get_free_ctx() 191 ctx->can = false; in mcba_usb_get_free_ctx() 232 if (ctx->can) { in mcba_usb_write_bulk_callback() 512 priv->can.state = CAN_STATE_BUS_OFF; in mcba_usb_process_ka_can() 516 priv->can.state = CAN_STATE_ERROR_PASSIVE; in mcba_usb_process_ka_can() 702 priv->can.state = CAN_STATE_ERROR_ACTIVE; in mcba_usb_open() 727 priv->can.state = CAN_STATE_STOPPED; in mcba_usb_close() 836 priv->can.state = CAN_STATE_STOPPED; in mcba_usb_probe() 839 priv->can.bitrate_const = mcba_bitrate; in mcba_usb_probe() [all …]
|
| /linux-6.15/Documentation/bpf/ |
| H A D | prog_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-6.15/drivers/hwmon/ |
| H 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 85 This driver can also be built as a module. If so, the module 95 This driver can also be built as a module. If so, the module 105 This driver can also be built as a module. If so, the module 116 This driver can also be built as a module. If so, the module 127 This driver can also be built as a module. If so, the module 1994 Threshold values can be configured using sysfs. [all …]
|
| /linux-6.15/net/netfilter/ipset/ |
| H 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 addresses) 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-6.15/drivers/rtc/ |
| H 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 212 This driver can also be built as a module. If so, the module 1416 LS1088A, LS208xA, we can use FTM as the wakeup source. 1456 This driver can also be built as a module, if so, module [all …]
|
| /linux-6.15/Documentation/userspace-api/accelerators/ |
| H A D | ocxl.rst | 14 device can also host its own memory, that can be accessed from the 28 implementing the DL and TL can start sharing memory. 58 device. So the host can discover AFUs by querying the config space. 64 enumeration. Commands like 'lspci' can therefore be used to see what 67 The configuration space defines the AFU(s) that can be found on the 68 physical adapter, such as its name, how many memory contexts it can 92 64-bit object handle, that can be passed to the AFU. 104 Char devices can be found in /dev/ocxl/ and are named as: 109 <location> is added by the driver and can help distinguish devices 143 the AFU can access its memory. [all …]
|