From: <nathan.taylor.sm...@gmail.com>
Reply-To: <beagleboard@googlegroups.com>
Date: Thursday, March 13, 2014 at 9:11 AM
To: <beagleboard@googlegroups.com>
Cc: Jacob Stockton <jacob.d.stock...@gmail.com>, <m...@grosen.org>
Subject: Re: [beagleboard] Device Tree Compiler
> Im looking through David Ander's article and I just dont understand whats
> going on when "applying diff to kernel"
>
> could you offer any assistance
Open the file drivers/spi/spidev.c and add the line:
{ .compatible = "linux,spidev" },
This line should be placed after the line:
{ .compatible = "rohm,dh2228fv" },
Regards,
John
>
>
> On Wednesday, August 7, 2013 12:58:42 PM UTC-5, Mark Grosen wrote:
>> If you want SPI in user-space, you need to mark the SPI device as "spidev"
>> compatible in the the dts file. See this recent article from David Anders:
>> http://elinux.org/BeagleBone_Black_Enable_SPIDEV
>>
>> Mark
>>
>>
>> Mark
>>
>>
>> On Wed, Aug 7, 2013 at 10:51 AM, Jacob Stockton <jacob.d....@gmail.com
>> <javascript:> > wrote:
>>> Thanks Charles. Ok, we are almost where I need to be. I got all of the UARTs
>>> working (1,2,4,5) that I need and I have i2c-port enabled, but I don't see
>>> the SPI in /dev. The literature I have found says it will be named spi1 or
>>> spidev, but I don't see it in /dev.
>>>
>>>
>>> ./pingroups
>>> [sudo] password for ubuntu:
>>> registered pin groups:
>>> group: pinmux_userled_pins
>>> pin 21 (44e10854)
>>> pin 22 (44e10858)
>>> pin 23 (44e1085c)
>>> pin 24 (44e10860)
>>>
>>> group: pinmux_rstctl_pins
>>> pin 20 (44e10850)
>>>
>>> group: pinmux_i2c0_pins
>>> pin 98 (44e10988)
>>> pin 99 (44e1098c)
>>>
>>> group: pinmux_i2c2_pins
>>> pin 94 (44e10978)
>>> pin 95 (44e1097c)
>>>
>>> group: pinmux_bb_i2c1_pins
>>> pin 86 (44e10958)
>>> pin 87 (44e1095c)
>>>
>>> group: pinmux_bb_uart1_pins
>>> pin 97 (44e10984)
>>> pin 96 (44e10980)
>>>
>>> group: pinmux_bb_uart2_pins
>>> pin 84 (44e10950)
>>> pin 85 (44e10954)
>>>
>>> group: pinmux_bb_uart4_pins
>>> pin 28 (44e10870)
>>> pin 29 (44e10874)
>>>
>>> group: pinmux_bb_uart5_pins
>>> pin 49 (44e108c4)
>>> pin 48 (44e108c0)
>>>
>>> group: pinmux_bb_spi1_pins
>>> pin 100 (44e10990)
>>> pin 101 (44e10994)
>>> pin 102 (44e10998)
>>> pin 103 (44e1099c)
>>>
>>> group: pinmux_emmc2_pins
>>> pin 32 (44e10880)
>>> pin 33 (44e10884)
>>> pin 0 (44e10800)
>>> pin 1 (44e10804)
>>> pin 2 (44e10808)
>>> pin 3 (44e1080c)
>>> pin 4 (44e10810)
>>> pin 5 (44e10814)
>>> pin 6 (44e10818)
>>> pin 7 (44e1081c)
>>>
>>> group: pinmux_userled_pins
>>> pin 21 (44e10854)
>>> pin 22 (44e10858)
>>> pin 23 (44e1085c)
>>> pin 24 (44e10860)
>>>
>>>
>>> And...
>>>
>>> ls /dev/
>>> alarm loop3 ram3 tty21 tty48 ttyS2
>>> ashmem loop4 ram4 tty22 tty49 ttyS3
>>> autofs loop5 ram5 tty23 tty5 ubi_ctrl
>>> binder loop6 ram6 tty24 tty50 uinput
>>> block loop7 ram7 tty25 tty51 urandom
>>> btrfs-control mapper ram8 tty26 tty52 usbmon0
>>> bus mem ram9 tty27 tty53 usbmon1
>>> char mmcblk0 random tty28 tty54 usbmon2
>>> console mmcblk0boot0 rtc0 tty29 tty55 vcs
>>> cpu_dma_latency mmcblk0boot1 shm tty3 tty56 vcs1
>>> disk mmcblk0p1 snd tty30 tty57 vcs2
>>> fd mmcblk0p2 stderr tty31 tty58 vcs3
>>> full net stdin tty32 tty59 vcs4
>>> fuse network_latency stdout tty33 tty6 vcs5
>>> i2c-0 network_throughput tty tty34 tty60 vcs6
>>> i2c-1 null tty0 tty35 tty61 vcs7
>>> i2c-2 ppp tty1 tty36 tty62 vcsa
>>> input psaux tty10 tty37 tty63 vcsa1
>>> kmem ptmx tty11 tty38 tty7 vcsa2
>>> kmsg pts tty12 tty39 tty8 vcsa3
>>> log ram0 tty13 tty4 tty9 vcsa4
>>> log_events ram1 tty14 tty40 ttyGS0 vcsa5
>>> log_main ram10 tty15 tty41 ttyO0 vcsa6
>>> log_radio ram11 tty16 tty42 ttyO1 vcsa7
>>> log_system ram12 tty17 tty43 ttyO2 watchdog
>>> loop-control ram13 tty18 tty44 ttyO4 watchdog0
>>> loop0 ram14 tty19 tty45 ttyO5 zero
>>> loop1 ram15 tty2 tty46 ttyS0
>>> loop2 ram2 tty20 tty47 ttyS1
>>>
>>> I know that UARTS are tty01, is the SPI named something similar?
>>>
>>> Thanks,
>>>
>>> Jacob
>>> --
>>> 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...@googlegroups.com <javascript:> .
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>
>
> --
> 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.
--
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.
