Searched full:remote (Results 1 – 25 of 745) sorted by relevance
12345678910>>...30
| /Documentation/ABI/testing/ |
| D | sysfs-class-remoteproc | 4 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 …]
|
| D | sysfs-bus-rpmsg | 6 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 …]
|
| /Documentation/hwmon/ |
| D | max1668.rst | 25 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 …]
|
| D | w83773g.rst | 22 chip. This chip implements one local and two remote sensors.
23 The chip also features offsets for the two remote sensors which get added to
29 degrees Celsius (for remote sensors).
30 Resolution for both the local and remote channels is 0.125 degree C.
|
| /Documentation/staging/ |
| D | rpmsg.rst | 2 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 …]
|
| D | remoteproc.rst | 2 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()).
76 the remote processor's refcount, so always use rproc_put() to
91 /* let's power on and boot our remote processor */
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | qcom,coresight-remote-etm.yaml | 4 $id: http://devicetree.org/schemas/arm/qcom,coresight-remote-etm.yaml#
7 title: Qualcomm Coresight Remote ETM(Embedded Trace Macrocell)
14 Support for ETM trace collection on remote processor using coresight
15 framework. Enabling this will allow turning on ETM tracing on remote
21 const: qcom,coresight-remote-etm
41 compatible = "qcom,coresight-remote-etm";
46 remote-endpoint = <&funnel_modem_in_modem_etm0>;
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | st,stm32-rproc.yaml | 7 title: STMicroelectronics STM32 remote processor controller
23 Address ranges of the RETRAM and MCU SRAM memories used by the remote
38 description: remote processor reset hold boot
69 remote proc.
71 - from local to remote = send message
72 - from remote to local = send message ack
76 A channel (c) used by the local proc to notify the remote proc that it
79 - from local to remote, where ACK from the remote means that it is
82 A channel (d) used by the local proc to notify the remote proc that it
85 - from local to remote, where ACK from the remote means that communication
[all …]
|
| D | qcom,glink-edge.yaml | 14 related to the remote processor.
49 qcom,remote-pid:
52 ID of the shared memory used by GLINK for communication with remote
59 - qcom,remote-pid
95 qcom,remote-pid = <13>;
|
| D | qcom,smd-edge.yaml | 13 Qualcomm SMD subnode represents a remote subsystem or a remote processor of
63 remote processor.
69 The identifier of the remote processor in the smd channel allocation
72 qcom,remote-pid:
75 The identifier for the remote processor as known by the rest of the
|
| /Documentation/admin-guide/media/ |
| D | remote-controller.rst | 4 Infrared remote control support in video4linux drivers
12 Most analog and digital TV boards support remote controllers. Several of
18 The support for remote controller in scancode mode is provided by the
23 two tools to handle remote controllers:
25 - ir-keytable: provides a way to query the remote controller, list the
29 - ir-ctl: provide tools to handle remote controllers that support raw mode
32 Usually, the remote controller module is auto-loaded when the TV card is
39 The modules register the remote as keyboard within the linux input
40 layer, i.e. you'll see the keys of the remote as normal key strokes
44 applications to access the remote via /dev/input/event<n> devices.
[all …]
|
| D | building.rst | 51 <M> Remote Controller support --->
57 The ``Remote Controller support`` option enables the core support for
58 remote controllers\ [2]_.
62 by a remote controller directly connected to the machine.
78 and remote controller support using Kernel modules, you could use::
83 .. [2] ``Remote Controller support`` should also be enabled if you
84 want to use some TV card drivers that may depend on the remote
111 Another example: the remote controller core requires support for
119 Enabling Remote Controller Support
122 The remote controller menu allows selecting drivers for specific devices.
[all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | maxim,max9286.yaml | 59 match the configuration of the remote serializers.
61 maxim,i2c-remote-bus-hz:
65 The I2C clock frequency for the remote I2C buses. The value must match
66 the configuration of the remote serializers.
76 configuration of the connected remote serializer.
85 a remote serializer whose high-threshold noise immunity is not enabled
101 When the remote cameras power is controlled by one of the MAX9286 gpio
103 available ones controls the remote camera power enablement.
162 Each serializer device on the GMSL link remote end is represented with
181 The remote camera device, composed by a GMSL serializer and a
[all …]
|
| D | tvp5150.txt | 71 remote-endpoint = <&tvp5150_to_composite0>;
83 remote-endpoint = <&tvp5150_to_composite1>;
98 remote-endpoint = <&tvp5150_to_svideo_luma>;
103 remote-endpoint = <&tvp5150_to_svideo_chroma>;
124 remote-endpoint = <&composite0_to_tvp5150>;
129 remote-endpoint = <&svideo_luma_to_tvp5150>;
140 remote-endpoint = <&composite1_to_tvp5150>;
145 remote-endpoint = <&svideo_chroma_to_tvp5150>;
153 remote-endpoint = <&ccdc_ep>;
|
| /Documentation/driver-api/media/ |
| D | rc-core.rst | 3 Remote Controller devices
6 Remote Controller core
9 The remote controller core implements infrastructure to receive and send
10 remote controller keyboard keystrokes and mouse events.
12 Every time a key is pressed on a remote controller, a scan code is produced.
16 remote controller core is implemented on the top of the linux input/evdev
23 infrared-based remote controllers, there's no key release event. Instead,
26 However, most of the remote controllers use infrared (IR) to transmit signals.
44 given remote controller), followed by 8 bits of code. A bit "1" is modulated
83 Remote controller data structures and functions
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | max6697.txt | 28 remote temperature channel 1.
32 Select bit 0 for local temperature, bit 1..7 for remote temperatures.
37 Select bit 0 for local temperature, bit 1..7 for remote temperatures.
42 cancellation on remote temperature channel 1.
45 Only supported for remote temperatures (bit 1..7).
50 select value as per MAX6581 data sheet. Select bit 1..7 for remote
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-atr.yaml | 26 used to access the remote peripherals on the serializer's I2C bus. The
28 remote peripheral is assigned an alias from the pool, and transactions to
29 that address will be forwarded to the remote peripheral, with the address
30 translated to the remote peripheral's real address. This property is not
31 needed if there are no I2C addressable remote peripherals.
|
| /Documentation/devicetree/bindings/media/ |
| D | renesas,csi2.yaml | 125 remote-endpoint = <&adv7482_txb>;
137 remote-endpoint = <&vin0csi20>;
141 remote-endpoint = <&vin1csi20>;
145 remote-endpoint = <&vin2csi20>;
149 remote-endpoint = <&vin3csi20>;
153 remote-endpoint = <&vin4csi20>;
157 remote-endpoint = <&vin5csi20>;
161 remote-endpoint = <&vin6csi20>;
165 remote-endpoint = <&vin7csi20>;
|
| D | renesas,isp.yaml | 137 remote-endpoint = <&csi41isp1>;
144 remote-endpoint = <&vin08isp1>;
151 remote-endpoint = <&vin09isp1>;
158 remote-endpoint = <&vin10isp1>;
165 remote-endpoint = <&vin11isp1>;
172 remote-endpoint = <&vin12isp1>;
179 remote-endpoint = <&vin13isp1>;
186 remote-endpoint = <&vin14isp1>;
193 remote-endpoint = <&vin15isp1>;
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | qcom,rmtfs-mem.yaml | 7 title: Qualcomm Remote File System Memory
10 This binding describes the Qualcomm remote filesystem memory, which serves the
11 purpose of describing the shared memory region used for remote processors to
12 access block device data using the Remote Filesystem protocol.
43 Array of vmids of the remote processors, to set up memory protection
|
| /Documentation/driver-api/mei/ |
| D | iamt.rst | 16 - Remote power off/on (useful for green computing or overnight IT
22 on policies set by a remote management console
23 - IDE device redirection from remote management console
27 HTTP/S that are received from a remote management console application.
42 local application using the same network interface as a remote application
67 2) Intel AMT Remote configuration using a Local Agent
70 without requiring installing additional data to enable setup. The remote
71 configuration process may involve an ISV-developed remote configuration
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smsm.yaml | 19 certain bit owned by a certain remote processor.
41 this client. Each entry represents the N:th remote processor by index
57 remote processor.
65 remote processor's state bits or the local processors bits. The node
75 belong to a remote processor.
83 One entry specifying remote IRQ used by the remote processor to
|
| D | qcom,smp2p.yaml | 17 writer (the local side) and a single reader (the remote side). Values are
19 remote processor ID) and a string identifier.
43 remote end of the smp2p edge.
51 qcom,remote-pid:
54 The identifier of the remote endpoint of this edge.
110 - qcom,remote-pid
134 qcom,remote-pid = <4>;
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | toshiba,tc358775.yaml | 54 DSI Input. The remote endpoint phandle should be a
137 remote-endpoint = <&dsi0_out>;
145 remote-endpoint = <&panel_in>;
162 remote-endpoint = <&d2l_in_test>;
196 remote-endpoint = <&dsi0_out_dual>;
204 remote-endpoint = <&panel_in0>;
211 remote-endpoint = <&panel_in1>;
228 remote-endpoint = <&d2l_in_dual>;
|
| /Documentation/driver-api/ |
| D | mailbox.rst | 10 very platform specific because the remote firmware is likely to be
16 nothing prevents the remote f/w to also be Linux based and use the
32 by the remote by getting an IRQ or polling some hardware flag
58 * This is the handler for data received from remote. The behaviour is purely
68 } else { /* A new message from remote */
72 /* Remote f/w sends only ACK packets on this channel */
116 /* Send async message to remote */
123 /* Send message to remote in blocking mode */
|
12345678910>>...30