Home
last modified time | relevance | path

Searched refs:can (Results 1 – 25 of 3530) sorted by relevance

12345678910>>...142

/Linux-v5.10/drivers/net/can/
Dkvaser_pciefd.c253 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 …]
DKconfig10 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 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
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"
[all …]
/Linux-v5.10/net/can/
Dproc.c81 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()
121 struct net *net = from_timer(net, t, can.stattimer); in can_stat_update()
122 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stat_update()
180 mod_timer(&net->can.stattimer, round_jiffies(jiffies + HZ)); in can_stat_update()
215 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stats_proc_show()
216 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_stats_proc_show()
225 if (net->can.stattimer.function == can_stat_update) { in can_stats_proc_show()
277 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_reset_stats_proc_show()
278 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_reset_stats_proc_show()
[all …]
DMakefile6 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 …]
Daf_can.c203 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()
449 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_rx_register()
464 spin_lock_bh(&net->can.rcvlists_lock); in can_rx_register()
483 spin_unlock_bh(&net->can.rcvlists_lock); in can_rx_register()
518 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_rx_unregister()
527 spin_lock_bh(&net->can.rcvlists_lock); in can_rx_unregister()
561 spin_unlock_bh(&net->can.rcvlists_lock); in can_rx_unregister()
647 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_receive()
661 matches = can_rcv_filter(net->can.rx_alldev_list, skb); in can_receive()
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/net/can/
Drcar_can.txt5 - compatible: "renesas,can-r8a7742" if CAN controller is a part of R8A7742 SoC.
6 "renesas,can-r8a7743" if CAN controller is a part of R8A7743 SoC.
7 "renesas,can-r8a7744" if CAN controller is a part of R8A7744 SoC.
8 "renesas,can-r8a7745" if CAN controller is a part of R8A7745 SoC.
9 "renesas,can-r8a77470" if CAN controller is a part of R8A77470 SoC.
10 "renesas,can-r8a774a1" if CAN controller is a part of R8A774A1 SoC.
11 "renesas,can-r8a774b1" if CAN controller is a part of R8A774B1 SoC.
12 "renesas,can-r8a774c0" if CAN controller is a part of R8A774C0 SoC.
13 "renesas,can-r8a774e1" if CAN controller is a part of R8A774E1 SoC.
14 "renesas,can-r8a7778" if CAN controller is a part of R8A7778 SoC.
[all …]
Datmel-can.txt4 - compatible: Should be "atmel,at91sam9263-can", "atmel,at91sam9x5-can" or
5 "microchip,sam9x60-can"
11 can0: can@f000c000 {
12 compatible = "atmel,at91sam9x5-can";
/Linux-v5.10/Documentation/power/regulator/
Dconsumer.rst12 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.10/drivers/net/can/ifi_canfd/
Difi_canfd.c220 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.10/drivers/net/can/peak_canfd/
Dpeak_canfd.c99 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()
397 } else if (priv->can.state != CAN_STATE_ERROR_ACTIVE) { in pucan_handle_status()
[all …]
/Linux-v5.10/drivers/hwmon/pmbus/
DKconfig12 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
56 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
75 This driver can also be built as a module. If so, the module will
84 This driver can also be built as a module. If so, the module will
93 This driver can also be built as a module. If so, the module will
102 This driver can also be built as a module. If so, the module will
[all …]
/Linux-v5.10/drivers/hwmon/
DKconfig13 can include temperature sensors, voltage sensors, fan speed
23 This support can also be built as a module. If so, the module
51 This driver can also be built as a module. If so, the module
61 chip can be found on Abit uGuru featuring motherboards (most modern
66 This driver can also be built as a module. If so, the module
76 uGuru chip can be found on recent Abit motherboards (since end
80 This driver can also be built as a module. If so, the module
90 This driver can also be built as a module. If so, the module
100 This driver can also be built as a module. If so, the module
110 This driver can also be built as a module. If so, the module
[all …]
/Linux-v5.10/drivers/accessibility/speakup/
DKconfig10 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
54 synthesizer. You can say y to build it into the kernel,
63 synthesizer. You can say y to build it into the kernel,
71 synthesizer. You can say y to build it into the kernel,
[all …]
/Linux-v5.10/drivers/net/can/usb/
Dmcba_usb.c68 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.10/Documentation/bpf/
Dbpf_lsm.rst15 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
24 for accessing information from the attached eBPF program's context. They can
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``
97 eBPF programs can be loaded with the :manpage:`bpf(2)` syscall's
107 This can be simplified by using a skeleton header generated by ``bpftool``:
113 and the program can be loaded by including ``my_prog.skel.h`` and using
[all …]
/Linux-v5.10/net/netfilter/ipset/
DKconfig9 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.10/drivers/block/paride/
DTransition-notes2 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.10/Documentation/devicetree/bindings/display/exynos/
Dexynos_dp.txt47 -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.10/drivers/rtc/
DKconfig69 one can sleep when setting time, because it runs in the workqueue
120 can be accessed as /dev/rtc, which is a name
142 RTC test driver. It's a software RTC which can be
149 This driver can also be built as a module. If so, the module
163 This driver can also be built as a module. If so, the module
173 This driver can also be built as a module. If so, the module
183 This driver can also be built as a module. If so, the module
193 This driver can also be built as a module. If so, the module
204 This driver can also be built as a module. If so, the module
214 This driver can also be built as a module. If so, the module
[all …]
/Linux-v5.10/Documentation/userspace-api/accelerators/
Docxl.rst11 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.10/drivers/net/can/sja1000/
Dsja1000.c127 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.10/fs/nls/
DKconfig43 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.10/Documentation/scsi/
Dscsi.rst11 It can also be found at:
16 The scsi support in the linux kernel can be modularized in a number of
21 support. Without it you can do nothing with any of the other scsi drivers.
22 The scsi core support can be a module (scsi_mod.o), or it can be built into
29 The individual upper and lower level drivers can be loaded in any order
33 level drivers to support the various assorted devices which can be
34 controlled. You can for example load the tape driver to use the tape drive,
42 Adaptec. Almost all lower level drivers can be built either as modules or
/Linux-v5.10/Documentation/hid/
Dhid-sensor.rst16 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 …]
/Linux-v5.10/Documentation/networking/
Dregulatory.rst10 More up to date information can be obtained at the project's web page:
37 A currently available userspace agent which can accomplish this
43 it needs a new regulatory domain. A udev rule can be put in place
47 Below is an example udev rule which can be used:
59 Users can use iw:
82 set they can inform the wireless core using regulatory_hint().
84 crda can provide back a regulatory domain for that country or
85 they can build their own regulatory domain based on internal
86 custom knowledge so the wireless core can respect it.
90 check that can be used to ensure compliance based on custom EEPROM
[all …]

12345678910>>...142