New driver for MCP2210 (USB to SPI bridge w/GPIO)

DISCUSSION Daniel Santos 1 participant 2 messages Apr 13, 2013 – Apr 14, 2013 2 messages not in the archive SPI

lore

Share & tools

lore

Daniel Santos

author

2013-04-13 23:47 UTC #2 lore raw

In reply to a message not in the archive

Quoted 6 lines

3. When my driver is called via the functions exported in the struct spi_master after I register it with spi_register_master(), I'm presuming these will never be in an interrupt context (soft or hard). Is that correct? (I'm planning on using simple mutexes for locking.)

Correction, I'll be calling transfer_one_message() instead of transfer(), as I now see that this function is depreciated (thanks to the output in dmesg). And the docs say that I can sleep in these functions, so I presume that mutex_(un)lock is fine.

Daniel

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter

Daniel Santos

author

2013-04-14 04:35 UTC #3 lore raw

In reply to a message not in the archive

Quoted 4 lines

4. How do I specify in my specific driver that it's dependent upon the generic MCP2210 driver? I know that's easy if it's in-tree via Kconfig, but out-of-tree, during module_init or some such?

hah! Well I appear to have answered two of my own questions now. Looks like depmod actually figures out what unresolved symbols you have and find the modules that way, very nice! Maybe this also answers my 5th question as well.

Daniel