Searched +full:platform +full:- +full:specific (Results 1 – 25 of 1131) sorted by relevance
12345678910>>...46
| /Linux-v5.10/arch/x86/include/asm/ |
| 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
42 * struct x86_init_irqs - platform specific interrupt setup
59 * struct x86_init_oem - oem platform specific customizing functions
60 * @arch_setup: platform specific architecture setup
61 * @banner: print a platform specific banner
[all …]
|
| /Linux-v5.10/drivers/scsi/ufs/ |
| D | Kconfig | 5 # Copyright (C) 2011-2013 Samsung India Software Operations
15 # See the COPYING file in the top-level directory or visit
16 # <http://www.gnu.org/licenses/gpl-2.0.html>
73 tristate "Platform bus based UFS Controller support"
77 you have an UFS controller on Platform bus.
84 tristate "Cadence UFS Controller platform driver"
87 This selects the Cadence-specific additions to UFSHCD platform driver.
92 tristate "DesignWare platform support using a G210 Test Chip"
100 tristate "QCOM specific hooks to UFS controller platform driver"
105 This selects the QCOM specific additions to UFSHCD platform driver.
[all …]
|
| /Linux-v5.10/include/linux/mtd/ |
| 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 …]
|
| /Linux-v5.10/drivers/usb/musb/ |
| 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 …]
|
| /Linux-v5.10/Documentation/powerpc/ |
| 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 …]
|
| /Linux-v5.10/include/linux/platform_data/ |
| 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 …]
|
| D | s3c-hsudc.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * S3C24XX USB 2.0 High-speed USB controller gadget driver
8 * The S3C24XX USB 2.0 high-speed USB controller supports upto 9 endpoints.
17 * s3c24xx_hsudc_platdata - Platform data for USB High-Speed gadget controller.
19 * @gpio_init: Platform specific USB related GPIO initialization.
20 * @gpio_uninit: Platform specific USB releted GPIO uninitialzation.
22 * Representation of platform data for the S3C24XX USB 2.0 High Speed gadget
|
| /Linux-v5.10/include/linux/ |
| 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)
38 /* arch specific additions */
42 #define platform_get_device_id(pdev) ((pdev)->id_entry)
44 #define dev_is_platform(dev) ((dev)->bus == &platform_bus_type)
102 * platform_device_register_resndata - add a platform-level device with
[all …]
|
| D | fsl_devices.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
5 * Definitions for any platform device related flags or structures for
17 PHY CLK to become stable - 10ms*/
30 * Each sub-arch has its own master list of unique devices and
31 * enumerates them by enum fsl_devices in a sub-arch specific header
33 * The platform data structure is broken into two parts. The
34 * first is device specific information that help identify any
40 * - platform data structures: <driver>_platform_data
41 * - platform data device flags: FSL_<driver>_DEV_<FLAG>
42 * - platform data board flags: FSL_<driver>_BRD_<FLAG>
[all …]
|
| /Linux-v5.10/drivers/pinctrl/samsung/ |
| 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.
57 * enum eint_type - possible external interrupt types.
77 /* maximum length of a pin in pin descriptor (example: "gpa0-0") */
108 * struct samsung_pin_bank_data: represent a controller pin-bank (init data).
110 * @pctl_offset: starting offset of the pin-bank registers.
111 * @pctl_res_idx: index of base address for pin-bank registers.
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/hwlock/ |
| 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 …]
|
| /Linux-v5.10/Documentation/staging/ |
| 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,
117 name of this remote processor, platform-specific ops handlers,
153 This is called by the platform-specific rproc implementation, whenever
171 This function should be called when the platform specific rproc
179 Returns 0 on success and -EINVAL if @rproc isn't valid.
188 platform specific rproc implementation. This should not be called from a
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/pm/ |
| 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 …]
|
| /Linux-v5.10/Documentation/driver-api/ |
| 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 …]
|
| /Linux-v5.10/drivers/hwspinlock/ |
| 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 * @relax: optional, platform-specific relax handler, called by hwspinlock
35 * struct hwspinlock - this struct represents a single hwspinlock instance
38 * @priv: private data, owned by the underlying platform-specific hwspinlock drv
47 * struct hwspinlock_device - a device which usually spans numerous hwspinlocks
49 * @ops: platform-specific hwspinlock handlers
64 int local_id = hwlock - &hwlock->bank->lock[0]; in hwlock_to_id()
[all …]
|
| /Linux-v5.10/drivers/net/ethernet/stmicro/stmmac/ |
| 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
80 will behave like standard non-accelerated ethernet interfaces.
219 This selects the Intel platform specific glue layer support for
230 This selects the Intel platform specific bus support for the
[all …]
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| 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 …]
|
| D | sysfs-devices-platform-ipmi | 1 What: /sys/devices/platform/ipmi_bmc.*/firmware_revision
4 Contact: openipmi-developer@lists.sourceforge.net
9 What: /sys/devices/platform/ipmi_bmc.*/aux_firmware_revision
12 Contact: openipmi-developer@lists.sourceforge.net
16 The meanings of the numbers are specific to the vendor
20 What: /sys/devices/platform/ipmi_bmc.*/revision
23 Contact: openipmi-developer@lists.sourceforge.net
30 What: /sys/devices/platform/ipmi_bmc.*/provides_device_sdrs
33 Contact: openipmi-developer@lists.sourceforge.net
39 What: /sys/devices/platform/ipmi_bmc.*/device_id
[all …]
|
| /Linux-v5.10/Documentation/driver-api/driver-model/ |
| 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 …]
|
| /Linux-v5.10/arch/arm/mach-mmp/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
23 Say 'Y' here if you want to support the Marvell PXA168-based
31 Say 'Y' here if you want to support the Marvell PXA168-based
39 Say 'Y' here if you want to support the Marvell PXA168-based
47 Say 'Y' here if you want to support the Marvell PXA910-based
55 Say 'Y' here if you want to support the Marvell PXA910-based
59 bool "Marvell's Brownstone Development Platform"
63 Say 'Y' here if you want to support the Marvell MMP2-based
64 Brown Development Platform.
65 MMP2-based board can't be co-existed with PXA168-based &
[all …]
|
| /Linux-v5.10/Documentation/driver-api/gpio/ |
| D | legacy.rst | 13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
37 - Input values are likewise readable (1, 0). Some chips support readback
38 of pins configured as "output", which is very useful in such "wire-OR"
40 input de-glitch/debounce logic, sometimes with software controls.
42 - Inputs can often be used as IRQ signals, often edge triggered but
[all …]
|
| /Linux-v5.10/Documentation/driver-api/backlight/ |
| D | lp855x-driver.rst | 15 -----------
36 Platform data for lp855x
37 ------------------------
39 For supporting platform specific data, the lp855x platform data can be used.
48 Platform specific PWM period value. unit is nano.
58 1) lp8552 platform data: i2c register mode with new eeprom data::
68 .name = "lcd-bl",
75 2) lp8556 platform data: pwm input mode with default rom data::
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| D | writing_musb_glue_layer.rst | 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.
46 ------------------------
47 | | <------- drivers/usb/gadget
48 | Linux USB Core Stack | <------- drivers/usb/host
49 | | <------- drivers/usb/core
[all …]
|
| /Linux-v5.10/drivers/misc/mei/ |
| D | hw-me.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Copyright (c) 2012-2020, Intel Corporation. All rights reserved.
18 * mei_cfg - mei device configuration
45 * struct mei_me_hw - me hw specific data
65 #define to_me_hw(dev) (struct mei_me_hw *)((dev)->hw)
68 * enum mei_cfg_idx - indices to platform specific configurations.
75 * @MEI_ME_PCH6_CFG: Platform Controller Hub platforms (Gen6).
76 * @MEI_ME_PCH7_CFG: Platform Controller Hub platforms (Gen7).
77 * @MEI_ME_PCH_CPT_PBG_CFG:Platform Controller Hub workstations
79 * @MEI_ME_PCH8_CFG: Platform Controller Hub Gen8 and newer
[all …]
|
| /Linux-v5.10/drivers/mmc/host/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
23 platform with a Multimedia Card slot, say Y or M here.
53 If you have a PXA(R) platform with a Multimedia Card slot,
85 implements a hardware byte swapper using a 32-bit datum.
114 disabled, it will steal the MMC cards away - rendering them
126 identified by ACPI Compatibility ID PNP0D40 or specific
134 tristate "SDHCI platform and OF driver helper"
138 Host Controller Interface based platform and OF drivers.
244 This selects the SDHCI support for CNS3xxx System-on-Chip devices.
291 tristate "SDHCI platform support for the Tegra SD/MMC Controller"
[all …]
|
12345678910>>...46
