From: Daniel Santos <danielfsantos-fOdFMYwuEsI@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: New driver for MCP2210 (USB to SPI bridge w/GPIO)
Date: Sat, 13 Apr 2013 18:47:29 -0500 [thread overview]
Message-ID: <5169EE91.9080308@att.net> (raw)
In-Reply-To: <5169DE3F.5030909-fOdFMYwuEsI@public.gmane.org>
> 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
next parent reply other threads:[~2013-04-13 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5169DE3F.5030909@att.net>
[not found] ` <5169DE3F.5030909-fOdFMYwuEsI@public.gmane.org>
2013-04-13 23:47 ` Daniel Santos [this message]
2013-04-14 4:35 ` New driver for MCP2210 (USB to SPI bridge w/GPIO) Daniel Santos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5169EE91.9080308@att.net \
--to=danielfsantos-fodfmywuesi@public.gmane.org \
--cc=daniel.santos-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.