From: Lei Li <lilei@linux.vnet.ibm.com>
To: Amos Kong <akong@redhat.com>
Cc: aliguori@us.ibm.com, lcapitulino@redhat.com, lersek@redhat.com,
qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH] ps2: add support of auto-repeat
Date: Thu, 16 May 2013 15:23:21 +0800 [thread overview]
Message-ID: <51948969.5050604@linux.vnet.ibm.com> (raw)
In-Reply-To: <1368678651-3561-1-git-send-email-akong@redhat.com>
On 05/16/2013 12:30 PM, Amos Kong wrote:
> Guest driver sets repeat rate and delay time by KBD_CMD_SET_RATE,
> but ps2 backend doesn't process it and no auto-repeat implementation.
> This patch adds support of auto-repeat feature.
>
> Guest ps2 driver sets autorepeat to fastest possible in reset,
> period: 250ms, delay: 33ms
>
> Tested by 'sendkey' monitor command.
>
> referenced: http://www.computer-engineering.org/ps2keyboard/
>
> Signed-off-by: Amos Kong <akong@redhat.com>
> ---
> hw/input/ps2.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/hw/input/ps2.c b/hw/input/ps2.c
> index 3412079..1cfe055 100644
> --- a/hw/input/ps2.c
> +++ b/hw/input/ps2.c
> @@ -94,6 +94,9 @@ typedef struct {
> int translate;
> int scancode_set; /* 1=XT, 2=AT, 3=PS/2 */
> int ledstate;
> + int repeat_period; /* typematic period, ms */
> + int repeat_delay; /* typematic delay, ms */
> + int repeat_key; /* keycode to repeat */
> } PS2KbdState;
>
> typedef struct {
> @@ -146,6 +149,22 @@ void ps2_queue(void *opaque, int b)
> s->update_irq(s->update_arg, 1);
> }
>
> +static QEMUTimer *repeat_timer;
> +static bool auto_repeat;
> +
> +static void repeat_ps2_queue(void *opaque)
> +{
> + PS2KbdState *s = opaque;
> +
> + if (auto_repeat) {
> + qemu_mod_timer(repeat_timer, qemu_get_clock_ns(vm_clock) +
> + muldiv64(get_ticks_per_sec(), s->repeat_period,
> + 1000));
> + ps2_queue(&s->common, s->repeat_key);
> + }
> +}
> +
> +
> /*
> keycode is expressed as follow:
> bit 7 - 0 key pressed, 1 = key released
> @@ -167,7 +186,17 @@ static void ps2_put_keycode(void *opaque, int keycode)
> keycode = ps2_raw_keycode_set3[keycode & 0x7f];
> }
> }
> +
> + /* only auto-repeat press event */
> + auto_repeat = ~keycode & 0x80;
Does this check allow to distinguish the difference between auto-repeat and
actual repeated entry by the user?
> ps2_queue(&s->common, keycode);
> +
> + if (auto_repeat) {
> + s->repeat_key = keycode;
> + /* delay a while before first repeat */
> + qemu_mod_timer(repeat_timer, qemu_get_clock_ns(vm_clock) +
> + muldiv64(get_ticks_per_sec(), s->repeat_delay, 1000));
> + }
> }
>
> uint32_t ps2_read_data(void *opaque)
> @@ -213,6 +242,11 @@ static void ps2_reset_keyboard(PS2KbdState *s)
>
> void ps2_write_keyboard(void *opaque, int val)
> {
> + /* repeat period/delay table from kernel (drivers/input/keyboard/atkbd.c) */
> + const short period[32] = { 33, 37, 42, 46, 50, 54, 58, 63, 67, 75,
> + 83, 92, 100, 109, 116, 125, 133, 149, 167, 182, 200, 217, 232,
> + 250, 270, 303, 333, 370, 400, 435, 470, 500 };
> + const short delay[4] = { 250, 500, 750, 1000 };
> PS2KbdState *s = (PS2KbdState *)opaque;
>
> switch(s->common.write_cmd) {
> @@ -288,6 +322,11 @@ void ps2_write_keyboard(void *opaque, int val)
> s->common.write_cmd = -1;
> break;
> case KBD_CMD_SET_RATE:
> + /* Bit0-4 specifies the repeat rate */
> + s->repeat_period = period[val & 0x1f];
> + /* Bit5-6 bit specifies the delay time */
> + s->repeat_delay = delay[(val & 0x60) >> 5];
> +
> ps2_queue(&s->common, KBD_REPLY_ACK);
> s->common.write_cmd = -1;
> break;
> @@ -536,6 +575,8 @@ static void ps2_kbd_reset(void *opaque)
> s->scan_enabled = 0;
> s->translate = 0;
> s->scancode_set = 0;
> + s->repeat_period = 92;
> + s->repeat_delay = 500;
> }
>
> static void ps2_mouse_reset(void *opaque)
> @@ -660,6 +701,7 @@ void *ps2_kbd_init(void (*update_irq)(void *, int), void *update_arg)
> vmstate_register(NULL, 0, &vmstate_ps2_keyboard, s);
> qemu_add_kbd_event_handler(ps2_put_keycode, s);
> qemu_register_reset(ps2_kbd_reset, s);
> + repeat_timer = qemu_new_timer_ns(vm_clock, repeat_ps2_queue, s);
> return s;
> }
>
--
Lei
next prev parent reply other threads:[~2013-05-16 7:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 4:30 [Qemu-devel] [PATCH] ps2: add support of auto-repeat Amos Kong
2013-05-16 5:30 ` li guang
2013-05-16 6:58 ` Amos Kong
2013-05-16 7:13 ` li guang
2013-05-16 7:28 ` Amos Kong
2013-05-16 15:04 ` Paolo Bonzini
2013-05-16 6:40 ` Jason Wang
2013-05-16 6:50 ` Peter Maydell
2013-05-16 7:17 ` Amos Kong
2013-05-16 7:23 ` Lei Li [this message]
2013-05-16 7:35 ` Amos Kong
2013-05-16 9:11 ` Lei Li
2013-05-16 20:37 ` Amos Kong
2013-05-16 15:09 ` Paolo Bonzini
2013-05-16 15:17 ` Peter Maydell
2013-05-16 15:20 ` Paolo Bonzini
2013-05-21 8:33 ` Amos Kong
2013-05-21 8:38 ` Paolo Bonzini
2013-05-21 9:04 ` Amos Kong
2013-05-21 9:51 ` Amos Kong
2013-05-21 9:54 ` Paolo Bonzini
2013-05-16 15:03 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51948969.5050604@linux.vnet.ibm.com \
--to=lilei@linux.vnet.ibm.com \
--cc=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kraxel@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).