/openbmc/linux/sound/soc/sprd/ |
H A D | Kconfig | 15 is used for sound stream transmission between audio subsystem 16 and other AP/CP subsystem.
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Nvme/ |
H A D | Status.errors.yaml | 11 The NVM subsystem reliability has been degraded due to significant media 12 related errors or any internal error that degrades NVM subsystem
|
H A D | Status.interface.yaml | 31 Represent the NVM subsystem reliability has been degraded due to 33 NVM subsystem reliability
|
/openbmc/linux/Documentation/gpu/ |
H A D | introduction.rst | 73 Developers interested in helping out with the DRM subsystem are very welcome. 83 Mostly the DRM subsystem works like any other kernel subsystem, see :ref:`the 85 Here we just document some of the specialities of the GPU subsystem. 119 The DRM subsystem contains a lot of helper functions to ease writing drivers for 124 any complexity of the DRM subsystem and just requires drivers to implement a few 134 Delving into a Linux kernel subsystem for the first time can be an overwhelming 136 subsystem's internals, among other details. 150 in which the changes to the DRM subsystem were made. 158 * `An introduction to the Linux DRM subsystem <https://www.youtube.com/watch?v=LbDOCJcDRoo>`_ - Max… 172 * `The DRM/KMS subsystem from a newbie’s point of view <https://bootlin.com/pub/conferences/2014/el…
|
/openbmc/linux/Documentation/timers/ |
H A D | hrtimers.rst | 2 hrtimers - subsystem for high-resolution kernel timers 5 This patch introduces a new subsystem for high-resolution kernel timers. 7 One might ask the question: we already have a timer subsystem 36 - the implementation of the current posix-timer subsystem on top of 51 largely expect the timer subsystem to have near-zero overhead. 62 high-resolution timer subsystem as well. 64 While this subsystem does not offer high-resolution clock sources just 65 yet, the hrtimer subsystem can be easily extended with high-resolution 75 hrtimers. E.g. we could decrease the frequency of the timeout subsystem 78 hrtimer subsystem implementation details [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | sprd-mcdt.txt | 4 transmission between audio subsystem and other AP/CP subsystem. It
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | intro.rst | 7 The media subsystem consists on Linux support for several different types 19 Due to the diversity of devices, the subsystem provides several different
|
/openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
H A D | qcom,rpm-proc.yaml | 15 Resource Power Manager (RPM) subsystem found in various Qualcomm platforms: 18 | RPM subsystem (qcom,rpm-proc) | 35 The firmware running on the processor inside the RPM subsystem allows each 99 channels and devices related to the RPM subsystem. 105 channels and devices related to the RPM subsystem.
|
/openbmc/linux/Documentation/driver-api/hte/ |
H A D | hte.rst | 52 - Pushes this hte_ts_data object to HTE subsystem. 53 - HTE subsystem increments seq counter and invokes consumer provided callback. 57 HTE subsystem debugfs attributes 59 HTE subsystem creates debugfs attributes at ``/sys/kernel/debug/hte/``.
|
/openbmc/linux/sound/pci/emu10k1/ |
H A D | emu10k1.c | 34 static uint subsystem[SNDRV_CARDS]; /* Force card subsystem model */ variable 54 module_param_array(subsystem, uint, NULL, 0444); 55 MODULE_PARM_DESC(subsystem, "Force card subsystem model."); 98 enable_ir[dev], subsystem[dev]); in snd_card_emu10k1_probe()
|
/openbmc/linux/Documentation/devicetree/bindings/clock/ |
H A D | marvell,pxa168.txt | 3 The PXA168 clock subsystem generates and supplies clock to various 11 - reg: physical base address of the clock subsystem and length of memory mapped
|
H A D | marvell,pxa910.txt | 3 The PXA910 clock subsystem generates and supplies clock to various 11 - reg: physical base address of the clock subsystem and length of memory mapped
|
/openbmc/linux/drivers/staging/fieldbus/Documentation/ |
H A D | fieldbus_dev.txt | 29 Part I - Why do we need this subsystem? 38 The purpose of this subsystem is: 42 Part II - How can drivers use the subsystem? 49 Part III - How can userspace use the subsystem?
|
/openbmc/linux/Documentation/devicetree/bindings/media/ |
H A D | imx.txt | 12 - compatible : "fsl,imx-capture-subsystem"; 18 capture-subsystem { 19 compatible = "fsl,imx-capture-subsystem";
|
/openbmc/linux/Documentation/leds/ |
H A D | leds-blinkm.rst | 27 brightness device max_brightness power subsystem trigger uevent 30 brightness device max_brightness power subsystem trigger uevent 33 brightness device max_brightness power subsystem trigger uevent
|
/openbmc/phosphor-logging/extensions/openpower-pels/ |
H A D | ascii_string.cpp | 52 setByte(2, entry.subsystem ? entry.subsystem.value() : 0x70); in AsciiString()
|
H A D | user_header.cpp | 82 subsys = entry.subsystem; in UserHeader() 255 std::string subsystem; in getJSON() local 260 subsystem = pv::getValue(_eventSubsystem, pel_values::subsystemValues); in getJSON() 286 jsonInsert(uh, "Subsystem", subsystem, 1); in getJSON()
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | configfs-iio | 21 will result in creating a hrtimer trigger in the IIO subsystem. 34 in creating a dummy IIO device in the IIO subsystem.
|
/openbmc/linux/lib/ |
H A D | kobject_uevent.c | 252 static int init_uevent_argv(struct kobj_uevent_env *env, const char *subsystem) in init_uevent_argv() argument 257 len = strlcpy(&env->buf[env->buflen], subsystem, buffer_size); in init_uevent_argv() 463 const char *subsystem; in kobject_uevent_env() local 513 subsystem = uevent_ops->name(kobj); in kobject_uevent_env() 515 subsystem = kobject_name(&kset->kobj); in kobject_uevent_env() 516 if (!subsystem) { in kobject_uevent_env() 542 retval = add_uevent_var(env, "SUBSYSTEM=%s", subsystem); in kobject_uevent_env() 609 retval = init_uevent_argv(env, subsystem); in kobject_uevent_env()
|
/openbmc/linux/net/rfkill/ |
H A D | Kconfig | 3 # RF switch subsystem configuration 6 tristate "RF switch subsystem support"
|
/openbmc/linux/Documentation/devicetree/bindings/iio/adc/ |
H A D | ti,twl4030-madc.yaml | 7 title: MADC subsystem in the TWL4030 power module 13 The MADC subsystem in the TWL4030 consists of a 10-bit ADC
|
/openbmc/linux/net/nfc/ |
H A D | Kconfig | 3 # NFC subsystem configuration 8 tristate "NFC subsystem support"
|
/openbmc/linux/Documentation/networking/ |
H A D | nfc.rst | 2 Linux NFC subsystem 5 The Near Field Communication (NFC) subsystem is required to standardize the 14 The NFC subsystem is responsible for: 19 The subsystem is divided in some parts. The 'core' is responsible for 58 When registering on the NFC subsystem, the device driver must inform the core
|
/openbmc/linux/Documentation/power/powercap/ |
H A D | powercap.rst | 60 │ │ ├──subsystem -> ../../../../../../class/power_cap 77 │ │ ├──subsystem -> ../../../../../../class/power_cap 86 │ ├──subsystem -> ../../../../../class/power_cap 113 │ │ ├──subsystem -> ../../../../../../class/power_cap 130 │ │ ├──subsystem -> ../../../../../../class/power_cap 139 │ ├──subsystem -> ../../../../../class/power_cap 144 ├──subsystem -> ../../../../class/power_cap
|
/openbmc/phosphor-logging/test/openpower-pels/ |
H A D | ascii_string_test.cpp | 29 entry.subsystem = 0x37; in TEST() 55 entry.subsystem = 0x37; in TEST()
|