Scheduler for amp architecture using a closed loop performance and thermal controller
US-2018349175-A1 · Dec 6, 2018 · US
US11032342B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11032342-B2 |
| Application number | US-201916503230-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 3, 2019 |
| Priority date | Jul 5, 2018 |
| Publication date | Jun 8, 2021 |
| Grant date | Jun 8, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
This disclosure relates to an electronic device including a memory and at least one processor coupled to the memory. The at least one processor is configured to execute a daemon process in one of a container or a host operating system, wherein the daemon process is configured to manage data transfer between the container and the host operating system, create, via the daemon process, an inter-process communication (IPC) channel between the container and the host operating system, receive incoming audio data, and buffer the incoming audio data to the IPC channel.
Opening claim text (preview).
What is claimed is: 1. An electronic device, comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: execute a daemon process in one of a host operating system or a container executing a guest operating system, wherein the daemon process is configured to manage data transfer between the container and the host operating system; create, via the daemon process, an inter-process communication (IPC) channel between the container and the host operating system; receive incoming audio data; and buffer the incoming audio data to the IPC channel. 2. The electronic device of claim 1 , wherein the incoming audio data includes audio output data from one or more container applications executed in the container. 3. The electronic device of claim 2 , further comprising an audio output device, and wherein the at least one processor is further configured to: buffer, in the host operating system, the audio output data from the IPC channel; and playback the audio output data through the audio output device. 4. The electronic device of claim 1 , further comprising an audio input device, wherein the incoming audio data includes audio input data from the audio input device. 5. The electronic device of claim 4 , wherein the at least one processor is further configured to: receive, in the container, the audio input data from the IPC channel; and transfer the audio input data to one or more container applications executed in the container. 6. The electronic device of claim 1 , wherein the IPC channel includes at least one of a shared memory and a socket. 7. The electronic device of claim 1 , wherein the at least one processor is further configured to: determine that no audio data is available; and terminate, via the daemon process, the IPC channel based on the determination that no audio data is available. 8. The electronic device of claim 1 , wherein the at least one processor is further configured to: execute an application in one of the container or the host operating system, wherein the application is configured to communicate with the daemon process, and wherein the IPC channel is configured to transfer data between the container and the host operating system. 9. A method for device audio, comprising: executing a daemon process in one of a host operating system or a container executing a guest operating system wherein the daemon process manages data transfer between the container and the host operating system; creating, via the daemon process, an inter-process communication (IPC) channel between the container and the host operating system; receiving incoming audio data; and buffering the incoming audio data to the IPC channel. 10. The method of claim 9 , wherein the incoming audio data includes audio output data from one or more container applications executed in the container. 11. The method of claim 10 , further comprising: buffering, in the host operating system, the audio output data from the IPC channel; and performing playback of the audio output data through an audio output device. 12. The method of claim 9 , wherein the incoming audio data includes audio input data from an audio input device. 13. The method of claim 12 , further comprising: receiving, in the container, the audio input data from the IPC channel; and transferring the audio input data to one or more container applications executed in the container. 14. The method of claim 9 , wherein the IPC channel includes at least one of a shared memory and a socket. 15. The method of claim 9 , further comprising: determining that no audio data is available; and terminating, via the daemon process, the IPC channel based on the determination that no audio data is available. 16. The method of claim 9 , further comprising: executing an application in one of the container or the host operating system, wherein the application communicates with the daemon process, and wherein the IPC channel transfers data between the container and the host operating system. 17. A non-transitory computer readable medium embodying a computer program for operating an electronic device including a memory and at least one processor, the computer program comprising computer readable instructions that, when executed by the at least one processor, cause the electronic device to: execute a daemon process in one of a host operating system or a container executing a guest operating system wherein the daemon process manages data transfer between the container and the host operating system; create, via the daemon process, an inter-process communication (IPC) channel between the container and the host operating system; receive incoming audio data; and buffer the incoming audio data to the IPC channel. 18. The non-transitory computer readable medium of claim 17 , wherein the incoming audio data includes audio output data from one or more container applications executed in the container, and wherein the computer program further comprises computer readable instructions that, when executed by the at least one processor, cause the electronic device to provide information to: buffer, in the host operating system, the audio output data from the IPC channel; and playback the audio output data through an audio output device. 19. The non-transitory computer readable medium of claim 17 , wherein the incoming audio data includes audio input data from an audio input device, and wherein the computer program further comprises computer readable instructions that, when executed by the at least one processor, cause the electronic device to provide information to: receive, in the container, the audio input data from the IPC channel; and transfer the audio input data to one or more container applications executed in the container. 20. The non-transitory computer readable medium of claim 17 , wherein the IPC channel includes at least one of a shared memory and a socket.
Media network packet handling · CPC title
Management of the audio stream, e.g. setting of volume, audio stream path · CPC title
Instruction completion, e.g. retiring, committing or graduating · CPC title
Concurrent instruction execution, e.g. pipeline or look ahead · CPC title
Buffers; Shared memory; Pipes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.