AM5748: SDK 09.03: Can pinmuxes be defined in kernel device tree?

Okay thanks for the guidance.  Is there a reason why the 57x differs from the L138/335x/62x?

Hello,

I am out of office today. Please expect a 1-2 business day delay in response.

-Josue

Jonathan,

These are all different processors/architectures.

-Josue

Lol okay, yes and?  How does that change my question?  I'm curious what is special about the 57x architecture that it affects the pinmux.

Jonathan,

This is clearly explained in the app-note you referenced:

"To ensure the IO timing values published in the Timing Requirements and Switching Characteristics tables of the AM57xx data manual over the lifetime of the device, the AM57xx software must implement the proper pad configuration requirements. The impact of not following these requirements may not be observed immediately. However, in the long term, failure to adhere to this procedure may cause system issues. It is recommended to read the Pad Configuration section of the Control Module in the AM57xx TRM to become familiar with the detailed requirements including the Pad Configuration registers, IOSETs, virtual IO timing modes, manual IO timing modes, isolation requirements, and IO delay recalibration. All of these requirements are automatically configured when the PinMux Tool is used in conjunction with the Board Library within Processor SDK RTOS or in conjunction with U-Boot when running Linux."

-Josue

Thanks. That is pretty clear.