From d1bdde56cced15cdc76625e4e1075abdcda3c9b5 Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Sat, 3 Jul 2021 22:52:42 -0400 Subject: samd_sercom: Specify the sercom explicitly in a config option Do not infer the sercom from the config section name, as that prevents one from using SPI buses on multiple samd mcus. Signed-off-by: Kevin O'Connor --- docs/Config_Reference.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) (limited to 'docs/Config_Reference.md') diff --git a/docs/Config_Reference.md b/docs/Config_Reference.md index 94b8d88f..f271d8d5 100644 --- a/docs/Config_Reference.md +++ b/docs/Config_Reference.md @@ -3793,13 +3793,17 @@ i2c_address: ## [samd_sercom] 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. +SERCOM. One may define any number of sections with a "samd_sercom" +prefix. 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 sercom0] +[samd_sercom my_sercom] +sercom: +# The name of the sercom bus to configure in the micro-controller. +# Available names are "sercom0", "sercom1", etc.. This parameter +# must be provided. tx_pin: # MOSI pin for SPI communication, or SDA (data) pin for I2C # communication. The pin must have a valid pinmux configuration -- cgit v1.2.3-70-g09d2