Utilizing spider, is there a simple way to control SPI timing parameters to match specifications of slave devices?
I'm interested in controlling various parameters such as setup/hold times, data valid times, etc. Thanks, David On Wednesday, May 22, 2013 6:21:54 PM UTC-4, Azure Wang wrote: > > After reading a lot of threads, I am still a little confused about device > tree mechanism. Could anyone give me a overview of how it works? > > - Update device tree on run time is called overlay. It need to create > a .dst file and compile it. then put it into a directory. > > > 1. it will tell kernel turn on the SPI hardware > 2. Set the pin to correct model, so that the signal is available at > headers > > > - Then I need to install spidev, which is the driver of SPI in linux > > This is my understanding, I would be surprised if it is correct, So please > point out where ever I am wrong. > > BTW, I have some silly question again: > > 1. Some guy mentioned SPI1 is used by HDMI, however, after I > went through the BBB_SRM. I merely found *Table13. P8 LCD conflict Pin* on > *Pg.87* shows the pin that hdmi uses. SPI1 is on *P9*, so where do you > guys finger out that SPI1 is used by hdmi. > 2. where can I find source of BONESCRIPT, or how do you find where is > the source of bonescript. > 3. On BBB_SRM.pdf *page 96*, the table shows AIN0-AIN3 is on P8, it is > different from Table 11 on *page 77. *is it typo? > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
