| /Linux-v6.6/drivers/gpu/drm/i915/gt/uc/ |
| D | intel_gsc_proxy.c | 20 * GSC proxy:
24 * and back. i915 must manually start the proxy flow after the GSC is loaded to
28 * The proxy flow is as follow:
30 * 2 - GSC replies with the proxy header + payload for CSME
31 * 3 - i915 sends the reply from GSC as-is to CSME via the mei proxy component
32 * 4 - CSME replies with the proxy header + payload for GSC
49 /* FW-defined proxy header */
53 * Bits 0-7: type of the proxy message (see enum intel_gsc_proxy_type)
55 * Bits 16-31: length in bytes of the payload following the proxy header
61 u32 source; /* Source of the Proxy message */
[all …]
|
| D | intel_gsc_uc.c | 34 /* setup proxy on a new load */ in gsc_work()
40 * The HuC auth can be done both before or after the proxy init; in gsc_work()
41 * if done after, a proxy request will be issued and must be in gsc_work()
43 * Since this worker also handles proxy requests, we can't in gsc_work()
44 * perform an action that requires the proxy from within it and in gsc_work()
47 * first and do proxy later. The GSC will ack the HuC auth and in gsc_work()
48 * then send the HuC proxy request as part of the proxy init in gsc_work()
60 gt_err(gt, "Proxy request received with GSC not loaded!\n"); in gsc_work()
68 * A proxy failure right after firmware load means the proxy-init in gsc_work()
72 "GSC proxy handler failed to init\n"); in gsc_work()
[all …]
|
| /Linux-v6.6/include/drm/ |
| D | i915_gsc_proxy_mei_interface.h | 15 * struct i915_gsc_proxy_component_ops - ops for GSC Proxy services.
17 * @send: sends a proxy message from GSC FW to ME FW
18 * @recv: receives a proxy message for GSC FW from ME FW
24 * send - Sends a proxy message to ME FW.
33 * recv - Receives a proxy message from ME FW.
44 * MEI drivers for GSC proxy services
45 * @mei_dev: device that provide the GSC proxy service.
46 * @ops: Ops implemented by GSC proxy driver, used by i915 driver.
|
| /Linux-v6.6/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
|
| /Linux-v6.6/arch/powerpc/boot/dts/fsl/ |
| D | p4080si-post.dtsi | 218 dcsr-cpu-sb-proxy@40000 {
219 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
223 dcsr-cpu-sb-proxy@41000 {
224 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
228 dcsr-cpu-sb-proxy@42000 {
229 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
233 dcsr-cpu-sb-proxy@43000 {
234 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
238 dcsr-cpu-sb-proxy@44000 {
239 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
[all …]
|
| D | t4240si-post.dtsi | 250 dcsr-cpu-sb-proxy@100000 {
251 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
255 dcsr-cpu-sb-proxy@108000 {
256 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
260 dcsr-cpu-sb-proxy@110000 {
261 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
265 dcsr-cpu-sb-proxy@118000 {
266 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
270 dcsr-cpu-sb-proxy@120000 {
271 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
[all …]
|
| D | b4860si-post.dtsi | 93 dcsr-cpu-sb-proxy@108000 {
94 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
98 dcsr-cpu-sb-proxy@110000 {
99 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
103 dcsr-cpu-sb-proxy@118000 {
104 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
|
| D | p2041si-post.dtsi | 212 dcsr-cpu-sb-proxy@40000 {
213 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
217 dcsr-cpu-sb-proxy@41000 {
218 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
222 dcsr-cpu-sb-proxy@42000 {
223 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
227 dcsr-cpu-sb-proxy@43000 {
228 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
|
| D | p3041si-post.dtsi | 239 dcsr-cpu-sb-proxy@40000 {
240 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
244 dcsr-cpu-sb-proxy@41000 {
245 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
249 dcsr-cpu-sb-proxy@42000 {
250 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
254 dcsr-cpu-sb-proxy@43000 {
255 compatible = "fsl,dcsr-e500mc-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
|
| D | p5040si-post.dtsi | 191 dcsr-cpu-sb-proxy@40000 {
192 compatible = "fsl,dcsr-e5500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
196 dcsr-cpu-sb-proxy@41000 {
197 compatible = "fsl,dcsr-e5500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
201 dcsr-cpu-sb-proxy@42000 {
202 compatible = "fsl,dcsr-e5500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
206 dcsr-cpu-sb-proxy@43000 {
207 compatible = "fsl,dcsr-e5500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
|
| D | t1040si-post.dtsi | 216 dcsr-cpu-sb-proxy@100000 {
217 compatible = "fsl,dcsr-e5500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
221 dcsr-cpu-sb-proxy@108000 {
222 compatible = "fsl,dcsr-e5500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
226 dcsr-cpu-sb-proxy@110000 {
227 compatible = "fsl,dcsr-e5500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
231 dcsr-cpu-sb-proxy@118000 {
232 compatible = "fsl,dcsr-e5500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
|
| D | t2081si-post.dtsi | 220 dcsr-cpu-sb-proxy@100000 {
221 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
225 dcsr-cpu-sb-proxy@108000 {
226 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
230 dcsr-cpu-sb-proxy@110000 {
231 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
235 dcsr-cpu-sb-proxy@118000 {
236 compatible = "fsl,dcsr-e6500-sb-proxy", "fsl,dcsr-cpu-sb-proxy";
|
| /Linux-v6.6/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.
|
| /Linux-v6.6/include/uapi/linux/ |
| D | vtpm_proxy.h | 3 * Definitions for the VTPM proxy driver
24 * enum vtpm_proxy_flags - flags for the proxy TPM
25 * @VTPM_PROXY_FLAG_TPM2: the proxy TPM uses TPM 2.0 protocol
34 * @flags: flags for the proxy TPM
36 * @fd: the file descriptor used by the proxy TPM
|
| /Linux-v6.6/security/apparmor/ |
| D | label.c | 42 static void free_proxy(struct aa_proxy *proxy) in free_proxy() argument
44 if (proxy) { in free_proxy()
46 aa_put_label(rcu_dereference_protected(proxy->label, true)); in free_proxy()
47 memset(proxy, 0, sizeof(*proxy)); in free_proxy()
48 RCU_INIT_POINTER(proxy->label, (struct aa_label *)PROXY_POISON); in free_proxy()
49 kfree(proxy); in free_proxy()
55 struct aa_proxy *proxy = container_of(kref, struct aa_proxy, count); in aa_proxy_kref() local
57 free_proxy(proxy); in aa_proxy_kref()
81 tmp = rcu_dereference_protected(orig->proxy->label, in __aa_proxy_redirect()
83 rcu_assign_pointer(orig->proxy->label, aa_get_label(new)); in __aa_proxy_redirect()
[all …]
|
| /Linux-v6.6/security/apparmor/include/ |
| D | label.h | 116 * @proxy: is set to the label that replaced this label
127 struct aa_proxy *proxy; member
281 struct aa_label *aa_label_alloc(int size, struct aa_proxy *proxy, gfp_t gfp);
427 AA_BUG(!l->proxy); in aa_get_newest_label()
428 AA_BUG(!l->proxy->label); in aa_get_newest_label()
433 tmp = aa_get_label_rcu(&l->proxy->label); in aa_get_newest_label()
452 static inline struct aa_proxy *aa_get_proxy(struct aa_proxy *proxy) in aa_get_proxy() argument
454 if (proxy) in aa_get_proxy()
455 kref_get(&(proxy->count)); in aa_get_proxy()
457 return proxy; in aa_get_proxy()
[all …]
|
| /Linux-v6.6/drivers/misc/mei/gsc_proxy/ |
| D | Kconfig | 5 tristate "Intel GSC Proxy services of ME Interface"
9 MEI Support for GSC Proxy Services on Intel platforms.
11 MEI GSC proxy enables messaging between GSC service on
|
| D | mei_gsc_proxy.c | 10 * proxy user (I915) and ME FW by proxying messages to ME FW
24 * mei_gsc_proxy_send - Sends a proxy message to ME FW.
45 * mei_gsc_proxy_recv - Receives a proxy message from ME FW.
98 * Intel VGA adapter, the subcomponent is SW Proxy
208 MODULE_DESCRIPTION("MEI GSC PROXY");
|
| /Linux-v6.6/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";
|
| /Linux-v6.6/drivers/soc/ti/ |
| D | k3-ringacc.c | 72 * struct k3_ringacc_proxy_gcfg_regs - RA Proxy Global Config MMIO Region
85 * struct k3_ringacc_proxy_target_regs - Proxy Datapath MMIO Region
87 * @control: Proxy Control Register
88 * @status: Proxy Status Register
90 * @data: Proxy Data Register
142 * @proxy: Ring Proxy Datapath registers
154 * @proxy_id: RA Ring Proxy Id (only if @K3_RINGACC_RING_USE_PROXY)
161 struct k3_ringacc_proxy_target_regs __iomem *proxy; member
190 * @proxy_gcfg: RA proxy global config registers
191 * @proxy_target_base: RA proxy datapath region
[all …]
|
| /Linux-v6.6/drivers/mailbox/ |
| D | ti-msgmgr.c | 24 #define Q_DATA_OFFSET(proxy, queue, reg) \ argument
25 ((0x10000 * (proxy)) + (0x80 * (queue)) + ((reg) * 4))
43 * @proxy_id: Proxy ID representing the processor in SoC
57 * @data_first_reg: First data register for proxy data region
58 * @data_last_reg: Last data register for proxy data region
64 * @data_region_name: Name of the proxy data region
65 * @status_region_name: Name of the proxy status region
66 * @ctrl_region_name: Name of the proxy control region
68 * @is_sproxy: Is this an Secure Proxy instance?
95 * @proxy_id: Proxy Identifier as mapped on SoC
[all …]
|
| /Linux-v6.6/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,
|
| /Linux-v6.6/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)
|
| /Linux-v6.6/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``
|
