Searched full:proxy (Results 1 – 25 of 39) sorted by relevance
12
| /Documentation/devicetree/bindings/mailbox/ |
| D | ti,secure-proxy.yaml | 4 $id: http://devicetree.org/schemas/mailbox/ti,secure-proxy.yaml#
7 title: Texas Instruments' Secure Proxy
13 The Texas Instruments' secure proxy is a mailbox controller that has
25 const: ti,am654-secure-proxy
30 Contains the secure proxy thread ID used for the specific transfer path.
48 secure proxy thread in the form 'rx_<PID>'.
55 proxy.
71 compatible = "ti,am654-secure-proxy";
|
| D | ti,message-manager.txt | 15 - reg-names queue_proxy_region - Map the queue proxy region.
19 - #mbox-cells Shall be 2. Contains the queue ID and proxy ID in that
45 # RX queue ID is 5, proxy ID is 2
46 # TX queue ID is 0, proxy ID is 0
|
| /Documentation/filesystems/nfs/ |
| D | rpc-server-gss.rst | 71 called gss-proxy, implemented by a userspace program called Gssproxy.
74 <https://fedorahosted.org/gss-proxy/wiki/ProtocolDocumentation>`_.
84 legacy mechanism. To switch to the new mechanism, gss-proxy must bind
86 /proc/net/rpc/use-gss-proxy. If gss-proxy dies, it must repeat both
92 from /proc/net/rpc/use-gss-proxy and checking that it contains a
93 "1"--the read will block until gss-proxy has done its write to the file.
|
| /Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 2 Virtual TPM Proxy Driver for Linux Containers
9 proxy device driver for Linux containers.
31 To support this, the virtual TPM proxy driver provides a device ``/dev/vtpmx``
|
| /Documentation/networking/ |
| D | tproxy.rst | 4 Transparent proxy support
7 This feature adds Linux 2.2-like transparent proxy support to current kernels.
11 From Linux 4.18 transparent proxy support is also available in nf_tables.
76 Note that for this to work you'll have to modify the proxy to enable (SOL_IP,
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | dcsr.txt | 347 Core Service Bridge Proxy
351 There is one Core Service Bridge Proxy device for each CPU in the system.
360 of the form "fsl,dcsr-<cpu>-sb-proxy" in addition to the
361 generic compatible string "fsl,dcsr-cpu-sb-proxy".
375 dcsr-cpu-sb-proxy@40000 {
376 compatible = "fsl,dcsr-e500mc-sb-proxy",
377 "fsl,dcsr-cpu-sb-proxy";
381 dcsr-cpu-sb-proxy@41000 {
382 compatible = "fsl,dcsr-e500mc-sb-proxy",
383 "fsl,dcsr-cpu-sb-proxy";
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,msm8916-mss-pil.yaml | 60 - description: XO proxy clock (control handed over after startup)
71 - description: CX proxy power domain (control handed over after startup)
72 - description: MX proxy power domain (control handed over after startup)
73 - description: MSS proxy power domain (control handed over after startup)
85 description: PLL proxy supply (control handed over after startup)
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | k3-ringacc.yaml | 41 - description: proxy gcfg registers regions
42 - description: proxy target registers regions
|
| D | keystone-navigator-qmss.txt | 41 - Queue Management/Queue Proxy region for queue Push.
42 - Queue Management/Queue Proxy region for queue Pop.
47 - Queue Management/Queue Proxy region for queue Push/Pop.
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,q6prm.yaml | 7 title: Qualcomm Proxy Resource Manager (Q6PRM)
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,apr-services.yaml | 35 2 = Proxy Resource Manager Service.
|
| /Documentation/devicetree/bindings/pci/ |
| D | ti,j721e-pci-host.yaml | 41 ti,syscon-acspcie-proxy-ctrl:
45 - description: Phandle to the ACSPCIE Proxy Control Register
|
| /Documentation/virt/gunyah/ |
| D | index.rst | 31 2. "Proxy" scheduling in which an owner-VM can donate the remainder of its
65 proxy-scheduled vCPUs can be handled directly by Linux to provide Type-2
|
| /Documentation/devicetree/bindings/soc/fsl/ |
| D | fsl,qman-fqd.yaml | 18 for BMan Free Buffer Proxy Records (FBPR). This memory is reserved/allocated as
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-priority.rst | 61 example monitoring VBI transmissions. A proxy application running
|
| D | format.rst | 90 seems useless, but there are applications serving as proxy between
|
| /Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 70 There is also a gdb proxy for firewire which allows to use gdb to access
74 The latest version of this gdb proxy (fireproxy-0.34) can communicate (not
|
| /Documentation/bpf/ |
| D | prog_sk_lookup.rst | 26 2. receiving connections on all or a wide range of ports, i.e. an L7 proxy use
|
| /Documentation/driver-api/ |
| D | dma-buf.rst | 247 * Proxy fences, proposed to handle &drm_syncobj for which the fence has not yet
285 userspace -> kernel [label="Future fence, fence proxy, ..."]
300 * No future fences, proxy fences or userspace fences imported as DMA fences,
|
| /Documentation/virt/kvm/s390/ |
| D | s390-diag.rst | 65 the subchannel of the virtio-ccw proxy device to be notified.
|
| /Documentation/driver-api/usb/ |
| D | typec_bus.rst | 27 The port alternate mode devices are used as a proxy between the partner and the
|
| /Documentation/dev-tools/ |
| D | kgdb.rst | 258 protocol. You must manually send a :kbd:`SysRq-G` unless you have a proxy
259 that splits console output to a terminal program. A console proxy has a
261 "human" console. The proxy can take care of sending the :kbd:`SysRq-G`
264 When using kgdboc with no debugger proxy, you can end up connecting the
273 on the initial connect, or to use a debugger proxy that allows an
|
| /Documentation/devicetree/bindings/mfd/ |
| D | syscon.yaml | 117 - ti,j784s4-acspcie-proxy-ctrl
|
| /Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | overview.rst | 401 plays a role of being a proxy between the PHY driver and the
402 MC. It does this proxy via the MC commands to a DPMAC object.
|
| /Documentation/driver-api/media/drivers/ |
| D | pvrusb2.rst | 109 (proxy through USB instead of PCI) are enough different that this
|
12