Searched +full:open +full:- +full:firmware (Results 1 – 25 of 88) sorted by relevance
1234
| /Documentation/arch/powerpc/ |
| D | booting.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------
9 bootloader <-> kernel interfaces, in order to avoid the degeneration that had
14 merged architecture for ppc32 and ppc64, new 32-bit platforms and 32-bit
19 of a device-tree whose format is defined after Open Firmware specification.
21 doesn't require the device-tree to represent every device in the system and only
41 a) Boot from Open Firmware. If your firmware is compatible
42 with Open Firmware (IEEE 1275) or provides an OF compatible
47 bindings to powerpc. Only the 32-bit client interface
54 extract the device-tree and other information from open
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 3 PCI Bus Binding to: IEEE Std 1275-1994
4 https://www.devicetree.org/open-firmware/bindings/pci/pci2_1.pdf
8 Open Firmware Recommended Practice: Interrupt Mapping
9 https://www.devicetree.org/open-firmware/practice/imap/imap0_9d.pdf
14 - linux,pci-domain:
21 - max-link-speed:
27 - reset-gpios:
30 - supports-clkreq:
34 not to advertise ASPM L1 Sub-States support if there is no CLKREQ signal.
36 PCI-PCI Bridge properties
[all …]
|
| /Documentation/arch/arm/keystone/ |
| D | knav-qmss.rst | 11 multi-core Navigator. QMSS consist of queue managers, packed-data structure
15 management of the packet queues. Packets are queued/de-queued by writing or
24 knav qmss driver provides a set of APIs to drivers to open/close qmss queues,
29 Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
31 Accumulator QMSS queues using PDSP firmware
33 The QMSS PDSP firmware support accumulator channel that can monitor a single
37 1 or 32 queues per channel. More description on the firmware is available in
40 git://git.ti.com/keystone-rtos/qmss-lld.git
42 k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports upto 48 accumulator
43 channels. This firmware is available under ti-keystone folder of
[all …]
|
| /Documentation/usb/ |
| D | gadget_printer.rst | 14 This driver may be used if you are writing printer firmware using Linux as
24 This driver is structured for printer firmware that runs in user mode. The
25 user mode printer firmware will read and write data from the kernel mode
28 user space firmware can read or write this status byte using a device file
29 /dev/g_printer . Both blocking and non-blocking read/write calls are supported.
62 to put your firmware version here.
97 gcc prn_example.c -o prn_example
103 # prn_example -read_data
108 # cat data_file | prn_example -write_data
113 # prn_example -get_status
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-block-aoe | 25 "down,closewait" state shows that the device is still open and
32 What: /sys/block/etherd*/firmware-version
37 (RO) Version of the firmware in the target.
|
| /Documentation/driver-api/gpio/ |
| D | intro.rst | 17 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
25 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
26 non-dedicated pin can be configured as a GPIO; and most chips have at least
31 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
32 firmware knowing how they're used).
36 - Output values are writable (high=1, low=0). Some chips also have
38 value might be driven, supporting "wire-OR" and similar schemes for the
39 other value (notably, "open drain" signaling).
41 - Input values are likewise readable (1, 0). Some chips support readback
42 of pins configured as "output", which is very useful in such "wire-OR"
[all …]
|
| /Documentation/devicetree/ |
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Open Firmware and Devicetree
12 usage-model
14 kernel-api
22 dynamic-resolution-notes
23 overlay-notes
|
| D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0
17 The "Open Firmware Device Tree", or simply Devicetree (DT), is a data
44 ----------
45 The DT was originally created by Open Firmware as part of the
46 communication method for passing data from Open Firmware to a client
52 Since Open Firmware is commonly used on PowerPC and SPARC platforms,
56 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit
57 and 64-bit support, the decision was made to require DT support on all
58 powerpc platforms, regardless of whether or not they used Open
59 Firmware. To do this, a DT representation called the Flattened Device
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 Platforms containing lids convey lid state (open/close) to OSPMs
67 firmware cannot make sure "opened"/"closed" events are paired, the ACPI
78 firmware implementation.
87 B. button.lid_init_state=open:
90 are paired fully relies on the firmware implementation.
111 firmware, the old userspace programs should still work. Otherwise, the
|
| /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
28 /dev/meiX is open. The binding to a specific feature is performed by calling
34 The driver is transparent to data that are passed between firmware feature
50 .. code-block:: C
53 fd = open(MEI_DEVICE);
83 -------------------------
84 Connect to firmware Feature/Client.
86 .. code-block:: none
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | nvidia,tegra20-ehci.txt | 4 SOC is as described in the document "Open Firmware Recommended
9 - compatible : For Tegra20, must contain "nvidia,tegra20-ehci".
10 For Tegra30, must contain "nvidia,tegra30-ehci". Otherwise, must contain
11 "nvidia,<chip>-ehci" plus at least one of the above, where <chip> is
13 - nvidia,phy : phandle of the PHY that the controller is connected to.
14 - clocks : Must contain one entry, for the module clock.
15 See ../clocks/clock-bindings.txt for details.
16 - resets : Must contain an entry for each entry in reset-names.
18 - reset-names : Must include the following entries:
19 - usb
[all …]
|
| D | fsl,usb2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Li <Frank.Li@nxp.com>
14 SOC is as described in the document "Open Firmware Recommended
21 - enum:
22 - fsl-usb2-mph
23 - fsl-usb2-dr
24 - items:
25 - enum:
[all …]
|
| /Documentation/translations/zh_CN/devicetree/ |
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
2 .. include:: ../disclaimer-zh_CN.rst
14 Open Firmware 和 Devicetree
25 usage-model
27 kernel-api
35 dynamic-resolution-notes
36 overlay-notes
|
| /Documentation/tee/ |
| D | op-tee.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 OP-TEE (Open Portable Trusted Execution Environment)
7 The OP-TEE driver handles OP-TEE [1] based TEEs. Currently it is only the ARM
8 TrustZone based OP-TEE solution that is supported.
10 Lowest level of communication with OP-TEE builds on ARM SMC Calling
11 Convention (SMCCC) [2], which is the foundation for OP-TEE's SMC interface
12 [3] used internally by the driver. Stacked on top of that is OP-TEE Message
15 OP-TEE SMC interface provides the basic functions required by SMCCC and some
16 additional functions specific for OP-TEE. The most interesting functions are:
18 - OPTEE_SMC_FUNCID_CALLS_UID (part of SMCCC) returns the version information
[all …]
|
| /Documentation/admin-guide/ |
| D | hw_random.rst | 12 sysfs support, plus a hardware-specific driver that plugs
17 latest version of the "rng-tools" package from:
19 https://github.com/nhorman/rng-tools
28 CHARACTER DEVICE. Using the standard open()
33 output if the hardware "has-data" flag is set, but nevertheless
34 a security-conscious person would run fitness tests on the
37 The rng-tools package uses such tests in "rngd", and lets you
44 "rng_available" attribute lists the hardware-specific drivers
54 - Copyright 2000,2001 Jeff Garzik <jgarzik@pobox.com>
55 - Copyright 2000,2001 Philipp Rumpf <prumpf@mandrakesoft.com>
[all …]
|
| /Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 In order to support ACPI open-ended hardware configurations (e.g. development
8 boards) we need a way to augment the ACPI configuration provided by the firmware
13 recompiling the firmware image with updated ACPI tables, neither is practical:
15 access to firmware tools which are often not publicly available.
18 way to augment firmware ACPI configuration is by dynamically loading
59 ASL Optimizing Compiler version 20140214-64 [Mar 29 2014]
60 Copyright (c) 2000 - 2014 Intel Corporation
62 ASL Input: minnomax.asl - 30 lines, 614 bytes, 7 keywords
63 AML Output: minnowmax.aml - 165 bytes, 6 named objects, 1 executable opcodes
[all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | ipu6.rst | 1 .. SPDX-License-Identifier: GPL-2.0
31 interrupt handling, firmware authentication and global timer sync.
34 ------------------------
51 ---------
60 Security and firmware authentication
61 -------------------------------------
63 To address the IPU6 firmware security concerns, the IPU6 firmware needs to
67 authenticating the IPU6 firmware. The authenticated firmware binary is copied
68 into an isolated memory region. Firmware authentication process is implemented
76 -----------------
[all …]
|
| /Documentation/nvme/ |
| D | feature-and-quirk-policy.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 NVM Express is an open collection of standards and information.
20 - the NVMe Base specification
21 - various Command Set specifications (e.g. NVM Command Set)
22 - various Transport specifications (e.g. PCIe, Fibre Channel, RDMA, TCP)
23 - the NVMe Management Interface specification
32 useful or suitable for specific use-cases. It is important to note that Linux
44 on-wire protocol, does not contradict any of the NVMe specifications.
47 3. Has a clear, indisputable value-proposition and a wide consensus across
62 Sometimes implementations of open standards fail to correctly implement parts
[all …]
|
| /Documentation/admin-guide/media/ |
| D | mgb4.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ---------------
13 There are two types of parameters - global / PCI card related, found under
23 | 0 - No module present
24 | 1 - FPDL3
25 | 2 - GMSL
31 Firmware type.
33 | 1 - FPDL3
34 | 2 - GMSL
37 Firmware version number.
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | fallback-mechanisms.rst | 6 filesystem lookup on the root filesystem or when the firmware simply cannot be
8 configuration options related to supporting the firmware fallback mechanism are:
10 * CONFIG_FW_LOADER_USER_HELPER: enables building the firmware fallback
15 enable the kobject uevent fallback mechanism on all firmware API calls
21 manually load the firmware. Read below for more details.
31 Justifying the firmware fallback mechanism
40 * Races upon resume from suspend. This is resolved by the firmware cache, but
41 the firmware cache is only supported if you use uevents, and its not
44 * Firmware is not accessible through typical means:
47 * The firmware provides very unique device specific data tailored for
[all …]
|
| /Documentation/networking/device_drivers/wifi/intel/ |
| D | ipw2100.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 - Intel(R) PRO/Wireless 2100 Network Connection
12 Copyright |copy| 2003-2006, Intel Corporation
16 :Version: git-1.1.5
23 2. Release git-1.1.5 Current Features
27 6. Dynamic Firmware
48 product is granted. Intel's wireless LAN's EEPROM, firmware, and
56 adapters (e.g., the EEPROM and firmware). Furthermore, if you use any
59 utilities, or code (including open source code modifications) which have
64 the warranty and/or issues arising from regulatory non-compliance, and
[all …]
|
| D | ipw2200.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 - Intel(R) PRO/Wireless 2200BG Network Connection
12 - Intel(R) PRO/Wireless 2915ABG Network Connection
20 Copyright |copy| 2004-2006, Intel Corporation
37 2. Ad-Hoc Networking
42 5. Firmware installation
62 product is granted. Intel's wireless LAN's EEPROM, firmware, and
70 adapters (e.g., the EEPROM and firmware). Furthermore, if you use any
73 utilities, or code (including open source code modifications) which have
78 the warranty and/or issues arising from regulatory non-compliance, and
[all …]
|
| /Documentation/core-api/irq/ |
| D | irq-domain.rst | 9 that each one gets assigned non-overlapping allocations of Linux
24 For this reason we need a mechanism to separate controller-local
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
34 preferred over interrupt controller drivers open coding their own
61 - irq_resolve_mapping() returns a pointer to the irq_desc structure
64 - irq_find_mapping() returns a Linux IRQ number for a given domain and
66 - irq_linear_revmap() is now identical to irq_find_mapping(), and is
68 - generic_handle_domain_irq() handles an interrupt described by a
72 compatible with a RCU read-side critical section.
80 callbacks) then it can be directly obtained from irq_data->hwirq.
[all …]
|
| /Documentation/driver-api/media/ |
| D | maintainer-entry-profile.rst | 5 --------
13 - drivers/media
14 - drivers/staging/media
15 - Documentation/admin-guide/media
16 - Documentation/driver-api/media
17 - Documentation/userspace-api/media
18 - Documentation/devicetree/bindings/media/\ [1]_
19 - include/media
22 OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS maintainers
33 maintainership model is to have sub-maintainers that have a broad
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | incomplete-devices.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/incomplete-devices.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
16 Examples are devices using ACPI PRP0001 with non-updatable firmware/ACPI
17 tables or old PowerPC platforms without in-tree DTS.
21 un-approved compatible.
24 even if they come from immutable firmware.
29 - description:
[all …]
|
1234