kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: ksashtekar@gmail.com (Kaustubh Ashtekar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: SPI over GPIO
Date: Fri, 11 Mar 2011 16:38:29 +0530	[thread overview]
Message-ID: <AANLkTinUSGt3P+s1uVFQt7Z6t+w3Wc-XrNg74rrQrO8c@mail.gmail.com> (raw)
In-Reply-To: <344296.43554.qm@web56301.mail.re3.yahoo.com>

Please paste the full log of what you typed on the console and also
paste output of:

strace <your full command>

On Fri, Mar 11, 2011 at 4:04 PM, Alexandru Caramida
<alexandruc1723@yahoo.com> wrote:
> Hello everyone,
> I am trying to emulate an SPI interface using four GPIO pins. This is a
> desktop computer with linux 2.6.28 kernel.
> The problem is I don't know if the pins are working. I read that if I have
> the sysfs support for the kernel (which I do :D) all I have to do
> is enable the respectiv pin using
> echo N > /sys/class/gpio/export
> And I would get a gpioN directory
> But I always get: "write error : invalid argument."
> Is there some other option i need to enable first? The people I am working
> with assured me that these pins are not used by any other device and they
> haven't found anything to suggest that they were turned off manualy.
> Please help,
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>

  parent reply	other threads:[~2011-03-11 11:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 10:34 SPI over GPIO Alexandru Caramida
2011-03-11 10:44 ` Tirtha Ghosh
2011-03-11 11:08 ` Kaustubh Ashtekar [this message]
2011-03-11 16:31   ` Vic
2011-03-12 21:03     ` LILO jump/retf question Andrzej Kardas
2011-03-13  8:31       ` Mulyadi Santosa

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=AANLkTinUSGt3P+s1uVFQt7Z6t+w3Wc-XrNg74rrQrO8c@mail.gmail.com \
    --to=ksashtekar@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).