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 12:56:26 +0200	[thread overview]
Message-ID: <20170419105626.gioset6qhr4ykyde@pengutronix.de> (raw)
In-Reply-To: <CAARUG96Bij4emjci_EO=yzeus22omFK_ajBH4d0muc=ViEMrAA@mail.gmail.com>

Hi Zdenek,

On Wed, Apr 19, 2017 at 12:39:14PM +0200, Zdenek Svachula wrote:
>    Hi Sascha
> 
>    yes. I look in these
>    I also  enable initcall debug output and see
>    initcall-> at25_driver_register+0x1/0x14
>    initcall-> at24_init+0x1/0x18
>    initcall-> gpio_keys_driver_register+0x1/0xc
>    initcall-> imx_keypad_driver_register+0x1/0xc
>    initcall-> imx_wd_driver_register+0x1/0xc
>    initcall-> null_init+0x1/0x24
> 
>    in of_dump is nothing about gpio_keys
>    drvinfo:
>    at24
>            24c320
>    gpio_keys
>    imx-kpp
>    imx-watchdog
>            20bc000.wdog
>    mem
> 
>    barebox@Phytec phyFLEX-i.MX6 Quad Carrier-Board:/ devinfo gpio_keys
>    devinfo: No such device

Maybe you have modified the wrong dts file. Which one have you modified?
Just to be sure: You modified some dts file in the barebox source tree,
compiled barebox and started the resulting binary, right?

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

      parent reply	other threads:[~2017-04-19 10:56 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
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 [this message]

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=20170419105626.gioset6qhr4ykyde@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