Searched full:fuse (Results 1 – 25 of 38) sorted by relevance
12
27 qcom,opp-fuse-level:29 A positive value representing the fuse corner/level associated with30 this OPP node. Sometimes several corners/levels shares a certain fuse31 corner/level. A fuse corner/level contains e.g. ref uV, min uV,39 - qcom,opp-fuse-level53 qcom,opp-fuse-level = <1>;57 qcom,opp-fuse-level = <2>;61 qcom,opp-fuse-level = <3>;
4 $id: http://devicetree.org/schemas/fuse/nvidia,tegra20-fuse.yaml#7 title: NVIDIA Tegra FUSE block38 - const: fuse45 - const: fuse81 fuse@7000f800 {85 clock-names = "fuse";87 reset-names = "fuse";
4 $id: http://devicetree.org/schemas/fuse/renesas,rcar-efuse.yaml#7 title: R-Car E-FUSE connected to PFC13 The E-FUSE is a type of non-volatile memory, which is accessible through the24 description: PFC System Group Fuse Control and Monitor register block49 fuse: fuse@e6078800 {
4 $id: http://devicetree.org/schemas/fuse/renesas,rcar-otp.yaml#7 title: R-Car E-FUSE connected to OTP_MEM13 The E-FUSE is a type of non-volatile memory, which is accessible through the
1 What: /sys/fs/fuse/features/fuse_bpf5 Read-only file that contains the word 'supported' if fuse-bpf is8 What: /sys/fs/fuse/features/fuse_passthrough12 Read-only file that contains the word 'supported' if fuse16 What: /sys/fs/fuse/bpf_prog_type_fuse21 may be passed to fuse-bpf. For upstream bpf program types, this
1 What: /sys/devices/*/<our-device>/fuse8 as decoded from the fuse registers. Bits order/assignment
15 and FUSE.70 mount that is prone to get stuck, or a FUSE mount which cannot83 in case of an NFS mount that is prone to get stuck, or a FUSE mount111 mount that is prone to get stuck, a FUSE mount which cannot be
46 ro, rw, context, etc. It also supports FUSE mount options.58 Since the virtio-fs device uses the FUSE protocol for file system requests, the59 virtiofs file system for Linux is integrated closely with the FUSE file system60 client. The guest acts as the FUSE client while the host acts as the FUSE61 server. The /dev/fuse interface between the kernel and userspace is replaced64 FUSE requests are placed into a virtqueue and processed by the host. The68 Mapping /dev/fuse to virtqueues requires solving differences in semantics69 between /dev/fuse and virtqueues. Each time the /dev/fuse device is read, the70 FUSE client may choose which request to transfer, making it possible to
4 FUSE title37 What is FUSE?40 FUSE is a userspace filesystem framework. It consists of a kernel41 module (fuse.ko), a userspace library (libfuse.*) and a mount utility44 One of the most important features of FUSE is allowing secure,50 `FUSE homepage: <https://github.com/libfuse/>`_57 fuse58 This is the usual way to mount a FUSE filesystem. The first72 obtained by opening the FUSE device ('/dev/fuse').84 By default FUSE doesn't check file access permissions, the[all …]
4 Fuse I/O Modes7 Fuse supports the following I/O modes:40 assumes that all changes to the filesystem go through the FUSE kernel module
98 fuse99 fuse-io
71 - description: Fuse revision112 qcom,opp-fuse-level = <1>;116 qcom,opp-fuse-level = <2>;120 qcom,opp-fuse-level = <3>;
7 title: Freescale Layerscape Security Fuse Processor13 SFP is the security fuse processor which among other things provides a
8 reg : Address and length of OTP controller and fuse map registers
200 qcom,opp-fuse-level = <1>;204 qcom,opp-fuse-level = <2>;208 qcom,opp-fuse-level = <3>;
31 - fuse108 clock-names = "gpu", "pwr", "fuse";
33 Override crystal frequency as determined from fuse bits.
35 - const: fuse137 clock-names = "nvdec", "fuse", "tsec_pka";
77 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
73 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
13 NXP i.MX8M series SoCs contain fuse entries from which SoC Unique ID can be
83 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
54 Deprecated property, phandle pointer to fuse controller that contains
17 fuse bank for device configurations.
293 FUSE subsection487 FUSE subsection