/Linux-v5.4/drivers/net/can/ |
D | kvaser_pciefd.c | 253 struct can_priv can; member 269 struct kvaser_pciefd_can *can[KVASER_PCIEFD_MAX_CAN_CHANNELS]; member 484 static void kvaser_pciefd_request_status(struct kvaser_pciefd_can *can) in kvaser_pciefd_request_status() argument 489 cmd |= ++can->cmd_seq << KVASER_PCIEFD_KCAN_CMD_SEQ_SHIFT; in kvaser_pciefd_request_status() 490 iowrite32(cmd, can->reg_base + KVASER_PCIEFD_KCAN_CMD_REG); in kvaser_pciefd_request_status() 493 static void kvaser_pciefd_enable_err_gen(struct kvaser_pciefd_can *can) in kvaser_pciefd_enable_err_gen() argument 498 spin_lock_irqsave(&can->lock, irq); in kvaser_pciefd_enable_err_gen() 499 mode = ioread32(can->reg_base + KVASER_PCIEFD_KCAN_MODE_REG); in kvaser_pciefd_enable_err_gen() 502 iowrite32(mode, can->reg_base + KVASER_PCIEFD_KCAN_MODE_REG); in kvaser_pciefd_enable_err_gen() 504 spin_unlock_irqrestore(&can->lock, irq); in kvaser_pciefd_enable_err_gen() [all …]
|
D | Kconfig | 10 This driver can also be built as a module. If so, the module 20 versa. The vxcan can be used for cross namespace communication. 28 This driver can also be built as a module. If so, the module 44 slcand) can be found in the can-utils at the SocketCAN SVN, see 48 can be changed by the 'maxdev=xx' module option. This driver can 120 This driver can also be built as a module. If so, the module will be 167 This driver can access CAN bus. 169 source "drivers/net/can/c_can/Kconfig" 170 source "drivers/net/can/cc770/Kconfig" 171 source "drivers/net/can/ifi_canfd/Kconfig" [all …]
|
/Linux-v5.4/net/can/ |
D | proc.c | 82 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_init_stats() 83 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_init_stats() 122 struct net *net = from_timer(net, t, can.stattimer); in can_stat_update() 123 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stat_update() 181 mod_timer(&net->can.stattimer, round_jiffies(jiffies + HZ)); in can_stat_update() 216 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stats_proc_show() 217 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_stats_proc_show() 226 if (net->can.stattimer.function == can_stat_update) { in can_stats_proc_show() 278 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_reset_stats_proc_show() 279 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_reset_stats_proc_show() [all …]
|
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
|
D | af_can.c | 203 struct can_pkg_stats *pkg_stats = dev_net(skb->dev)->can.pkg_stats; in can_send() 310 return net->can.rx_alldev_list; in can_dev_rcv_lists_find() 448 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_rx_register() 463 spin_lock_bh(&net->can.rcvlists_lock); in can_rx_register() 482 spin_unlock_bh(&net->can.rcvlists_lock); in can_rx_register() 516 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_rx_unregister() 525 spin_lock_bh(&net->can.rcvlists_lock); in can_rx_unregister() 556 spin_unlock_bh(&net->can.rcvlists_lock); in can_rx_unregister() 642 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_receive() 656 matches = can_rcv_filter(net->can.rx_alldev_list, skb); in can_receive() [all …]
|
/Linux-v5.4/Documentation/devicetree/bindings/net/can/ |
D | rcar_can.txt | 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. 14 "renesas,can-r8a7791" if CAN controller is a part of R8A7791 SoC. [all …]
|
D | sun4i_can.txt | 5 - compatible: "allwinner,sun4i-a10-can" 17 allwinner,function = "can"; 22 can0: can@1c2bc00 { 23 compatible = "allwinner,sun4i-a10-can"; 32 can0: can@1c2bc00 {
|
D | atmel-can.txt | 4 - compatible: Should be "atmel,at91sam9263-can" or "atmel,at91sam9x5-can" 10 can0: can@f000c000 { 11 compatible = "atmel,at91sam9x5-can";
|
/Linux-v5.4/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 …]
|
/Linux-v5.4/drivers/net/can/ifi_canfd/ |
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() 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() 473 priv->can.state = CAN_STATE_ERROR_WARNING; in ifi_canfd_handle_state_change() 477 priv->can.can_stats.error_passive++; in ifi_canfd_handle_state_change() 478 priv->can.state = CAN_STATE_ERROR_PASSIVE; in ifi_canfd_handle_state_change() 482 priv->can.state = CAN_STATE_BUS_OFF; in ifi_canfd_handle_state_change() [all …]
|
/Linux-v5.4/drivers/net/can/peak_canfd/ |
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 & CAN_CTRLMODE_3_SAMPLES); in pucan_set_timing_slow() 347 priv->can.state = CAN_STATE_BUS_OFF; in pucan_handle_status() 348 priv->can.can_stats.bus_off++; in pucan_handle_status() 355 priv->can.state = CAN_STATE_ERROR_PASSIVE; in pucan_handle_status() 356 priv->can.can_stats.error_passive++; in pucan_handle_status() 368 priv->can.state = CAN_STATE_ERROR_WARNING; in pucan_handle_status() 369 priv->can.can_stats.error_warning++; in pucan_handle_status() 379 } else if (priv->can.state != CAN_STATE_ERROR_ACTIVE) { in pucan_handle_status() [all …]
|
/Linux-v5.4/drivers/hwmon/pmbus/ |
D | Kconfig | 12 This driver can also be built as a module. If so, the module will 26 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 46 This driver can also be built as a module. If so, the module will 55 This driver can also be built as a module. If so, the module will 64 This driver can also be built as a module. If so, the module will 73 This driver can also be built as a module. If so, the module will 82 This driver can also be built as a module. If so, the module will 91 This driver can also be built as a module. If so, the module will 100 This driver can also be built as a module. If so, the module will [all …]
|
/Linux-v5.4/drivers/hwmon/ |
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 50 This driver can also be built as a module. If so, the module 60 chip can be found on Abit uGuru featuring motherboards (most modern 65 This driver can also be built as a module. If so, the module 75 uGuru chip can be found on recent Abit motherboards (since end 79 This driver can also be built as a module. If so, the module 89 This driver can also be built as a module. If so, the module 99 This driver can also be built as a module. If so, the module 109 This driver can also be built as a module. If so, the module [all …]
|
/Linux-v5.4/drivers/staging/speakup/ |
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 49 synthesizer. You can say y to build it into the kernel, 58 synthesizer. You can say y to build it into the kernel, 66 synthesizer. You can say y to build it into the kernel, [all …]
|
/Linux-v5.4/drivers/net/can/usb/ |
D | mcba_usb.c | 68 bool can; member 73 struct can_priv can; /* must be the first member */ member 186 ctx->can = true; in mcba_usb_get_free_ctx() 189 ctx->can = false; in mcba_usb_get_free_ctx() 232 if (ctx->can) { in mcba_usb_write_bulk_callback() 476 priv->can.termination = MCBA_TERMINATION_ENABLED; in mcba_usb_process_ka_usb() 478 priv->can.termination = MCBA_TERMINATION_DISABLED; in mcba_usb_process_ka_usb() 506 if (bitrate != priv->can.bittiming.bitrate) in mcba_usb_process_ka_can() 510 bitrate, priv->can.bittiming.bitrate); in mcba_usb_process_ka_can() 517 priv->can.state = CAN_STATE_BUS_OFF; in mcba_usb_process_ka_can() [all …]
|
/Linux-v5.4/net/netfilter/ipset/ |
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. 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-v5.4/drivers/block/paride/ |
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. 49 1) at any time at most one thread of execution can be in that area or 60 (1) can become not true if some thread enters that area while another is there. 61 a) do_pd_request1() can be called from next_request() or do_pd_request() [all …]
|
/Linux-v5.4/Documentation/devicetree/bindings/display/exynos/ |
D | exynos_dp.txt | 47 -video interfaces: Device node can contain video interface port 60 -interlaced: deprecated prop that can parsed from drm_display_mode. 61 -vsync-active-high: deprecated prop that can parsed from drm_display_mode. 62 -hsync-active-high: deprecated prop that can parsed from drm_display_mode. 63 -samsung,ycbcr-coeff: deprecated prop that can parsed from drm_display_mode. 64 -samsung,dynamic-range: deprecated prop that can parsed from drm_display_mode. 65 -samsung,color-space: deprecated prop that can parsed from drm_display_info. 66 -samsung,color-depth: deprecated prop that can parsed from drm_display_info. 67 -samsung,link-rate: deprecated prop that can reading from monitor by dpcd method. 68 -samsung,lane-count: deprecated prop that can reading from monitor by dpcd method.
|
/Linux-v5.4/Documentation/devicetree/bindings/usb/ |
D | atmel-usb.txt | 102 - atmel,can-dma: Boolean to specify if the endpoint support DMA. 103 - atmel,can-isoc: Boolean to specify if the endpoint support ISOC. 126 atmel,can-dma; 127 atmel,can-isoc; 134 atmel,can-dma; 135 atmel,can-isoc; 142 atmel,can-dma; 149 atmel,can-dma; 156 atmel,can-dma; 157 atmel,can-isoc; [all …]
|
/Linux-v5.4/Documentation/userspace-api/accelerators/ |
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-v5.4/drivers/net/can/sja1000/ |
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() 209 if (priv->can.state != CAN_STATE_STOPPED) in sja1000_start() 247 struct can_bittiming *bt = &priv->can.bittiming; in sja1000_set_bittiming() 253 if (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) in sja1000_set_bittiming() 324 if (priv->can.ctrlmode & CAN_CTRLMODE_ONE_SHOT) in sja1000_start_xmit() 327 if (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK) in sja1000_start_xmit() [all …]
|
/Linux-v5.4/drivers/rtc/ |
D | Kconfig | 72 one can sleep when setting time, because it runs in the workqueue 123 can be accessed as /dev/rtc, which is a name 145 RTC test driver. It's a software RTC which can be 152 This driver can also be built as a module. If so, the module 166 This driver can also be built as a module. If so, the module 176 This driver can also be built as a module. If so, the module 186 This driver can also be built as a module. If so, the module 196 This driver can also be built as a module. If so, the module 207 This driver can also be built as a module. If so, the module 217 This driver can also be built as a module. If so, the module [all …]
|
/Linux-v5.4/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
|
/Linux-v5.4/fs/nls/ |
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-v5.4/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 …]
|