mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Zdenek Svachula <zdenek.svachula@medictech.com>
Cc: barebox@lists.infradead.org
Subject: Re: gpio-keys on barebox 2015.11
Date: Wed, 19 Apr 2017 08:42:24 +0200	[thread overview]
Message-ID: <20170419064224.rbteqga5qnxl6vab@pengutronix.de> (raw)
In-Reply-To: <CAARUG94vbynM7MJu=kfPynABwf5rhDDd3OBM-2SyRy0PFO_8kQ@mail.gmail.com>

On Wed, Apr 12, 2017 at 05:35:46PM +0200, Zdenek Svachula wrote:
> Hi all,
> 
> I'm working with barebox 2015.11 phy4 (from phytex.de) I try add to dts
>         gpio_keys {
>                 compatible = "gpio-keys";
>                 #address-cells = <1>;
>                 #size-cells = <0>;
>                 autorepeat;
>                 up {
>                                 label = "GPIO Key up";
>                                 linux,code = <103>;
>                                 gpios = <&gpio2 24 1>;
>                 };
>                 enter {
>                                 label = "GPIO Key ENTER";
>                                 linux,code = <28>;
>                                 gpios = <&gpio5 8 1>;
>                 };
> 
> 
>         };
> 
> to allow boot selection boot menu via 2 gpio button  I also enable
> GPIO-buttons in menuconfig but it seem not workin.
> 
> Can you please me point to some method how to debug if gpio polling
> works or if dts is for barebox wrong.

Generally the above looks ok and should work like this. Try 'devinfo'
command and identify the gpio-keys device (usually named gpio-keys.<x>).
Use 'devinfo gpio-keys.<x>' to find out if there is a driver attached to
this device. If there isn't, do you find something about gpio-keys in
the boot log?

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

  reply	other threads:[~2017-04-19  6:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAARUG94j21s-AC0-gXYG81SjnCa1ahPfH1oaq=fb+rFgEpSE8A@mail.gmail.com>
2017-04-12 15:35 ` Zdenek Svachula
2017-04-19  6:42   ` Sascha Hauer [this message]
2017-04-19  8:49     ` Zdenek Svachula
2017-04-19  9:50       ` Sascha Hauer
     [not found]         ` <CAARUG96Bij4emjci_EO=yzeus22omFK_ajBH4d0muc=ViEMrAA@mail.gmail.com>
2017-04-19 10:56           ` Fwd: " Zdenek Svachula
2017-04-19 10:56           ` Sascha Hauer

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=20170419064224.rbteqga5qnxl6vab@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=zdenek.svachula@medictech.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