| /openbmc/linux/Documentation/sound/designs/ |
| H A D | seq-oss.rst | 2 OSS Sequencer Emulation on ALSA
12 This directory contains the OSS sequencer emulation driver on ALSA. Note
15 What this does - it provides the emulation of the OSS sequencer, access
16 via ``/dev/sequencer`` and ``/dev/music`` devices.
18 sequencer is prepared.
22 * Normal sequencer and MIDI events:
24 They are converted to the ALSA sequencer events, and sent to the
52 sequencer)!
74 Run configure script with both sequencer support (``--with-sequencer=yes``)
82 already connected to the sequencer. Once after that, the creation and deletion
[all …]
|
| H A D | midi-2.0.rst | 37 implemented differently (e.g. as a ALSA sequencer client), too.
40 rawmidi device and the access via ALSA sequencer API.
42 ALSA sequencer API was extended to allow the payload of UMP packets.
43 It's allowed to connect freely between MIDI 1.0 and MIDI 2.0 sequencer
55 the core support for UMP (`CONFIG_SND_UMP`) and the sequencer binding
169 ALSA Sequencer with USB MIDI 2.0
172 In addition to the rawmidi interfaces, ALSA sequencer interface
173 supports the new UMP MIDI 2.0 device, too. Now, each ALSA sequencer
177 sequencer event as was. Meanwhile, UMP MIDI 1.0 and 2.0 clients send
181 A UMP packet can be sent/received in a sequencer event embedded by
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | README.md | 1 # phosphor-power-sequencer
5 The phosphor-power-sequencer application powers the chassis on/off and monitors
6 the power sequencer device.
9 application uses information from the power sequencer device to determine the
20 creates a collection of C++ objects. These objects represent the power sequencer
23 ## Power sequencer device
25 A power sequencer device enables (turns on) the voltage rails in the correct
28 This application currently supports the following power sequencer device types:
40 - The phosphor-power-sequencer application writes the value 1 to the named GPIO
44 - The power sequencer device powers on all the voltage rails in the correct
[all …]
|
| /openbmc/linux/sound/core/seq/ |
| H A D | Kconfig | 3 tristate "Sequencer support"
7 Say Y or M to enable MIDI sequencer and router support. This
17 tristate "Sequencer dummy client"
19 Say Y here to enable the dummy sequencer client. This client
30 tristate "OSS Sequencer API"
34 Say Y here to enable OSS sequencer emulation (both
35 /dev/sequencer and /dev/music interfaces).
43 bool "Use HR-timer as default sequencer timer"
47 Say Y here to use the HR-timer backend as the default sequencer
68 Packet) events via ALSA sequencer infrastructure, which is an
[all …]
|
| /openbmc/phosphor-power/ |
| H A D | meson.build | 101 ['sequencer-monitor', 'pseq-monitor-pgood.service'],
102 ['sequencer-monitor', 'pseq-monitor.service'],
122 # Get the power sequencer class name
123 sequencer = get_option('power_sequencer') variable
124 if sequencer == 'ucd90160' variable
126 elif sequencer == 'mihawk-cpld' variable
129 # power sequencer is incorrect
130 error('power sequencer is incorrect')
144 conf.set('SEQUENCER', sequencer_class)
187 if get_option('sequencer-monitor')
[all …]
|
| H A D | README.md | 12 - [phosphor-power-sequencer](phosphor-power-sequencer/README.md): JSON-driven
13 application that powers the chassis on/off and monitors the power sequencer
23 - power-sequencer: Original power sequencer monitoring application.
45 - Application-specific configuration data, such as power sequencer type.
|
| H A D | meson.options | 32 description: 'The power sequencer',
53 description: 'The sequencer definition file to use.',
82 'sequencer-monitor',
84 description: 'Enable support for power sequencer control',
89 …description: 'Enable support for power sequencer control utilizing JSON configuration and supporti…
|
| /openbmc/phosphor-power/phosphor-power-sequencer/src/ |
| H A D | device_finder.hpp | 28 namespace phosphor::power::sequencer namespace
36 * Power sequencer device properties.
49 * Class that finds power sequencer devices in the system.
67 * Callback function that is called when a power sequencer device is found.
84 * sequencer device is found
90 * contains power sequencer device properties.
114 * Callback function that is called each time a power sequencer device is
120 * Class used to find D-Bus interfaces that contain power sequencer device
126 } // namespace phosphor::power::sequencer
|
| H A D | rail.hpp | 27 namespace phosphor::power::sequencer namespace
58 * A voltage rail that is enabled or monitored by the power sequencer device.
199 * @param device Power sequencer device that enables and monitors the rail
211 * @param device Power sequencer device that enables and monitors the rail
224 * @param device Power sequencer device that enables and monitors the rail
237 * @param device Power sequencer device that enables and monitors the rail
248 * @param device Power sequencer device that enables and monitors the rail
266 * @param device Power sequencer device that enables and monitors the rail
283 * @param device Power sequencer device that enables and monitors the rail
301 * @param device Power sequencer device that enables and monitors the rail
[all …]
|
| H A D | power_control.hpp | 24 namespace phosphor::power::sequencer namespace
78 * Callback that is called when a power sequencer device is found.
107 * Object that finds the power sequencer device in the system.
112 * Power sequencer device properties.
117 * Power sequencer device that enables and monitors the voltage rails.
226 * Loads the JSON configuration file and creates the power sequencer device
258 * Creates the power sequencer device object based on the device properties.
267 } // namespace phosphor::power::sequencer
|
| /openbmc/phosphor-power/phosphor-power-sequencer/test/ |
| H A D | config_file_parser_error_tests.cpp | 22 using namespace phosphor::power::sequencer;
27 "/usr/share/phosphor-power-sequencer/foo.json"}; in TEST()
32 "ConfigFileParserError: /usr/share/phosphor-power-sequencer/foo.json: " in TEST()
39 "/usr/share/phosphor-power-sequencer/bar.json"}; in TEST()
47 "/usr/share/phosphor-power-sequencer/bar.json"}; in TEST()
51 "ConfigFileParserError: /usr/share/phosphor-power-sequencer/bar.json: " in TEST()
|
| /openbmc/linux/include/sound/ |
| H A D | seq_virmidi.h | 6 * Virtual Raw MIDI client on Sequencer
45 int device; /* sequencer device */
54 /* sequencer mode:
56 * attached sequencer port. sequencer port is not created
61 * sequencer port is created in virmidi.
|
| /openbmc/linux/include/linux/soc/qcom/ |
| H A D | geni-se.h | 324 * geni_se_setup_m_cmd() - Setup the primary sequencer
326 * @cmd: Command/Operation to setup in the primary sequencer.
327 * @params: Parameter for the sequencer command.
329 * This function is used to configure the primary sequencer with the
341 * geni_se_setup_s_cmd() - Setup the secondary sequencer
343 * @cmd: Command/Operation to setup in the secondary sequencer.
344 * @params: Parameter for the sequencer command.
346 * This function is used to configure the secondary sequencer with the
362 * sequencer
366 * primary sequencer.
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| H A D | frontend.json | 145 …uops are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
149 …ops are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy.",
154 …DSB) are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
158 …SB) are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy.",
163 …Decode Queue (IDQ) initiated by Decode Stream Buffer (DSB) while Microcode Sequencer (MS) is busy",
168 …ecode Queue (IDQ) initiated by Decode Stream Buffer (DSB) while Microcode Sequencer (MS) is busy.",
173 …that are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
181 …ed by MITE and delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
189 …tches from DSB (Decode Stream Buffer) or MITE (legacy decode pipeline) to the Microcode Sequencer",
194 …ches from DSB (Decode Stream Buffer) or MITE (legacy decode pipeline) to the Microcode Sequencer.",
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
| H A D | frontend.json | 128 …uops are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
132 …e being delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
137 …DSB) are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
141 …e being delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
146 …Decode Queue (IDQ) initiated by Decode Stream Buffer (DSB) while Microcode Sequencer (MS) is busy",
151 …Queue (IDQ) initiated by Decode Stream Buffer (DSB) while the Microcode Sequencer (MS) is busy. Co…
156 …that are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
159 …e being delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
164 …ed by MITE and delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
167 …ITE and delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
| H A D | frontend.json | 128 …uops are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
132 …e being delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
137 …DSB) are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
141 …e being delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
146 …Decode Queue (IDQ) initiated by Decode Stream Buffer (DSB) while Microcode Sequencer (MS) is busy",
151 …Queue (IDQ) initiated by Decode Stream Buffer (DSB) while the Microcode Sequencer (MS) is busy. Co…
156 …that are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
159 …e being delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
164 …ed by MITE and delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
167 …ITE and delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/broadwell/ |
| H A D | frontend.json | 128 …uops are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
132 …e being delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
137 …DSB) are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
141 …e being delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
146 …Decode Queue (IDQ) initiated by Decode Stream Buffer (DSB) while Microcode Sequencer (MS) is busy",
151 …Queue (IDQ) initiated by Decode Stream Buffer (DSB) while the Microcode Sequencer (MS) is busy. Co…
156 …that are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
159 …e being delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
164 …ed by MITE and delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
167 …ITE and delivered to Instruction Decode Queue (IDQ) while the Microcode Sequencer (MS) is busy. Co…
[all …]
|
| /openbmc/linux/sound/core/seq/oss/ |
| H A D | seq_oss_device.h | 3 * OSS compatible sequencer driver
67 * sequencer client information
73 int cseq; /* sequencer client number */
74 int port; /* sequencer port number */
75 int queue; /* sequencer queue number */
79 int seq_mode; /* sequencer mode */
105 /* create/delete OSS sequencer client */
|
| H A D | seq_oss_init.c | 3 * OSS compatible sequencer driver
30 static int system_client = -1; /* ALSA sequencer client number */
60 * create sequencer client for OSS sequencer
77 "OSS sequencer"); in snd_seq_oss_create_client()
152 * delete OSS sequencer client
168 * open sequencer device
296 * create sequencer port
307 sprintf(port.name, "Sequencer-%d", dp->index); in create_port()
355 strcpy(qinfo.name, "OSS Sequencer Emulation"); in alloc_seq_queue()
402 * close sequencer device
[all …]
|
| /openbmc/linux/sound/core/ |
| H A D | seq_device.c | 3 * ALSA sequencer device management
8 * This device handler separates the card driver module from sequencer
9 * stuff (sequencer core, synth drivers, etc), so that user can avoid
13 * The card (or lowlevel) driver creates a sequencer device entry
15 * with the sequencer device "driver", which is involved with the
16 * actual part to communicate with the sequencer core.
17 * Each sequencer device entry has an id string and the corresponding
37 MODULE_DESCRIPTION("ALSA sequencer device management");
192 * register a sequencer device
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/config_file/ |
| H A D | README.md | 1 # phosphor-power-sequencer Configuration File
13 The `phosphor-power-sequencer` configuration file (config file) contains
14 information about the power sequencer device within a system. This device is
50 The `phosphor-power-sequencer` application searches for a config file name that
72 The config file is installed in the `/usr/share/phosphor-power-sequencer`
|
| /openbmc/witherspoon-pfault-analysis/power-sequencer/ |
| H A D | pgood_monitor.hpp | 18 * Monitors PGOOD and checks for errors on the power sequencer
22 * power sequencer device is told to kick off a power on.
24 * Future commits will analyze the power sequencer chip for errors
52 * Analyzes the power sequencer for fails and then
62 * it will analyze the power sequencer for faults.
|
| /openbmc/phosphor-power/power-sequencer/ |
| H A D | pgood_monitor.hpp | 18 * Monitors PGOOD and checks for errors on the power sequencer
22 * power sequencer device is told to kick off a power on.
24 * Future commits will analyze the power sequencer chip for errors
52 * Analyzes the power sequencer for fails and then
62 * it will analyze the power sequencer for faults.
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/ |
| H A D | frontend.json | 132 …uops are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
136 …"PublicDescription": "This event counts cycles during which the microcode sequencer assisted the F…
141 …SB) are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy.",
149 …ecode Queue (IDQ) initiated by Decode Stream Buffer (DSB) while Microcode Sequencer (MS) is busy.",
158 …that are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
166 …ed by MITE and delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
174 …ches from DSB (Decode Stream Buffer) or MITE (legacy decode pipeline) to the Microcode Sequencer.",
183 …iption": "Uops delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
186 …ts uops delivered by the Front-end with the assistance of the microcode sequencer. Microcode assi…
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/haswell/ |
| H A D | frontend.json | 132 …uops are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
136 …"PublicDescription": "This event counts cycles during which the microcode sequencer assisted the F…
141 …SB) are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy.",
149 …ecode Queue (IDQ) initiated by Decode Stream Buffer (DSB) while Microcode Sequencer (MS) is busy.",
158 …that are being delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
166 …ed by MITE and delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
174 …ches from DSB (Decode Stream Buffer) or MITE (legacy decode pipeline) to the Microcode Sequencer.",
183 …iption": "Uops delivered to Instruction Decode Queue (IDQ) while Microcode Sequencer (MS) is busy",
186 …ts uops delivered by the Front-end with the assistance of the microcode sequencer. Microcode assi…
|