Skip to content

Commit

Permalink
kernel: i2c-comm: Explain why the I2C bus needs pull-ups
Browse files Browse the repository at this point in the history
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
  • Loading branch information
miquelraynal authored and tpetazzoni committed Oct 29, 2021
1 parent 4adf140 commit 205d7e3
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions labs/kernel-i2c-communication/kernel-i2c-communication.tex
Expand Up @@ -136,8 +136,11 @@ \section{Add pinctrl properties to the Device Tree}
\item \ksym{MUX_MODE2} corresponds to muxing mode 2, as explained in the
datasheet.
\item \ksym{PIN_INPUT_PULLUP} puts the pin in pull-up mode (remember
that our pins support both pull-up and pull-down). It seems to
be needed for I2C bus operation.
that our pins support both pull-up and pull-down). By design, an
I2C line is never actively driven high, devices either pull the
line low or let it floating. As we plug our device directly on the
bus without more analog electronics, we need to enable the
internal pull-up.
\end{itemize}

Now that pin muxing settings have been explained, edit your board
Expand Down

0 comments on commit 205d7e3

Please sign in to comment.