Hi Kurt, On Sun, Jan 5, 2025, at 11:45 PM, Kurt Borja wrote: > Hello, > > Some drivers may need to dynamically modify their selected `choices`. > Such is the case of the acer-wmi driver, which implemented their own > profile cycling method, because users expect different profiles to be > available whether the laptop is on AC or not [1]. > > These series would allow acer-wmi to simplify this custom cycling method > to use platform_profile_cycle(), as it's already being proposed in these > series [2]; without changing expected behaviors, by refreshing their > selected choices on AC connect/disconnect events, which would also solve > this discussion [3]. > > Additionally, I think the platform_profile_ops approach would enable us > to hide the platform_profile_handler in the future, and instead just pass > the class device to get/set methods like the HWMON subsystem does. > > I think having this kind of flexibility is valuable. Let me know what you > think! > I personally would love to see how this would be used for the acer issue highlighted to see how it would work out. It feels like the series is short a patch :) As a side note, I did (many moons ago) propose a change to alter profiles used depending on AC/battery mode (in the thinkpad driver), and it was rejected as something that should be done in user space. Your use case does seem somewhat different, but it's similar enough that if you get it working I'd be interested to see if I can take advantage of the approach too. Mark
