Can multiple PWM channels on Jetson Thor be synchronized?

Hi NVIDIA team,

On Jetson Thor, I’d like to output several PWM signals from different PWM channels at the same time, with the same frequency and phase-aligned edges (no drift over time).

Do the PWM channels share a common clock source, and is there any way to start them together or align their phase (e.g. a synchronized start or phase offset register)?

Thanks very much!

Hi owenturing1224,

Are you using the devkit or custom board for Thor?
What’s the Jetpack version in use?

You should be able to output them with different PWM period/duty_cycle respectively.

Hi Kevin,

Custom carrier board, Jetpack 7.1.

Independent output already works. What I need is to output 4 PWM channels synchronized with each other — same clock source (no drift), started together or phase-aligned so the edges stay locked. Is that possible on Thor?

Thanks.

Jetson Thor PWM is exposed through the standard pwm-tegra framework and supports normal PWM configuration, but it should not be treated as a guaranteed hardware-synchronized multi-channel solution for 4 outputs with phase-aligned edges and no drift.
For strict synchronization, the recommended approach is to use an external MCU, FPGA, or dedicated PWM generator.

Hi Kevin,

Understood, thanks.

Even without a hardware guarantee, I’d like to try implementing it first. Within the pwm-tegra framework, are the 4 channels driven from a common clock, and is there any way to start them together or align their phase? Any pointers on how to approach this would be appreciated.

These might be relevant. clock-names = "tach";

jp7.2/Linux_for_Tegra/source/nvidia-oot/drivers/pwm/pwm-tegra-tachometer.c
cd jp7.2/Linux_for_Tegra/source/
nvidia-oot/Documentation/devicetree/bindings/pwm/nvidia,pwm-tegra264-tachometer.yaml
nvidia-oot/Documentation/devicetree/bindings/pwm/pwm-tegra-tachometer.yaml
jp7.2/Linux_for_Tegra/source/hardware/nvidia$ grep -irl tachometer@

t264/nv-public/nv-platform/tegra264-p3971-0000.dtsi
t264/nv-public/nv-platform/tegra264-p4071-0000.dtsi
t264/nv-public/nv-platform/tegra264-p3740-0002.dtsi
t264/nv-public/tegra264.dtsi
                tachometer@810c5c0000 {
                        capture-window-length = <0x02>;
                        disable-clk-gate;
                        clock-names = "tach";
                        resets = <0x02 0x2c>;
                        clocks = <0x02 0x158>;
                        pulse-per-rev = <0x02>;
                        #pwm-cells = <0x02>;
                        compatible = "nvidia,pwm-tegra264-tachometer";
                        status = "okay";
                        reg = <0x81 0xc5c0000 0x00 0x10>;
                        reset-names = "tach";
                };
--
                tachometer@810c5d0000 {
                        capture-window-length = <0x02>;
                        disable-clk-gate;
                        clock-names = "tach";
                        resets = <0x02 0x2a>;
                        clocks = <0x02 0x158>;
                        pulse-per-rev = <0x02>;
                        #pwm-cells = <0x02>;
                        compatible = "nvidia,pwm-tegra264-tachometer";
                        status = "disabled";
                        reg = <0x81 0xc5d0000 0x00 0x10>;
                        reset-names = "tach";
                };

Yes, you can try that.
The 4 PWM channels can be configured to use the same parent clock in DTS, so that is the first thing I would do. But each Tegra264 PWM controller is still independent, so there is no obvious built-in group-start or phase-align mechanism in pwm-tegra.

My suggestion is to put all 4 channels on the same parent clock, use the same pwm-depth, same period/duty, and enable them from one kernel path/custom driver as closely together as possible, then check the skew on the scope.