From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/4] add gpio keyboard support
Date: Thu, 16 Feb 2012 08:51:03 +0100 [thread overview]
Message-ID: <20120216075103.GJ3852@pengutronix.de> (raw)
In-Reply-To: <20120215161426.GJ1214@game.jcrosoft.org>
On Wed, Feb 15, 2012 at 05:14:26PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >
> > This information would be far more informative if you printed the
> > button that is pressed/released here.
> ok
> >
> > > + }
> > > + gb->previous_state = val;
> > > + }
> >
> > You do nothing for debouncing the keys.
> yes my hardware manage directly (gpio IP)
>
> we can add it later
> > > + return ret;
> > > + }
> > > + gpio_direction_input(gpio);
> > > + }
> > > +
> > > + pdata->poller.func = gpio_key_poller;
> > > +
> > > + cdev = &pdata->cdev;
> > > + dev->type_data = cdev;
> > > + cdev->dev = dev;
> > > + cdev->f_caps = CONSOLE_STDIN;
> > > + cdev->tstc = gpio_keys_tstc;
> > > + cdev->getc = gpio_keys_getc;
> > > +
> > > + console_register(&pdata->cdev);
> >
> > As I tried to explain yesterday I'm not sure that directly registering
> > the gpio keys as a console is the right thing to do. A keyboard has
> > more attributes than what we have in the console. For example a keyboard
> > has a button press / button release event which we don't have on the
> > console.
> agreed but today we do not have a input framework yet
>
> I'm planning to add such framework but as a second step
> I'll add the usb keyboard too
Ok, we can to it like this.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-02-16 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 14:31 Jean-Christophe PLAGNIOL-VILLARD
2012-02-14 14:31 ` [PATCH 2/4] readkey: add define for Ascii keys Jean-Christophe PLAGNIOL-VILLARD
2012-02-14 14:31 ` [PATCH 3/4] at91: at91_register_uart return device Jean-Christophe PLAGNIOL-VILLARD
2012-02-14 14:31 ` [PATCH 4/4] usb-a926x: add DAB MMX Daughter board support Jean-Christophe PLAGNIOL-VILLARD
2012-02-15 9:31 ` [PATCH 1/4] add gpio keyboard support Sascha Hauer
2012-02-15 16:14 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-16 7:51 ` Sascha Hauer [this message]
2012-02-16 10:20 ` [PATCH 1/4 v2] " Jean-Christophe PLAGNIOL-VILLARD
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=20120216075103.GJ3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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