€•˜ˆ      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ/translations/zh_CN/spi/spidev”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/zh_TW/spi/spidev”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/it_IT/spi/spidev”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/ja_JP/spi/spidev”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/ko_KR/spi/spidev”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/pt_BR/spi/spidev”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/sp_SP/spi/spidev”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒSPI userspace API”h]”hŒSPI userspace API”…””}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³Œ8/var/lib/git/docbuild/linux/Documentation/spi/spidev.rst”h´KubhŒ	paragraph”“”)”}”(hŒÖSPI devices have a limited userspace API, supporting basic half-duplex
read() and write() access to SPI slave devices.  Using ioctl() requests,
full duplex transfers and device I/O configuration are also available.”h]”hŒÖSPI devices have a limited userspace API, supporting basic half-duplex
read() and write() access to SPI slave devices.  Using ioctl() requests,
full duplex transfers and device I/O configuration are also available.”…””}”(hhÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubhŒliteral_block”“”)”}”(hŒt#include <fcntl.h>
#include <unistd.h>
#include <sys/ioctl.h>
#include <linux/types.h>
#include <linux/spi/spidev.h>”h]”hŒt#include <fcntl.h>
#include <unistd.h>
#include <sys/ioctl.h>
#include <linux/types.h>
#include <linux/spi/spidev.h>”…””}”hhÝsbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1hÛh³hÊh´Khh·h²hubhÌ)”}”(hŒFSome reasons you might want to use this programming interface include:”h]”hŒFSome reasons you might want to use this programming interface include:”…””}”(hhíh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubhŒblock_quote”“”)”}”(hX  * Prototyping in an environment that's not crash-prone; stray pointers
  in userspace won't normally bring down any Linux system.

* Developing simple protocols used to talk to microcontrollers acting
  as SPI slaves, which you may need to change quite often.
”h]”hŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒ~Prototyping in an environment that's not crash-prone; stray pointers
in userspace won't normally bring down any Linux system.
”h]”hÌ)”}”(hŒ}Prototyping in an environment that's not crash-prone; stray pointers
in userspace won't normally bring down any Linux system.”h]”hŒPrototyping in an environment thatâ€™s not crash-prone; stray pointers
in userspace wonâ€™t normally bring down any Linux system.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj  )”}”(hŒ}Developing simple protocols used to talk to microcontrollers acting
as SPI slaves, which you may need to change quite often.
”h]”hÌ)”}”(hŒ|Developing simple protocols used to talk to microcontrollers acting
as SPI slaves, which you may need to change quite often.”h]”hŒ|Developing simple protocols used to talk to microcontrollers acting
as SPI slaves, which you may need to change quite often.”…””}”(hj$  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1j  h³hÊh´Khhýubah}”(h]”h ]”h"]”h$]”h&]”uh1hûh³hÊh´Khh·h²hubhÌ)”}”(hŒÒOf course there are drivers that can never be written in userspace, because
they need to access kernel interfaces (such as IRQ handlers or other layers
of the driver stack) that are not accessible to userspace.”h]”hŒÒOf course there are drivers that can never be written in userspace, because
they need to access kernel interfaces (such as IRQ handlers or other layers
of the driver stack) that are not accessible to userspace.”…””}”(hjF  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubh¶)”}”(hhh]”(h»)”}”(hŒDEVICE CREATION, DRIVER BINDING”h]”hŒDEVICE CREATION, DRIVER BINDING”…””}”(hjW  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjT  h²hh³hÊh´KubhÌ)”}”(hŒwThe spidev driver contains lists of SPI devices that are supported for
the different hardware topology representations.”h]”hŒwThe spidev driver contains lists of SPI devices that are supported for
the different hardware topology representations.”…””}”(hje  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K!hjT  h²hubhÌ)”}”(hŒGThe following are the SPI device tables supported by the spidev driver:”h]”hŒGThe following are the SPI device tables supported by the spidev driver:”…””}”(hjs  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K$hjT  h²hubhü)”}”(hXD  - struct spi_device_id spidev_spi_ids[]: list of devices that can be
  bound when these are defined using a struct spi_board_info with a
  .modalias field matching one of the entries in the table.

- struct of_device_id spidev_dt_ids[]: list of devices that can be
  bound when these are defined using a Device Tree node that has a
  compatible string matching one of the entries in the table.

- struct acpi_device_id spidev_acpi_ids[]: list of devices that can
  be bound when these are defined using a ACPI device object with a
  _HID matching one of the entries in the table.
”h]”j  )”}”(hhh]”(j  )”}”(hŒ¿struct spi_device_id spidev_spi_ids[]: list of devices that can be
bound when these are defined using a struct spi_board_info with a
.modalias field matching one of the entries in the table.
”h]”hÌ)”}”(hŒ¾struct spi_device_id spidev_spi_ids[]: list of devices that can be
bound when these are defined using a struct spi_board_info with a
.modalias field matching one of the entries in the table.”h]”hŒ¾struct spi_device_id spidev_spi_ids[]: list of devices that can be
bound when these are defined using a struct spi_board_info with a
.modalias field matching one of the entries in the table.”…””}”(hjŒ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K&hjˆ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj…  ubj  )”}”(hŒ¾struct of_device_id spidev_dt_ids[]: list of devices that can be
bound when these are defined using a Device Tree node that has a
compatible string matching one of the entries in the table.
”h]”hÌ)”}”(hŒ½struct of_device_id spidev_dt_ids[]: list of devices that can be
bound when these are defined using a Device Tree node that has a
compatible string matching one of the entries in the table.”h]”hŒ½struct of_device_id spidev_dt_ids[]: list of devices that can be
bound when these are defined using a Device Tree node that has a
compatible string matching one of the entries in the table.”…””}”(hj¤  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K*hj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj…  ubj  )”}”(hŒ³struct acpi_device_id spidev_acpi_ids[]: list of devices that can
be bound when these are defined using a ACPI device object with a
_HID matching one of the entries in the table.
”h]”hÌ)”}”(hŒ²struct acpi_device_id spidev_acpi_ids[]: list of devices that can
be bound when these are defined using a ACPI device object with a
_HID matching one of the entries in the table.”h]”hŒ²struct acpi_device_id spidev_acpi_ids[]: list of devices that can
be bound when these are defined using a ACPI device object with a
_HID matching one of the entries in the table.”…””}”(hj¼  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K.hj¸  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj…  ubeh}”(h]”h ]”h"]”h$]”h&]”j>  Œ-”uh1j  h³hÊh´K&hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hûh³hÊh´K&hjT  h²hubhÌ)”}”(hŒ×You are encouraged to add an entry for your SPI device name to relevant
tables, if these don't already have an entry for the device. To do that,
post a patch for spidev to the linux-spi@vger.kernel.org mailing list.”h]”(hŒ²You are encouraged to add an entry for your SPI device name to relevant
tables, if these donâ€™t already have an entry for the device. To do that,
post a patch for spidev to the ”…””}”(hjÝ  h²hh³Nh´NubhŒ	reference”“”)”}”(hŒlinux-spi@vger.kernel.org”h]”hŒlinux-spi@vger.kernel.org”…””}”(hjç  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ mailto:linux-spi@vger.kernel.org”uh1jå  hjÝ  ubhŒ mailing list.”…””}”(hjÝ  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K2hjT  h²hubhÌ)”}”(hX  It used to be supported to define an SPI device using the "spidev" name.
For example, as .modalias = "spidev" or compatible = "spidev".  But this
is no longer supported by the Linux kernel and instead a real SPI device
name as listed in one of the tables must be used.”h]”hX  It used to be supported to define an SPI device using the â€œspidevâ€ name.
For example, as .modalias = â€œspidevâ€ or compatible = â€œspidevâ€.  But this
is no longer supported by the Linux kernel and instead a real SPI device
name as listed in one of the tables must be used.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K6hjT  h²hubhÌ)”}”(hŒmNot having a real SPI device name will lead to an error being printed and
the spidev driver failing to probe.”h]”hŒmNot having a real SPI device name will lead to an error being printed and
the spidev driver failing to probe.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K;hjT  h²hubhÌ)”}”(hŒÏSysfs also supports userspace driven binding/unbinding of drivers to
devices that do not bind automatically using one of the tables above.
To make the spidev driver bind to such a device, use the following::”h]”hŒÎSysfs also supports userspace driven binding/unbinding of drivers to
devices that do not bind automatically using one of the tables above.
To make the spidev driver bind to such a device, use the following:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K>hjT  h²hubhÜ)”}”(hŒhecho spidev > /sys/bus/spi/devices/spiB.C/driver_override
echo spiB.C > /sys/bus/spi/drivers/spidev/bind”h]”hŒhecho spidev > /sys/bus/spi/devices/spiB.C/driver_override
echo spiB.C > /sys/bus/spi/drivers/spidev/bind”…””}”hj+  sbah}”(h]”h ]”h"]”h$]”h&]”hëhìuh1hÛh³hÊh´KBhjT  h²hubhÌ)”}”(hŒ÷When the spidev driver is bound to a SPI device, the sysfs node for the
device will include a child device node with a "dev" attribute that will
be understood by udev or mdev (udev replacement from BusyBox; it's less
featureful, but often enough).”h]”hŒýWhen the spidev driver is bound to a SPI device, the sysfs node for the
device will include a child device node with a â€œdevâ€ attribute that will
be understood by udev or mdev (udev replacement from BusyBox; itâ€™s less
featureful, but often enough).”…””}”(hj9  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KEhjT  h²hubhÌ)”}”(hŒ<For a SPI device with chipselect C on bus B, you should see:”h]”hŒ<For a SPI device with chipselect C on bus B, you should see:”…””}”(hjG  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KJhjT  h²hubhü)”}”(hX
  /dev/spidevB.C ...
    character special device, major number 153 with
    a dynamically chosen minor device number.  This is the node
    that userspace programs will open, created by "udev" or "mdev".

/sys/devices/.../spiB.C ...
    as usual, the SPI device node will
    be a child of its SPI master controller.

/sys/class/spidev/spidevB.C ...
    created when the "spidev" driver
    binds to that device.  (Directory or symlink, based on whether
    or not you enabled the "deprecated sysfs files" Kconfig option.)
”h]”hŒdefinition_list”“”)”}”(hhh]”(hŒdefinition_list_item”“”)”}”(hŒ¿/dev/spidevB.C ...
character special device, major number 153 with
a dynamically chosen minor device number.  This is the node
that userspace programs will open, created by "udev" or "mdev".
”h]”(hŒterm”“”)”}”(hŒ/dev/spidevB.C ...”h]”hŒ/dev/spidevB.C ...”…””}”(hjf  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  h³hÊh´KOhj`  ubhŒ
definition”“”)”}”(hhh]”hÌ)”}”(hŒ«character special device, major number 153 with
a dynamically chosen minor device number.  This is the node
that userspace programs will open, created by "udev" or "mdev".”h]”hŒ³character special device, major number 153 with
a dynamically chosen minor device number.  This is the node
that userspace programs will open, created by â€œudevâ€ or â€œmdevâ€.”…””}”(hjy  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KMhjv  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jt  hj`  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j^  h³hÊh´KOhj[  ubj_  )”}”(hŒh/sys/devices/.../spiB.C ...
as usual, the SPI device node will
be a child of its SPI master controller.
”h]”(je  )”}”(hŒ/sys/devices/.../spiB.C ...”h]”hŒ/sys/devices/.../spiB.C ...”…””}”(hj—  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  h³hÊh´KShj“  ubju  )”}”(hhh]”hÌ)”}”(hŒKas usual, the SPI device node will
be a child of its SPI master controller.”h]”hŒKas usual, the SPI device node will
be a child of its SPI master controller.”…””}”(hj¨  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KRhj¥  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jt  hj“  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j^  h³hÊh´KShj[  ubj_  )”}”(hŒÁ/sys/class/spidev/spidevB.C ...
created when the "spidev" driver
binds to that device.  (Directory or symlink, based on whether
or not you enabled the "deprecated sysfs files" Kconfig option.)
”h]”(je  )”}”(hŒ/sys/class/spidev/spidevB.C ...”h]”hŒ/sys/class/spidev/spidevB.C ...”…””}”(hjÆ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  h³hÊh´KXhjÂ  ubju  )”}”(hhh]”hÌ)”}”(hŒ created when the "spidev" driver
binds to that device.  (Directory or symlink, based on whether
or not you enabled the "deprecated sysfs files" Kconfig option.)”h]”hŒ¨created when the â€œspidevâ€ driver
binds to that device.  (Directory or symlink, based on whether
or not you enabled the â€œdeprecated sysfs filesâ€ Kconfig option.)”…””}”(hj×  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KVhjÔ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jt  hjÂ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j^  h³hÊh´KXhj[  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjU  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hûh³hÊh´KLhjT  h²hubhÌ)”}”(hŒÒDo not try to manage the /dev character device special file nodes by hand.
That's error prone, and you'd need to pay careful attention to system
security issues; udev/mdev should already be configured securely.”h]”hŒÖDo not try to manage the /dev character device special file nodes by hand.
Thatâ€™s error prone, and youâ€™d need to pay careful attention to system
security issues; udev/mdev should already be configured securely.”…””}”(hjý  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KZhjT  h²hubhÌ)”}”(hX²  If you unbind the "spidev" driver from that device, those two "spidev" nodes
(in sysfs and in /dev) should automatically be removed (respectively by the
kernel and by udev/mdev).  You can unbind by removing the "spidev" driver
module, which will affect all devices using this driver.  You can also unbind
by having kernel code remove the SPI device, probably by removing the driver
for its SPI controller (so its spi_master vanishes).”h]”hX¾  If you unbind the â€œspidevâ€ driver from that device, those two â€œspidevâ€ nodes
(in sysfs and in /dev) should automatically be removed (respectively by the
kernel and by udev/mdev).  You can unbind by removing the â€œspidevâ€ driver
module, which will affect all devices using this driver.  You can also unbind
by having kernel code remove the SPI device, probably by removing the driver
for its SPI controller (so its spi_master vanishes).”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K^hjT  h²hubhÌ)”}”(hX%  Since this is a standard Linux device driver -- even though it just happens
to expose a low level API to userspace -- it can be associated with any number
of devices at a time.  Just provide one spi_board_info record for each such
SPI device, and you'll get a /dev device node for each device.”h]”hX'  Since this is a standard Linux device driver -- even though it just happens
to expose a low level API to userspace -- it can be associated with any number
of devices at a time.  Just provide one spi_board_info record for each such
SPI device, and youâ€™ll get a /dev device node for each device.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KehjT  h²hubeh}”(h]”Œdevice-creation-driver-binding”ah ]”h"]”Œdevice creation, driver binding”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒBASIC CHARACTER DEVICE API”h]”hŒBASIC CHARACTER DEVICE API”…””}”(hj2  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj/  h²hh³hÊh´KlubhÌ)”}”(hŒVNormal open() and close() operations on /dev/spidevB.D files work as you
would expect.”h]”hŒVNormal open() and close() operations on /dev/spidevB.D files work as you
would expect.”…””}”(hj@  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kmhj/  h²hubhÌ)”}”(hX  Standard read() and write() operations are obviously only half-duplex, and
the chipselect is deactivated between those operations.  Full-duplex access,
and composite operation without chipselect de-activation, is available using
the SPI_IOC_MESSAGE(N) request.”h]”hX  Standard read() and write() operations are obviously only half-duplex, and
the chipselect is deactivated between those operations.  Full-duplex access,
and composite operation without chipselect de-activation, is available using
the SPI_IOC_MESSAGE(N) request.”…””}”(hjN  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kphj/  h²hubhÌ)”}”(hŒuSeveral ioctl() requests let your driver read or override the device's current
settings for data transfer parameters:”h]”hŒwSeveral ioctl() requests let your driver read or override the deviceâ€™s current
settings for data transfer parameters:”…””}”(hj\  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kuhj/  h²hubhü)”}”(hXÇ  SPI_IOC_RD_MODE, SPI_IOC_WR_MODE ...
    pass a pointer to a byte which will
    return (RD) or assign (WR) the SPI transfer mode.  Use the constants
    SPI_MODE_0..SPI_MODE_3; or if you prefer you can combine SPI_CPOL
    (clock polarity, idle high iff this is set) or SPI_CPHA (clock phase,
    sample on trailing edge iff this is set) flags.
    Note that this request is limited to SPI mode flags that fit in a
    single byte.

SPI_IOC_RD_MODE32, SPI_IOC_WR_MODE32 ...
    pass a pointer to a uin32_t
    which will return (RD) or assign (WR) the full SPI transfer mode,
    not limited to the bits that fit in one byte.

SPI_IOC_RD_LSB_FIRST, SPI_IOC_WR_LSB_FIRST ...
    pass a pointer to a byte
    which will return (RD) or assign (WR) the bit justification used to
    transfer SPI words.  Zero indicates MSB-first; other values indicate
    the less common LSB-first encoding.  In both cases the specified value
    is right-justified in each word, so that unused (TX) or undefined (RX)
    bits are in the MSBs.

SPI_IOC_RD_BITS_PER_WORD, SPI_IOC_WR_BITS_PER_WORD ...
    pass a pointer to
    a byte which will return (RD) or assign (WR) the number of bits in
    each SPI transfer word.  The value zero signifies eight bits.

SPI_IOC_RD_MAX_SPEED_HZ, SPI_IOC_WR_MAX_SPEED_HZ ...
    pass a pointer to a
    u32 which will return (RD) or assign (WR) the maximum SPI transfer
    speed, in Hz.  The controller can't necessarily assign that specific
    clock speed.
”h]”jZ  )”}”(hhh]”(j_  )”}”(hX•  SPI_IOC_RD_MODE, SPI_IOC_WR_MODE ...
pass a pointer to a byte which will
return (RD) or assign (WR) the SPI transfer mode.  Use the constants
SPI_MODE_0..SPI_MODE_3; or if you prefer you can combine SPI_CPOL
(clock polarity, idle high iff this is set) or SPI_CPHA (clock phase,
sample on trailing edge iff this is set) flags.
Note that this request is limited to SPI mode flags that fit in a
single byte.
”h]”(je  )”}”(hŒ$SPI_IOC_RD_MODE, SPI_IOC_WR_MODE ...”h]”hŒ$SPI_IOC_RD_MODE, SPI_IOC_WR_MODE ...”…””}”(hju  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  h³hÊh´Khjq  ubju  )”}”(hhh]”hÌ)”}”(hXo  pass a pointer to a byte which will
return (RD) or assign (WR) the SPI transfer mode.  Use the constants
SPI_MODE_0..SPI_MODE_3; or if you prefer you can combine SPI_CPOL
(clock polarity, idle high iff this is set) or SPI_CPHA (clock phase,
sample on trailing edge iff this is set) flags.
Note that this request is limited to SPI mode flags that fit in a
single byte.”h]”hXo  pass a pointer to a byte which will
return (RD) or assign (WR) the SPI transfer mode.  Use the constants
SPI_MODE_0..SPI_MODE_3; or if you prefer you can combine SPI_CPOL
(clock polarity, idle high iff this is set) or SPI_CPHA (clock phase,
sample on trailing edge iff this is set) flags.
Note that this request is limited to SPI mode flags that fit in a
single byte.”…””}”(hj†  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kyhjƒ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jt  hjq  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j^  h³hÊh´Khjn  ubj_  )”}”(hŒµSPI_IOC_RD_MODE32, SPI_IOC_WR_MODE32 ...
pass a pointer to a uin32_t
which will return (RD) or assign (WR) the full SPI transfer mode,
not limited to the bits that fit in one byte.
”h]”(je  )”}”(hŒ(SPI_IOC_RD_MODE32, SPI_IOC_WR_MODE32 ...”h]”hŒ(SPI_IOC_RD_MODE32, SPI_IOC_WR_MODE32 ...”…””}”(hj¤  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  h³hÊh´K„hj   ubju  )”}”(hhh]”hÌ)”}”(hŒ‹pass a pointer to a uin32_t
which will return (RD) or assign (WR) the full SPI transfer mode,
not limited to the bits that fit in one byte.”h]”hŒ‹pass a pointer to a uin32_t
which will return (RD) or assign (WR) the full SPI transfer mode,
not limited to the bits that fit in one byte.”…””}”(hjµ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K‚hj²  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jt  hj   ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j^  h³hÊh´K„hjn  ubj_  )”}”(hXu  SPI_IOC_RD_LSB_FIRST, SPI_IOC_WR_LSB_FIRST ...
pass a pointer to a byte
which will return (RD) or assign (WR) the bit justification used to
transfer SPI words.  Zero indicates MSB-first; other values indicate
the less common LSB-first encoding.  In both cases the specified value
is right-justified in each word, so that unused (TX) or undefined (RX)
bits are in the MSBs.
”h]”(je  )”}”(hŒ.SPI_IOC_RD_LSB_FIRST, SPI_IOC_WR_LSB_FIRST ...”h]”hŒ.SPI_IOC_RD_LSB_FIRST, SPI_IOC_WR_LSB_FIRST ...”…””}”(hjÓ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  h³hÊh´KŒhjÏ  ubju  )”}”(hhh]”hÌ)”}”(hXE  pass a pointer to a byte
which will return (RD) or assign (WR) the bit justification used to
transfer SPI words.  Zero indicates MSB-first; other values indicate
the less common LSB-first encoding.  In both cases the specified value
is right-justified in each word, so that unused (TX) or undefined (RX)
bits are in the MSBs.”h]”hXE  pass a pointer to a byte
which will return (RD) or assign (WR) the bit justification used to
transfer SPI words.  Zero indicates MSB-first; other values indicate
the less common LSB-first encoding.  In both cases the specified value
is right-justified in each word, so that unused (TX) or undefined (RX)
bits are in the MSBs.”…””}”(hjä  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K‡hjá  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jt  hjÏ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j^  h³hÊh´KŒhjn  ubj_  )”}”(hŒÊSPI_IOC_RD_BITS_PER_WORD, SPI_IOC_WR_BITS_PER_WORD ...
pass a pointer to
a byte which will return (RD) or assign (WR) the number of bits in
each SPI transfer word.  The value zero signifies eight bits.
”h]”(je  )”}”(hŒ6SPI_IOC_RD_BITS_PER_WORD, SPI_IOC_WR_BITS_PER_WORD ...”h]”hŒ6SPI_IOC_RD_BITS_PER_WORD, SPI_IOC_WR_BITS_PER_WORD ...”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  h³hÊh´K‘hjþ  ubju  )”}”(hhh]”hÌ)”}”(hŒ’pass a pointer to
a byte which will return (RD) or assign (WR) the number of bits in
each SPI transfer word.  The value zero signifies eight bits.”h]”hŒ’pass a pointer to
a byte which will return (RD) or assign (WR) the number of bits in
each SPI transfer word.  The value zero signifies eight bits.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jt  hjþ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j^  h³hÊh´K‘hjn  ubj_  )”}”(hŒÞSPI_IOC_RD_MAX_SPEED_HZ, SPI_IOC_WR_MAX_SPEED_HZ ...
pass a pointer to a
u32 which will return (RD) or assign (WR) the maximum SPI transfer
speed, in Hz.  The controller can't necessarily assign that specific
clock speed.
”h]”(je  )”}”(hŒ4SPI_IOC_RD_MAX_SPEED_HZ, SPI_IOC_WR_MAX_SPEED_HZ ...”h]”hŒ4SPI_IOC_RD_MAX_SPEED_HZ, SPI_IOC_WR_MAX_SPEED_HZ ...”…””}”(hj1  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  h³hÊh´K—hj-  ubju  )”}”(hhh]”hÌ)”}”(hŒ¨pass a pointer to a
u32 which will return (RD) or assign (WR) the maximum SPI transfer
speed, in Hz.  The controller can't necessarily assign that specific
clock speed.”h]”hŒªpass a pointer to a
u32 which will return (RD) or assign (WR) the maximum SPI transfer
speed, in Hz.  The controller canâ€™t necessarily assign that specific
clock speed.”…””}”(hjB  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K”hj?  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jt  hj-  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j^  h³hÊh´K—hjn  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jY  hjj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hûh³hÊh´Kxhj/  h²hubhÌ)”}”(hŒNOTES:”h]”hŒNOTES:”…””}”(hjh  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K™hj/  h²hubhü)”}”(hXê  - At this time there is no async I/O support; everything is purely
  synchronous.

- There's currently no way to report the actual bit rate used to
  shift data to/from a given device.

- From userspace, you can't currently change the chip select polarity;
  that could corrupt transfers to other devices sharing the SPI bus.
  Each SPI device is deselected when it's not in active use, allowing
  other drivers to talk to other devices.

- There's a limit on the number of bytes each I/O request can transfer
  to the SPI device.  It defaults to one page, but that can be changed
  using a module parameter.

- Because SPI has no low-level transfer acknowledgement, you usually
  won't see any I/O errors when talking to a non-existent device.

”h]”j  )”}”(hhh]”(j  )”}”(hŒNAt this time there is no async I/O support; everything is purely
synchronous.
”h]”hÌ)”}”(hŒMAt this time there is no async I/O support; everything is purely
synchronous.”h]”hŒMAt this time there is no async I/O support; everything is purely
synchronous.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K›hj}  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjz  ubj  )”}”(hŒbThere's currently no way to report the actual bit rate used to
shift data to/from a given device.
”h]”hÌ)”}”(hŒaThere's currently no way to report the actual bit rate used to
shift data to/from a given device.”h]”hŒcThereâ€™s currently no way to report the actual bit rate used to
shift data to/from a given device.”…””}”(hj™  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Kžhj•  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjz  ubj  )”}”(hŒôFrom userspace, you can't currently change the chip select polarity;
that could corrupt transfers to other devices sharing the SPI bus.
Each SPI device is deselected when it's not in active use, allowing
other drivers to talk to other devices.
”h]”hÌ)”}”(hŒóFrom userspace, you can't currently change the chip select polarity;
that could corrupt transfers to other devices sharing the SPI bus.
Each SPI device is deselected when it's not in active use, allowing
other drivers to talk to other devices.”h]”hŒ÷From userspace, you canâ€™t currently change the chip select polarity;
that could corrupt transfers to other devices sharing the SPI bus.
Each SPI device is deselected when itâ€™s not in active use, allowing
other drivers to talk to other devices.”…””}”(hj±  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¡hj­  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjz  ubj  )”}”(hŒ¤There's a limit on the number of bytes each I/O request can transfer
to the SPI device.  It defaults to one page, but that can be changed
using a module parameter.
”h]”hÌ)”}”(hŒ£There's a limit on the number of bytes each I/O request can transfer
to the SPI device.  It defaults to one page, but that can be changed
using a module parameter.”h]”hŒ¥Thereâ€™s a limit on the number of bytes each I/O request can transfer
to the SPI device.  It defaults to one page, but that can be changed
using a module parameter.”…””}”(hjÉ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¦hjÅ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjz  ubj  )”}”(hŒ„Because SPI has no low-level transfer acknowledgement, you usually
won't see any I/O errors when talking to a non-existent device.

”h]”hÌ)”}”(hŒ‚Because SPI has no low-level transfer acknowledgement, you usually
won't see any I/O errors when talking to a non-existent device.”h]”hŒ„Because SPI has no low-level transfer acknowledgement, you usually
wonâ€™t see any I/O errors when talking to a non-existent device.”…””}”(hjá  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´KªhjÝ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjz  ubeh}”(h]”h ]”h"]”h$]”h&]”j>  jÖ  uh1j  h³hÊh´K›hjv  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hûh³hÊh´K›hj/  h²hubeh}”(h]”Œbasic-character-device-api”ah ]”h"]”Œbasic character device api”ah$]”h&]”uh1hµhh·h²hh³hÊh´Klubh¶)”}”(hhh]”(h»)”}”(hŒ FULL DUPLEX CHARACTER DEVICE API”h]”hŒ FULL DUPLEX CHARACTER DEVICE API”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj	  h²hh³hÊh´K¯ubhÌ)”}”(hXg  See the spidev_fdx.c sample program for one example showing the use of the
full duplex programming interface.  (Although it doesn't perform a full duplex
transfer.)  The model is the same as that used in the kernel spi_sync()
request; the individual transfers offer the same capabilities as are
available to kernel drivers (except that it's not asynchronous).”h]”hXk  See the spidev_fdx.c sample program for one example showing the use of the
full duplex programming interface.  (Although it doesnâ€™t perform a full duplex
transfer.)  The model is the same as that used in the kernel spi_sync()
request; the individual transfers offer the same capabilities as are
available to kernel drivers (except that itâ€™s not asynchronous).”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K±hj	  h²hubhÌ)”}”(hXŽ  The example shows one half-duplex RPC-style request and response message.
These requests commonly require that the chip not be deselected between
the request and response.  Several such requests could be chained into
a single kernel request, even allowing the chip to be deselected after
each response.  (Other protocol options include changing the word size
and bitrate for each transfer segment.)”h]”hXŽ  The example shows one half-duplex RPC-style request and response message.
These requests commonly require that the chip not be deselected between
the request and response.  Several such requests could be chained into
a single kernel request, even allowing the chip to be deselected after
each response.  (Other protocol options include changing the word size
and bitrate for each transfer segment.)”…””}”(hj(  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K·hj	  h²hubhÌ)”}”(hŒ€To make a full duplex request, provide both rx_buf and tx_buf for the
same transfer.  It's even OK if those are the same buffer.”h]”hŒ‚To make a full duplex request, provide both rx_buf and tx_buf for the
same transfer.  Itâ€™s even OK if those are the same buffer.”…””}”(hj6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K¾hj	  h²hubeh}”(h]”Œ full-duplex-character-device-api”ah ]”h"]”Œ full duplex character device api”ah$]”h&]”uh1hµhh·h²hh³hÊh´K¯ubeh}”(h]”Œspi-userspace-api”ah ]”h"]”Œspi userspace api”ah$]”h&]”uh1hµhhh²hh³hÊh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÊuh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hºNŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jw  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÊŒ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jQ  jN  j,  j)  j  j  jI  jF  uŒ	nametypes”}”(jQ  ‰j,  ‰j  ‰jI  ‰uh}”(jN  h·j)  jT  j  j/  jF  j	  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nh²hub.