Home
last modified time | relevance | path

Searched full:remote (Results 1 – 25 of 2151) sorted by relevance

12345678910>>...87

/Linux-v5.4/drivers/input/misc/
Dkeyspan_remote.c26 /* Defines for converting the data from the remote. */
85 /* Structure to store all the real stuff that a remote sends to us. */
115 /* variables used to parse messages from remote. */
124 * Debug routine that prints out what we've received from the remote.
167 static void keyspan_report_button(struct usb_keyspan *remote, int button, int press) in keyspan_report_button() argument
169 struct input_dev *input = remote->input; in keyspan_report_button()
172 input_report_key(input, remote->keymap[button], press); in keyspan_report_button()
177 * Routine that handles all the logic needed to parse out the message from the remote.
179 static void keyspan_check_data(struct usb_keyspan *remote) in keyspan_check_data() argument
185 switch(remote->stage) { in keyspan_check_data()
[all …]
/Linux-v5.4/drivers/scsi/isci/
Dremote_node_table.c67 * @remote_node_table: This is the remote node index table from which the
102 * @out]: remote_node_table This the remote node table in which to clear the
104 * @set_index: This is the remote node selector in which the change will be
132 * @out]: remote_node_table This the remote node table in which to set the
134 * @group_table_index: This is the remote node selector in which the change
162 * @out]: remote_node_table This is the remote node table in which to modify
163 * the remote node availability.
164 * @remote_node_index: This is the remote node index that is being returned to
167 * This method will set the remote to available in the remote node allocation
195 * @out]: remote_node_table This is the remote node table from which to clear
[all …]
Dscu_remote_node_context.h61 * describe a remote node context.
68 * definition for an SSP remote node.
76 * This field is the remote node index assigned for this remote node. All
77 * remote nodes must have a unique remote node index. The value of the remote
78 * node index can not exceed the maximum number of remote nodes reported in
86 * this remote node will support.
92 * remote node.
98 * This field will enable the I_T nexus loss timer for this remote node.
108 * This field must be set to true when the hardware DMAs the remote node
109 * context to the hardware SRAM. When the remote node is being invalidated
[all …]
Dremote_node_context.h61 * the remote node context in the silicon. It exists to model and manage
62 * the remote node context in the silicon.
72 * This constant represents an invalid remote device id, it is used to program
94 * @SCI_RNC_INITIAL initial state for a remote node context. On a resume
95 * request the remote node context will transition to the posting state.
98 * the RNC is posted the remote node context will be made ready.
101 * the hardware. Once the invalidate is complete the remote node context will
106 * remote node context will transition to the ready state.
108 * @SCI_RNC_READY: state that the remote node context must be in to accept io
111 * @SCI_RNC_TX_SUSPENDED: state that the remote node context transitions to when
[all …]
Dremote_node_table.h64 * Remote node sets are sets of remote node index in the remtoe node table The
65 * SCU hardware requires that STP remote node entries take three consecutive
66 * remote node index so the table is arranged in sets of three. The bits are
67 * used as 0111 0111 to make a byte and the bits define the set of three remote
75 * Since the remote node table is organized as DWORDS take the remote node sets
85 * This is a count of the numeber of remote nodes that can be represented in a
94 * This is a count of the number of remote nodes that can be represented in a
103 * This is the number of bits in a remote node group
114 * Expander attached sata remote node count
121 * Expander or direct attached ssp remote node count
[all …]
/Linux-v5.4/Documentation/hwmon/
Dmax1668.rst25 set; only two remote temperature inputs vs the four available on the other
39 temp2_input ro remote temperature 1
40 temp2_max rw remote temperature 1 maximum threshold for alarm
41 temp2_max_alarm ro remote temperature 1 maximum threshold alarm
42 temp2_min rw remote temperature 1 minimum threshold for alarm
43 temp2_min_alarm ro remote temperature 1 minimum threshold alarm
44 temp3_input ro remote temperature 2
45 temp3_max rw remote temperature 2 maximum threshold for alarm
46 temp3_max_alarm ro remote temperature 2 maximum threshold alarm
47 temp3_min rw remote temperature 2 minimum threshold for alarm
[all …]
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-class-remoteproc4 Description: Remote processor firmware
7 remote processor.
9 To change the running firmware, ensure the remote processor is
15 Description: Remote processor state
17 Reports the state of the remote processor, which will be one of:
25 "offline" means the remote processor is powered off.
27 "suspended" means that the remote processor is suspended and
30 "running" is the normal state of an available remote processor
33 the remote processor.
35 "invalid" is returned if the remote processor is in an
[all …]
Dsysfs-bus-rpmsg6 Every rpmsg device is a communication channel with a remote
18 Every rpmsg device is a communication channel with a remote
20 and remote ("destination") rpmsg address. When an entity
36 Every rpmsg device is a communication channel with a remote
38 and remote ("destination") rpmsg address. When an entity
44 This sysfs entry contains the dst (remote) rpmsg address
48 remote processor. This make it a local rpmsg server,
50 from any remote rpmsg client; it is not bound to a single
51 remote entity).
58 Every rpmsg device is a communication channel with a remote
[all …]
/Linux-v5.4/arch/arm64/boot/dts/hisilicon/
Dhi3660-coresight.dtsi24 remote-endpoint =
41 remote-endpoint =
58 remote-endpoint =
75 remote-endpoint =
91 remote-endpoint =
104 remote-endpoint = <&etm0_out>;
111 remote-endpoint = <&etm1_out>;
118 remote-endpoint = <&etm2_out>;
125 remote-endpoint = <&etm3_out>;
140 remote-endpoint =
[all …]
Dhi6220-coresight.dtsi22 remote-endpoint =
31 remote-endpoint =
47 remote-endpoint =
56 remote-endpoint =
71 remote-endpoint =
84 remote-endpoint =
92 remote-endpoint =
108 remote-endpoint =
124 remote-endpoint =
140 remote-endpoint =
[all …]
/Linux-v5.4/arch/arm/boot/dts/
Dhip04.dtsi280 remote-endpoint = <&replicator0_out_port0>;
295 remote-endpoint = <&replicator1_out_port0>;
310 remote-endpoint = <&replicator2_out_port0>;
325 remote-endpoint = <&replicator3_out_port0>;
340 remote-endpoint = <&funnel4_out_port0>;
360 remote-endpoint = <&etb0_in_port>;
367 remote-endpoint = <&funnel4_in_port0>;
375 remote-endpoint = <&funnel0_out_port0>;
395 remote-endpoint = <&etb1_in_port>;
402 remote-endpoint = <&funnel4_in_port1>;
[all …]
Dimx6q.dtsi225 remote-endpoint = <&mipi_vc2_to_ipu2_csi0>;
233 remote-endpoint = <&ipu2_csi1_mux_to_ipu2_csi1>;
248 remote-endpoint = <&hdmi_mux_2>;
253 remote-endpoint = <&mipi_mux_2>;
258 remote-endpoint = <&lvds0_mux_2>;
263 remote-endpoint = <&lvds1_mux_2>;
274 remote-endpoint = <&hdmi_mux_3>;
279 remote-endpoint = <&mipi_mux_3>;
284 remote-endpoint = <&lvds0_mux_3>;
289 remote-endpoint = <&lvds1_mux_3>;
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/sound/
Daudio-graph-card.txt49 remote-endpoint = <&codec_endpoint>;
61 remote-endpoint = <&cpu_endpoint>;
84 remote-endpoint = <&cpu_endpoint0>;
93 remote-endpoint = <&cpu_endpoint1>;
102 remote-endpoint = <&cpu_endpoint2>;
112 remote-endpoint = <&codec0_endpoint>;
120 remote-endpoint = <&codec1_endpoint>;
128 remote-endpoint = <&codec2_endpoint>;
158 remote-endpoint = <&cpu_endpoint>;
167 remote-endpoint = <&codec_endpoint>;
[all …]
/Linux-v5.4/drivers/media/rc/
DKconfig4 tristate "Remote Controller support"
7 Enable support for Remote Controllers on Linux. This is
24 Enable this option to enable the Linux Infrared Remote
43 bool "Remote controller decoders"
71 Enable this option if you have an infrared remote control which
80 Enable this option if you have an infrared remote control which
89 Enable this option if you have an infrared remote control which
97 Enable this option if you have an infrared remote control which
106 Enable this option if you have an infrared remote control which
116 Enable this option if you have a Microsoft Remote Keyboard for
[all …]
/Linux-v5.4/Documentation/
Drpmsg.txt2 Remote Processor Messaging (rpmsg) Framework
14 Modern SoCs typically employ heterogeneous remote processor devices in
24 Typically AMP remote processors employ dedicated DSP codecs and multimedia
28 These remote processors could also be used to control latency-sensitive
32 Users of those remote processors can either be userland apps (e.g. multimedia
33 frameworks talking with remote OMX components) or kernel drivers (controlling
34 hardware accessible only by the remote processor, reserving kernel-controlled
35 resources on behalf of the remote processor, etc..).
38 with remote processors available on the system. In turn, drivers could then
42 keep in mind that remote processors might have direct access to the
[all …]
Dremoteproc.txt2 Remote Processor Framework
8 Modern SoCs typically have heterogeneous remote processor devices in asymmetric
18 control (power on, load firmware, power off) those remote processors while
21 for remote processors that supports this kind of communication. This way,
29 existing virtio drivers with remote processor backends at a minimal development
39 Boot a remote processor (i.e. load its firmware, power it on, ...).
41 If the remote processor is already powered on, this function immediately
54 Power off a remote processor (previously booted with rproc_boot()).
75 the remote processor's refcount, so always use rproc_put() to
90 /* let's power on and boot our remote processor */
[all …]
/Linux-v5.4/drivers/remoteproc/
DKconfig5 bool "Support for Remote Processor subsystem"
12 Support for remote processors (such as DSP coprocessors). These
21 Say y here to support iMX's remote processors (Cortex M4
22 on iMX7D) via the remote processor framework.
33 Say y here to support OMAP's remote processors (dual M3
34 and DSP on OMAP4) via the remote processor framework.
40 offloaded to remote DSP processors using this framework).
49 Say y here to support Wakeup M3 remote processor on TI AM33xx
54 firmware onto these remote processors.
62 Say y here to support DA8xx/OMAP-L13x remote processors via the
[all …]
/Linux-v5.4/drivers/gpu/drm/
Ddrm_of.c119 struct device_node *ep, *port, *remote; in drm_of_component_probe() local
153 * For bound crtcs, bind the encoders attached to their remote endpoint in drm_of_component_probe()
166 remote = of_graph_get_remote_port_parent(ep); in drm_of_component_probe()
167 if (!remote || !of_device_is_available(remote)) { in drm_of_component_probe()
168 of_node_put(remote); in drm_of_component_probe()
170 } else if (!of_device_is_available(remote->parent)) { in drm_of_component_probe()
172 remote); in drm_of_component_probe()
173 of_node_put(remote); in drm_of_component_probe()
178 remote); in drm_of_component_probe()
179 of_node_put(remote); in drm_of_component_probe()
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/remoteproc/
Dstm32-rproc.txt9 remote processor.
10 - resets: Reference to a reset controller asserting the remote processor.
12 remote processor reset hold boot
27 remote proc.
29 - from local to remote = send message
30 - from remote to local = send message ack
32 - a channel (c) used by the local proc to notify the remote proc
35 - from local to remote, where ACK from the remote means
43 memories shared with the remote processor (eg: remoteproc
46 - st,syscfg-pdds: Reference to the system configuration which holds the remote
[all …]
/Linux-v5.4/drivers/media/rc/keymaps/
Drc-fusionhdtv-mce.c2 // fusionhdtv-mce.h - Keytable for fusionhdtv_mce Remote Controller
11 /* DViCO FUSION HDTV MCE remote */
32 { 0x02, KEY_TV }, /* Labeled DTV on remote */
35 { 0x1e, KEY_FAVORITES }, /* Labeled CPF on remote */
37 { 0x46, KEY_POWER2 }, /* TV On/Off button on remote */
38 { 0x0a, KEY_EPG }, /* Labeled Guide on remote */
41 { 0x59, KEY_INFO }, /* Labeled MORE on remote */
42 { 0x4d, KEY_MENU }, /* Labeled DVDMENU on remote */
43 { 0x55, KEY_CYCLEWINDOWS }, /* Labeled ALT-TAB on remote */
45 { 0x0f, KEY_PREVIOUSSONG }, /* Labeled |<< REPLAY on remote */
[all …]
/Linux-v5.4/tools/usb/usbip/doc/
Dusbip.829 Connect to PORT on remote host (used for attach and list --remote).
47 \fBattach\fR \-\-remote=<\fIhost\fR> \-\-busid=<\fIbus_id\fR>
49 Attach a remote USB device.
71 \fBlist\fR \-\-remote=<\fIhost\fR>
73 List USB devices exported by a remote host.
85 client:# usbip list --remote=server
88 client:# usbip attach --remote=server --busid=1-2
89 - Connect the remote USB device.
/Linux-v5.4/Documentation/media/v4l-drivers/
Dv4l-with-ir.rst3 Infrared remote control support in video4linux drivers
11 Most analog and digital TV boards support remote controllers. Several of
17 The support for remote controller in scancode mode is provided by the
22 two tools to handle remote controllers:
24 - ir-keytable: provides a way to query the remote controller, list the
28 - ir-ctl: provide tools to handle remote controllers that support raw mode
31 Usually, the remote controller module is auto-loaded when the TV card is
38 The modules register the remote as keyboard within the linux input
39 layer, i.e. you'll see the keys of the remote as normal key strokes
43 applications to access the remote via /dev/input/event<n> devices.
[all …]
/Linux-v5.4/drivers/vlynq/
Dvlynq.c72 printk(KERN_DEBUG "VLYNQ local=%p remote=%p\n", in vlynq_dump_regs()
73 dev->local, dev->remote); in vlynq_dump_regs()
77 printk(KERN_DEBUG "VLYNQ: remote %d: %08x\n", in vlynq_dump_regs()
78 i + 1, ((u32 *)dev->remote)[i]); in vlynq_dump_regs()
133 val = readl(&dev->remote->int_device[virq >> 2]); in vlynq_irq_unmask()
135 writel(val, &dev->remote->int_device[virq >> 2]); in vlynq_irq_unmask()
146 val = readl(&dev->remote->int_device[virq >> 2]); in vlynq_irq_mask()
148 writel(val, &dev->remote->int_device[virq >> 2]); in vlynq_irq_mask()
159 val = readl(&dev->remote->int_device[virq >> 2]); in vlynq_irq_type()
178 writel(val, &dev->remote->int_device[virq >> 2]); in vlynq_irq_type()
[all …]
/Linux-v5.4/arch/arm64/boot/dts/sprd/
Dsc9860.dtsi310 remote-endpoint = <&etb_in>;
322 remote-endpoint =
330 remote-endpoint =
345 remote-endpoint =
362 remote-endpoint =
377 remote-endpoint =
390 remote-endpoint = <&etm0_out>;
397 remote-endpoint = <&etm1_out>;
404 remote-endpoint = <&etm2_out>;
411 remote-endpoint = <&etm3_out>;
[all …]
/Linux-v5.4/tools/testing/selftests/ntb/
Dntb_test.sh26 echo "use the -r option to specify the hostname for the remote"
27 echo "device. SSH will then be used to test the remote side."
34 echo " -l list available local and remote PCI ids"
35 echo " -r REMOTE_HOST specify the remote's hostname to connect"
91 REMOTE=
94 REMOTE=${VPATH%%:*}
102 if [[ "$REMOTE" != "" ]]; then
103 ssh "$REMOTE" cat "$VPATH"
114 if [[ "$REMOTE" != "" ]]; then
115 ssh "$REMOTE" "echo \"$VALUE\" > \"$VPATH\""
[all …]

12345678910>>...87