Home
last modified time | relevance | path

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

12345678910>>...43

/kernel/linux/linux-4.19/arch/x86/include/asm/
Dx86_init.h1 /* SPDX-License-Identifier: GPL-2.0 */
13 * struct x86_init_mpparse - platform specific mpparse ops
14 * @mpc_record: platform specific mpc record accounting
15 * @setup_ioapic_ids: platform specific ioapic id override
16 * @mpc_apic_id: platform specific mpc apic id assignment
17 * @smp_read_mpc_oem: platform specific oem mpc table setup
18 * @mpc_oem_pci_bus: platform specific pci bus setup (default NULL)
19 * @mpc_oem_bus_info: platform specific mpc bus info
35 * struct x86_init_resources - platform specific resource related ops
38 * platform
[all …]
/kernel/linux/linux-5.10/arch/x86/include/asm/
Dx86_init.h1 /* 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 …]
/kernel/linux/linux-4.19/arch/arm/mach-imx/
DKconfig13 Support for Freescale MXC/iMX-based family of processors
24 bool "Enable MXC debug board(for 3-stack)"
27 The debug board is an integral part of the MXC 3-stack(PDK)
32 data/address de-multiplexing and decode, signal level shift,
84 bool "MX21ADS platform"
91 Include support for MX21ADS platform. This includes specific
97 bool "MX27ADS platform"
106 Include support for MX27ADS platform. This includes specific
110 bool "MX27PDK platform"
126 Include support for MX27PDK platform. This includes specific
[all …]
/kernel/linux/linux-5.10/drivers/scsi/ufs/
DKconfig5 # 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"
78 you have an UFS controller on Platform bus.
85 tristate "Cadence UFS Controller platform driver"
88 This selects the Cadence-specific additions to UFSHCD platform driver.
93 tristate "DesignWare platform support using a G210 Test Chip"
101 tristate "QCOM specific hooks to UFS controller platform driver"
106 This selects the QCOM specific additions to UFSHCD platform driver.
[all …]
/kernel/linux/linux-5.10/include/linux/mtd/
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 …]
/kernel/linux/linux-5.10/drivers/usb/musb/
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 …]
/kernel/linux/linux-4.19/Documentation/powerpc/
Dbootwrapper.txt2 ------------------------
15 others. U-Boot is typically found on embedded PowerPC hardware, but there
25 U-Boot (for versions that don't understand the device
28 are all embedded inside the U-Boot uImage file format
33 bd_info structure used in the old U-Boot interfaces,
34 cuImages are platform specific. Each specific
35 U-Boot platform has a different platform init file
37 from the platform specific bd_info file. The platform
38 specific cuImage platform init code can be found in
40 cuImage init code for a specific board can be found in
[all …]
/kernel/linux/linux-4.19/Documentation/media/v4l-drivers/
Ddavinci-vpbe.rst5 -----------------
8 drivers/media/platform/davinci/vpbe_display.c
9 drivers/media/platform/davinci/vpbe_display.h
12 drivers/media/platform/davinci/vpbe.c
13 drivers/media/platform/davinci/vpbe.h
16 drivers/media/platform/davinci/vpbe_venc.c
17 drivers/media/platform/davinci/vpbe_venc.h
18 drivers/media/platform/davinci/vpbe_venc_regs.h
21 drivers/media/platform/davinci/vpbe_osd.c
22 drivers/media/platform/davinci/vpbe_osd.h
[all …]
/kernel/linux/linux-4.19/drivers/usb/musb/
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 …]
/kernel/linux/linux-5.10/Documentation/powerpc/
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 …]
/kernel/linux/linux-4.19/include/linux/platform_data/
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 …]
/kernel/linux/linux-5.10/include/linux/platform_data/
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 …]
/kernel/linux/linux-4.19/drivers/scsi/ufs/
DKconfig5 # 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>
41 ---help---
56 ---help---
67 ---help---
73 tristate "Platform bus based UFS Controller support"
75 ---help---
77 you have an UFS controller on Platform bus.
84 tristate "DesignWare platform support using a G210 Test Chip"
[all …]
/kernel/linux/linux-5.10/include/linux/
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)
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 …]
/kernel/linux/linux-4.19/include/linux/
Dplatform_device.h2 * platform_device.h - generic, centralized driver model
4 * Copyright (c) 2001-2003 Patrick Mochel <mochel@osdl.org>
8 * See Documentation/driver-model/ for more information.
16 #define PLATFORM_DEVID_NONE (-1)
17 #define PLATFORM_DEVID_AUTO (-2)
37 /* arch specific additions */
41 #define platform_get_device_id(pdev) ((pdev)->id_entry)
82 * platform_device_register_resndata - add a platform-level device with
83 * resources and platform-specific data
90 * @data: platform specific data for this platform device
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/pm/
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 …]
/kernel/linux/linux-5.10/drivers/pinctrl/samsung/
Dpinctrl-samsung.h1 /* 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 …]
/kernel/linux/linux-4.19/drivers/pinctrl/samsung/
Dpinctrl-samsung.h1 /* 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 …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/hwlock/
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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/hwlock/
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 …]
/kernel/linux/linux-4.19/Documentation/
DSM501.txt15 ----
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 …]
/kernel/linux/linux-5.10/Documentation/driver-api/
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 …]
/kernel/linux/linux-5.10/Documentation/staging/
Dremoteproc.rst10 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 …]
/kernel/linux/linux-4.19/drivers/hwspinlock/
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 * @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 …]
/kernel/linux/linux-5.10/drivers/hwspinlock/
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 * @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 …]

12345678910>>...43