/linux/drivers/net/can/ |
H A D | kvaser_pciefd.c | 408 struct can_priv can; member 424 struct kvaser_pciefd_can *can[KVASER_PCIEFD_MAX_CAN_CHANNELS]; member 510 static inline void kvaser_pciefd_send_kcan_cmd(struct kvaser_pciefd_can *can, u32 cmd) in kvaser_pciefd_send_kcan_cmd() argument 513 FIELD_PREP(KVASER_PCIEFD_KCAN_CMD_SEQ_MASK, ++can->cmd_seq), in kvaser_pciefd_send_kcan_cmd() 514 can->reg_base + KVASER_PCIEFD_KCAN_CMD_REG); in kvaser_pciefd_send_kcan_cmd() 517 static inline void kvaser_pciefd_request_status(struct kvaser_pciefd_can *can) in kvaser_pciefd_request_status() argument 519 kvaser_pciefd_send_kcan_cmd(can, KVASER_PCIEFD_KCAN_CMD_SRQ); in kvaser_pciefd_request_status() 522 static inline void kvaser_pciefd_abort_flush_reset(struct kvaser_pciefd_can *can) in kvaser_pciefd_abort_flush_reset() argument 524 kvaser_pciefd_send_kcan_cmd(can, KVASER_PCIEFD_KCAN_CMD_AT); in kvaser_pciefd_abort_flush_reset() 527 static void kvaser_pciefd_enable_err_gen(struct kvaser_pciefd_can *can) in kvaser_pciefd_enable_err_gen() argument [all …]
|
H A D | Kconfig | 14 PF_CAN is contained in <Documentation/networking/can.rst>. 21 can-dev. 31 This driver can also be built as a module. If so, the module 41 versa. The vxcan can be used for cross namespace communication. 49 This driver can also be built as a module. If so, the module 62 can-dev module. 82 can-dev module. 106 This driver can also be built as a module. If so, the module 118 designed to be used as a standalone CAN interface. However, it can 123 Documentation/networking/device_drivers/can/can327.rst [all …]
|
/linux/net/can/ |
H A D | proc.c | 81 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_init_stats() 82 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_init_stats() 117 struct net *net = from_timer(net, t, can.stattimer); in can_stat_update() 118 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stat_update() 176 mod_timer(&net->can.stattimer, round_jiffies(jiffies + HZ)); in can_stat_update() 213 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stats_proc_show() 214 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_stats_proc_show() 223 if (net->can.stattimer.function == can_stat_update) { in can_stats_proc_show() 275 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_reset_stats_proc_show() 276 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_reset_stats_proc_show() [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 …]
|
/linux/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/Documentation/power/regulator/ |
H A 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 …]
|
/linux/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. 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 …]
|
/linux/drivers/net/can/ifi_canfd/ |
H A D | ifi_canfd.c | 220 struct can_priv can; /* must be the first member */ member 237 if (priv->can.ctrlmode & CAN_CTRLMODE_BERR_REPORTING) in ifi_canfd_irq_enable() 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() 489 priv->can.state = CAN_STATE_ERROR_WARNING; in ifi_canfd_handle_state_change() 493 priv->can.can_stats.error_passive++; in ifi_canfd_handle_state_change() 494 priv->can.state = CAN_STATE_ERROR_PASSIVE; in ifi_canfd_handle_state_change() 498 priv->can.state = CAN_STATE_BUS_OFF; in ifi_canfd_handle_state_change() [all …]
|
/linux/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() 398 } else if (priv->can.state != CAN_STATE_ERROR_ACTIVE) { in pucan_handle_status() [all …]
|
/linux/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 36 The Dectalk pc driver can only be built as a module, and 38 the module can be loaded. See the decpc choice below 55 synthesizer. You can say y to build it into the kernel, 64 synthesizer. You can say y to build it into the kernel, 72 synthesizer. You can say y to build it into the kernel, [all …]
|
/linux/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() 152 if (priv->can.ctrlmode & CAN_CTRLMODE_BERR_REPORTING) in set_normal_mode() 161 if (priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY) in set_normal_mode() 163 if (priv->can.ctrlmode & CAN_CTRLMODE_PRESUME_ACK) in set_normal_mode() 210 if (priv->can.state != CAN_STATE_STOPPED) in sja1000_start() 249 struct can_bittiming *bt = &priv->can.bittiming; in sja1000_set_bittiming() 255 if (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) in sja1000_set_bittiming() 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() [all …]
|
/linux/drivers/net/can/usb/ |
H A D | mcba_usb.c | 67 bool can; member 72 struct can_priv can; /* must be the first member */ 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() 471 priv->can.termination = MCBA_TERMINATION_ENABLED; in mcba_usb_process_ka_usb() 473 priv->can.termination = MCBA_TERMINATION_DISABLED; in mcba_usb_process_ka_usb() 501 if (bitrate != priv->can.bittiming.bitrate) in mcba_usb_process_ka_can() 505 bitrate, priv->can.bittiming.bitrate); in mcba_usb_process_ka_can() 512 priv->can.state = CAN_STATE_BUS_OFF; in mcba_usb_process_ka_can() [all …]
|
H A D | ucan.c | 276 struct can_priv can; member 452 up->can.clock.freq = le32_to_cpu(device_info->freq); in ucan_parse_device_info() 466 up->can.ctrlmode_supported = 0; in ucan_parse_device_info() 469 up->can.ctrlmode_supported |= CAN_CTRLMODE_LOOPBACK; in ucan_parse_device_info() 471 up->can.ctrlmode_supported |= CAN_CTRLMODE_LISTENONLY; in ucan_parse_device_info() 473 up->can.ctrlmode_supported |= CAN_CTRLMODE_3_SAMPLES; in ucan_parse_device_info() 475 up->can.ctrlmode_supported |= CAN_CTRLMODE_ONE_SHOT; in ucan_parse_device_info() 477 up->can.ctrlmode_supported |= CAN_CTRLMODE_BERR_REPORTING; in ucan_parse_device_info() 487 enum can_state new_state = up->can.state; in ucan_handle_error_frame() 489 struct can_device_stats *can_stats = &up->can.can_stats; in ucan_handle_error_frame() [all …]
|
H A D | esd_usb.c | 282 struct can_priv can; /* must be the first member */ member 316 if (!(priv->can.ctrlmode & CAN_CTRLMODE_BERR_REPORTING) && in esd_usb_rx_event() 348 if (new_state != priv->can.state) { in esd_usb_rx_event() 355 priv->can.can_stats.bus_error++; in esd_usb_rx_event() 433 can_frame_set_cc_len(cf, msg->rx.dlc & ~ESD_USB_RTR, priv->can.ctrlmode); in esd_usb_rx_can_msg() 755 priv->can.state = CAN_STATE_ERROR_ACTIVE; in esd_usb_start() 862 msg->tx.dlc = can_get_cc_dlc((struct can_frame *)cfd, priv->can.ctrlmode); in esd_usb_start_xmit() 979 priv->can.state = CAN_STATE_STOPPED; in esd_usb_close() 1017 struct can_bittiming *bt = &priv->can.bittiming; in esd_usb_2_set_bittiming() 1024 if (priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY) in esd_usb_2_set_bittiming() [all …]
|
/linux/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 48 chip can be found on Abit uGuru featuring motherboards (most modern 53 This driver can also be built as a module. If so, the module 63 uGuru chip can be found on recent Abit motherboards (since end 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 [all …]
|
/linux/Documentation/devicetree/bindings/net/can/ |
H 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/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 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 …]
|
/linux/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. 42 can store IPv4 address and (source) MAC address pairs from a range. 51 can store TCP/UDP port numbers from a range. 60 can store arbitrary IPv4 or IPv6 addresses (or network addresses) 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 [all …]
|
/linux/drivers/rtc/ |
H A D | Kconfig | 69 one can sleep when setting time, because it runs in the workqueue 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 223 This driver can also be built as a module. If so, the module [all …]
|
/linux/Documentation/gpu/amdgpu/display/ |
H A D | display-contributing.rst | 10 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 …]
|
/linux/Documentation/userspace-api/accelerators/ |
H 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. 98 function can have multiple AFUs. At the time of this writing though, 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 [all …]
|
/linux/fs/nls/ |
H A D | Kconfig | 43 The Microsoft FAT file system family can deal with filenames in 48 only, not to the file contents. You can include several codepages; 55 The Microsoft FAT file system family can deal with filenames in 60 only, not to the file contents. You can include several codepages; 67 The Microsoft FAT file system family can deal with filenames in 72 only, not to the file contents. You can include several codepages; 80 The Microsoft FAT file system family can deal with filenames in 85 only, not to the file contents. You can include several codepages; 96 The Microsoft FAT file system family can deal with filenames in 101 only, not to the file contents. You can include several codepages; [all …]
|
/linux/Documentation/dev-tools/kunit/ |
H A D | running_tips.rst | 13 It can be handy to create a bash function like: 38 We can filter down to just the "write" tests via: 57 regular basis (especially if they have other dependencies), you can create a 67 file ``.kunitconfig``, you can just pass in the dir, e.g. 93 You can use ``--kernel_args`` to pass arbitrary kernel arguments, e.g. 111 Instead of enabling ``CONFIG_GCOV_KERNEL=y``, we can set these options: 131 # E.g. can generate an HTML report in a tmp dir like so: 135 If your installed version of gcc doesn't work, you can tweak the steps: 142 Alternatively, LLVM-based toolchains can also be used: 150 …# The coverage.info file is in lcov-compatible format and it can be used to e.g. generate HTML rep… [all …]
|
/linux/Documentation/core-api/ |
H A D | maple_tree.rst | 17 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 …]
|
/linux/Documentation/hid/ |
H A 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 …]
|