Re: gpio-keys on barebox 2015.11

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox




[Index of Archives]     [Linux Embedded]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux