From 2f37d71e790262d3a3f6720a7cb567330007fc60 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Wed, 20 Jun 2018 08:53:33 +0100 Subject: [PATCH] alter slide order --- pinmux/pinmux_chennai_2018.tex | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/pinmux/pinmux_chennai_2018.tex b/pinmux/pinmux_chennai_2018.tex index 8dbcacc9a..1b0837aaa 100644 --- a/pinmux/pinmux_chennai_2018.tex +++ b/pinmux/pinmux_chennai_2018.tex @@ -276,7 +276,7 @@ } -\frame{\frametitle{Input Mux Wiring} +\frame{\frametitle{Input Priority-Mux Wiring: very different from Out-Mux} \begin{center} \includegraphics[height=2.5in]{reg_gpio_in_wiring.jpg}\\ {\bf Pin Mux selection vals NOT same as FN selection vals} @@ -284,6 +284,29 @@ } +\frame{\frametitle{Input Priority-Mux Wiring} + + \begin{itemize} + \item In-Muxer selection number (0,1,2,3) obviously has to match + with Out-Muxer order (otherwise a bi-directional FN + needs different Mux-register settings for + selecting either IN or OUT) + \vspace{6pt} + \item Priority-mux selection values do not actually matter, + and have nothing to do with the actual Muxer settings. + \vspace{6pt} + \item GPIO FN's input muxer is nothing more than an AND gate\\ + (you never route more than one pin to one GPIO) + \vspace{6pt} + \item Any other FN with only 1:1 In also an AND gate \\ + (this just always happens to be true for GPIO) + \vspace{6pt} + \item Not all FNs have input capability: clearly they will not + be included in the In-Muxing. + \end{itemize} +} + + \frame{\frametitle{Summary} \begin{itemize} -- 2.30.2