Closed cfriedt closed 1 week ago
@cfriedt what about the existing binding slew-rate
and already implemented in STM32 pinctrl:
slew-rate = "very-high-speed";
@erwango - oh wow - I just saw that. Would it make sense to change the TI one to use the same terminology?
@vaishnavachath - Was is already discussed at some point about using a common DT binding for drive strength / slew rate in Zephyr?
@erwango - oh wow - I just saw that. Would it make sense to change the TI one to use the same terminology?
Maybe. For the record, we've taken this from Linux.
If they are generic, that's probably the best solution then. I wonder if TI has custom bindings in Linux. Do you know, @vaishnavachath ?
Is your feature request related to a problem? Please describe.
This is not at all a bug, it's more of a "nice to have".
When using some peripheral alternate functions (e.g. i2c), it would be really nice to be able to configure the drive strength via Devicetree (as it's done for e.g. TI cc13xx-cc26xx)
I believe the GPIO drive strength is configured on ST parts using the following bits from stm32-pinctrl.h.
Describe the solution you'd like The ability to specify high drive strength with 1 additional, generic devicetree property. Something like the following:
Describe alternatives you've considered I think the only way to do this currently is to create a custom pinmux with additional bits or'ed together.
Additional context