RDKB-62572 : [SKY-VL-QE][Sprint]: LED status is not changing on WAN cable disconnect.#178
Conversation
…able disconnect. Reason for change: This issue is a regression due to RDKB-59763 US changes. Where interface state machine used to start after physical status Up event only but now we have changed the flow where interface state machine starts before Phy up and wait for Up. So LED status behavior also changed accordingly so corrected this behavior now. Signed-off-by: LakshminarayananShenbagaraj <lakshminarayanan.shenbagaraj2@sky.uk>
There was a problem hiding this comment.
Pull request overview
This PR fixes a regression in LED status behavior introduced by RDKB-59763, where the LED status was not updating correctly when a WAN cable is disconnected. The root cause was a change in the interface state machine (ISM) flow, which now starts before the physical link is UP, affecting the LED update logic.
Key Changes:
- Restructured the LED status update logic to prioritize physical link status checks before state machine status
- Added separate handling for when PHY is UP vs DOWN, with appropriate LED state updates for each scenario
- Updated the order of state tracking to reflect PHY state changes first, then state machine state changes
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…able disconnect. Reason for change: This issue is a regression due to RDKB-59763 US changes. Where interface state machine used to start after physical status Up event only but now we have changed the flow where interface state machine starts before Phy up and wait for Up. So LED status behavior also changed accordingly so corrected this behavior now. Signed-off-by: LakshminarayananShenbagaraj <lakshminarayanan.shenbagaraj2@sky.uk>
…able disconnect. Reason for change: This issue is a regression due to RDKB-59763 US changes. Where interface state machine used to start after physical status Up event only but now we have changed the flow where interface state machine starts before Phy up and wait for Up. So LED status behavior also changed accordingly so corrected this behavior now. Signed-off-by: LakshminarayananShenbagaraj <lakshminarayanan.shenbagaraj2@sky.uk>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Pull request overview
This PR fixes a regression in LED status behavior introduced by RDKB-59763, where the LED status was not updating correctly when a WAN cable is disconnected. The root cause was a change in the interface state machine (ISM) flow, which now starts before the physical link is UP, affecting the LED update logic.
Key Changes:
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.