@@ -292,11 +292,15 @@ mod ioset {
292
292
/// After implementing `IoSet` type checking, it became clear that some
293
293
/// existing boards were using a combinations of pins that did not match any
294
294
/// IOSET in the datasheet. From that, we infer that there must be at least
295
- /// one undocumented IOSET, and we added this new `IoSet` to account for it.
295
+ /// two undocumented IOSETs, and we added these new `IoSet`s to account for
296
+ /// it.
296
297
///
297
- /// As of writing this documentation, only one undocumented IOSET has been
298
- /// discovered: PA16, PA17, PB22 & PB23 configured for `Sercom1`. Both the
298
+ /// As of writing this documentation, only two undocumented IOSETs have been
299
+ /// discovered:
300
+ /// - PA16, PA17, PB22 & PB23 configured for `Sercom1`. Both the
299
301
/// pygamer & feather_m4 uses this combination.
302
+ /// - PA00, PA01, PB22 & PB23 configured for `Sercom1`. The itsybitsy_m4
303
+ /// uses this combination.
300
304
///
301
305
/// See the [type-level enum] documentation for more details on type-level
302
306
/// variants.
@@ -306,6 +310,10 @@ mod ioset {
306
310
impl Sealed for UndocIoSet1 { }
307
311
impl IoSet for UndocIoSet1 { }
308
312
313
+ pub enum UndocIoSet2 { }
314
+ impl Sealed for UndocIoSet2 { }
315
+ impl IoSet for UndocIoSet2 { }
316
+
309
317
/// Type class for SERCOM pads in a given [`IoSet`]
310
318
///
311
319
/// This trait is used to label each [`Pin`] implementing [`IsPad`] with its
0 commit comments