Hello,
I have some problems (probably misconfigured gpio or pwm pad) driving a custom add-on board since I use jetpack-6. It worked well with jetpack-5.1.2. The specific GPIO is PI.00 and the pwm is pwm3.
Parsing Jetson AGX Orin Platform Adaptation and Bring-Up — NVIDIA Jetson Linux Developer Guide 1 documentation I have found the following note :
Currently, to update pinmux, users cannot use the pinctrl APIs.
This is because the upstreamed GPIO driver does not yet support
calling the pinctrl APIs to make changes in the pinmux registers.
Is that still true ? Is it impossible to change pinmux/pinctrl after the initial flashing ?
If I am not mistaken, the last update to that driver in jetpack-6.1 is
commit 5362f5c76bb98c5a0125c96be07348716ebf79b3
Author: Prathamesh Shete <pshete@nvidia.com>
Date: Mon Jun 5 17:42:29 2023 +0200
pinctrl: tegra: Add Tegra234 pinmux driver
BugLink: https://bugs.launchpad.net/bugs/2028400
This change adds support for the two pin controllers found on Tegra234.
(cherry-picked from commit 6d8257ca39884a90bbb61e3441f7d578abc53bac)
Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Link: https://lore.kernel.org/r/20230605154230.2910847-3-thierry.reding@gmail.com
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
Reviewed-by: Jonathan Hunter <jonathanh@nvidia.com>
Signed-off-by: Abhilash G <abhilashg@nvidia.com>
Acked-by: Jacob Martin <jacob.martin@canonical.com>
Acked-by: Ian May <ian.may@canonical.com>
Signed-off-by: Jacob Martin <jacob.martin@canonical.com>