atsamd: Add support for programming SERCOM pins

Signed-off-by: Florian Heilmann <Florian.Heilmann@gmx.net>
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>

1 files changed, 21 insertions, 0 deletions

diff --git a/config/example-extras.cfg b/config/example-extras.cfg
index 7e239f09..2645c6cb 100644
--- a/config/example-extras.cfg
+++ b/config/example-extras.cfg
@@ -721,6 +721,27 @@
 #   parameter must be provided.
 
 
+# SAMD SERCOM configuration to specify which pins to use on a given SERCOM.
+# One may define one section with the "samd_sercom" prefix per
+# SERCOM available. Each SERCOM must be configured prior to using it as
+# SPI or I2C peripheral. Place this config section above any other section
+# that makes use of SPI or I2C buses.
+#[samd_sercom 0]
+#tx_pin:
+#   MOSI pin for SPI communication, or SDA (data) pin for I2C
+#   communication. The pin must have a valid pinmux configuration
+#   for the given SERCOM peripheral. This parameter must be provided.
+#rx_pin:
+#   MISO pin for SPI communication. This pin is not used for I2C
+#   communication (I2C uses tx_pin for both sending and receiving).
+#   The pin must have a valid pinmux configuration for the given
+#   SERCOM peripheral. This parameter is optional.
+#clk_pin:
+#   CLK pin for SPI communication, or SCL (clock) pin for I2C
+#   communication. The pin must have a valid pinmux configuration
+#   for the given SERCOM peripheral. This parameter must be provided.
+
+
 # Statically configured AD5206 digipots connected via SPI bus (one may
 # define any number of sections with an "ad5206" prefix).
 #[ad5206 my_digipot]