-
Notifications
You must be signed in to change notification settings - Fork 8.3k
boards: thingy52_nrf52832: Update gpio-leds binding #34412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Change updates gpio-leds DTS binding. The colors should be defined in RGB order. Signed-off-by: Marek Pieta <Marek.Pieta@nordicsemi.no>
|
I don't mind the change but some applications may actually depend on the old order. |
|
Yes, I am aware of this. Still I think that we should consistently use RGB order for all the boards (otherwise porting may cause troubles). |
|
I'm not convinced about the change. We've got more boards in the tree with the LED order different than RGB, see for instance nRF52840 dongle. And as @pdunaj already signaled, this change might affect existing applications - some may blink in red now instead of blinking in green ( |
|
@anangl, on the dongle the colors of a single LED are in order. There is only added a first channel of other monochromatic LED before them. |
I think boards should not try to define leds order in the first place. This is something that zephyr often does to try to make its samples working out-of-the-box but which later has to be untangled at application level as often this is either done wrong (like in this case) or is not complete. I am against this change as some people may depend on it. But if we fix the order now fewer applications may depend on it in the future. And this won't be the first case when application has to track and fix random change happening in Zephyr. |
@MarekPieta Please don't do it. The whole thing is the effect of adding stuff that does not belong in board dts. The main justification is what I mentioned in my first post - some people may depend on the CURRENT order. Although I think it is wrong, objectively speaking the order cannot be wrong. It is something that is purely subjective and people may set leds in ways that are more convenient for the application logic to handle them. |
Okay, this was not a best example. But there are others, like nrf52840_mdk or lpcxpresso11u68. Why not use aliases for this, like it is for PWM LEDs? |
@anangl Adding aliases is not a fix. If somebody else comes in few months and says that the order is not matching app yet again will we add another set of aliases? This will only make dts a bigger mess. |
Is it the discussion about an unique LED ID? See also #21578 (comment) |
Hi @jfischer-no , it seems we simply have some time to spent on chatting :) I think we have enough problems without id mentioned in the discussion. I don't like board dts being messed with things that are application dependent. But that's life - some configurations will simply not fit all cases. In my opinion this should close within 5 minutes as discussion it any longer is waste of time. Zephyr should either keep the old order or take new one. Either choice will make some people unhappy and force them to change dts in application's overlay. Hi @anangl , are you happy with this change or should we scrap it? |
I'm still not convinced it's worth applying. That's why I haven't added my approval. But I won't insist on discarding it either. Since others accept it, that's fine with me. |
Change updates gpio-leds DTS binding. The colors should be defined in RGB order.