[Linux-stm32] [PATCH] ARM: dts: stm32: Fill GPIO line names on AV96
Ahmad Fatoum
a.fatoum at pengutronix.de
Mon Mar 15 12:05:05 GMT 2021
On 15.03.21 12:41, Christoph Niedermaier wrote:
>> So I'll pose another question here to the GPIO maintainers.
>>
>> Is it OK to define gpio-line-names in SoM DTSI even for pins which will
>> not be used as GPIOs e.g. because they are muxed differently in the
>> carrier board DTS ?
>>
>> If that is OK, then the above approach is then also OK.
>
> In our case, we cannot mux the GPIO pins in the carrier board DTS
> to another functions, because then we break our SOM standard (DHCOM).
> So in the case we relabel a GPIO in the carrier board e.g. "DHCOM-I"
> becomes "LED1" the mux function have to be GPIO.
For standards like SMARC, where the interface is predefined, I think it makes
much sense to have the SoM dtsi contain not only the line-names, but also
ready-to-use, pinmuxing settings.
Base boards can then either enable peripherals with just a status = "okay"
if they follow the standard or just override it if they choose to do
stuff differently.
Cheers,
Ahmad
>
> Regards,
> Christoph
> _______________________________________________
> Linux-stm32 mailing list
> Linux-stm32 at st-md-mailman.stormreply.com
> https://st-md-mailman.stormreply.com/mailman/listinfo/linux-stm32
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the linux-arm-kernel
mailing list