Searched +full:firmware +full:- +full:initialized (Results 1 – 25 of 47) sorted by relevance
12
| /Documentation/arch/arm/ |
| D | firmware.rst | 2 Interface for registering and calling firmware-specific operations for ARM
7 Some boards are running with secure firmware running in TrustZone secure
8 world, which changes the way some things have to be initialized. This makes
9 a need to provide an interface for such platforms to specify available firmware
12 Firmware operations can be specified by filling in a struct firmware_ops
18 The ops pointer must be non-NULL. More information about struct firmware_ops
19 and its members can be found in arch/arm/include/asm/firmware.h header.
22 set anything if platform does not require firmware operations.
24 To call a firmware operation, a helper macro is provided::
27 ((firmware_ops->op) ? firmware_ops->op(__VA_ARGS__) : (-ENOSYS))
[all …]
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | nxp,88w8987-bt.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/bluetooth/nxp,88w8987-bt.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 This binding describes UART-attached NXP bluetooth chips. These chips
11 are dual-radio chips supporting WiFi and Bluetooth. The bluetooth
12 works on standard H4 protocol over 4-wire UART. The RTS and CTS lines
14 asserts break signal over UART-TX line to put the chip into power save
15 state. De-asserting break wakes up the BT chip.
18 - Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-firmware | 1 What: /sys/class/firmware/.../data
5 Description: The data sysfs file is used for firmware-fallback and for
6 firmware uploads. Cat a firmware image to this sysfs file
7 after you echo 1 to the loading sysfs file. When the firmware
9 sequence will signal the completion of the firmware write and
10 signal the lower-level driver that the firmware data is
13 What: /sys/class/firmware/.../cancel
17 Description: Write-only. For firmware uploads, write a "1" to this file to
18 request that the transfer of firmware data to the lower-level
21 progress) or (ENODEV) if there is no firmware update in progress.
[all …]
|
| /Documentation/driver-api/mei/ |
| D | mei.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 resource (Co-processor) residing inside certain Intel chipsets. The Intel ME
18 each client has its own protocol. The protocol is message-based with a
34 The driver is transparent to data that are passed between firmware feature
50 .. code-block:: C
83 -------------------------
84 Connect to firmware Feature/Client.
86 .. code-block:: none
96 struct mei_connect_client_data - contain the following
99 in_client_uuid - GUID of the FW Feature that needs
[all …]
|
| /Documentation/iio/ |
| D | bno055.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 became locked (the IMU firmware controls them).
30 The user can save this blob in a firmware file (i.e. in /lib/firmware) that
31 the driver looks for at probe time. If found, then the IMU is initialized
44 bno055-caldata-0e7c26a33541515120204a35342b04ff.dat
45 bno055-caldata.dat
47 In non-fusion mode the IIO 'offset' attributes provide access to the
50 needed (the IMU firmware internally applies those corrections) and they
|
| /Documentation/devicetree/bindings/rtc/ |
| D | rtc-cmos.txt | 5 - compatible : "motorola,mc146818"
6 - reg : should contain registers location and length.
9 - interrupts : should contain interrupt.
10 - ctrl-reg : Contains the initial value of the control register also
12 - freq-reg : Contains the initial value of the frequency register also
15 "Register A" and "B" are usually initialized by the firmware (BIOS for
23 interrupt-parent = <&ioapic1>;
24 ctrl-reg = <2>;
25 freq-reg = <0x26>;
|
| /Documentation/devicetree/bindings/pci/ |
| D | host-generic-pci.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/host-generic-pci.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Will Deacon <will@kernel.org>
13 Firmware-initialised PCI host controllers and PCI emulations, such as the
14 virtio-pci implementations found in kvmtool and other para-virtualised
21 Configuration Space is assumed to be memory-mapped (as opposed to being
26 For CAM, this 24-bit offset is:
41 - description:
[all …]
|
| /Documentation/virt/kvm/arm/ |
| D | fw-pseudo-registers.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ARM firmware pseudo-registers interface
12 two different "firmware" revisions. This could cause issues if a given guest
17 In order to remedy this situation, KVM exposes a set of "firmware
18 pseudo-registers" that can be manipulated using the GET/SET_ONE_REG
28 and power-off to the guest.
30 - Only valid if the vcpu has the KVM_ARM_VCPU_PSCI_0_2 feature set
31 (and thus has already been initialized)
32 - Returns the current PSCI version on GET_ONE_REG (defaulting to the
34 - Allows any PSCI version implemented by KVM and compatible with
[all …]
|
| /Documentation/arch/riscv/ |
| D | boot.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 RISC-V Kernel Boot Requirements and Constraints
10 This document describes what the RISC-V kernel expects from bootloaders and
11 firmware, and also the constraints that any developer must have in mind when
16 Pre-kernel Requirements and Constraints
19 The RISC-V kernel expects the following of bootloaders and platform firmware:
22 --------------
24 The RISC-V kernel expects:
30 ---------
32 The RISC-V kernel expects:
[all …]
|
| /Documentation/watchdog/ |
| D | pcwd-watchdog.rst | 24 drivers have initialized, you can then talk to the card using a PC
27 I suggest putting a "watchdog -d" before the beginning of an fsck, and
28 a "watchdog -e -t 1" immediately after the end of an fsck. (Remember
33 tools/testing/selftests/watchdog/watchdog-test.c
45 (Firmware version of the card)
49 WDIOF_* bitwise-anded into the value. (The comments
70 -- Ken Hollis
|
| /Documentation/virt/kvm/x86/ |
| D | amd-memory-encryption.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 SEV is an extension to the AMD-V architecture which supports running
46 Hence, the ASID for the SEV-enabled guests must be from 1 to a maximum value
57 of zero if SEV is enabled). If non-NULL, the argument to
74 are defined in ``<linux/psp-dev.h>``.
80 ----------------
91 Returns: 0 on success, -negative on error
127 ``debug_swap`` parameter of ``kvm-amd.ko``.
130 -----------------------
134 the owner's public Diffie-Hellman (PDH) key and session information.
[all …]
|
| /Documentation/arch/x86/ |
| D | tdx.rst | 1 .. SPDX-License-Identifier: GPL-2.0
18 CPU-attested software module called 'the TDX module' runs inside the new
22 TDX also leverages Intel Multi-Key Total Memory Encryption (MKTME) to
23 provide crypto-protection to the VMs. TDX reserves part of MKTME KeyIDs
28 must be loaded into the isolated range and properly initialized. The TDX
32 TDX boot-time detection
33 -----------------------
41 ---------------------------------------
59 Besides initializing the TDX module, a per-cpu initialization SEAMCALL
89 User can consult dmesg to see whether the TDX module has been initialized.
[all …]
|
| D | iommu.rst | 7 - Intel: http://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/vt-dire…
8 - AMD: https://www.amd.com/content/dam/amd/en/documents/processor-tech-docs/specifications/48882_3_…
13 -----------
21 - DMAR - Intel DMA Remapping table
22 - DRHD - Intel DMA Remapping Hardware Unit Definition
23 - RMRR - Intel Reserved Memory Region Reporting Structure
24 - IVRS - AMD I/O Virtualization Reporting Structure
25 - IVDB - AMD I/O Virtualization Definition Block
26 - IVHD - AMD I/O Virtualization Hardware Definition
41 The architecture defines an ACPI-compatible data structure called an I/O
[all …]
|
| /Documentation/devicetree/bindings/arm/keystone/ |
| D | ti,sci.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI-SCI controller
10 - Nishanth Menon <nm@ti.com>
20 initialized early into boot process and provides services to Operating Systems
23 See https://software-dl.ti.com/tisci/esd/latest/index.html for protocol definition.
25 The TI-SCI node describes the Texas Instrument's System Controller entity node.
29 relationship between the TI-SCI parent node to the child node.
33 pattern: "^system-controller@[0-9a-f]+$"
[all …]
|
| /Documentation/arch/powerpc/ |
| D | firmware-assisted-dump.rst | 2 Firmware-Assisted Dump
7 The goal of firmware-assisted dump is to enable the dump of
8 a crashed system, and to do so from a fully-reset system, and
12 - Firmware-Assisted Dump (FADump) infrastructure is intended to replace
14 - Fadump uses the same firmware interfaces and memory reservation model
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
19 - Unlike phyp dump, userspace tool does not need to refer any sysfs
21 - Unlike phyp dump, FADump allows user to release all the memory reserved
23 - Once enabled through kernel boot parameter, FADump can be
28 Comparing with kdump or other strategies, firmware-assisted
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | driver.rst | 42 model because the bus they belong to has a bus-specific structure with
43 bus-specific fields that cannot be generalized.
48 completely bus-specific. Defining them as bus-specific entities would
49 sacrifice type-safety, so we keep bus-specific structures around.
51 Bus-specific drivers should include a generic struct device_driver in
52 the definition of the bus-specific driver. Like this::
59 A definition that included bus-specific fields would look like
85 no bus-specific fields (i.e. don't have a bus-specific driver
89 Most drivers, however, will have a bus-specific structure and will
105 define generic callbacks that forward the call to the bus-specific
[all …]
|
| /Documentation/driver-api/fpga/ |
| D | fpga-mgr.rst | 5 --------
14 contiguous buffer, or a firmware file. Because allocating contiguous kernel
20 FPGA image as well as image-specific particulars such as whether the image was
24 --------------------------------
39 struct device *dev = &pdev->dev;
46 return -ENOMEM;
90 struct fpga_image_info. Before parse_header call, header_size is initialized
97 whole buffer will be passed into .parse_header. If image is in scatter-gather
100 size into info->header_size and return -EAGAIN, then it will be called again
104 buffer passed into .write_init will be at least info->header_size bytes long;
[all …]
|
| /Documentation/arch/arm64/ |
| D | arm-acpi.rst | 23 industry-standard Arm systems, they also apply to more than one operating
25 ACPI and Linux only, on an Arm system -- that is, what Linux expects of
30 ----------------
33 exist in Linux for describing non-enumerable hardware, after all. In this
40 - ACPI’s byte code (AML) allows the platform to encode hardware behavior,
45 - ACPI’s OSPM defines a power management model that constrains what the
49 - In the enterprise server environment, ACPI has established bindings (such
52 and x86 would end up using completely different code paths in both firmware
55 - Choosing a single interface to describe the abstraction between a platform
61 - The new ACPI governance process works well and Linux is now at the same
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | intel_idle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
22 firmware. [To understand ``intel_idle`` it is necessary to know how ``CPUIdle``
24 Documentation/admin-guide/pm/cpuidle.rst if you have not done that yet.]
28 processor's functional blocks into low-power states. That instruction takes two
34 via the platform firmware configuration menu) or which do not support that
38 only way to pass early-configuration-time parameters to it is via the kernel
42 .. _intel-idle-enumeration-of-states:
50 as C-states (in the ACPI terminology) or idle states. The list of meaningful
51 ``MWAIT`` hint values and idle states (i.e. low-power configurations of the
56 subsystem (see :ref:`idle-states-representation` in
[all …]
|
| /Documentation/scsi/ |
| D | scsi_mid_low_api.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 SCSI mid_level - lower_level driver interface
14 (SCSI terminology, see SAM-3 at http://www.t10.org) sends SCSI commands
22 Examples are the usb-storage driver (found in the drivers/usb/storage
30 HBAs. These HBAs might be either on PCI daughter-boards or built into
33 has its own PCI device address. [The one-to-one correspondence between
49 documented in Documentation/scsi (e.g. aic7xxx.rst). The SCSI mid-level is
53 scsi-generic.rst (for the sg driver).
68 and OS-specific code (e.g. FreeBSD and Linux). Such drivers tend to have
108 pointer members not explicitly initialized.
[all …]
|
| /Documentation/mm/ |
| D | physical_memory.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 architecture-independent abstraction to represent the physical memory. This
13 `Non-Uniform Memory Access (NUMA)
14 <https://en.wikipedia.org/wiki/Non-uniform_memory_access>`_.
15 With multi-core and multi-socket machines, memory may be arranged into banks
42 memory with DMA specific requirements (Documentation/core-api/dma-api.rst),
47 ``CONFIG_ZONE_DMA32`` configuration options. Some 64-bit platforms may need
59 only on some 32-bit architectures and is enabled with ``CONFIG_HIGHMEM``.
69 Documentation/admin-guide/mm/memory-hotplug.rst for additional details.
82 map reported by the firmware, architectural constraints for memory addressing
[all …]
|
| /Documentation/driver-api/usb/ |
| D | power-management.rst | 1 .. _usb-power-management:
7 :Date: Last-updated: February 2014
11 ---------
17 * Changing the default idle-delay time
31 -------------------------
35 component is ``suspended`` it is in a nonfunctional low-power state; it
37 ``resumed`` (returned to a functional full-power state) when the kernel
67 ----------------------
85 --------------------------
101 -------------------
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 20 - The physical memory available to a machine can be adjusted at runtime, up- or
25 - Replacing hardware, such as DIMMs or whole NUMA nodes, without downtime. One
28 - Reducing energy consumption either by physically unplugging memory modules or
32 used to expose persistent memory, other performance-differentiated memory and
39 ------------------------------
54 ------------------------
62 for the direct mapping, is allocated and initialized, and memory blocks are
71 --------------------------
90 systems that support ACPI; mechanisms specific to other firmware interfaces or
94 ------------------
[all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | cx2341x-devel.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 -----------------------
12 .. note:: the memory long words are little-endian ('intel format').
21 .. code-block:: none
23 ivtvctl -O min=0x02000000,max=0x020000ff
26 register space :-).
35 .. code-block:: none
37 0x00000000-0x00ffffff Encoder memory space
38 0x00000000-0x0003ffff Encode.rom
39 ???-??? MPEG buffer(s)
[all …]
|
| /Documentation/power/ |
| D | energy-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 -----------
12 subsystems willing to use that information to make energy-aware decisions.
16 devicetree data in some cases. In others, the firmware will know better.
18 each and every client subsystem to re-implement support for each and every
23 The power values might be expressed in micro-Watts or in an 'abstract scale'.
26 can be found in the Energy-Aware Scheduler documentation
27 Documentation/scheduler/sched-energy.rst. For some subsystems like thermal or
30 thus the real micro-Watts might be needed. An example of these requirements can
32 Documentation/driver-api/thermal/power_allocator.rst.
[all …]
|
12