martinayotte Posted July 16, 2016 Posted July 16, 2016 I've been studying and working on Dynamic Device-Tree Overlays since awhile, but after hard work, I've finally got a working prototype using the work from Pantelis Antoniou. During last few days, I was doing debugging to find out why it wasn't working, even if I got the ConfigFS working, it was refusing to grab my simple overlay test. I've finally figured out this afternoon : the Root/Base DTB need also to be compiled with the "symbols" list generated with the Antoniou's version of "dtc". So, I will probably prepare a patch soon and submit it thru a PR. 4
Kamil Židek Posted July 19, 2016 Posted July 19, 2016 it is possible to add spi-gpios: for cs1 on spidev0.1 i need working touchscreen which need second cs1
martinayotte Posted July 19, 2016 Author Posted July 19, 2016 Unfortunately, I don't know how, it should be doable since the schematic mentioned that SPI1_CS1 is the PH7 pin, but it is already used in DTS for UART3 as well as for Codec (which lead me to some confusion). Also, I don't know how the kernel drivers will handle it ...
martinayotte Posted July 26, 2016 Author Posted July 26, 2016 Unfortunately, I don't see much comments about my recent works ... http://forum.armbian.com/index.php/topic/1537-397-maintainfix-dts-entries-for-some-devices-such-i2cspiw1/#entry13032
Kamil Židek Posted August 14, 2016 Posted August 14, 2016 spi1 cs0 works but not in connector i must use mute testpoint and led pin (mosi miso), i need two spi0 cs0 (is in hardware) spi lcd, and second spi0 cs1 for touch only way is dts overlay thru software cs-gpios function in dts but i found nothing for orange pi...
tkaiser Posted August 23, 2016 Posted August 23, 2016 Martin, when building mainline kernel images for the NEO using 4.7.2 I noticed your DT overlay patches break. In case you work already on 4.7 could you please switch to megi's orange-pi-4.7 branch and enable there the new schedutil governor (default should still be ondemand)?
martinayotte Posted August 23, 2016 Author Posted August 23, 2016 HI TKaiser, Ok, until recently (my last build on Aug 20th), we were still using the orange-pi-4.6, so I will take a look. In fact, for the sunxi-dev, I've already done the change by simply using the same patch done for 4.8 into 4.7. So, I'm currently doing a new build, if it is the same case, I will commit the things needed : delete or disabling the old 4.6.x and copy the 4.8 into a 4.7.x. EDIT : We are still using orange-pi-4.6 in the sun8i-dev config, but I gave a try switching it to orange-pi-4.7. I will commit those changes soon. I hope the switch from 4.6.x to 4.7.x won't cause any other patch issues. (For the schedutil governor, I'm not fluent with those pieces ... What we have to do exactly ?) 1
Recommended Posts