Home
last modified time | relevance | path

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

12345678910>>...202

/openbmc/linux/drivers/net/can/
H A Dkvaser_pciefd.c371 struct can_priv can; member
387 struct kvaser_pciefd_can *can[KVASER_PCIEFD_MAX_CAN_CHANNELS]; member
465 static inline void kvaser_pciefd_send_kcan_cmd(struct kvaser_pciefd_can *can, u32 cmd) in kvaser_pciefd_send_kcan_cmd() argument
468 FIELD_PREP(KVASER_PCIEFD_KCAN_CMD_SEQ_MASK, ++can->cmd_seq), in kvaser_pciefd_send_kcan_cmd()
469 can->reg_base + KVASER_PCIEFD_KCAN_CMD_REG); in kvaser_pciefd_send_kcan_cmd()
472 static inline void kvaser_pciefd_request_status(struct kvaser_pciefd_can *can) in kvaser_pciefd_request_status() argument
474 kvaser_pciefd_send_kcan_cmd(can, KVASER_PCIEFD_KCAN_CMD_SRQ); in kvaser_pciefd_request_status()
477 static inline void kvaser_pciefd_abort_flush_reset(struct kvaser_pciefd_can *can) in kvaser_pciefd_abort_flush_reset() argument
479 kvaser_pciefd_send_kcan_cmd(can, KVASER_PCIEFD_KCAN_CMD_AT); in kvaser_pciefd_abort_flush_reset()
482 static void kvaser_pciefd_enable_err_gen(struct kvaser_pciefd_can *can) in kvaser_pciefd_enable_err_gen() argument
[all …]
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.
49 This driver can also be built as a module. If so, the module
62 can-dev module.
82 can-dev module.
105 This driver can also be built as a module. If so, the module
117 designed to be used as a standalone CAN interface. However, it can
122 Documentation/networking/device_drivers/can/can327.rst
[all …]
/openbmc/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 = 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 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.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()
463 spin_lock_bh(&net->can.rcvlists_lock); in can_rx_register()
482 spin_unlock_bh(&net->can.rcvlists_lock); in can_rx_register()
517 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_rx_unregister()
526 spin_lock_bh(&net->can.rcvlists_lock); in can_rx_unregister()
560 spin_unlock_bh(&net->can.rcvlists_lock); in can_rx_unregister()
646 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_receive()
660 matches = can_rcv_filter(net->can.rx_alldev_list, skb); in can_receive()
[all …]
/openbmc/qemu/tests/qemu-iotests/
H A D083.out4 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
8 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
12 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
16 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
20 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
24 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
28 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
32 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
36 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
40 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
[all …]
H A D092.out5 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
6 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
7 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
8 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
12 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
13 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
14 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
15 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
19 qemu-io: can't open device TEST_DIR/t.qcow: Image too large
20 qemu-io: can't open device TEST_DIR/t.qcow: Image too large
[all …]
H A D075.out3 == check that the first sector can be read ==
7 == check that the last sector can be read ==
12 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: block_size 513 must be a multiple of 512
15 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: block_size cannot be zero
18 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: block_size 4294966784 must be 64 MB or le…
21 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: n_blocks 4294967295 must be 536870911 or …
24 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: image requires too many offsets, try incr…
27 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: offsets not monotonically increasing at i…
30 qemu-io: can't open device TEST_DIR/simple-pattern.cloop: invalid compressed block size at index 1,…
H A D226.out6 qemu-io: can't open: 'file' driver requires 'TEST_DIR/t.IMGFMT' to be a regular file
7 qemu-io: can't open: 'file' driver requires '/dev/null' to be a regular file
9 qemu-io: can't open: Could not open 'TEST_DIR/t.IMGFMT': Is a directory
10 qemu-io: can't open: 'file' driver requires '/dev/null' to be a regular file
15 qemu-io: can't open: 'host_device' driver requires 'TEST_DIR/t.IMGFMT' to be either a character or …
17 qemu-io: can't open: Could not open 'TEST_DIR/t.IMGFMT': Is a directory
22 qemu-io: can't open: 'host_cdrom' driver requires 'TEST_DIR/t.IMGFMT' to be either a character or b…
24 qemu-io: can't open: Could not open 'TEST_DIR/t.IMGFMT': Is a directory
H A D088.out5 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 0
6 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 0
7 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 128
8 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 128
9 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 305419896
10 qemu-io: can't open device TEST_DIR/t.vpc: Invalid block size 305419896
H A D080.out5 qemu-io: can't open device TEST_DIR/t.qcow2: qcow2 header exceeds cluster size
6 qemu-io: can't open device TEST_DIR/t.qcow2: qcow2 header exceeds cluster size
10 qemu-io: can't open device TEST_DIR/t.qcow2: Invalid backing file offset
11 qemu-io: can't open device TEST_DIR/t.qcow2: Header extension too large
12 qemu-io: can't open device TEST_DIR/t.qcow2: Header extension too large
16 qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table too large
17 qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table too large
21 qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table offset invalid
25 qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table offset invalid
29 qemu-io: can't open device TEST_DIR/t.qcow2: Snapshot table too large
[all …]
/openbmc/openbmc/poky/meta/lib/oeqa/runtime/cases/
H A Dparselogs-ignores-qemuall.txt9 # pci 0000:00:00.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
10 # pci 0000:00:00.0: [Firmware Bug]: reg 0x14: invalid BAR (can't size)
11 # pci 0000:00:00.0: [Firmware Bug]: reg 0x18: invalid BAR (can't size)
12 # pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
13 # pci 0000:00:00.0: [Firmware Bug]: reg 0x20: invalid BAR (can't size)
14 # pci 0000:00:00.0: [Firmware Bug]: reg 0x24: invalid BAR (can't size)
15 invalid BAR (can't size)
17 # pci 0000:00:00.0: [Firmware Bug]: BAR 0: invalid; can't size
18 # pci 0000:00:00.0: [Firmware Bug]: BAR 1: invalid; can't size
19 # pci 0000:00:00.0: [Firmware Bug]: BAR 2: invalid; can't size
[all …]
/openbmc/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
/openbmc/qemu/docs/system/devices/
H A Dcan.rst6 can be connected to host system CAN API (at this time only Linux
10 can be implemented.
17 interface to implement because such device can be easily connected
36 CAN boards can be selected
40 -object can-bus,id=canbus0
43 Add "can-host-socketcan" object to connect device to host system CAN bus::
45 -object can-host-socketcan,id=canhost0,if=can0,canbus=canbus0
49 -object can-bus,id=canbus0
54 -object can-bus,id=canbus0
55 -object can-bus,id=canbus1
[all …]
/openbmc/openbmc/poky/meta/recipes-devtools/expect/expect/
H A D0001-configure.in.patch13 - AC_MSG_ERROR([Expect can't be cross compiled])
22 - AC_MSG_ERROR([Expect can't be cross compiled])
33 -, AC_MSG_WARN([Expect can't be cross compiled])
43 - AC_MSG_ERROR([Expect can't be cross compiled])
54 - AC_MSG_ERROR([Expect can't be cross compiled])
65 - AC_MSG_ERROR([Expect can't be cross compiled])
76 - AC_MSG_ERROR([Expect can't be cross compiled])
85 - AC_MSG_ERROR([Expect can't be cross compiled])
94 - AC_MSG_ERROR([Expect can't be cross compiled])
103 - AC_MSG_ERROR([Expect can't be cross compiled])
/openbmc/linux/drivers/hwmon/pmbus/
H A DKconfig12 This driver can also be built as a module. If so, the module will
27 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
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
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
94 This driver can also be built as a module. If so, the module
104 This driver can also be built as a module. If so, the module will
[all …]
/openbmc/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 …]
/openbmc/linux/drivers/net/can/ifi_canfd/
H A 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()
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 …]
/openbmc/linux/Documentation/power/regulator/
H A 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 …]
/openbmc/u-boot/doc/
H A DREADME.at9120 U-Boot environment variables can be stored at different places:
25 You can choose your storage location at config step (here for at91sam9260ek) :
42 U-Boot environment variables can be stored at different places:
47 You can choose your storage location at config step (here for at91sam9260ek) :
63 U-Boot environment variables can be stored at different places:
68 You can choose your storage location at config step (here for at91sam9260ek) :
73 You can choose to boot directly from U-Boot at config step
86 U-Boot environment variables can be stored at different places:
89 You can choose your storage location at config step (here for at91sam9m10g45ek) :
103 U-Boot environment variables can be stored at different places:
[all …]
/openbmc/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 …]
/openbmc/phosphor-fan-presence/docs/control/
H A Ddebug.md3 Fan control's internal data structures can be dumped at runtime using the
5 `/tmp/fan_control_dump.json` file. That file is a normal JSON file that can be
6 viewed, or the `fanctl query_dump` command can be used as a shortcut to just
17 It can be printed with:
29 It can be printed with:
35 One can restrict the output to specific names with `-n` and properties with
64 It can be printed with:
74 They can be printed with:
85 It can be printed with:
93 Fan control can dump a list of all of its configured event names along with
[all …]
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Drenesas,rsnd.txt27 Multi-SSI : 6ch case, you can use stereo x 3 SSI
28 TDM-SSI : 6ch case, you can use TDM
36 ${LINUX}/arch/arm/boot/dts/r8a7790-lager.dts can be good example.
44 You can use below.
45 ${LINUX}/arch/arm/boot/dts/r8a7790.dts can be good example.
65 SRC can convert [xx]Hz to [yy]Hz. Then, it has below 2 modes
68 you can use this mode on Playback / Capture
72 you can use this mode on Playback
97 CTU can convert [xx]ch to [yy]ch, or exchange outputted channel.
140 MIX merges 2 sounds path. You can see 2 sound interface on system,
[all …]
/openbmc/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 …]
/openbmc/linux/Documentation/devicetree/bindings/net/can/
H A 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";

12345678910>>...202