| /openbmc/linux/drivers/ufs/host/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0+
5 # Copyright (C) 2011-2013 Samsung India Software Operations
31 tristate "Platform bus based UFS Controller support"
35 you have an UFS controller on Platform bus.
42 tristate "Cadence UFS Controller platform driver"
45 This selects the Cadence-specific additions to UFSHCD platform driver.
50 tristate "DesignWare platform support using a G210 Test Chip"
58 tristate "QCOM specific hooks to UFS controller platform driver"
64 This selects the QCOM specific additions to UFSHCD platform driver.
65 UFS host on QCOM needs some vendor specific configuration before
[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
31 * platform
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
[all …]
|
| /openbmc/linux/include/linux/mtd/ |
| H A D | platnand.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Copyright © 2000-2010 David Woodhouse <dwmw2@infradead.org>
7 * Contains all platform NAND related definitions.
18 * struct platform_nand_chip - chip level device structure
26 * @part_probe_types: NULL-terminated array of probe types
40 * struct platform_nand_ctrl - controller level device structure
41 * @probe: platform specific function to probe/setup hardware
42 * @remove: platform specific function to remove/teardown hardware
43 * @dev_ready: platform specific function to read ready/busy pin
44 * @select_chip: platform specific chip select function
[all …]
|
| /openbmc/linux/drivers/media/platform/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # Platform drivers
7 bool "Media platform devices"
10 Say Y here to enable support for platform-specific media drivers.
15 bool "V4L platform devices"
17 Say Y here to enable support for platform-specific V4L drivers.
20 bool "SDR platform devices"
23 Say Y here to enable support for platform-specific SDR Drivers.
26 bool "DVB platform devices"
29 Say Y here to enable support for platform-specific Digital TV drivers.
[all …]
|
| /openbmc/linux/drivers/usb/musb/ |
| H A D | musb_io.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
6 * Copyright (C) 2005-2006 by Texas Instruments
7 * Copyright (C) 2006-2007 Nokia Corporation
15 #define musb_ep_select(_mbase, _epnum) musb->io.ep_select((_mbase), (_epnum))
18 * struct musb_io - IO functions for MUSB
19 * @ep_offset: platform specific function to get end point offset
20 * @ep_select: platform specific function to select end point
21 * @fifo_offset: platform specific function to get fifo offset
22 * @read_fifo: platform specific function to read fifo
23 * @write_fifo: platform specific function to write fifo
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-kernel/linux/ |
| H A D | cve-exclusion.inc | 1 CVE_STATUS[CVE-1999-0656] = "not-applicable-config: specific to ugidd, part of the old user-mode NF…
3 CVE_STATUS[CVE-2006-2932] = "not-applicable-platform: specific to RHEL"
5 CVE_STATUS[CVE-2007-2764] = "not-applicable-platform: specific to Sun/Brocade SilkWorm switches"
7 CVE_STATUS[CVE-2007-4998] = "cpe-incorrect: a historic cp bug, no longer an issue as per https://bu…
9 CVE_STATUS[CVE-2008-2544] = "disputed: not an issue as per https://bugzilla.redhat.com/show_bug.cgi…
11 CVE_STATUS[CVE-2010-0298] = "fixed-version: 2.6.34 (1871c6)"
13 CVE_STATUS[CVE-2014-2648] = "cpe-incorrect: not Linux"
15 CVE_STATUS[CVE-2016-0774] = "ignored: result of incomplete backport"
17 CVE_STATUS[CVE-2016-3695] = "not-applicable-platform: specific to RHEL with securelevel patches"
19 CVE_STATUS[CVE-2016-3699] = "not-applicable-platform: specific to RHEL with securelevel patches"
[all …]
|
| /openbmc/linux/drivers/gpio/ |
| H A D | gpio-tangier.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
23 /* Elkhart Lake specific wake registers */
28 /* Merrifield specific wake registers */
34 * struct tng_wake_regs - Platform specific wake registers
46 * struct tng_gpio_pinrange - Map pin numbers to gpio numbers
61 .npins = (gend) - (gstart) + 1, \
65 * struct tng_gpio_pin_info - Platform specific pinout information
77 * struct tng_gpio_info - Platform specific GPIO and IRQ information
89 * struct tng_gpio - Platform specific private data
95 * @ctx: Context to be saved during suspend-resume
[all …]
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | bootwrapper.rst | 17 others. U-Boot is typically found on embedded PowerPC hardware, but there
28 U-Boot (for versions that don't understand the device
31 are all embedded inside the U-Boot uImage file format
37 bd_info structure used in the old U-Boot interfaces,
38 cuImages are platform specific. Each specific
39 U-Boot platform has a different platform init file
41 from the platform specific bd_info file. The platform
42 specific cuImage platform init code can be found in
44 cuImage init code for a specific board can be found in
50 binary depending on the platform.
[all …]
|
| /openbmc/linux/include/linux/platform_data/ |
| H A D | brcmfmac.h | 27 * Platform specific driver functions and data. Through the platform specific
29 * operate with the device in combination with the used platform.
34 * Note: the brcmfmac can be loaded as module or be statically built-in into
35 * the kernel. If built-in then do note that it uses module_init (and
37 * create a module with the platform specific data for the brcmfmac and have
38 * it built-in to the kernel then use a higher initcall then device_initcall
40 * but will not pickup the platform data.
42 * When the driver does not "detect" platform driver data then it will continue
48 * enum brcmf_bus_type - Bus type identifier. Currently SDIO, USB and PCIE are
59 * struct brcmfmac_sdio_pd - SDIO Device specific platform data.
[all …]
|
| /openbmc/linux/drivers/hwspinlock/ |
| H A D | hwspinlock_internal.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
5 * Copyright (C) 2010 Texas Instruments Incorporated - http://www.ti.com
7 * Contact: Ohad Ben-Cohen <ohad@wizery.com>
19 * struct hwspinlock_ops - platform-specific hwspinlock handlers
24 * @bust: optional, platform-specific bust handler, called by hwspinlock
25 * core to bust a specific lock.
26 * @relax: optional, platform-specific relax handler, called by hwspinlock
38 * struct hwspinlock - this struct represents a single hwspinlock instance
41 * @priv: private data, owned by the underlying platform-specific hwspinlock drv
50 * struct hwspinlock_device - a device which usually spans numerous hwspinlocks
[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"
29 tristate "STMMAC Platform bus support"
34 This selects the platform specific bus support for the stmmac driver.
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
92 will behave like standard non-accelerated ethernet interfaces.
94 Select the QCOM_SOCINFO config flag to enable specific dwmac
166 Support for ethernet controllers on StarFive RISC-V SoCs
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/hwlock/ |
| H A D | hwlock.txt | 4 Generic bindings that are common to all the hwlock platform specific driver
7 Please also look through the individual platform specific hwlock binding
8 documentations for identifying any additional properties specific to that
9 platform.
15 - #hwlock-cells: Specifies the number of cells needed to represent a
16 specific lock.
21 Consumers that require specific hwlock(s) should specify them using the
22 property "hwlocks", and an optional "hwlock-names" property.
25 - hwlocks: List of phandle to a hwlock provider node and an
27 #hwlock-cells. The list can have just a single hwlock
[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.
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.
119 * @pctl_res_idx: index of base address for pin-bank registers.
[all …]
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | suspend-flows.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 At least one global system-wide transition needs to be carried out for the
14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
27 significant differences between the :ref:`suspend-to-idle <s2idle>` code flows
28 and the code flows related to the :ref:`suspend-to-RAM <s2ram>` and
31 The :ref:`suspend-to-RAM <s2ram>` and :ref:`standby <standby>` sleep states
32 cannot be implemented without platform support and the difference between them
33 boils down to the platform-specific actions carried out by the suspend and
34 resume hooks that need to be provided by the platform driver to make them
[all …]
|
| /openbmc/linux/Documentation/staging/ |
| H A D | remoteproc.rst | 10 of operating system, whether it's Linux or any other flavor of real-time OS.
12 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
13 In a typical configuration, the dual cortex-A9 is running Linux in a SMP
22 platform-specific remoteproc drivers only need to provide a few low-level
24 (for more information about the virtio-based rpmsg bus and its drivers,
118 name of this remote processor, platform-specific ops handlers,
154 This is called by the platform-specific rproc implementation, whenever
172 This function should be called when the platform specific rproc
180 Returns 0 on success and -EINVAL if @rproc isn't valid.
189 platform specific rproc implementation. This should not be called from a
[all …]
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | sm501.rst | 15 ----
18 drivers which manage the specific hardware blocks. These services
23 chips via the platform device and driver system.
26 be specified by the platform data) and then exports the selected
27 peripheral set as platform devices for the specific drivers.
29 The core re-uses the platform device system as the platform device
31 need to create a new bus-type and the associated code to go with it.
35 ---------
38 the specific set of resources that peripheral requires in order to
43 as this is by-far the most resource-sensitive of the on-chip functions.
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | platform_device.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * platform_device.h - generic, centralized driver model
5 * Copyright (c) 2001-2003 Patrick Mochel <mochel@osdl.org>
7 * See Documentation/driver-api/driver-model/ for more information.
15 #define PLATFORM_DEVID_NONE (-1)
16 #define PLATFORM_DEVID_AUTO (-2)
43 /* arch specific additions */
47 #define platform_get_device_id(pdev) ((pdev)->id_entry)
49 #define dev_is_platform(dev) ((dev)->bus == &platform_bus_type)
83 return ERR_PTR(-EINVAL); in devm_platform_get_and_ioremap_resource()
[all …]
|
| /openbmc/pldm/ |
| H A D | README.md | 1 # PLDM - Platform Level Data Model
3 [](LICENSE)
7 PLDM (Platform Level Data Model) is a key component of the OpenBMC project,
8 providing a standardized data model and message formats for various platform
18 - **Standardized Messaging:** Adheres to the DMTF's PLDM specifications,
21 - **Modularity:** Supports multiple PLDM types, including base, FRU,Firmware
22 update, Platform Monitoring and Control, and BIOS Control and Configuration.
23 - **Extensibility:** Easily extendable to support new PLDM types and custom OEM
25 - **Integration:** Seamlessly integrates with other OpenBMC components for
34 - `Meson`
[all …]
|
| /openbmc/docs/designs/ |
| H A D | redfish-resource-supplement-for-pfr.md | 1 # Redfish resource supplement for Platform Firmware Resilience (PFR)
7 Created: 2019-09-12
11 The platform is a collection of fundamental hardware and firmware components
12 needed to boot and operate a system. The Platform Firmware Resiliency(PFR) in
13 NIST SP 800-193 provides technical guidelines and recommendations supporting
14 resiliency of platform firmware and data against potentially destructive
21 represent the PFR provisioning status such as platform firmware is provisioned
27 Platform Firmware Resilience technology in NIST SP 800-93 provide common
31 resiliency by protecting, detecting and recovering platform assets. Management
32 controller running on server platform can be used to indicate the status of
[all …]
|
| H A D | entity-manager-hw-id-vpd-discover-via-device-tree.md | 1 # Entity-Manager HW ID: VPD Discovery via Device-Tree Properties
12 data via non-I2C channels and in a proprietary format that is not covered by
13 Entity-Manager's 'fru-device' daemon that most platforms rely on.
16 gathered from device tree file paths for Entity-Manager consumption.
20 Typical platforms provide HW ID data - often referred to as 'vital product data'
21 (VPD) - for the baseboard as a FRU storage blob held in a physical EEPROM.
23 [As described in Entity-Manager documentation](https://github.com/openbmc/entity-manager/blob/maste…
25 copied to D-Bus as properties of the `xyz.openbmc_project.FruDevice` interface
26 by Entity-Manager's fru-device daemon. The current FRU-device daemon is able to
27 decode IPMI-FRU storage formatted blobs, as well as the Tyan data format.
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-hidma-mgmt | 1 What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/priority
2 /sys/devices/platform/QCOM8060:*/chanops/chan*/priority
10 What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/weight
11 /sys/devices/platform/QCOM8060:*/chanops/chan*/weight
19 What: /sys/devices/platform/hidma-mgmt*/chreset_timeout_cycles
20 /sys/devices/platform/QCOM8060:*/chreset_timeout_cycles
25 Contains the platform specific cycle value to wait after a
28 is platform specific and should not be changed without
31 What: /sys/devices/platform/hidma-mgmt*/dma_channels
32 /sys/devices/platform/QCOM8060:*/dma_channels
[all …]
|
| /openbmc/docs/ |
| H A D | community-membership.md | 8 …------------------- | ------------------------------------------------------ | -------------------…
11 …Platform Maintainer | Review and maintain contributions to a single platform | History of testing …
27 Role-specific expectations, responsibilities, and requirements are enumerated
34 Gerrit, and pre-submit tests are automatically run for their reviews. Members
41 - Have made multiple contributions to the project or community. Contribution may
43 - Authoring or reviewing code reviews on Gerrit
44 - Filing or commenting on issues on GitHub
45 - Contributing to design review, subproject, or community discussions (e.g.
47 - Subscribed to the [mailing list]
48 - Have read the [contributor guide]
[all …]
|
| /openbmc/linux/Documentation/driver-api/driver-model/ |
| H A D | platform.rst | 2 Platform Devices and Drivers
6 platform bus: platform_device, and platform_driver. This pseudo-bus
8 like those used to integrate peripherals on many system-on-chip
13 Platform devices
15 Platform devices are devices that typically appear as autonomous
16 entities in the system. This includes legacy port-based devices and
18 into system-on-chip platforms. What they usually have in common
23 Platform devices are given a name, used in driver binding, and a
35 Platform drivers
37 Platform drivers follow the standard driver model convention, where
[all …]
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | pfrut.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
3 * Platform Firmware Runtime Update header
16 * PFRU_IOC_SET_REV - _IOW(PFRUT_IOCTL_MAGIC, 0x01, unsigned int)
19 * * 0 - success
20 * * -EFAULT - fail to read the revision id
21 * * -EINVAL - user provides an invalid revision id
23 * Set the Revision ID for Platform Firmware Runtime Update.
28 * PFRU_IOC_STAGE - _IOW(PFRUT_IOCTL_MAGIC, 0x02, unsigned int)
31 * * 0 - success
32 * * -EINVAL - stage phase returns invalid result
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/perf/ |
| H A D | riscv,pmu.yaml | 1 # SPDX-License-Identifier: BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: RISC-V SBI PMU events
10 - Atish Patra <atishp@rivosinc.com>
18 The platform must provide information about PMU event to counter mappings
19 either via device tree or another way, specific to the platform.
24 MHPMCOUNTERx for that specific event. The can either be done via device tree
25 or another way, specific to the platform.
27 platform.
[all …]
|