Home
last modified time | relevance | path

Searched +full:firmware +full:- +full:initialized (Results 1 – 25 of 32) sorted by relevance

12

/Documentation/arm/
Dfirmware.rst2 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/virt/kvm/arm/
Dpsci.rst1 .. SPDX-License-Identifier: GPL-2.0
9 and power-off to the guest.
16 observe two different "firmware" revisions. This could cause issues if
21 In order to remedy this situation, KVM exposes a set of "firmware
22 pseudo-registers" that can be manipulated using the GET/SET_ONE_REG
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
36 - Affects the whole VM (even if the register view is per-vcpu)
[all …]
/Documentation/driver-api/mei/
Dmei.rst1 .. 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/devicetree/bindings/rtc/
Drtc-cmos.txt5 - 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/
Dhost-generic-pci.yaml1 # 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/powerpc/
Dfirmware-assisted-dump.rst2 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/watchdog/
Dpcwd-watchdog.rst24 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/devicetree/bindings/arm/keystone/
Dti,sci.txt1 Texas Instruments System Control Interface (TI-SCI) Message Protocol
2 --------------------------------------------------------------------
11 initialized early into boot process and provides services to Operating Systems
16 TI-SCI controller Device Node:
19 The TI-SCI node describes the Texas Instrument's System Controller entity node.
23 relationship between the TI-SCI parent node to the child node.
26 -------------------
27 - compatible: should be "ti,k2g-sci" for TI 66AK2G SoC
28 should be "ti,am654-sci" for for TI AM654 SoC
29 - mbox-names:
[all …]
/Documentation/driver-api/driver-model/
Ddriver.rst42 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/arm64/
Darm-acpi.rst22 industry-standard ARMv8 servers, they also apply to more than one operating
24 ACPI and Linux only, on an ARMv8 system -- that is, what Linux expects of
29 ----------------
32 exist in Linux for describing non-enumerable hardware, after all. In this
39 - ACPI’s byte code (AML) allows the platform to encode hardware behavior,
44 - ACPI’s OSPM defines a power management model that constrains what the
48 - In the enterprise server environment, ACPI has established bindings (such
51 and x86 would end up using completely different code paths in both firmware
54 - Choosing a single interface to describe the abstraction between a platform
60 - The new ACPI governance process works well and Linux is now at the same
[all …]
/Documentation/admin-guide/pm/
Dintel_idle.rst1 .. SPDX-License-Identifier: GPL-2.0
22 firmware. [To understand ``intel_idle`` it is necessary to know how ``CPUIdle``
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 :doc:`cpuidle`),
65 `below <intel-idle-parameters_>`_.]
[all …]
Dcpufreq.rst1 .. SPDX-License-Identifier: GPL-2.0
20 Operating Performance Points or P-states (in ACPI terminology). As a rule,
24 time (or the more power is drawn) by the CPU in the given P-state. Therefore
29 as possible and then there is no reason to use any P-states different from the
30 highest one (i.e. the highest-performance frequency/voltage configuration
38 put into different P-states.
41 capacity, so as to decide which P-states to put the CPUs into. Of course, since
64 information on the available P-states (or P-state ranges in some cases) and
65 access platform-specific hardware interfaces to change CPU P-states as requested
70 performance scaling algorithms for P-state selection can be represented in a
[all …]
Dintel_pstate.rst1 .. SPDX-License-Identifier: GPL-2.0
24 For the processors supported by ``intel_pstate``, the P-state concept is broader
27 information about that). For this reason, the representation of P-states used
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
38 Since the hardware P-state selection interface used by ``intel_pstate`` is
43 time the corresponding CPU is taken offline and need to be re-initialized when
47 only way to pass early-configuration-time parameters to it is via the kernel
66 -----------
69 hardware-managed P-states (HWP) support. If it works in this mode, the
74 provides its own scaling algorithms for P-state selection. Those algorithms
[all …]
/Documentation/scsi/
Dscsi_mid_low_api.rst1 .. 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 Many LLDs are documented there (e.g. aic7xxx.txt). The SCSI mid-level is
53 scsi-generic.txt (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 …]
DChangeLog.megaraid_sas1 Release Date : Thu. Jun 19, 2014 17:00:00 PST 2014 -
2 (emaild-id:megaraidlinux@lsi.com)
7 Current Version : 06.803.02.00-rc1
8 Old Version : 06.803.01.00-rc1
14 -------------------------------------------------------------------------------
15 Release Date : Mon. Mar 10, 2014 17:00:00 PST 2014 -
16 (emaild-id:megaraidlinux@lsi.com)
20 Current Version : 06.803.01.00-rc1
21 Old Version : 06.700.06.00-rc1
25 4. Add Dell PowerEdge VRTX SR-IOV VF device support.
[all …]
/Documentation/driver-api/media/drivers/
Dcx2341x-devel.rst1 .. 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/driver-api/usb/
Dpower-management.rst1 .. _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/isdn/
Dinterface_capi.rst9 COMMON-ISDN-API (CAPI) is an application programming interface standard used
74 ----------------------
78 the following non-private fields, all to be set by the driver before calling
82 the name of the driver, as a zero-terminated ASCII string
84 the revision number of the driver, as a zero-terminated ASCII string
87 -------------------
94 It contains the following non-private fields:
106 the name of the controller, as a zero-terminated ASCII string
109 the name of the driver, as a zero-terminated ASCII string
112 (optional) pointer to a callback function for sending firmware and
[all …]
/Documentation/admin-guide/
Dkernel-parameters.txt5 force -- enable ACPI if default was off
6 on -- enable ACPI but allow fallback to DT [arm64]
7 off -- disable ACPI if default was on
8 noirq -- do not use ACPI for IRQ routing
9 strict -- Be less tolerant of platforms that are not
11 rsdt -- prefer RSDT over (default) XSDT
12 copy_dsdt -- copy DSDT to memory
26 If set to vendor, prefer vendor-specific driver
35 64 bit X_* addresses. Some firmware have broken 64
58 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]
/Documentation/i2c/
Dwriting-clients.rst19 it for non-exported symbols too. We will use the prefix ``foo_`` in this
28 routines, and should be zero-initialized except for fields with data you
29 provide. A client structure holds device-specific information like the
66 All other fields are for call-back functions which will be explained
74 structure at all. You should use this to keep device-specific data.
85 to NULL in remove() or if probe() failed anymore. The i2c-core does this
99 but many chips have some kind of register-value idea that can easily
107 if (reg < 0x10) /* byte-sized register */
109 else /* word-sized register */
115 if (reg == 0x10) /* Impossible to write - driver error! */
[all …]
/Documentation/x86/
Dpat.rst1 .. SPDX-License-Identifier: GPL-2.0
20 WB Write-back
22 WC Write-combined
23 WT Write-through
24 UC- Uncached Minus
38 +------------------------+----------+--------------+------------------+
40 +------------------------+----------+--------------+------------------+
41 | ioremap | -- | UC- | UC- |
42 +------------------------+----------+--------------+------------------+
43 | ioremap_cache | -- | WB | WB |
[all …]
/Documentation/networking/
Dtls-offload.rst1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
13 For details regarding the user-facing interface refer to the TLS
18 * Software crypto mode (``TLS_SW``) - CPU handles the cryptography.
24 * Packet-based NIC offload mode (``TLS_HW``) - the NIC handles crypto
28 (``ethtool`` flags ``tls-hw-tx-offload`` and ``tls-hw-rx-offload``).
29 * Full TCP NIC offload mode (``TLS_HW_RECORD``) - mode of operation where
30 NIC driver and firmware replace the kernel networking stack
33 abilities or QoS and packet scheduling (``ethtool`` flag ``tls-hw-record``).
36 offload opt-in or opt-out on per-connection basis is not currently supported.
39 --
[all …]
/Documentation/driver-api/pm/
Ddevices.rst1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 management (PM) code is also driver-specific. Most drivers will do very
22 This writeup gives an overview of how drivers interact with system-wide
25 background for the domain-specific work you'd do with any specific driver.
31 Drivers will use one or both of these models to put devices into low-power
36 Drivers can enter low-power states as part of entering system-wide
37 low-power states like "suspend" (also known as "suspend-to-RAM"), or
39 "suspend-to-disk").
42 by implementing various role-specific suspend and resume methods to
[all …]
/Documentation/filesystems/
Dfsverity.rst1 .. SPDX-License-Identifier: GPL-2.0
6 fs-verity: read-only file-based authenticity protection
12 fs-verity (``fs/verity/``) is a support layer that filesystems can
14 of read-only files. Currently, it is supported by the ext4 and f2fs
15 filesystems. Like fscrypt, not too much filesystem-specific code is
16 needed to support fs-verity.
18 fs-verity is similar to `dm-verity
19 <https://www.kernel.org/doc/Documentation/device-mapper/verity.txt>`_
21 filesystems supporting fs-verity, userspace can execute an ioctl that
23 it to a filesystem-specific location associated with the file.
[all …]
/Documentation/admin-guide/mm/
Dnuma_memory_policy.rst12 supported platforms with Non-Uniform Memory Access architectures since 2.4.?.
18 (``Documentation/admin-guide/cgroup-v1/cpusets.rst``)
21 programming interface that a NUMA-aware application can take advantage of. When
30 ------------------------
43 not to overload the initial boot node with boot-time
47 this is an optional, per-task policy. When defined for a
63 In a multi-threaded task, task policies apply only to the thread
100 mapping-- i.e., at Copy-On-Write.
103 virtual address space--a.k.a. threads--independent of when
108 are NOT inheritable across exec(). Thus, only NUMA-aware
[all …]

12