Home
last modified time | relevance | path

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

12345678910>>...124

/linux/net/can/
H A 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()
117 struct net *net = timer_container_of(net, t, can.stattimer); in can_stat_update()
118 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()
219 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stats_proc_show()
220 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_stats_proc_show()
232 if (net->can.stattimer.function == can_stat_update) { in can_stats_proc_show()
284 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_reset_stats_proc_show()
285 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_reset_stats_proc_show()
[all …]
H A 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 …]
H A Daf_can.c205 struct can_pkg_stats *pkg_stats = dev_net(skb->dev)->can.pkg_stats; in can_send()
312 return net->can.rx_alldev_list; in can_dev_rcv_lists_find()
451 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_rx_register()
465 spin_lock_bh(&net->can.rcvlists_lock); in can_rx_register()
484 spin_unlock_bh(&net->can.rcvlists_lock); in can_rx_register()
519 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_rx_unregister()
528 spin_lock_bh(&net->can.rcvlists_lock); in can_rx_unregister()
562 spin_unlock_bh(&net->can.rcvlists_lock); in can_rx_unregister()
658 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_receive()
670 matches = can_rcv_filter(net->can.rx_alldev_list, skb); in can_receive()
[all …]
/linux/drivers/net/can/kvaser_pciefd/
H A Dkvaser_pciefd_devlink.c38 int kvaser_pciefd_devlink_port_register(struct kvaser_pciefd_can *can) in kvaser_pciefd_devlink_port_register() argument
43 .phys.port_number = can->can.dev->dev_port, in kvaser_pciefd_devlink_port_register()
45 devlink_port_attrs_set(&can->devlink_port, &attrs); in kvaser_pciefd_devlink_port_register()
47 ret = devlink_port_register(priv_to_devlink(can->kv_pcie), in kvaser_pciefd_devlink_port_register()
48 &can->devlink_port, can->can.dev->dev_port); in kvaser_pciefd_devlink_port_register()
52 SET_NETDEV_DEVLINK_PORT(can->can.dev, &can->devlink_port); in kvaser_pciefd_devlink_port_register()
57 void kvaser_pciefd_devlink_port_unregister(struct kvaser_pciefd_can *can) in kvaser_pciefd_devlink_port_unregister() argument
59 devlink_port_unregister(&can->devlink_port); in kvaser_pciefd_devlink_port_unregister()
/linux/drivers/net/can/dev/
H A DMakefile3 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/drivers/net/can/
H A DKconfig14 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.
46 This driver can also be built as a module. If so, the module
59 can-dev module.
79 can-dev module.
103 This driver can also be built as a module. If so, the module
115 designed to be used as a standalone CAN interface. However, it can
120 Documentation/networking/device_drivers/can/can327.rst
[all …]
H A Ddummy_can.c20 struct can_priv can; member
120 struct can_priv *can_priv = &priv->can; in dummy_can_print_ctrlmode()
142 struct can_priv *can_priv = &priv->can; in dummy_can_print_bittiming_info()
246 priv->can.bittiming_const = &dummy_can_bittiming_const; in dummy_can_init()
247 priv->can.bitrate_max = 20 * MEGA /* BPS */; in dummy_can_init()
248 priv->can.clock.freq = 160 * MEGA /* Hz */; in dummy_can_init()
249 priv->can.fd.data_bittiming_const = &dummy_can_fd_databittiming_const; in dummy_can_init()
250 priv->can.fd.tdc_const = &dummy_can_fd_tdc_const; in dummy_can_init()
251 priv->can.xl.data_bittiming_const = &dummy_can_xl_databittiming_const; in dummy_can_init()
252 priv->can.xl.tdc_const = &dummy_can_xl_tdc_const; in dummy_can_init()
[all …]
H A Dgrcan.c251 struct can_priv can; /* must be the first member */ member
409 struct can_bittiming *bt = &priv->can.bittiming; in grcan_set_bittiming()
473 priv->can.state = CAN_STATE_STOPPED; in grcan_reset()
563 !(priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY)) { in grcan_lost_one_shot_frame()
591 if (priv->can.ctrlmode & CAN_CTRLMODE_ONE_SHOT) in grcan_err()
609 enum can_state state = priv->can.state; in grcan_err()
634 priv->can.can_stats.bus_off++; in grcan_err()
639 if (!priv->can.restart_ms) in grcan_err()
647 priv->can.can_stats.error_passive++; in grcan_err()
658 priv->can.can_stats.error_warning++; in grcan_err()
[all …]
/linux/scripts/kconfig/tests/err_transitional/
H A Dexpected_stderr2 Kconfig:7: error: transitional symbols can only have help sections
3 Kconfig:14: error: transitional symbols can only have help sections
4 Kconfig:21: error: transitional symbols can only have help sections
5 Kconfig:28: error: transitional symbols can only have help sections
6 Kconfig:32: error: transitional symbols can only have help sections
7 Kconfig:42: error: transitional symbols can only have help sections
/linux/Documentation/sound/cards/
H A Dpcmtest.rst6 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/peak_canfd/
H A Dpeak_canfd.c100 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 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
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/usb/
H A Dmcba_usb.c67 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 Ducan.c276 struct can_priv can; member
453 up->can.clock.freq = le32_to_cpu(device_info->freq); in ucan_parse_device_info()
467 up->can.ctrlmode_supported = 0; in ucan_parse_device_info()
470 up->can.ctrlmode_supported |= CAN_CTRLMODE_LOOPBACK; in ucan_parse_device_info()
472 up->can.ctrlmode_supported |= CAN_CTRLMODE_LISTENONLY; in ucan_parse_device_info()
474 up->can.ctrlmode_supported |= CAN_CTRLMODE_3_SAMPLES; in ucan_parse_device_info()
476 up->can.ctrlmode_supported |= CAN_CTRLMODE_ONE_SHOT; in ucan_parse_device_info()
478 up->can.ctrlmode_supported |= CAN_CTRLMODE_BERR_REPORTING; in ucan_parse_device_info()
488 enum can_state new_state = up->can.state; in ucan_handle_error_frame()
490 struct can_device_stats *can_stats = &up->can.can_stats; in ucan_handle_error_frame()
[all …]
/linux/Documentation/bpf/
H A Dprog_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
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/Documentation/core-api/real-time/
H A Dhardware.rst9 The way a workload is handled can be influenced by the hardware it runs on.
13 can affect the deterministic handling of workloads in other applications.
21 tasks in a system. One task can dominate the available caches, forcing another
22 task to wait until a cache line is written back to main memory before it can
25 can be buffered before being written back. Conversely, certain write patterns
29 This issue can be partly mitigated if applications do not share the same CPU
32 project (https://www.open-mpi.org/projects/hwloc/) can visualize the hierarchy.
35 is minimized, bottlenecks can still occur when accessing system memory. Memory
39 In some cases, cache and memory bottlenecks can be controlled if the hardware
46 These features can be configured through the Linux Resource Control interface.
[all …]
/linux/drivers/rtc/
H A DKconfig69 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/dev-tools/kunit/
H A Drun_manual.rst8 with other systems, or run tests on real hardware), we can
18 KUnit tests can run without kunit_tool. This can be useful, if:
26 tests can also be built by enabling their config options in our
28 ending in ``_KUNIT_TEST``. Most tests can either be built as a module,
33 We can enable the ``KUNIT_ALL_TESTS`` config option to
38 KUnit can be enabled or disabled at boot time, and this behavior is
61 KUnit can be accessed from userspace via the debugfs filesystem (See more
65 mounted at /sys/kernel/debug/kunit. You can use this filesystem to perform
71 You can use debugfs to retrieve KUnit test results. The test results are
84 You can use the debugfs filesystem to trigger built-in tests to run after
[all …]
H A Drunning_tips.rst13 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/fs/nls/
H A 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/Documentation/core-api/
H A Dmaple_tree.rst17 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 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/Documentation/networking/
H A 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 …]
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-pci-drivers-xhci_hcd7 Capability (DbC). It can present a debug device which
24 can be one of the following states: disabled, enabled,
34 Value can only be changed while debug capability (DbC) is in
38 It can be any 16-bit integer.
47 Value can only be changed while debug capability (DbC) is in
50 The default value is 0x0010. It can be any 16-bit integer.
59 Value can only be changed while debug capability (DbC) is in
63 It can be any 16-bit integer.
72 Value can only be changed while debug capability (DbC) is in
98 Value can only be changed while debug capability (DbC) is in
[all …]
H A Dsysfs-class-powercap17 controlled. A <control type> can contain multiple power zones.
32 A power zone is a single or a collection of devices, which can
45 power zone for a whole CPU package, each CPU core in it can
61 If the counter can not be reset, then this attribute is
91 Each power zone can define one or more constraints. Each
92 constraint can have an optional name. Here "X" can have values
102 Here "X" can have values from 0 to max integer.
111 Here "X" can have values from 0 to max integer.
120 Here "X" can have values from 0 to max integer.
128 Here "X" can have values from 0 to max integer.
[all …]

12345678910>>...124