From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: Looking for information on modern(ish) use of spidev
Date: Wed, 20 Apr 2016 23:20:52 +0300 [thread overview]
Message-ID: <20160420202052.GM2476@tarshish> (raw)
In-Reply-To: <CAF_dkJDRaidOF5p1B+ssx=SKgUHonMj5TbG2mT3wE5bOdDw69g@mail.gmail.com>
Hi Patrick,
On Wed, Apr 20, 2016 at 03:55:42PM -0400, Patrick Doyle wrote:
> Can anybody point me at a relatively recent tutorial/explanation of
> the current usage of spidev?
There is a dedicated list to the SPI subsystem (linux-spi at vger.kernel.org).
See MAINTAINERS.
> What should I put in my device tree? Should I modprobe spidev?
The spidev binding is not documented, but you can find a few examples under
arch/arm/boot/dts/.
> I have 2 devices hanging off a SPI bus and I would like to verify that
> they work. All I need to be able to do is to transfer some data to
> and from the devices and see that it looks reasonable. I'll figure
> out the correct device driver later, but I just want to see some
> transactions on the bus today.
>
> What's the simplest way to do that? If spidev isn't the right tree to
> climb, where should I look instead?
For half duplex transfers just read/write the spidev device node. For
something more complex see the examples under tools/spi/.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2016-04-20 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 19:55 Looking for information on modern(ish) use of spidev Patrick Doyle
2016-04-20 20:20 ` Baruch Siach [this message]
2016-04-20 20:29 ` Patrick Doyle
2016-04-20 20:32 ` Baruch Siach
2016-04-20 20:35 ` Patrick Doyle
2016-04-20 20:44 ` Andy Gross
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=20160420202052.GM2476@tarshish \
--to=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.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