Home
last modified time | relevance | path

Searched +full:composite +full:- +full:in (Results 1 – 25 of 360) sorted by relevance

12345678910>>...15

/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DStorageControllerMetrics.v1_0_3.json4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 …"longDescription": "The object shall contain the NVMe-defined 'Endurance Group Critical Warning Su…
39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
54 … indication of whether namespaces in one or more Endurance Groups are in read-only mode not as a r…
55 …shall indicate whether namespaces in one or more Endurance Groups are in read-only mode not as a r…
63 …ability of one or more Endurance Groups is degraded due to significant media-related errors or any…
[all …]
/openbmc/u-boot/doc/
H A DREADME.video1 SPDX-License-Identifier: GPL-2.0+
4 * Paolo Scaffardi, AIRVENT SAM s.p.a - RIMINI(ITALY), arsenio@tin.it
7 "video-mode" environment variable
10 The 'video-mode' environment variable can be used to enable and configure
11 some video drivers. The format matches the video= command-line option used
14 video-mode=<driver>:<xres>x<yres>-<depth>@<freq><,option=string>
16 <driver> The video driver name, ignored by U-Boot
17 <xres> The X resolution (in pixels) to use.
18 <yres> The Y resolution (in pixels) to use.
19 <depth> The color depth (in bits) to use.
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DStorageControllerMetrics_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################
4 <!--# Redfish Schema: StorageControllerMetrics v1.0.3
5 <!--#
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle,
7 <!--# available at http://www.dmtf.org/standards/redfish
8 <!--# Copyright 2014-2024 DMTF in cooperation with Storage Networking Industry Association (SNIA).
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright
10 <!--################################################################################
[all …]
/openbmc/linux/Documentation/devicetree/bindings/clock/ti/
H A Dcomposite.txt1 Binding for TI composite clock.
3 Binding status: Unstable - ABI compatibility may be broken in the future
6 register-mapped composite clock with multiple different sub-types;
18 "ti,*composite*-clock" types.
20 [1] Documentation/devicetree/bindings/clock/clock-bindings.txt
26 - compatible : shall be: "ti,composite-clock"
27 - clocks : link phandles of component clocks
28 - #clock-cells : from common clock binding; shall be set to 0.
31 - clock-output-names : from common clock binding.
36 #clock-cells = <0>;
[all …]
H A Dgate.txt3 Binding status: Unstable - ABI compatibility may be broken in the future
6 quite much similar to the basic gate-clock [2], however,
9 will be controlled instead and the corresponding hw-ops for
12 [1] Documentation/devicetree/bindings/clock/clock-bindings.txt
13 [2] Documentation/devicetree/bindings/clock/gpio-gate-clock.yaml
17 - compatible : shall be one of:
18 "ti,gate-clock" - basic gate clock
19 "ti,wait-gate-clock" - gate clock which waits until clock is active before
21 "ti,dss-gate-clock" - gate clock with DSS specific hardware handling
22 "ti,am35xx-gate-clock" - gate clock with AM35xx specific hardware handling
[all …]
H A Dmux.txt3 Binding status: Unstable - ABI compatibility may be broken in the future
6 register-mapped multiplexer with multiple input clock signals or
10 By default the "clocks" property lists the parents in the same order
15 results in programming the register as follows:
24 "index-starts-at-one" modified the scheme as follows:
32 the number of bits to shift the control field in the register can be
36 [1] Documentation/devicetree/bindings/clock/clock-bindings.txt
39 - compatible : shall be "ti,mux-clock" or "ti,composite-mux-clock".
40 - #clock-cells : from common clock binding; shall be set to 0.
41 - clocks : link phandles of parent clocks
[all …]
/openbmc/u-boot/drivers/usb/gadget/
H A Dcomposite.c1 // SPDX-License-Identifier: GPL-2.0+
3 * composite.c - infrastructure for Composite USB Gadgets
5 * Copyright (C) 2006-2008 David Brownell
6 * U-Boot porting: Lukasz Majewski <l.majewski@samsung.com>
11 #include <linux/usb/composite.h>
15 static struct usb_composite_driver *composite; variable
18 * usb_add_function() - add a function to a configuration
34 int value = -EINVAL; in usb_add_function()
37 function->name, function, in usb_add_function()
38 config->label, config); in usb_add_function()
[all …]
/openbmc/linux/drivers/usb/gadget/legacy/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
23 # Gadget drivers are hardware-neutral, or "platform independent",
32 # gadget configuration. In the device model, each option contains
44 Gadget Zero is a two-configuration device. It either sinks and
[all …]
/openbmc/linux/Documentation/usb/
H A Dmass-storage.rst9 appearing to the host as a disk or a CD-ROM drive. It supports
12 to read-only, and gadget can indicate that it is removable and/or
13 CD-ROM (the latter implies read-only access).
15 Its requirements are modest; only a bulk-in and a bulk-out endpoint
17 Support is included for full-speed, high-speed and SuperSpeed
20 Note that the driver is slightly non-portable in that it assumes
21 a single memory/DMA buffer will be usable for bulk-in and bulk-out
29 (which is no longer included in Linux). It will talk only briefly
30 about how to use MSF within composite gadgets.
38 - file=filename[,filename...]
[all …]
H A Dgadget_multi.rst2 Multifunction Composite Gadget
8 The Multifunction Composite Gadget (or g_multi) is a composite gadget
9 that makes extensive use of the composite framework to provide
12 In its standard configuration it provides a single USB configuration
18 have two configurations -- one with RNDIS and another with CDC ECM[3].
20 Please note that if you use non-standard configuration (that is enable
26 To make use of the gadget one needs to make it work on host side --
31 ------------------
33 Since the gadget uses standard composite framework and appears as such
38 This is also true for two configuration set-up with RNDIS
[all …]
H A Dfunctionfs.rst5 From kernel point of view it is just a composite function with some
9 that kernel level composite functions provide when they are added to
12 This in particular means that the composite initialisation functions
13 may not be in init section (ie. may not use the __init tag).
22 them as needed also handling situation when numbers differ in
35 What I also want to mention is that the FunctionFS is designed in such
36 a way that it is possible to mount it several times so in the end
46 $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp
47 $ ( cd /dev/ffs-mtp && mtp-daemon ) &
48 $ mkdir /dev/ffs-hid && mount -t functionfs hid /dev/ffs-hid
[all …]
/openbmc/u-boot/include/linux/usb/
H A Dcomposite.h1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * composite.h -- framework for usb gadgets which are composite devices
5 * Copyright (C) 2006-2008 David Brownell
13 * making it easier to build (a) Composite devices, supporting multiple
14 * functions within any single configuration, and (b) Multi-configuration
19 * link and mass storage functions is a composite device. Those functions
20 * might alternatively be packaged in individual configurations, but in
21 * the composite model the host can use both functions at the same time.
41 * struct usb_function - describes one function of a configuration
44 * and by language IDs provided in control requests
[all …]
/openbmc/linux/drivers/clk/rockchip/
H A Dclk-rk3368.c1 // SPDX-License-Identifier: GPL-2.0-or-later
6 #include <linux/clk-provider.h>
11 #include <dt-bindings/clock/rk3368-cru.h>
200 /* cluster_b: aclkm in clksel0, rest in clksel1 */
210 /* cluster_l: aclkm in clksel2, rest in clksel3 */
276 * Clock-Architecture Diagram 2
320 COMPOSITE(0, "aclk_cci_pre", mux_pll_src_cpll_gpll_usb_npll_p, CLK_IGNORE_UNUSED,
356 COMPOSITE(0, "fclk_mcu_src", mux_pll_src_cpll_gpll_p, CLK_IGNORE_UNUSED,
360 * stclk_mcu is listed as child of fclk_mcu_src in diagram 5,
361 * but stclk_mcu has an additional own divider in diagram 2
[all …]
H A Dclk-rk3399.c1 // SPDX-License-Identifier: GPL-2.0-or-later
4 * Author: Xing Zheng <zhengxing@rock-chips.com>
7 #include <linux/clk-provider.h>
15 #include <dt-bindings/clock/rk3399-cru.h>
337 /* cluster_l: aclkm in clksel0, rest in clksel1 */
347 /* cluster_b: aclkm in clksel2, rest in clksel3 */
402 * CRU Clock-Architecture
425 COMPOSITE(ACLK_USB3, "aclk_usb3", mux_pll_src_cpll_gpll_npll_p, 0,
444 COMPOSITE(SCLK_USB3OTG0_SUSPEND, "clk_usb3otg0_suspend", mux_pll_p, 0,
448 COMPOSITE(SCLK_USB3OTG1_SUSPEND, "clk_usb3otg1_suspend", mux_pll_p, 0,
[all …]
H A Dclk-rk3288.c1 // SPDX-License-Identifier: GPL-2.0-or-later
7 #include <linux/clk-provider.h>
12 #include <dt-bindings/clock/rk3288-cru.h>
284 * Clock-Architecture Diagram 1
360 COMPOSITE(0, "i2s_src", mux_pll_src_cpll_gpll_p, 0,
411 * Clock-Architecture Diagram 2
414 COMPOSITE(0, "aclk_vepu", mux_pll_src_cpll_gpll_usb480m_p, 0,
417 COMPOSITE(0, "aclk_vdpu", mux_pll_src_cpll_gpll_usb480m_p, 0,
431 COMPOSITE(0, "aclk_vio0", mux_pll_src_cpll_gpll_usb480m_p, CLK_IGNORE_UNUSED,
434 COMPOSITE(0, "aclk_vio1", mux_pll_src_cpll_gpll_usb480m_p, CLK_IGNORE_UNUSED,
[all …]
/openbmc/linux/drivers/usb/gadget/
H A Dconfigfs.c1 // SPDX-License-Identifier: GPL-2.0
8 #include <linux/usb/composite.h>
26 return -EINVAL; in check_user_usb_string()
28 stringtab_dev->language = num; in check_user_usb_string()
50 struct usb_composite_driver composite; member
86 return container_of(cfg->c.cdev, struct gadget_info, cdev); in cfg_to_gadget_info()
121 return -EOVERFLOW; in usb_string_copy()
123 return -EINVAL; in usb_string_copy()
130 return -ENOMEM; in usb_string_copy()
133 if (str[ret - 1] == '\n') in usb_string_copy()
[all …]
/openbmc/linux/include/media/i2c/
H A Dupd64083.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * upd6408x - NEC Electronics 3-Dimensional Y/C separation input defines
11 /* There are two bits of information that the driver needs in order
15 The first two operating modes expect a composite signal on the Y input,
18 Normally YCS_MODE is used for tuner and composite inputs, and the
19 YCNR mode is used for S-Video inputs.
21 The external Y-ADC is selected when the composite input comes from a
23 the input is a S-Video signal, then the internal Y-ADC input should
33 /* Note: the following two modes cannot be used in combination with the
34 external Y-ADC. */
[all …]
/openbmc/linux/include/linux/usb/
H A Dcomposite.h1 // SPDX-License-Identifier: GPL-2.0+
3 * composite.h -- framework for usb gadgets which are composite devices
5 * Copyright (C) 2006-2008 David Brownell
13 * making it easier to build (a) Composite devices, supporting multiple
14 * functions within any single configuration, and (b) Multi-configuration
19 * link and mass storage functions is a composite device. Those functions
20 * might alternatively be packaged in individual configurations, but in
21 * the composite model the host can use both functions at the same time.
51 * struct usb_os_desc_ext_prop - describes one "Extended Property"
58 * @item: Represents this Extended Property in configfs
[all …]
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/
H A Dlibxcomposite_0.4.6.bb1 SUMMARY = "Xcomposite: X Composite extension library"
3 DESCRIPTION = "The composite extension provides three related \
4 mechanisms: per-hierarchy storage, automatic shadow update, and external \
5 parent. In per-hierarchy storage, the rendering of an entire hierarchy \
6 of windows is redirected to off-screen storage. In automatic shadow \
7 update, when a hierarchy is rendered off-screen, the X server provides \
9 window. In external parent, a mechanism for providing redirection of \
12 require xorg-lib-common.inc
/openbmc/linux/drivers/media/pci/ivtv/
H A Divtv-routing.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 Audio/video-routing-related ivtv functions.
4 Copyright (C) 2003-2004 Kevin Thayer <nufan_wfk at yahoo.com>
5 Copyright (C) 2005-2007 Hans Verkuil <hverkuil@xs4all.nl>
9 #include "ivtv-driver.h"
10 #include "ivtv-i2c.h"
11 #include "ivtv-cards.h"
12 #include "ivtv-gpio.h"
13 #include "ivtv-routing.h"
15 #include <media/drv-intf/msp3400.h>
[all …]
/openbmc/linux/drivers/media/platform/xilinx/
H A Dxilinx-dma.h1 /* SPDX-License-Identifier: GPL-2.0 */
5 * Copyright (C) 2013-2015 Ideas on Board
6 * Copyright (C) 2013-2015 Xilinx, Inc.
20 #include <media/media-entity.h>
21 #include <media/v4l2-dev.h>
22 #include <media/videobuf2-v4l2.h>
29 * struct xvip_pipeline - Xilinx Video IP pipeline structure
34 * @num_dmas: number of DMA engines in the pipeline
59 * struct xvip_dma - Video DMA channel
60 * @list: list entry in a composite device dmas list
[all …]
/openbmc/linux/Documentation/driver-api/media/drivers/
H A Dzoran.rst1 .. SPDX-License-Identifier: GPL-2.0
8 website: http://mjpeg.sourceforge.net/driver-zoran/
12 --------------------------
15 ------------------------
28 Drivers to use: videodev, i2c-core, i2c-algo-bit,
31 Inputs/outputs: Composite and S-video
45 Drivers to use: videodev, i2c-core, i2c-algo-bit,
49 Six physical inputs. 1-6 are composite,
50 1-2, 3-4, 5-6 doubles as S-video,
51 1-3 triples as component.
[all …]
/openbmc/pldm/libpldmresponder/test/pdr_jsons/state_sensor/malformed/
H A Dsensor_pdr.json2 // composite sensors.
7 // Each sensor in each group of composite sensors has a separate entry and the
9 // The "dbus" section contains information about the corresponding D-Bus
10 // property for the sensor and "property_values" are the D-Bus property values
11 // for each corresponding entry in the "states".
/openbmc/pldm/libpldmresponder/
H A Doem_handler.hpp23 * @param[in] entityType - entity type corresponding to the sensor
24 * @param[in] entityInstance - entity instance number
25 * @param[in] entityContainerID - container id
26 * @param[in] stateSetId - state set id
27 * @param[in] compSensorCnt - composite sensor count
28 * @param[in] sensorId - sensor ID
29 * @param[out] stateField - The state field data for each of the states,
30 * equal to composite sensor count in number
32 * @return - Success or failure in getting the states. Returns failure in
48 * @param[in] entityType - entity type corresponding to the effecter id
[all …]
H A Dplatform_state_effecter.hpp11 #include <phosphor-logging/lg2.hpp>
26 * @tparam[in] DBusInterface - DBus interface type
27 * @tparam[in] Handler - pldm::responder::platform::Handler
28 * @param[in] dBusIntf - The interface object of DBusInterface
29 * @param[in] handler - The interface object of
31 * @param[in] effecterId - Effecter ID sent by the requester to act on
32 * @param[in] stateField - The state field data for each of the states,
33 * equal to composite effecter count in number
34 * @return - Success or failure in setting the states. Returns failure in
72 if (pdr->effecter_id != effecterId) in setStateEffecterStatesHandler()
[all …]

12345678910>>...15