Documentation ¶
Overview ¶
Package conn defines core interfaces for protocols and connections.
Is it now superseded by https://periph.io/x/conn/v3 (or later).
See https://periph.io/news/2020/a_new_start/ for more details.
Example ¶
package main import ( "fmt" "log" "github.com/meandrewdev/periph/conn/physic" "github.com/meandrewdev/periph/conn/spi" "github.com/meandrewdev/periph/conn/spi/spireg" "github.com/meandrewdev/periph/host" ) func main() { // Make sure periph is initialized. if _, err := host.Init(); err != nil { log.Fatal(err) } // Using SPI as an example. See package ./spi/spireg for more details. p, err := spireg.Open("") if err != nil { log.Fatal(err) } defer p.Close() c, err := p.Connect(physic.MegaHertz, spi.Mode3, 8) if err != nil { log.Fatal(err) } // Write 0x10 to the device, and read a byte right after. write := []byte{0x10, 0x00} read := make([]byte, len(write)) if err := c.Tx(write, read); err != nil { log.Fatal(err) } // Use read. fmt.Printf("%v\n", read[1:]) }
Output:
Index ¶
Examples ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Conn ¶
type Conn interface { String() string // Tx does a single transaction. // // For full duplex protocols (generally SPI, UART), the two buffers must have // the same length as both reading and writing happen simultaneously. // // For half duplex protocols (I²C), there is no restriction as reading // happens after writing, and r can be nil. // // Query Limits.MaxTxSize() to know if there is a limit on the buffer size // per Tx() call. Tx(w, r []byte) error // Duplex returns the current duplex setting for this point-to-point // connection. // // It is expected to be either Half or Full unless the connection itself is // in an unknown state. Duplex() Duplex }
Conn defines the interface for a connection on a point-to-point communication channel.
The connection can either be unidirectional (read-only, write-only) or bidirectional (read-write). It can either be half-duplex or full duplex.
This is the lowest common denominator for all point-to-point communication channels.
Implementation are expected but not required to also implement the following interfaces:
- fmt.Stringer which returns something meaningful to the user like "SPI0.1", "I2C1.76", "COM6", etc.
- io.Reader and io.Writer as a way to use io.Copy() for half duplex operation.
- io.Closer for the owner of the communication channel.
type Duplex ¶
type Duplex int
Duplex declares whether communication can happen simultaneously both ways.
Some protocol can be either depending on configuration settings, like UART.
const ( // DuplexUnknown is used when the duplex of a connection is yet to be known. // // Some protocol can be configured either as half-duplex or full-duplex and // the connection is not yet is a determinate state. DuplexUnknown Duplex = 0 // Half means that communication can only occurs one way at a time. // // Examples include 1-wire and I²C. Half Duplex = 1 // Full means that communication occurs simultaneously both ways in a // synchronized manner. // // Examples include SPI (except 3-wire variant). Full Duplex = 2 )
type Limits ¶
type Limits interface { // MaxTxSize returns the maximum allowed data size to be sent as a single // I/O. // // Returns 0 if undefined. MaxTxSize() int }
Limits returns information about the connection's limits.
type Resource ¶
type Resource interface { // String returns a human readable identifier representing this resource in a // descriptive way for the user. It is the same signature as fmt.Stringer. String() string // Halt stops the resource. // // Unlike a Conn, a Resource may not be closable, On the other hand, a // resource can be halted. What halting entails depends on the resource // device but it should stop motion, sensing loop, light emission or PWM // output and go back into an inert state. Halt() error }
Resource is a basic resource (like a gpio pin) or a device.
Directories ¶
Path | Synopsis |
---|---|
Package conntest implements fakes for package conn.
|
Package conntest implements fakes for package conn. |
Package display implements interfaces for visual output devices.
|
Package display implements interfaces for visual output devices. |
displaytest
Package displaytest contains non-hardware devices implementations for testing or emulation purpose.
|
Package displaytest contains non-hardware devices implementations for testing or emulation purpose. |
Package gpio defines digital pins.
|
Package gpio defines digital pins. |
gpioreg
Package gpioreg defines a registry for the known digital pins.
|
Package gpioreg defines a registry for the known digital pins. |
gpiostream
Package gpiostream defines digital streams.
|
Package gpiostream defines digital streams. |
gpiostream/gpiostreamtest
Package gpiostreamtest enables testing device driver using gpiostream.PinIn or PinOut.
|
Package gpiostreamtest enables testing device driver using gpiostream.PinIn or PinOut. |
gpiotest
Package gpiotest is meant to be used to test drivers using fake Pins.
|
Package gpiotest is meant to be used to test drivers using fake Pins. |
Package i2c defines the API to communicate with devices over the I²C protocol.
|
Package i2c defines the API to communicate with devices over the I²C protocol. |
i2creg
Package i2creg defines I²C bus registry to list buses present on the host.
|
Package i2creg defines I²C bus registry to list buses present on the host. |
i2ctest
Package i2ctest is meant to be used to test drivers over a fake I²C bus.
|
Package i2ctest is meant to be used to test drivers over a fake I²C bus. |
Package i2s will eventually define the API to communicate with devices over the I²S protocol.
|
Package i2s will eventually define the API to communicate with devices over the I²S protocol. |
Package ir defines InfraRed codes for use with a IR remote control.
|
Package ir defines InfraRed codes for use with a IR remote control. |
Package jtag will eventually define the API to communicate with devices over the JTAG protocol.
|
Package jtag will eventually define the API to communicate with devices over the JTAG protocol. |
Package mmr defines helpers to interact with devices exposing Memory Mapped Registers protocol.
|
Package mmr defines helpers to interact with devices exposing Memory Mapped Registers protocol. |
Package onewire defines the API to communicate with devices over the Dallas Semiconductor / Maxim Integrated 1-wire protocol.
|
Package onewire defines the API to communicate with devices over the Dallas Semiconductor / Maxim Integrated 1-wire protocol. |
onewirereg
Package onewirereg defines a registry for onewire buses present on the host.
|
Package onewirereg defines a registry for onewire buses present on the host. |
onewiretest
Package onewiretest is meant to be used to test drivers over a fake 1-wire bus.
|
Package onewiretest is meant to be used to test drivers over a fake 1-wire bus. |
Package physic declares types for physical input, outputs and measurement units.
|
Package physic declares types for physical input, outputs and measurement units. |
Package pin declare well known pins.
|
Package pin declare well known pins. |
pinreg
Package pinreg is a registry for the physical headers (made up of pins) on a host.
|
Package pinreg is a registry for the physical headers (made up of pins) on a host. |
Package spi defines the API to communicate with devices over the SPI protocol.
|
Package spi defines the API to communicate with devices over the SPI protocol. |
spireg
Package spireg defines the SPI registry for SPI ports discovered on the host.
|
Package spireg defines the SPI registry for SPI ports discovered on the host. |
spitest
Package spitest is meant to be used to test drivers over a fake SPI port.
|
Package spitest is meant to be used to test drivers over a fake SPI port. |
Package uart will eventually define the API to communicate with devices over the UART protocol.
|
Package uart will eventually define the API to communicate with devices over the UART protocol. |