Hi Lukas,
On 5/6/26 1:13 AM, Lukas Timmermann wrote:
This patch series adds the necessary files to use a modern pinctrl driver
with an exynos5250 SoC. The changes are well tested and are working.
In contrast to v1, this reenables GPIO functionality. But as I'm still
lacking experience, I'm not quite sure on how to prevent s5p_gpio to
load when using upstream DTS in a clean way. Because of that, this
patch series is marked as an RFC.
checkpatch complains about using #ifdef.
We already have an issue with samsung,exynos78x0-gpio so we'd need a
similar work-around for that one.
An easy way to sort this out would be to know if we know of devices
which are still using the old binding? Qualcomm is rather special, is
Samsung Exynos also special with regard to how it handles Device Trees?
Do we get it from an earlier boot stage or is everything coming from
U-Boot itself? If the latter, we can always migrate the existing devices
to the new binding and remove support for the old binding and with it
the same compatible in two drivers. Another question would be, does it
make sense for both drivers to be compiled? If not (e.g. it's only
pinctrl IPs inside an SoC and there's only one pinctrl device per SoC,
so if your device supports the new binding, you only need the new
driver). Then we can add a
depends on !PINCTRL_EXYNOS5250
for CONFIG_S5P (we probably should have a different symbol for the GPIO
driver though, maybe CONFIG_GPIO_S5P?).
Cheers,
Quentin
