djsundog
/
circuitpython
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #4569 from lesamouraipourpre/displayio-doc-fixes 

Minor documentation fixes in displayio
This commit is contained in:
Limor "Ladyada" Fried 2021-04-06 10:41:22 -04:00 committed by GitHub
parent bf58afdb2a 8958c1e227
commit 354be8cbcc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
shared-bindings/displayio/FourWire.c
View File

@ -48,7 +48,7 @@
//| The SPI bus and pins are then in use by the display until `displayio.release_displays()` is //| The SPI bus and pins are then in use by the display until `displayio.release_displays()` is
//| called even after a reload. (It does this so CircuitPython can use the display after your code //| called even after a reload. (It does this so CircuitPython can use the display after your code
//| is done.) So, the first time you initialize a display bus in code.py you should call //| is done.) So, the first time you initialize a display bus in code.py you should call
//| :py:func`displayio.release_displays` first, otherwise it will error after the first code.py run. //| :py:func:`displayio.release_displays` first, otherwise it will error after the first code.py run.
//| //|
//| :param busio.SPI spi_bus: The SPI bus that make up the clock and data lines //| :param busio.SPI spi_bus: The SPI bus that make up the clock and data lines
//| :param microcontroller.Pin command: Data or command pin //| :param microcontroller.Pin command: Data or command pin

2
shared-bindings/displayio/I2CDisplay.c
View File

@ -48,7 +48,7 @@
//| The I2C bus and pins are then in use by the display until `displayio.release_displays()` is //| The I2C bus and pins are then in use by the display until `displayio.release_displays()` is
//| called even after a reload. (It does this so CircuitPython can use the display after your code //| called even after a reload. (It does this so CircuitPython can use the display after your code
//| is done.) So, the first time you initialize a display bus in code.py you should call //| is done.) So, the first time you initialize a display bus in code.py you should call
//| :py:func`displayio.release_displays` first, otherwise it will error after the first code.py run. //| :py:func:`displayio.release_displays` first, otherwise it will error after the first code.py run.
//| //|
//| :param busio.I2C i2c_bus: The I2C bus that make up the clock and data lines //| :param busio.I2C i2c_bus: The I2C bus that make up the clock and data lines
//| :param int device_address: The I2C address of the device //| :param int device_address: The I2C address of the device

2
shared-bindings/displayio/ParallelBus.c
View File

@ -49,7 +49,7 @@
//| The parallel bus and pins are then in use by the display until `displayio.release_displays()` //| The parallel bus and pins are then in use by the display until `displayio.release_displays()`
//| is called even after a reload. (It does this so CircuitPython can use the display after your //| is called even after a reload. (It does this so CircuitPython can use the display after your
//| code is done.) So, the first time you initialize a display bus in code.py you should call //| code is done.) So, the first time you initialize a display bus in code.py you should call
//| :py:func`displayio.release_displays` first, otherwise it will error after the first code.py run. //| :py:func:`displayio.release_displays` first, otherwise it will error after the first code.py run.
//| //|
//| :param microcontroller.Pin data0: The first data pin. The rest are implied //| :param microcontroller.Pin data0: The first data pin. The rest are implied
//| :param microcontroller.Pin command: Data or command pin //| :param microcontroller.Pin command: Data or command pin