On 4 October 2017 at 06:52, Robert Nelson <[email protected]> wrote: > On Wed, Oct 4, 2017 at 1:28 AM, Henner Zeller <[email protected]> wrote: >> Hi, >> Little heads-up: I just spent an hour or so to realize that the simple 'CS' >> (ChipSelect) printed on the silkscreen for SPI1 bus on the PocketBeagle is >> not CS0 as I expected, but CS1. So this is actually bus /dev/spidev2.1 >> >> Not sure if this was intended, but if it is, it should probably be marked on >> the silk-screen as CS1 to avoid future confusion; I can send a pull request >> for the board (in general, even CS0 should be marked as such) >> >> If it is _not_ intended, the am335x-pocketbeagle.dts would need to be >> changed before capes start assuming this is CS1 (around line 389 Jason). > > HI Henner, > > I've noticed this to while doing the overlays: > > SPI1 CS1 is used as CS > > https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/PB-SPI1-ETH-CLICK.dts#L83 > > SPI0 CS0 is used as CS > > https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/PB-SPI0-ETH-CLICK.dts#L83 > > I haven't looked to closely, (just let my automated script setup the > pinmux's).. But if SPI1 (CS0) and SPI0 (CS1) is not on the header, we > should remove them from the base tree
Yes, this would certainly less confusing to leave out the non-available chip-selects in the /dev/spidev* devices. Is there a reason why SPI0 shows up as /dev/spidev1.* and SPI1 as /dev/spidev2.* ? This does look like an off-by-one. Is this intentional ? Thanks, Henner. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAEQqtJzA_JPqBjzat6f_gRKm0xaNRcZ2MBoNBYS%2BUuKrjE_LMA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
