/Linux-v4.19/net/can/ |
D | proc.c | 80 struct s_stats *can_stats = net->can.can_stats; in can_init_stats() 81 struct s_pstats *can_pstats = net->can.can_pstats; in can_init_stats() 120 struct net *net = from_timer(net, t, can.can_stattimer); in can_stat_update() 121 struct s_stats *can_stats = net->can.can_stats; in can_stat_update() 179 mod_timer(&net->can.can_stattimer, round_jiffies(jiffies + HZ)); in can_stat_update() 214 struct s_stats *can_stats = net->can.can_stats; in can_stats_proc_show() 215 struct s_pstats *can_pstats = net->can.can_pstats; in can_stats_proc_show() 224 if (net->can.can_stattimer.function == can_stat_update) { in can_stats_proc_show() 276 struct s_pstats *can_pstats = net->can.can_pstats; in can_reset_stats_proc_show() 277 struct s_stats *can_stats = net->can.can_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 | 220 struct s_stats *can_stats = dev_net(skb->dev)->can.can_stats; in can_send() 328 return net->can.can_rx_alldev_list; in find_dev_rcv_lists() 468 struct s_pstats *can_pstats = net->can.can_pstats; in can_rx_register() 483 spin_lock(&net->can.can_rcvlists_lock); in can_rx_register() 508 spin_unlock(&net->can.can_rcvlists_lock); in can_rx_register() 544 struct s_pstats *can_pstats = net->can.can_pstats; in can_rx_unregister() 553 spin_lock(&net->can.can_rcvlists_lock); in can_rx_unregister() 601 spin_unlock(&net->can.can_rcvlists_lock); in can_rx_unregister() 687 struct s_stats *can_stats = net->can.can_stats; in can_receive() 701 matches = can_rcv_filter(net->can.can_rx_alldev_list, skb); in can_receive() [all …]
|
/Linux-v4.19/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-r8a7745" if CAN controller is a part of R8A7745 SoC. 7 "renesas,can-r8a7778" if CAN controller is a part of R8A7778 SoC. 8 "renesas,can-r8a7779" if CAN controller is a part of R8A7779 SoC. 9 "renesas,can-r8a7790" if CAN controller is a part of R8A7790 SoC. 10 "renesas,can-r8a7791" if CAN controller is a part of R8A7791 SoC. 11 "renesas,can-r8a7792" if CAN controller is a part of R8A7792 SoC. 12 "renesas,can-r8a7793" if CAN controller is a part of R8A7793 SoC. 13 "renesas,can-r8a7794" if CAN controller is a part of R8A7794 SoC. 14 "renesas,can-r8a7795" if CAN controller is a part of R8A7795 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-v4.19/Documentation/power/regulator/ |
D | consumer.txt | 11 A consumer driver can get access to its supply regulator by calling :- 24 Consumers can be supplied by more than one regulator e.g. codec consumer with 37 A consumer can enable its power supply by calling:- 45 A consumer can determine if a regulator is enabled by calling :- 52 A consumer can disable its supply when no longer needed by calling :- 59 Finally, a regulator can be forcefully disabled in the case of an emergency :- 71 voltage to match system operating points. e.g. CPUfreq drivers can scale 75 Consumers can control their supply voltage by calling :- 82 NOTE: this can be called when the regulator is enabled or disabled. If called 87 The regulators configured voltage output can be found by calling :- [all …]
|
/Linux-v4.19/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-v4.19/drivers/net/can/peak_canfd/ |
D | peak_canfd.c | 108 priv->can.state = CAN_STATE_ERROR_ACTIVE; in pucan_set_normal_mode() 120 priv->can.state = CAN_STATE_ERROR_ACTIVE; in pucan_set_listen_only_mode() 133 priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES); in pucan_set_timing_slow() 355 priv->can.state = CAN_STATE_BUS_OFF; in pucan_handle_status() 356 priv->can.can_stats.bus_off++; in pucan_handle_status() 363 priv->can.state = CAN_STATE_ERROR_PASSIVE; in pucan_handle_status() 364 priv->can.can_stats.error_passive++; in pucan_handle_status() 376 priv->can.state = CAN_STATE_ERROR_WARNING; in pucan_handle_status() 377 priv->can.can_stats.error_warning++; in pucan_handle_status() 387 } else if (priv->can.state != CAN_STATE_ERROR_ACTIVE) { in pucan_handle_status() [all …]
|
/Linux-v4.19/drivers/hwmon/ |
D | Kconfig | 12 can include temperature sensors, voltage sensors, fan speed 22 This support can also be built as a module. If so, the module 49 This driver can also be built as a module. If so, the module 59 chip can be found on Abit uGuru featuring motherboards (most modern 64 This driver can also be built as a module. If so, the module 74 uGuru chip can be found on recent Abit motherboards (since end 78 This driver can also be built as a module. If so, the module 88 This driver can also be built as a module. If so, the module 98 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 [all …]
|
/Linux-v4.19/drivers/staging/speakup/ |
D | Kconfig | 9 kernel, it can speak everything on the text console from 13 can subscribe to. 21 that can be used with a plain text terminal. 23 Speakup can either be built in or compiled as a module 27 the synthesizer drivers below can only be built as 35 The Dectalk pc driver can only be built as a module, and 37 the module can be loaded. See the decpc choice below 48 synthesizer. You can say y to build it into the kernel, 57 synthesizer. You can say y to build it into the kernel, 65 synthesizer. You can say y to build it into the kernel, [all …]
|
/Linux-v4.19/net/netfilter/ipset/ |
D | Kconfig | 8 ipset(8). You can use the sets in netfilter via the "set" match 21 You can define here default value of the maximum number 24 The value can be overridden by the 'max_sets' module 32 can store IPv4 addresses (or network addresse) from a range. 41 can store IPv4 address and (source) MAC address pairs from a range. 50 can store TCP/UDP port numbers from a range. 59 can store arbitrary IPv4 or IPv6 addresses (or network addresses) 69 can store IPv4/IPv6 address and mark pairs. 78 can store IPv4/IPv6 address and protocol/port pairs. 87 one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6 [all …]
|
/Linux-v4.19/drivers/net/can/usb/ |
D | mcba_usb.c | 79 bool can; member 84 struct can_priv can; /* must be the first member */ member 197 ctx->can = true; in mcba_usb_get_free_ctx() 200 ctx->can = false; in mcba_usb_get_free_ctx() 243 if (ctx->can) { in mcba_usb_write_bulk_callback() 487 priv->can.termination = MCBA_TERMINATION_ENABLED; in mcba_usb_process_ka_usb() 489 priv->can.termination = MCBA_TERMINATION_DISABLED; in mcba_usb_process_ka_usb() 517 if (bitrate != priv->can.bittiming.bitrate) in mcba_usb_process_ka_can() 521 bitrate, priv->can.bittiming.bitrate); in mcba_usb_process_ka_can() 528 priv->can.state = CAN_STATE_BUS_OFF; in mcba_usb_process_ka_can() [all …]
|
D | ucan.c | 279 struct can_priv can; member 456 up->can.clock.freq = le32_to_cpu(device_info->freq); in ucan_parse_device_info() 470 up->can.ctrlmode_supported = 0; in ucan_parse_device_info() 473 up->can.ctrlmode_supported |= CAN_CTRLMODE_LOOPBACK; in ucan_parse_device_info() 475 up->can.ctrlmode_supported |= CAN_CTRLMODE_LISTENONLY; in ucan_parse_device_info() 477 up->can.ctrlmode_supported |= CAN_CTRLMODE_3_SAMPLES; in ucan_parse_device_info() 479 up->can.ctrlmode_supported |= CAN_CTRLMODE_ONE_SHOT; in ucan_parse_device_info() 481 up->can.ctrlmode_supported |= CAN_CTRLMODE_BERR_REPORTING; in ucan_parse_device_info() 491 enum can_state new_state = up->can.state; in ucan_handle_error_frame() 493 struct can_device_stats *can_stats = &up->can.can_stats; in ucan_handle_error_frame() [all …]
|
/Linux-v4.19/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 37 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 78 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 105 This driver can also be built as a module. If so, the module will 115 This driver can also be built as a module. If so, the module will [all …]
|
/Linux-v4.19/drivers/net/can/ |
D | Kconfig | 9 This driver can also be built as a module. If so, the module 19 versa. The vxcan can be used for cross namespace communication. 27 This driver can also be built as a module. If so, the module 43 slcand) can be found in the can-utils at the SocketCAN SVN, see 47 can be changed by the 'maxdev=xx' module option. This driver can 119 This driver can also be built as a module. If so, the module will be 153 This driver can access CAN bus. 155 source "drivers/net/can/c_can/Kconfig" 156 source "drivers/net/can/cc770/Kconfig" 157 source "drivers/net/can/ifi_canfd/Kconfig" [all …]
|
/Linux-v4.19/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-v4.19/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-v4.19/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-v4.19/Documentation/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-v4.19/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-v4.19/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-v4.19/fs/nls/ |
D | Kconfig | 42 The Microsoft FAT file system family can deal with filenames in 47 only, not to the file contents. You can include several codepages; 54 The Microsoft FAT file system family can deal with filenames in 59 only, not to the file contents. You can include several codepages; 66 The Microsoft FAT file system family can deal with filenames in 71 only, not to the file contents. You can include several codepages; 79 The Microsoft FAT file system family can deal with filenames in 84 only, not to the file contents. You can include several codepages; 95 The Microsoft FAT file system family can deal with filenames in 100 only, not to the file contents. You can include several codepages; [all …]
|
/Linux-v4.19/Documentation/hid/ |
D | hid-sensor.txt | 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. 61 function will be called. So an accelerometer processing driver can register 64 The core driver provides a set of APIs which can be used by the processing 71 the report and get the indexes of the fields and also can get events. This driver 72 can use IIO interface to use the standard ABI defined for a type of sensor. 79 Each processing driver can use this structure to set some callbacks. 83 int (*send_event)(..): One complete event is received which can have [all …]
|
/Linux-v4.19/Documentation/networking/ |
D | regulatory.txt | 7 More up to date information can be obtained at the project's web page: 34 A currently available userspace agent which can accomplish this 40 it needs a new regulatory domain. A udev rule can be put in place 44 Below is an example udev rule which can be used: 56 Users can use iw: 79 set they can inform the wireless core using regulatory_hint(). 81 crda can provide back a regulatory domain for that country or 82 they can build their own regulatory domain based on internal 83 custom knowledge so the wireless core can respect it. 87 check that can be used to ensure compliance based on custom EEPROM [all …]
|