Thomas Weißschuh

Please try https://git.sr.ht/~t-8ch/linux/log/b4/cros_ec-charge-control It should only show the `charge_behaviour` sysfs file. Can your device do force discharge?

> This is my first time using custom kernel packages so it may take a while for me to figure it out. Good luck! Note: I have some other drivers...

All your guesses are correct. The keyboard backlight is probably already probed through ACPI.

I pushed it now to the same repo, branch `b4/cros_ec-kbd-led-framework`. Could you first test the tag `sent/20240505-cros_ec-kbd-led-framework-7e2e831bc79c-v2` instead? With it you may see the following warning in dmesg: ``` Led...

Thanks for your tests! It would be great to get some Tested-by tags for them on LKML. If you give me an email address I'll add you to Cc for...

FYI I wrote a generic ChromeOS EC charge control driver [0] While it won't probe by default on Framework (because the upstream CrOS EC commands are overridden by their downstream...

The driver will (most likely) be called `cros_charge-control`. It supports start/stop thresholds and `charge_behaviour` through the standard sysfs attributes. On older hardware it only supports `charge_behaviour` but no thresholds. AFAIK...

If the cros_charge_ctl module is used, should the TLP functionality still be called "framework"? > Really? No way TLP will implement that :-D. Not saying that it's reasonable, only possible.

@BurntSushi I didn't test it but the changelog of Graphviz says, it is now compatible to 7.10.* http://projects.haskell.org/graphviz/changelog.html

FWIW I'm using a normal sofle choc with RP2040. The only thing needed was `CONVERT_TO = kb2040` in QMK `rules.mk`