Controlling method for sound receiving unit and electronic device using the same

Abstract

A controlling method for a sound receiving unit and an electronic device using the same are provided. The controlling method for the sound receiving unit includes the following steps. If an embedded controller (EC) receives a shortcut key pressing signal, a human interface device (HID) input report is sent to a software unit. The software unit sends a notification signal to an operating system unit. After receiving the notification signal, the operating system unit sends a call signal to an audio driver unit. After the audio driving unit receives the calling signal, the audio driving unit controls an audio codec to turn off or turn on the sound receiving unit.

Description

[Technical Field]

[0001] This disclosure relates to a control method and an electronic device using the same, and more particularly to a control method for a radio unit and an electronic device using the same. [Previous Technology]

[0002] With the development of technology, various electronic devices are constantly being innovated. Electronic devices can realize various functions through audio recording units. For example, when electronic devices control audio recording units such as microphones, the audio driver mainly controls the audio recording unit to turn it on or off. For corresponding lighting effects, GPIO pins are also needed to notify the embedded controller (EC) to turn the lighting effects on or off.

[0003] However, the audio driver unit must be modified accordingly for different computer systems. This will seriously affect the product development flexibility of computer system vendors. [Summary of the Invention]

[0004] This disclosure relates to a control method for a radio unit and an electronic device using the same, which achieves communication with an audio driver unit through a software unit and an operating system unit. For different computer systems, communication with the audio driver unit can still be achieved through the software unit and the operating system unit without modifying the audio driver unit. This significantly improves the flexibility of product development for computer system manufacturers.

[0005] According to one aspect of this disclosure, a control method for a radio unit is provided. The control method for the radio unit includes the following steps: If an embedded controller (EC) receives a shortcut key press signal, it transmits a Human Interface Device input report (HID input report) to a software unit. The software unit sends a notification signal to an operating system unit. After receiving the notification signal, the operating system unit sends a call signal to an audio driver unit. After receiving the call signal, the audio driver unit controls an audio codec to turn the radio unit on or off.

[0006] According to another aspect of this disclosure, an electronic device is provided. The electronic device includes an embedded controller (EC), a software unit, an operating system unit, an audio driver unit, an audio decoder, and a radio unit. The software unit is connected to the embedded controller. If the embedded controller receives a shortcut key press signal, it transmits a Human Interface Device Input Report (HID Input Report) to the software unit. The operating system unit is connected to the software unit. The software unit is used to send a notification signal to the operating system unit. The audio driver unit is connected to the operating system unit. After receiving the notification signal, the operating system unit is used to send a call signal to the audio driver unit. The audio decoder is connected to the audio driver unit. The radio unit is connected to the audio decoder. After receiving the call signal, the audio driver unit is used to control the audio decoder to turn the radio unit on or off.

[0007] To provide a better understanding of the above and other aspects of this disclosure, specific embodiments are described below in conjunction with the accompanying drawings:

Implementation Method

[0008] The technical terms used in this specification are based on common terminology in the field. Where this specification provides explanations or definitions for certain terms, the interpretation of those terms shall be based on the explanations or definitions provided in this specification. Each embodiment disclosed herein has one or more technical features. Where feasible, those skilled in the art may selectively implement some or all of the technical features in any embodiment, or selectively combine some or all of the technical features in these embodiments.

[0009] Please refer to Figure 1, which illustrates an example of a control method for a microphone unit 160 according to an embodiment of this disclosure. The microphone unit 160 is, for example, a microphone built into the sidewall of the electronic device 100 (the sidewall is not visible in Figure 1 and is therefore indicated by a dashed line). Alternatively, the microphone unit 160 may be, for example, an external microphone or a microphone of a mobile device connected to the electronic device 100. In the embodiment of Figure 1, the user can turn the microphone unit 160 on or off by pressing a shortcut key.

[0010] Alternatively, please refer to Figure 2, which illustrates an example of a control method for a radio unit 160 according to another embodiment of this disclosure. In the embodiment of Figure 2, the user can turn the radio unit 160 off or on via interface settings.

[0011] Please refer to Figure 3, which illustrates a block diagram of an electronic device 100 according to an embodiment of this disclosure. The electronic device 100 includes an embedded controller (EC) 110, a software unit 120, an operating system unit 130, an audio driver 140, an audio codec 150, the aforementioned radio unit 160, and a light-emitting element 170. The software unit 120 is connected to the embedded controller 110. The software unit 120 is used to execute various program interfaces. The operating system unit 130 is connected to the software unit 120. The operating system unit 130 is used to manage computer hardware and software resources. The audio driver 140 is connected to the operating system unit 130. The audio driver 130 is used to perform audio input / output management, audio format conversion, and other programs. The audio codec 150 is connected to the audio driver unit 140. Audio decoder 150 is used to encode and decode audio signals for efficient storage, transmission, and playback across different devices and applications. Radio unit 160 is connected to audio decoder 150. Light-emitting element 170 is used to generate illumination.

[0012] The embedded controller 110, software unit 120, operating system unit 130, audio driver unit 140, and / or audio decoder 150 are, for example, a circuit, a circuit board, a storage device for stored program code, or a chip. The chip is, for example, a programmable general-purpose or special-purpose microcontroller (MCU), microprocessor, digital signal processor (DSP), programmable controller, application-specific integrated circuit (ASIC), arithmetic logic unit (ALU), complex programmable logic device (CPLD), field-programmable gate array (FPGA), or other similar components or combinations thereof. The light-emitting unit 170 is, for example, an LED or a light strip.

[0013] In this disclosure, communication with the audio driver unit 140 can be achieved through the software unit 120 and the operating system unit 130, whether via the shortcut key method shown in Figure 1 or the interface settings shown in Figure 2. For different computer systems, communication with the audio driver unit 140 can still be achieved through the software unit 120 and the operating system unit 130 without requiring modification to the audio driver unit. This significantly improves the flexibility of product development for computer system vendors.

[0014] Please refer to Figures 3 and 4. Figure 3 further illustrates a control method for a radio unit 160 according to an embodiment of the present disclosure, and Figure 4 illustrates the operation of a software unit 120 according to an embodiment of the present disclosure. As shown in Figure 3, the control method for the radio unit 160 includes, for example, steps S110 to S150.

[0015] In step S110, the embedded controller 110 receives a shortcut key press signal PS. The shortcut key is, for example, the Fn key and the F5 key, but this disclosure is not limited to this.

[0016] Next, in step S120, the embedded controller 110 transmits a Human Interface Device input report (HID input report) RPi to the software unit 120. As shown in Figure 4, the software unit 120 obtains the HID input report RPi, for example, through a registration function. The registration function is, for example, the Register Raw Input Devices API, but this disclosure is not limited thereto.

[0017] Then, in step S130, the software unit 120 sends a notification signal NS to the operating system unit 130. As shown in Figure 4, in this step, the software unit 120 sends the notification signal NS to the operating system unit 130, for example, via a volume application programming interface (Volume API). The volume application programming interface is, for example, the Microsoft Core Audio EndpointVolume API, but this disclosure is not limited thereto.

[0018] Next, in step S140, the operating system unit 130 sends a call signal CL to the audio driving unit 140.

[0019] Then, in step S150, the audio driver unit 140 controls the audio decoder 150 to turn the radio unit 160 off or on.

[0020] Through the above steps S110 to S150, the radio unit 160 can be turned on or off by pressing a shortcut key. During the operation of steps S110 to S150, communication with the audio driver unit 140 is mainly achieved through the software unit 120 and the operating system unit 130. For different computer systems, communication with the audio driver unit 140 can still be achieved through the software unit 120 and the operating system unit 130 without requiring modification to the audio driver unit. This significantly improves the flexibility of product development for computer system vendors.

[0021] Furthermore, as shown in Figure 3, the control method of the radio unit 160 disclosed herein includes, for example, steps S110 to S120 and S160 to S170.

[0022] In step S110, the embedded controller 110 receives a shortcut key press signal PS. The shortcut key is, for example, the Fn key and the F5 key, but this disclosure is not limited to these.

[0023] Next, in step S120, the embedded controller 110 transmits the human-machine interface device input report RPi to the software unit 120. As shown in Figure 4, the software unit 120 obtains the human-machine interface device input report RPi, for example, through a registration function. The registration function is, for example, the Register Raw Input Devices API, but this disclosure is not limited thereto.

[0024] Then, in step S160, software unit 120 transmits a HID output report (RPo) to embedded controller 110. Step S160 is performed, for example, after step S130 described above. As shown in Figure 4, software unit 120 transmits the HID output report RPo to embedded controller 110, for example, using a report application programming interface (API). The report application programming interface is, for example, the HidD_Set Output Report API, but this disclosure is not limited thereto.

[0025] Next, in step S170, the embedded controller 110 controls the light-emitting element 170 to light up or turn off.

[0026] Through the above steps S110-S120 and S160-S170, the lighting effect corresponding to the state of the radio unit 160 can be generated when the shortcut key is pressed. During the operation of steps S110-S120 and S160-S170, the communication with the embedded controller 110 is mainly realized through the software unit 120, without occupying a hardware GPIO pin.

[0027] As shown in Figure 3, the control method of the radio unit 160 disclosed herein includes steps S210 to S230, for example.

[0028] In step S210, the operating system unit 130 receives a setting signal SS. The user may make settings, for example, through a setting interface, to change the state of the radio unit 160.

[0029] Next, in step S220, the operating system unit 130 sends a call signal CL to the audio driving unit 140.

[0030] Then, in step S230, the audio driver unit 140 controls the audio decoder 150 to turn the radio unit 160 off or on.

[0031] Through the above steps S210 to S230, the radio unit 160 can be turned on or off via interface settings. During the operation of steps S210 to S230, communication with the audio driver unit 140 is primarily achieved through the operating system unit 130. For different computer systems, communication with the audio driver unit 140 can still be achieved through the operating system unit 130 without requiring modification to the audio driver unit. This significantly improves the flexibility of product development for computer system vendors.

[0032] As shown in Figure 3, the control method of the radio unit 160 disclosed herein includes, for example, steps S210, S240 to S260.

[0033] In step S210, the operating system unit 130 receives a setting signal SS. The user may change the state of the radio unit 160, for example, through a setting interface.

[0034] Next, in step S240, the operating system unit 130 transmits a setting event EV to the software unit 120. As shown in Figure 4, in this step, the software unit 120 receives the setting event EV, for example, through a callback interface. The callback interface is, for example, the Microsoft Core Audio IAudioEndpointVolumeCallback interface, but this disclosure is not limited thereto.

[0035] Then, in step S250, the software unit 120 transmits the HID output report RPo to the embedded controller 110. As shown in Figure 4, the software unit 120 transmits the HID output report RPo to the embedded controller 110, for example, via a report application programming interface (API). The report application programming interface is, for example, the HidD_Set Output Report API, but this disclosure is not limited thereto.

[0036] Next, in step S260, the embedded controller 110 controls the light-emitting element 170 to light up or turn off.

[0037] Through the above steps S210, S240 to S260, the lighting effect can be generated according to the state of the radio unit 160 under the interface setting method. During the operation of steps S210, S240 to S260, the communication with the embedded controller 110 is mainly realized through the software unit 120 and the operating system unit 130, without occupying a hardware GPIO pin.

[0038] According to the above embodiments, the technology disclosed herein can be continued on different platforms. For different computers, since the software specifications (HID and Windows Core Audio API) are the same, project development time can be greatly reduced. In addition, Core Audio APIs are the APIs of Windows Universal Audio Architecture (UAA). Many audio functions have been moved from kernel mode to user mode, thus improving reliability. As long as the operating system supports this API, it can operate successfully. If the operating system changes the audio API, the software unit 120 can still complete the function as long as it adopts the new API.

[0039] Furthermore, the HID input / output report of the disclosed technology adopts a custom specification. Any software can control the indicator display of the radio unit 160 as long as it follows this defined specification, thus enabling more creative ideas to be generated.

[0040] In addition, the technology disclosed herein can save hardware GPIO pins and reduce the cost of the motherboard.

[0041] The foregoing disclosure provides different features for implementing some embodiments or examples of this disclosure. Specific examples of components and configurations described above (e.g., mentioned values ​​or names) are used to simplify / illustrate some embodiments of this disclosure. Of course, these components and configurations are merely examples and are not intended to be limiting. Furthermore, reference numerals and / or letters may be repeated in various instances of some embodiments of this disclosure. This repetition is for simplicity and clarity and does not in itself indicate a relationship between the various embodiments and / or configurations discussed.

[0042] In summary, although this disclosure has been presented above with reference to embodiments, it is not intended to limit this disclosure. Those skilled in the art to which this disclosure pertains can make various modifications and refinements without departing from the spirit and scope of this disclosure. Therefore, the scope of protection of this disclosure shall be determined by the appended claims. [Simplified Explanation of the Diagram]

[0043] Figure 1 illustrates a control method for a radio unit according to an embodiment of the present disclosure. Figure 2 illustrates a control method for a radio unit according to another embodiment of the present disclosure. Figure 3 is a block diagram of an electronic device according to an embodiment of the present disclosure. Figure 4 illustrates the operation of a software unit according to an embodiment of the present disclosure.

Claims

1. A method for controlling a radio unit, comprising: If an embedded controller (EC) receives a shortcut key press signal, it sends a Human Interface Device input report (HID input report) to a software unit; the software unit sends a notification signal to an operating system unit; after receiving the notification signal, the operating system unit sends a call signal to an audio driver; and after receiving the call signal, the audio driver unit controls an audio codec to turn the radio unit on or off.

2. The control method for the radio unit as described in claim 1, wherein the software unit obtains the input report of the human-machine interface device via a registration function.

3. The control method for the radio unit as described in claim 1, wherein the software unit sends the notification signal to the operating system unit via a volume application programming interface (Volume API).

4. The control method for the radio unit as described in claim 1 further includes: After the software unit sends the notification signal to the operating system unit, the software unit transmits an HID output report to the embedded controller; and after the embedded controller receives the HID output report, it controls a light-emitting element to turn on or off.

5. The control method for the radio unit as described in claim 4, wherein the software unit transmits the HID output report to the embedded controller via a Report Application Programming Interface (Repot API).

6. The control method for the radio unit as described in claim 1 further includes: If the operating system unit receives a setting signal, the operating system unit sends the call signal to the audio driver unit; And after the audio driver unit receives the call signal, the audio driver unit controls the audio decoder to turn the radio unit off or on.

7. The control method for the radio unit as described in claim 6 further includes: After receiving the setting signal, the operating system unit transmits a setting event to the software unit; After receiving the setting event, the software unit sends an HID output report to the embedded controller; and after the embedded controller receives the HID output report, it controls a light-emitting element to turn on or off.

8. The control method for the radio unit as described in claim 7, wherein the software unit receives the setting event via a callback interface.

9. The control method for the radio unit as described in claim 7, wherein the software unit transmits the HID output report to the embedded controller via a reporting application interface.

10. An electronic device comprising: An embedded controller (EC); a software unit connected to the embedded controller, which, upon receiving a shortcut key press signal, transmits a Human Interface Device input report (HID input report) to the software unit; an operating system unit connected to the software unit, which sends a notification signal to the operating system unit; an audio driver unit connected to the operating system unit, which, upon receiving the notification signal, sends a call signal to the audio driver unit; an audio codec connected to the audio driver unit; and a radio unit connected to the audio codec, which, upon receiving the call signal, controls the audio codec to turn the radio unit on or off.

11. The electronic device as described in claim 10, further comprising: After the software unit sends the notification signal to the operating system unit, the software unit transmits an HID output report to the embedded controller. After the embedded controller receives the HID output report, the embedded controller controls the light-emitting element to turn on or off.

12. The electronic device as claimed in claim 10, wherein if the operating system unit receives a setting signal, the operating system unit sends the call signal to the audio driver unit; and after the audio driver unit receives the call signal, the audio driver unit controls the audio decoder to turn the radio unit off or on.

13. The electronic device as claimed in claim 12, wherein after the operating system unit receives the setting signal, the operating system unit transmits a setting event to the software unit; after the software unit receives the setting event, the software unit transmits a HID output report to the embedded controller; and after the embedded controller receives the HID output report, the embedded controller controls a light-emitting element to light up or turn off.

Images