Home
last modified time | relevance | path

Searched +full:platform +full:- +full:specific (Results 1 – 25 of 1139) sorted by relevance

12345678910>>...46

/linux/drivers/ufs/host/
H A DKconfig1 # 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 …]
/linux/include/linux/mtd/
H A Dplatnand.h1 /* 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/drivers/usb/musb/
H A Dmusb_io.h1 /* 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/drivers/gpio/
H A Dgpio-tangier.h1 /* SPDX-License-Identifier: GPL-2.0-only */
24 /* Elkhart Lake specific wake registers */
29 /* Merrifield specific wake registers */
35 * struct tng_wake_regs - Platform specific wake registers
47 * struct tng_gpio_pinrange - Map pin numbers to gpio numbers
62 .npins = (gend) - (gstart) + 1, \
66 * struct tng_gpio_pin_info - Platform specific pinout information
78 * struct tng_gpio_info - Platform specific GPIO and IRQ information
90 * struct tng_gpio - Platform specific private data
96 * @ctx: Context to be saved during suspend-resume
[all …]
/linux/Documentation/arch/powerpc/
H A Dbootwrapper.rst17 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/include/linux/platform_data/
H A Dbrcmfmac.h27 * 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 …]
/linux/drivers/hwspinlock/
H A Dhwspinlock_internal.h1 /* 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 …]
/linux/Documentation/admin-guide/pm/
H A Dsuspend-flows.rst1 .. 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/include/linux/
H A Dplatform_device.h1 /* 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 …]
H A Dfsl_devices.h1 /* 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/Documentation/devicetree/bindings/hwlock/
H A Dhwlock.txt4 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/Documentation/driver-api/
H A Dsm501.rst15 ----
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/Documentation/driver-api/cxl/linux/
H A Dearly-boot.rst1 .. SPDX-License-Identifier: GPL-2.0
7 Linux configuration is split into two major steps: Early-Boot and everything else.
16 (:doc:`ACPI tables <../platform/acpi>`) and turns them into resources that the
23 There are 4 pre-boot options that need to be considered during kernel build
29 Specific Purpose. Specific Purpose memory will be deferred to
30 drivers to manage - and not immediately exposed as system RAM.
35 Specific Purpose memory.
39 * Linux Build config that dictates whether and how Specific Purpose memory
51 While the kernel parses the EFI memory map, if :code:`Specific Purpose` memory
56 :code:`nosoftreserve=y` - Linux will default a CXL device memory region to
[all …]
/linux/include/uapi/linux/
H A Dpfrut.h1 /* 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 …]
/linux/Documentation/ABI/testing/
H A Dsysfs-platform-hidma-mgmt1 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 …]
H A Dsysfs-devices-platform-ipmi1 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 …]
H A Dsysfs-devices-removable6 platform by the user. This is determined by its subsystem in a
7 bus / platform-specific way. This attribute is only present for
11 "removable" device can be removed from the platform by the user
12 "fixed" device is fixed to the platform / cannot be removed
19 platform-specific data such as ACPI) and PCI (which gets this
/linux/Documentation/devicetree/bindings/perf/
H A Driscv,pmu.yaml1 # 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 …]
/linux/drivers/net/ethernet/microchip/vcap/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
9 bool "VCAP (Versatile Content-Aware Processor) library"
15 - Programmable key fields
16 - Programmable action fields
17 - A counter (which may be only one bit wide)
21 - A number of lookups
22 - A keyset configuration per port per lookup
27 - Creating and deleting rules
28 - Updating and getting rules
30 The platform specific configuration as well as the platform specific model
[all …]
/linux/Documentation/driver-api/backlight/
H A Dlp855x-driver.rst15 -----------
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/drivers/misc/mei/
H A Dhw-me.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Copyright (c) 2012-2022, Intel Corporation. All rights reserved.
18 * mei_cfg - mei device configuration
45 * struct mei_me_hw - me hw specific data
72 #define to_me_hw(dev) (struct mei_me_hw *)((dev)->hw)
76 return hw->irq < 0; in mei_me_hw_use_polling()
80 * enum mei_cfg_idx - indices to platform specific configurations.
87 * @MEI_ME_PCH6_CFG: Platform Controller Hub platforms (Gen6).
88 * @MEI_ME_PCH7_CFG: Platform Controller Hub platforms (Gen7).
89 * @MEI_ME_PCH_CPT_PBG_CFG:Platform Controller Hub workstations
[all …]
/linux/drivers/dax/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
14 device. Platform firmware or a device driver may identify a
15 platform memory resource that is differentiated from the
26 libnvdimm sub-system.
31 tristate "HMEM DAX: direct access to 'specific purpose' memory"
36 EFI 2.8 platforms, and others, may advertise 'specific purpose'
38 indication from platform firmware is meant to reserve the
40 device-dax instances for these memory ranges, and that also
52 CXL RAM regions are either mapped by platform-firmware
53 and published in the initial system-memory map as "System RAM", mapped
[all …]
/linux/Documentation/devicetree/bindings/pci/
H A Dsnps,dw-pcie-ep.yaml1 # 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>
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
23 - compatible
[all …]
/linux/Documentation/devicetree/bindings/tpm/
H A Dtcg,tpm-tis-i2c.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/tpm/tcg,tpm-tis-i2c.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: I²C-attached Trusted Platform Module conforming to TCG TIS specification
10 - Lukas Wunner <lukas@wunner.de>
13 The Trusted Computing Group (TCG) has defined a multi-vendor standard
16 TCG PC Client Specific TPM Interface Specification (TIS)
17 …tps://trustedcomputinggroup.org/resource/pc-client-work-group-pc-client-specific-tpm-interface-spe…
21 TCG PC Client Platform TPM Profile Specification for TPM 2.0 (PTP)
[all …]
/linux/Documentation/sound/soc/
H A Doverview.rst6 provide better ALSA support for embedded system-on-chip processors (e.g.
9 had some limitations:-
12 CPU. This is not ideal and leads to code duplication - for example,
18 machine specific code to re-route audio, enable amps, etc., after such an
31 features :-
50 * Machine specific controls: Allow machines to add controls to the sound card
54 multiple re-usable component drivers :-
56 * Codec class drivers: The codec class driver is platform independent and
62 * Platform class drivers: The platform class driver includes the audio DMA
64 and any audio DSP drivers for that platform.
[all …]

12345678910>>...46