From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Nikesh Gawande <nikelinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Segmentation fault when calling spi_sync function
Date: Wed, 30 Jan 2008 10:45:29 -0800 [thread overview]
Message-ID: <200801301045.29630.david-b@pacbell.net> (raw)
In-Reply-To: <c60870f00801300218u799eb1pebbf2681bb6865b5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wednesday 30 January 2008, Nikesh Gawande wrote:
> I am doing this in my
> driver but at the point when spi_sync() is called I get the following
> messages. which is something about segmentation fault. I am not
> understanding the error.
Presumably you didn't set up the spi_message correctly or spi_device
correctly. Find what the code at that location was referencing, and
then you'll know what initialization you forgot.
> Is it compulsory to call spi_sync() or spi_async() functions for data
> transfer. Is there any other way to do it?
The spi_sync() call wraps spi_async(); there are a few other wrappers
too. Fundamentally everything boils down to a spi_async() call; there
is no other primitive at the controller level.
- Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-01-30 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 10:18 Segmentation fault when calling spi_sync function Nikesh Gawande
[not found] ` <c60870f00801300218u799eb1pebbf2681bb6865b5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-30 18:45 ` David Brownell [this message]
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=200801301045.29630.david-b@pacbell.net \
--to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
--cc=nikelinux-Re5JQEeQqe8AvxtiuMwx3w@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.