From: Subhashini Rao Beerisetty <subhashbeerisetty@gmail.com>
To: linux-spi@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: spi: Inquiry Regarding Linux Kernel SPI Subsystem device drivers
Date: Sat, 11 May 2024 00:39:50 +0530 [thread overview]
Message-ID: <CAPY=qRQR-wJ70gQfxxQ8m6r9XCKbQK5tWL9u=MNGbjb58=_huQ@mail.gmail.com> (raw)
Hi all,
I hope this email finds you well. I am new to the Linux kernel SPI
subsystem, I am currently in the process of learning about its
functionalities and intricacies. I have a few doubts and questions
that I would like to clarify, and I am hoping you could provide some
assistance.
As I understand it, the Linux kernel SPI subsystem supports two main
types of SPI drivers: SPI controller drivers and SPI protocol drivers.
Much like the USB Skeleton driver (drivers/usb/usb-skeleton.c) serves
as an excellent reference example for new engineers developing USB
device drivers, I am wondering if there exists a similar skeleton
driver for both SPI controller and SPI protocol drivers within the
Linux kernel tree. Would it be possible for you to share any reference
code or examples for these drivers?
Additionally, I am curious about the interaction between user space
applications and SPI hardware devices on the target side through the
SPI protocol driver. Could you please clarify if user space
applications communicate with the hardware device on the target side
via the SPI protocol driver running on the host side?
Furthermore, I would like to inquire about the availability of an SPI
library for user space applications, similar to libusb for USB
communication. Does the SPI subsystem provide any such library, or do
user space applications communicate directly with the SPI protocol or
controller driver through system call?
Your insights into these matters would be immensely helpful for my
understanding of the Linux kernel SPI subsystem. Thank you very much
for your time and consideration.
Thank You!
reply other threads:[~2024-05-10 19:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAPY=qRQR-wJ70gQfxxQ8m6r9XCKbQK5tWL9u=MNGbjb58=_huQ@mail.gmail.com' \
--to=subhashbeerisetty@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).