| /openbmc/linux/drivers/ufs/host/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0+
3 # Kernel configuration file for the UFS host controller drivers.
5 # Copyright (C) 2011-2013 Samsung India Software Operations
12 tristate "PCI bus based UFS Controller support"
15 This selects the PCI UFS Host Controller Interface. Select this if
16 you have UFS Host Controller with PCI Interface.
18 If you have a controller with this interface, say Y or M here.
31 tristate "Platform bus based UFS Controller support"
34 This selects the UFS host controller support. Select this if
35 you have an UFS controller on Platform bus.
[all …]
|
| H A D | ufs-qcom.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
2 /* Copyright (c) 2013-2015, The Linux Foundation. All rights reserved.
8 #include <linux/reset-controller.h>
26 /* vendor specific pre-defined parameters */
32 /* QCOM UFS host controller vendor specific registers */
53 * QCOM UFS host controller vendor specific registers
61 /* QCOM UFS host controller vendor specific debug registers */
128 /* QUniPro Vendor specific attributes */
170 /* Host controller hardware version: major.minor.step */
186 * Set this capability if host controller supports the QUniPro mode
[all …]
|
| /openbmc/linux/drivers/pci/controller/dwc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 menu "DesignWare-based PCIe controllers"
18 bool "Amazon Annapurna Labs PCIe controller"
25 controller IP on Amazon SoCs. The PCIe controller uses the DesignWare
27 required only for DT-based platforms. ACPI platforms with the
28 Annapurna Labs PCIe controller don't need to enable this.
31 tristate "Amlogic Meson PCIe controller"
36 Say Y here if you want to enable PCI controller support on Amlogic
37 SoCs. The PCI controller on Amlogic is based on DesignWare hardware
38 and therefore the driver re-uses the DesignWare core functions to
[all …]
|
| /openbmc/linux/drivers/pinctrl/samsung/ |
| H A D | pinctrl-samsung.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * pin-controller/pin-mux/pin-config/gpio-driver for Samsung's SoC's.
25 * enum pincfg_type - possible pin configuration types supported.
46 * packed together into a 16-bits. The upper 8-bits represent the configuration
47 * type and the lower 8-bits hold the value of the configuration type.
65 * enum eint_type - possible external interrupt types.
71 * Samsung GPIO controller groups all the available pins into banks. The pins
85 /* maximum length of a pin in pin descriptor (example: "gpa0-0") */
116 * struct samsung_pin_bank_data: represent a controller pin-bank (init data).
118 * @pctl_offset: starting offset of the pin-bank registers.
[all …]
|
| /openbmc/linux/drivers/net/ethernet/stmicro/stmmac/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "STMicroelectronics Multi-Gigabit Ethernet driver"
34 This selects the platform specific bus support for the stmmac driver.
38 If you have a controller with this interface, say Y or M here.
45 tristate "Support for snps,dwc-qos-ethernet.txt DT binding."
50 Support for chips using the snps,dwc-qos-ethernet.txt DT binding.
57 platform specific code to function or is using platform
65 Support for Adaptrum Anarion GMAC Ethernet controller.
75 Support for ethernet controller on Ingenic SoCs.
79 MAC ethernet controller.
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | StorageControllerMetrics.v1_0_3.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 …"longDescription": "The object shall contain the NVMe-defined 'Endurance Group Critical Warning Su…
39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
54 …indication of whether namespaces in one or more Endurance Groups are in read-only mode not as a re…
55 …hall indicate whether namespaces in one or more Endurance Groups are in read-only mode not as a re…
63 …ability of one or more Endurance Groups is degraded due to significant media-related errors or any…
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.fsl-hwconfig | 1 Freescale-specific 'hwconfig' options.
3 This file documents Freescale-specific key:value pairs for the 'hwconfig'
7 Specific to the P1022DS reference board.
13 will be programmed accordingly. Second, the clock-frequency property
24 Specific to boards have USB controller
26 This option specifies the following for a USB controller:
28 - which controller mode to use
29 - which USB PHY to use
31 This is used by generic USB device-tree fixup function to update
32 modified values of phy type and controller mode.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | mpic.txt | 2 Freescale MPIC Interrupt Controller Node
6 The Freescale MPIC interrupt controller is found on all PowerQUICC
14 - compatible
22 - reg
24 Value type: <prop-encoded-array>
29 - interrupt-controller
33 controller
35 - #interrupt-cells
39 specifiers do not contain the interrupt-type or type-specific
42 - #address-cells
[all …]
|
| /openbmc/linux/drivers/mmc/host/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # MMC/SD host controller drivers
6 comment "MMC/SD/SDIO Host Controller Drivers"
18 tristate "Sunplus SP7021 MMC Controller"
37 bool "Qualcomm Data Mover for SD Card Controller"
41 This selects the Qualcomm Data Mover lite/local on SD Card controller.
48 bool "STMicroelectronics STM32 SDMMC Controller"
52 This selects the STMicroelectronics STM32 SDMMC host controller.
68 tristate "Secure Digital Host Controller Interface support"
71 This selects the generic Secure Digital Host Controller Interface.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/pci/ |
| H A D | snps,dw-pcie-ep.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
14 Synopsys DesignWare PCIe host controller endpoint
16 # Please create a separate DT-schema for your DWC PCIe Endpoint controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie-ep
[all …]
|
| H A D | snps,dw-pcie.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
14 Synopsys DesignWare PCIe host controller
16 # Please create a separate DT-schema for your DWC PCIe Root Port controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ |
| H A D | mc-peripheral-props.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/mc-peripheral-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Peripheral-specific properties for a Memory Controller bus.
11 They could be common properties like reg or they could be controller
12 specific like delay in clock or data lines, etc. These properties need
13 to be defined in the peripheral node because they are per-peripheral
14 and there can be multiple peripherals attached to a controller. All
15 those properties are listed here. The controller specific properties
[all …]
|
| /openbmc/u-boot/drivers/mmc/ |
| H A D | Kconfig | 1 menu "MMC Host controller Support"
12 also to your specific host controller driver.
31 Secure Digital I/O (SDIO) cards. Both removable (SD, micro-SD, etc.)
32 and non-removable (e.g. eMMC chip) devices are supported. These
33 appear as block devices in U-Boot and can support filesystems such
42 Secure Digital I/O (SDIO) cards. Both removable (SD, micro-SD, etc.)
43 and non-removable (e.g. eMMC chip) devices are supported. These
44 appear as block devices in U-Boot and can support filesystems such
161 you are reading this help text, you most likely have no idea :-)
188 bool "Exynos specific extensions for Synopsys DW Memory Card Interface"
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | samsung-keypad.txt | 1 * Samsung's Keypad Controller device tree bindings
3 Samsung's Keypad controller is used to interface a SoC with a matrix-type
4 keypad device. The keypad controller supports multiple row and column lines.
6 The keypad controller can sense a key-press and key-release and report the
9 Required SoC Specific Properties:
10 - compatible: should be one of the following
11 - "samsung,s3c6410-keypad": For controllers compatible with s3c6410 keypad
12 controller.
13 - "samsung,s5pv210-keypad": For controllers compatible with s5pv210 keypad
14 controller.
[all …]
|
| H A D | brcm,bcm-keypad.txt | 1 * Broadcom Keypad Controller device tree bindings
3 Broadcom Keypad controller is used to interface a SoC with a matrix-type
4 keypad device. The keypad controller supports multiple row and column lines.
6 The keypad controller can sense a key-press and key-release and report the
9 This binding is based on the matrix-keymap binding with the following
12 keypad,num-rows and keypad,num-columns are required.
14 Required SoC Specific Properties:
15 - compatible: should be "brcm,bcm-keypad"
17 - reg: physical base address of the controller and length of memory mapped
20 - interrupts: The interrupt number to the cpu.
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | peci.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
2 /* Copyright (c) 2018-2021 Intel Corporation */
21 * struct peci_controller_ops - PECI controller specific methods
24 * PECI controllers may have different hardware interfaces - the drivers
29 int (*xfer)(struct peci_controller *controller, u8 addr, struct peci_request *req);
33 * struct peci_controller - PECI controller
34 * @dev: device object to register PECI controller to the device model
35 * @ops: pointer to device specific controller operations
37 * @id: PECI controller ID
39 * PECI controllers usually connect to their drivers using non-PECI bus,
[all …]
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | x86_init.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
16 * struct x86_init_mpparse - platform specific mpparse ops
17 * @setup_ioapic_ids: platform specific ioapic id override
28 * struct x86_init_resources - platform specific resource related ops
32 * @memory_setup: platform specific memory setup
33 * @dmi_setup: platform specific DMI setup
43 * struct x86_init_irqs - platform specific interrupt setup
60 * struct x86_init_oem - oem platform specific customizing functions
61 * @arch_setup: platform specific architecture setup
62 * @banner: print a platform specific banner
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | StorageControllerMetrics_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ …
4 <!--# Redfish Schema: StorageControllerMetrics v1.0.3 …
5 <!--# …
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, …
7 <!--# available at http://www.dmtf.org/standards/redfish …
8 <!--# Copyright 2014-2024 DMTF in cooperation with Storage Networking Industry Association (SNIA). …
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright …
10 <!--################################################################################ …
[all …]
|
| /openbmc/u-boot/include/ |
| H A D | nvme.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
13 * nvme_identify - identify controller or namespace capabilities and status
15 * This issues an identify command to the NVMe controller to return a data
16 * buffer that describes the controller or namespace capabilities and status.
18 * @dev: NVMe controller device
19 * @nsid: 0 for controller, namespace id for namespace to identify
20 * @cns: 1 for controller, 0 for namespace
22 * @return: 0 on success, -ETIMEDOUT on command execution timeout,
23 * -EIO on command execution fails
29 * nvme_get_features - retrieve the attributes of the feature specified
[all …]
|
| /openbmc/linux/drivers/nvme/host/ |
| H A D | fabrics.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
4 * Copyright (c) 2015-2016 HGST, a Western Digital Company.
18 /* default is -1: the fail fast mechanism is disabled */
19 #define NVMF_DEF_FAIL_FAST_TMO -1
37 * enum nvmf_parsing_opts - used to define the sysfs parsing options used.
69 * struct nvmf_ctrl_options - Used to hold the options specified
72 * on adding a NVMe controller.
74 * the controller, (-1) means reconnect forever, zero means remove
77 * better description) that will be used by an NVMe controller
81 * @traddr: The transport-specific TRADDR field for a port on the
[all …]
|
| /openbmc/linux/drivers/staging/fieldbus/Documentation/devicetree/bindings/fieldbus/ |
| H A D | arcx,anybus-controller.txt | 1 * Arcx Anybus-S controller
8 --------------------
10 - compatible : The following chip-specific string:
11 "arcx,anybus-controller"
13 - reg : three areas:
15 index 1: bus memory area of the first host's dual-port ram.
16 index 2: bus memory area of the second host's dual-port ram.
18 - reset-gpios : the GPIO pin connected to the reset line of the controller.
20 - interrupts : two interrupts:
24 interrupt-controller/interrupts.txt
[all …]
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | writing_musb_glue_layer.rst | 12 use Universal Host Controller Interface (UHCI) or Open Host Controller
15 Instead, these embedded UDC rely on the USB On-the-Go (OTG)
18 Dual-Role Controller (MUSB HDRC) found in the Mentor Graphics Inventra™
21 As a self-taught exercise I have written an MUSB glue layer for the
28 .. _musb-basics:
33 To get started on the topic, please read USB On-the-Go Basics (see
37 albeit focused on some specific devices provided by these companies.
42 Linux USB stack is a layered architecture in which the MUSB controller
43 hardware sits at the lowest. The MUSB controller driver abstract the
44 MUSB controller hardware to the Linux USB stack::
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-led-flash | 55 Flash faults are re-read after strobing the flash. Possible
58 * led-over-voltage
59 flash controller voltage to the flash LED
60 has exceeded the limit specific to the flash controller
61 * flash-timeout-exceeded
65 * controller-over-temperature
66 the flash controller has
68 * controller-short-circuit
70 of the flash controller has been triggered
71 * led-power-supply-over-current
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mmc/ |
| H A D | k3-dw-mshc.txt | 1 * Hisilicon specific extensions to the Synopsys Designware Mobile
2 Storage Host Controller
4 Read synopsys-dw-mshc.txt for more details
6 The Synopsys designware mobile storage host controller is used to interface
8 differences between the core Synopsys dw mshc controller properties described
9 by synopsys-dw-mshc.txt and the properties used by the Hisilicon specific
10 extensions to the Synopsys Designware Mobile Storage Host Controller.
15 - "hisilicon,hi3660-dw-mshc": for controllers with hi3660 specific extensions.
16 - "hisilicon,hi3670-dw-mshc", "hisilicon,hi3660-dw-mshc": for controllers
17 with hi3670 specific extensions.
[all …]
|
| /openbmc/linux/drivers/platform/mips/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # MIPS Platform Specific Drivers
7 bool "MIPS Platform Specific Device Drivers"
12 MIPS platforms, including vendor-specific netbook/laptop/desktop
21 bool "Loongson-3 CPU HWMon Driver"
26 Loongson-3A/3B CPU Hwmon (temperature sensor) driver.
29 bool "Loongson RS780E ACPI Controller"
32 Loongson RS780E PCH ACPI Controller driver.
35 bool "Loongson-2K1000 Reset Controller"
38 Loongson-2K1000 Reset Controller driver.
|