Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Problem
When using I2S connector pins as GPIO via libgpio, pins revert to their bootloader default state on application exit or crash. A customer reported this caused unintended 3.3V on pins that need to be 0V by default.
Changes
Pinmux BCT (
tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi):pull=NONE,tristate=DISABLE,enable-input=DISABLEon all 5 pins, configuring pads as actively driven outputs (matches existinggpio-output-lowpin patterns likeuart4_cts_ph6)GPIO BCT (
tegra234-mb1-bct-gpio-p3767-dp-a03.dtsi):H,7/I,0/I,1/I,2/AC,6fromgpio-inputtogpio-output-lowTest plan
gpioinfo//sys/kernel/debug/gpio)ark_i2s_gpio.dtsoverlay still works for normal GPIO usage