From bd5bbf5b9b3cebf8ea52e20439771fe6e4f74657 Mon Sep 17 00:00:00 2001 From: lkcl Date: Sun, 28 Nov 2021 22:07:29 +0000 Subject: [PATCH] --- docs/pinmux.mdwn | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/pinmux.mdwn b/docs/pinmux.mdwn index efecbfa8c..133d8d51d 100644 --- a/docs/pinmux.mdwn +++ b/docs/pinmux.mdwn @@ -63,7 +63,7 @@ on a given PCB, and they should not have to. Through the Resources, Platforms and Pins API, a level of abstraction between peripherals, boards and HDL designs is provided. Peripherals -may be given `(nane, number)` tuples, the HDL design may "request" +may be given `(name, number)` tuples, the HDL design may "request" a peripheral, which is described in terms of Resources, managed by a ResourceManager, and a Platform may provide that peripheral. The Platform is given @@ -85,8 +85,8 @@ Here is a function that defines a UART Resource: Note that the Subsignal is given a convenient name (tx, rx) and that there are Pins associated with it. -UARTResource would typically be part of a larger function that defines, for either -an FPGA or an ASIC, a full array of IO Connections: +UARTResource would typically be part of a larger function that defines, +for either an FPGA or an ASIC, a full array of IO Connections: def create_resources(pinset): resources = [] -- 2.30.2