From b37ee41cdbcc025f050acd4f81bfff3b592c1454 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Sun, 17 Jun 2018 07:48:20 +0100 Subject: [PATCH] add new slide --- pinmux/pinmux_chennai_2018.tex | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/pinmux/pinmux_chennai_2018.tex b/pinmux/pinmux_chennai_2018.tex index 37826be6a..e866254a1 100644 --- a/pinmux/pinmux_chennai_2018.tex +++ b/pinmux/pinmux_chennai_2018.tex @@ -52,6 +52,23 @@ } +\frame{\frametitle{Why, How and What is a Pinmux?} + + \begin{itemize} + \item Why? To save cost, increase yield, and to target multiple + markets with the same design, thereby increasing uptake + and consequently taking advantage of volume pricing.\vspace{10pt} + \\ + Summary: it's all about making more money!\vspace{10pt} + \item How? By multiplexing many more functions (100 to 1,200) than there + are actual available pins (48 to 500), the required chip package + is far less costly and the chip more desirable\vspace{10pt} + \item What? A many-to-many dynamically-configureable router of + I/O functions to I/O pins\vspace{10pt} + \end{itemize} +} + + \frame{\frametitle{Muxer cases to handle} \begin{itemize} -- 2.30.2