| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/ |
| H A D | iwl-drv.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
3 * Copyright (C) 2005-2014, 2020-2021, 2023 Intel Corporation
4 * Copyright (C) 2013-2014 Intel Mobile Communications GmbH
14 #define NVM_RF_CFG_DASH_MSK(x) (x & 0x3) /* bits 0-1 */
15 #define NVM_RF_CFG_STEP_MSK(x) ((x >> 2) & 0x3) /* bits 2-3 */
16 #define NVM_RF_CFG_TYPE_MSK(x) ((x >> 4) & 0x3) /* bits 4-5 */
17 #define NVM_RF_CFG_PNUM_MSK(x) ((x >> 6) & 0x3) /* bits 6-7 */
18 #define NVM_RF_CFG_TX_ANT_MSK(x) ((x >> 8) & 0xF) /* bits 8-11 */
19 #define NVM_RF_CFG_RX_ANT_MSK(x) ((x >> 12) & 0xF) /* bits 12-15 */
29 * DOC: Driver system flows - drv component
[all …]
|
| /openbmc/linux/Documentation/driver-api/driver-model/ |
| H A D | driver.rst | 18 The driver must initialize at least the name and bus fields. It should
33 .bus = &pci_bus_type,
42 model because the bus they belong to has a bus-specific structure with
43 bus-specific fields that cannot be generalized.
48 completely bus-specific. Defining them as bus-specific entities would
49 sacrifice type-safety, so we keep bus-specific structures around.
51 Bus-specific drivers should include a generic struct device_driver in
52 the definition of the bus-specific driver. Like this::
59 A definition that included bus-specific fields would look like
66 .bus = &pci_bus_type,
[all …]
|
| H A D | porting.rst | 12 Please refer to `Documentation/driver-api/driver-model/*.rst` for definitions of
16 at the bus driver layer. This was intentional, to minimize the
18 of bus drivers.
21 be embedded in larger, bus-specific objects. Fields in these generic
22 objects can replace fields in the bus-specific objects.
28 # mount -t sysfs sysfs /sys
36 Step 1: Registering the bus driver.
39 - Define a struct bus_type for the bus driver::
46 - Register the bus type.
48 This should be done in the initialization function for the bus type,
[all …]
|
| H A D | bus.rst | 2 Bus Types
9 int bus_register(struct bus_type * bus);
15 Each bus type in the kernel (PCI, USB, etc) should declare one static
32 When a bus driver is initialized, it calls bus_register. This
33 initializes the rest of the fields in the bus object and inserts it
34 into a global list of bus types. Once the bus object is registered,
35 the fields in it are usable by the bus driver.
45 them are inherently bus-specific. Drivers typically declare an array
46 of device IDs of devices they support that reside in a bus-specific
49 The purpose of the match callback is to give the bus an opportunity to
[all …]
|
| H A D | overview.rst | 16 bus-specific drivers for bridges and devices by consolidating a set of data
19 Traditional driver models implemented some sort of tree-like structure
21 uniformity across the different bus types.
24 a bus and the devices that can appear under the bus. The unified bus
26 of common callbacks, such as device discovery during bus probing, bus
27 shutdown, bus power management, etc.
32 Microsoft (namely ACPI) ensures that almost every device on almost any bus
33 on an x86-compatible system can work within this paradigm. Of course,
34 not every bus is able to support all such operations, although most
41 Common data fields have been moved out of individual bus layers into a common
[all …]
|
| /openbmc/linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-driver-hid-roccat-isku | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
4 Description: The integer value of this attribute ranges from 0-4.
12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
20 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
35 capslock key for a specific profile. Profile number is included
41 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
45 easyzone keys for a specific profile. Profile number is included
51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
55 function keys for a specific profile. Profile number is included
[all …]
|
| H A D | sysfs-driver-hid-roccat-ryos | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
9 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
21 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
25 a specific profile. Profile index is included in written data.
31 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
35 function keys for a specific profile. Profile index is included
41 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
45 keys for a specific profile. Profile index is included in
51 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
55 thumbster keys for a specific profile. Profile index is included
[all …]
|
| /openbmc/linux/drivers/bcma/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
8 tristate "Broadcom specific AMBA"
11 Bus driver for Broadcom specific Advanced Microcontroller Bus
16 # Support for Block-I/O. SELECT this from the driver that needs it.
26 bool "Support for BCMA on PCI-host bus"
35 Host interface for a Broadcom AIX bus directly mapped into
46 BCMA bus may have many versions of PCIe core. This driver
61 PCI core hostmode operation (external PCI bus).
67 Driver for the Broadcom MIPS core attached to Broadcom specific
68 Advanced Microcontroller Bus.
[all …]
|
| /openbmc/linux/include/linux/device/ |
| H A D | bus.h | 1 // SPDX-License-Identifier: GPL-2.0
3 * bus.h - the bus-specific portions of the driver model
5 * Copyright (c) 2001-2003 Patrick Mochel <mochel@osdl.org>
6 * Copyright (c) 2004-2009 Greg Kroah-Hartman <gregkh@suse.de>
7 * Copyright (c) 2008-2009 Novell Inc.
8 * Copyright (c) 2012-2019 Greg Kroah-Hartman <gregkh@linuxfoundation.org>
9 * Copyright (c) 2012-2019 Linux Foundation
11 * See Documentation/driver-api/driver-model/ for more information.
25 * struct bus_type - The bus type of the device
27 * @name: The name of the bus.
[all …]
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | typec_bus.rst | 2 API for USB Type-C Alternate Mode drivers
6 ------------
9 Messages (VDM) as defined in USB Type-C and USB Power Delivery Specifications.
10 The communication is SVID (Standard or Vendor ID) specific, i.e. specific for
13 USB Type-C bus allows binding a driver to the discovered partner alternate
16 :ref:`USB Type-C Connector Class <typec>` provides a device for every alternate
29 specific commands from the alternate mode drivers to the partner, and from the
30 partners to the alternate mode drivers. No direct SVID specific communication is
36 ------
43 space (See Documentation/ABI/testing/sysfs-class-typec). Port drivers should not
[all …]
|
| /openbmc/linux/Documentation/driver-api/i3c/ |
| H A D | protocol.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 everything hardware related (like how things are transmitted on the bus, how
17 https://resources.mipi.org/mipi-i3c-v1-download).
22 The I3C (pronounced 'eye-three-see') is a MIPI standardized protocol designed
24 interrupts, no automatic detection of the devices connected to the bus, ...)
25 while remaining power-efficient.
27 I3C Bus
30 An I3C bus is made of several I3C devices and possibly some I2C devices as
33 An I3C device on the I3C bus can have one of the following roles:
35 * Master: the device is driving the bus. It's the one in charge of initiating
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/exynos/ |
| H A D | dwmmc.txt | 4 . Embedded Multimedia Cards (EMMC-version 4.5)
5 . Secure Digital memory (SD mem-version 2.0)
6 . Secure Digital I/O (SDIO-version 3.0)
7 . Consumer Electronics Advanced Transport Architecture (CE-ATA-version 1.1)
10 SOC specific and Board specific properties are channel specific.
12 Required SoC Specific Properties:
14 - compatible: should be
15 - samsung,exynos-dwmmc: for exynos platforms
17 - reg: physical base address of the controller and length of memory mapped
20 - interrupts: The interrupt number to the cpu.
[all …]
|
| /openbmc/dbus-sensors/include/linux/ |
| H A D | peci-ioctl.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
2 /* Copyright (c) 2018-2019 Intel Corporation */
4 // clang-format off
26 /* Device Specific Completion Code (CC) Definition */
48 * enum peci_cmd - PECI client commands
55 * @PECI_CMD_RD_IA_MSR: read access to MSRs (Model Specific Registers)
56 * @PECI_CMD_WR_IA_MSR: write access to MSRs (Model Specific Registers)
57 * @PECI_CMD_RD_IA_MSREX: read access to MSRs (Model Specific Registers)
91 * struct peci_xfer_msg - raw PECI transfer command
110 * struct peci_ping_msg - ping command
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.drivers.eth | 5 U-Boot core driver model. See doc/driver-model/README.txt
7 -----------------------
9 -----------------------
11 The networking stack in Das U-Boot is designed for multiple network devices
16 ------------------
18 ------------------
21 meaning of 0 for success and non-zero for failure.
23 ----------
25 ----------
27 When U-Boot initializes, it will call the common function eth_initialize().
[all …]
|
| /openbmc/docs/designs/ |
| H A D | nmi-dbus-interface.md | 7 Created: 2019-05-21
19 causing system hang(https://github.com/ibm-openbmc/dev/issues/457). This means
24 which, in turn, triggers an architecture-dependent procedure that fires an
30 architecture-specific procedure that enables data collection followed by
34 ### D-Bus
36 Introducing new D-Bus interface in the control.host namespace
37 (/openbmc/phosphor-dbus-interfaces/xyz/openbmc_project/Control/Host/
38 NMI.interface.yaml) and implement the new D-Bus back-end for respective
39 processor specific targets.
43 Enable NMI D-Bus phosphor interface and support this via Redfish
[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 …]
|
| H A D | pldm-stack.md | 5 Created: 2019-01-22
9 On OpenBMC, in-band IPMI is currently the primary industry-standard means of
24 PLDM's purpose is to enable all sorts of "inside the box communication": BMC -
25 Host, BMC - BMC, BMC - Network Controller and BMC - Other (for e.g. sensor)
31 efficient access to low-level platform inventory, monitoring, control, event,
48 - Common in-band communication protocol.
50 - Already existing PLDM Type specifications that cover the most common
55 - PLDM sensors are 2 bytes in length.
57 - PLDM introduces the concept of effecters - a control mechanism. Both sensors
64 - A very active PLDM related working group in the DMTF.
[all …]
|
| /openbmc/linux/Documentation/leds/ |
| H A D | leds-lp55xx.rst | 8 -----------
14 Device attributes for user-space interface
47 To support device specific configurations, special structure
50 - Maximum number of channels
51 - Reset command, chip enable command
52 - Chip specific initialization
53 - Brightness control register access
54 - Setting LED output current
55 - Program memory address access for running patterns
56 - Additional device specific attributes
[all …]
|
| /openbmc/linux/drivers/interconnect/qcom/ |
| H A D | icc-rpm.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
9 #include <linux/soc/qcom/smd-rpm.h>
11 #include <dt-bindings/interconnect/qcom,rpm-icc.h>
13 #include <linux/interconnect-provider.h>
29 * struct rpm_clk_resource - RPM bus clock resource
31 * @clock_id: index of the clock resource of a specific resource type
41 * struct qcom_icc_provider - Qualcomm specific interconnect provider
47 * @bus_clk_rate: bus clock rate in Hz
48 * @bus_clk_desc: a pointer to a rpm_clk_resource description of bus clocks
49 * @bus_clk: a pointer to a HLOS-owned bus clock
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-opal.txt | 1 Device-tree bindings for I2C OPAL driver
2 ----------------------------------------
4 Most of the device node and properties layout is specific to the firmware and
6 perspective, the properties of use are "ibm,port-name" and "ibm,opal-id".
10 - reg: Port-id within a given master
11 - compatible: must be "ibm,opal-i2c"
12 - ibm,opal-id: Refers to a specific bus and used to identify it when calling
14 - bus-frequency: Operating frequency of the i2c bus (in HZ). Informational for
18 - ibm,port-name: Firmware provides this name that uniquely identifies the i2c
22 and depend on the specific hardware implementation. The example below depicts
[all …]
|
| /openbmc/linux/include/linux/platform_data/ |
| H A D | brcmfmac.h | 27 * Platform specific driver functions and data. Through the platform specific
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
48 * enum brcmf_bus_type - Bus type identifier. Currently SDIO, USB and PCIE are
59 * struct brcmfmac_sdio_pd - SDIO Device specific platform data.
69 * in-band interrupts are relatively slow and for having
88 * specific and this function should return only after the
104 * struct brcmfmac_pd_cc_entry - Struct for translating user space country code
[all …]
|
| /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
12 tristate "PCI bus based UFS Controller support"
31 tristate "Platform bus based UFS Controller support"
35 you have an UFS controller on Platform bus.
45 This selects the Cadence-specific additions to UFSHCD platform driver.
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
67 specific registers.
[all …]
|
| /openbmc/linux/drivers/staging/fieldbus/Documentation/devicetree/bindings/fieldbus/ |
| H A D | arcx,anybus-controller.txt | 1 * Arcx Anybus-S controller
3 This chip communicates with the SoC over a parallel bus. It is
5 corresponding to the parallel bus used for communication.
8 --------------------
10 - compatible : The following chip-specific string:
11 "arcx,anybus-controller"
13 - reg : three areas:
14 index 0: bus memory area where the cpld registers are located.
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.
[all …]
|
| /openbmc/linux/drivers/i3c/ |
| H A D | device.c | 1 // SPDX-License-Identifier: GPL-2.0
18 * i3c_device_do_priv_xfers() - do I3C SDR private transfers directed to a
19 * specific device
42 return -EINVAL; in i3c_device_do_priv_xfers()
45 i3c_bus_normaluse_lock(dev->bus); in i3c_device_do_priv_xfers()
46 ret = i3c_dev_do_priv_xfers_locked(dev->desc, xfers, nxfers); in i3c_device_do_priv_xfers()
47 i3c_bus_normaluse_unlock(dev->bus); in i3c_device_do_priv_xfers()
54 * i3c_device_do_setdasa() - do I3C dynamic address assignement with
65 i3c_bus_normaluse_lock(dev->bus); in i3c_device_do_setdasa()
66 ret = i3c_dev_setdasa_locked(dev->desc); in i3c_device_do_setdasa()
[all …]
|
| /openbmc/linux/include/linux/i3c/ |
| H A D | master.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
38 * struct i3c_i2c_dev_desc - Common part of the I3C/I2C device descriptor
44 * add master specific information
61 * struct i2c_dev_boardinfo - I2C device board information
67 * This structure is used to attach board-level information to an I2C device.
68 * Each I2C device connected on the I3C bus should have one.
77 * struct i2c_dev_desc - I2C device descriptor
85 * Each I2C device connected on the bus will have an i2c_dev_desc.
87 * using &struct_i3c_master_controller->ops->attach_i2c_dev().
90 * connected on an I3C bus. This object is also passed to all
[all …]
|