Skip to content

FW 13 AMD 7040 series (Lotus Azalea): Power Button RGB Control #101

Open

Description

@0x3C50

Hi!

I've recently taken a look at https://github.com/FrameworkComputer/Framework-Laptop-13/tree/main/Fingerprint%20Reader, the documentation for the fingerprint reader module, and discovered that there are 2 more color pins: FPR_LED_G and FPR_LED_R. According to https://github.com/FrameworkComputer/Framework-Laptop-13/blob/main/Mainboard/Mainboard_Interfaces_Schematic_7040_Series.pdf, those pins are wired into the board as the W pin is, so it should be possible to control them from the EC. However, looking at the current implementation for the 7040 series firmware, this doesn't seem to be implemented anywhere.

https://github.com/FrameworkComputer/EmbeddedController/blob/fwk-lotus-azalea-19573/zephyr/program/framework/lotus/led_pins.dtsi:

power_led: power-led {
                        led-id = "EC_LED_ID_POWER_LED";
                        led-pwms = <&pwm_power_w>;

                        color_power_off: color-power-off {
                                led-color = "LED_OFF";
                                led-values = <0>;
                        };

                        color_power_white: color-power-white {
                                led-color = "LED_WHITE";
                                br-color = "EC_LED_COLOR_WHITE";
                                led-values = <55>;
                        };
                };

Only the white pin is set up for zephyr, the other 2 are not mentioned anywhere. The EC itself also only talks to this pin.

Would it be possible to add the other 2 pins into the firmware as well, just exposing them to the EC command bus? I think this would allow for a great deal of tinkering with the power button, for example changing the color when the battery is low or some error occurred.

Thanks!

Activity

  1. DHowett commented on Nov 9, 2026

    @DHowett

    Alas, no. The fingerprint module only supported the red, green and amber LEDs when it first came out.

    It has been simplified since then, and as far as anybody can determine those traces are not connected to either the EC or the fingerprint module.

    If you have an old 11th gen machine, you will be able to get colors out of it. Nothing newer though.

  2. marlenemeows commented on Nov 9, 2026

    @marlenemeows

    Adding to this; this seems to be implemented on the Intel side of things:

    [PWM_LED2] = {
    /* Power Button LEDs */
    .ch0 = PWM_CH_FPR_LED_RED,
    .ch1 = PWM_CH_FPR_LED_GREEN,
    .ch2 = PWM_CH_FPR_LED_BLUE,
    .enable = &pwm_enable,
    .set_duty = &pwm_set_duty,
    },

    This has been used for pretty neat things by the community in the past and I would also love if this was supported on the AMD variants as well.
    I unfortunately don't know anything about embedded and/or hardware development, and am scared of bricking my laptop, else I'd try to implement this myself.

  3. marlenemeows commented on Nov 9, 2026

    @marlenemeows

    @DHowett aw, just saw your comment right after posting mine. That sucks, especially considering how neat this would be. Board schematics do suggest that the EC is still connected to the traces, but I'm not an expert, nor do I have access to the full schematics, so I can't really tell.
    Would be neat to at least get feedback from Framework at least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions