IRC #olimex 2017-12-14

[09:26:57] <leon-anavi> hi
[12:01:41] <kr_eten> hello people, does anyone have experience with device tree overlays with mainline kernel?
[12:02:11] <kr_eten> specifically for olinuxino micro - still failing to get both spidev properly enabled
[12:05:54] <kr_eten> i'd like to enable overlays so I can change DT without restarting
[12:55:14] <keesj> Well if you problem is that you can not get both spidev to work properly first try without adding the additional overlay problems
[12:55:55] <keesj> Normal device tree (with build time overlays) are still very nice and easy to maintain and updating is really easy as "cp mydeb to my boot"
[12:58:00] <keesj> I still have some documentation laying around on spidev http://keesj.github.io/A10-OLinuXino-LIME-5510-Shield/sw_install.html but this on the A10
[13:14:25] <kr_eten> hi keesj, I did some changes to that trees, but sometimes I get myself not booting, which requires removal of sdcard and replacing from backup by another PC
[13:14:33] <kr_eten> which is annoying if I need to change often :)
[13:14:36] <kr_eten> let me check your link
[13:23:53] <kr_eten> mine is A20 and I actually managed to get one of the two SPIs working, the other one is created, but evidently does not communicate with the SPI slave device
[13:24:04] <kr_eten> from your changes I don't understand:
[13:24:07] <kr_eten> +&codec {
[13:24:07] <kr_eten> + status = "okay";
[13:24:07] <kr_eten> +};
[13:24:52] <kr_eten> also in the other file: + compatible = "spidev";
[14:43:44] <keesj> yea.. it is kinda a while ago: to prevent from having to remove the sd-card you can try adding a u-boot script to offer alternative boot
[14:44:23] <kr_eten> this might be worth trying
[14:44:49] <kr_eten> but will require serial connection to decide what to boot I guess
[14:44:57] <kr_eten> I will check what the options are
[15:08:20] <keesj> the +&codec statuc ="okay" is using overlays , so somewhere else the codec is defined and this one just adds the status = okay (I also used dtb to convert the dtb back to dts to "see" what I was doing
[15:09:46] <keesj> IMHO the device tree makes it very hard to understand stuff and to really know what you need to do (besides reading the kernel docs devicetree documentation) is going quite deep into the kernel code and the datasheets of the vendor
[15:10:21] <keesj> Having the serial is always nice/needed
[15:14:41] <keesj> kr_eten: so it can also be a pin muxing problem
[15:43:23] <kr_eten> to be honest I also thought it might be mux problem
[15:43:49] <kr_eten> that is why I updated some gpio library to mi liking and made a tool to delve into gpio memory registers
[15:44:20] <kr_eten> the only thing that I identified is that with that tool I made it is not possible to change the configuration of many of the GPIO
[15:45:18] <kr_eten> also I am not very sure that the code is working correctly :)
[15:45:43] <kr_eten> my liking*
[17:52:02] <keesj> http://keesj.github.io/A10-OLinuXino-LIME-5510-Shield/hw_proto_and_debug.html?highlight=gpio
[17:52:23] <keesj> omimex has some libraries for messing around with the GPIO (and there is also a gpio kernel driver)
[17:53:02] <keesj> olimex
[19:01:20] <kr_eten> I have read trough your site for that project, I also have some starting point for that gpio library - too many macros and not very clear math (for me) so I rewrote most of it
[19:01:35] <kr_eten> I might check olimex examples again as I have not for long time