Open whitslack opened 4 months ago
I got it working by changing the return -EINVAL
in framework_probe(…)
to return -EPROBE_DEFER
so that the kernel will try probing the device again later if it fails initially because the CrOS EC device has not yet been registered. I don't know if this is the Right Way™, but it works for me, although I still get the error message in the kernel log.
I have always been suspicious of the way I hooked up the module dependencies here. I suspect that I should have relied on Chrome MFD's ability to load additional drivers, but I wanted it to work as an external module.
EPROBE_DEFER
seems like an alright solution. Thanks. I'd happily look over a PR for that!
Is it okay for
framework_laptop
to be loading beforecros_ec_lpcs
? (My kernel doesn't support loadable modules, so I integrated yourframework_laptop.c
into my kernel tree indrivers/platform/x86/
.)Maybe there is a missing dependency specification somehow, or maybe I need to enable another piece of CrOS support that you didn't mention in your README? (I initially didn't have
MFD_CROS_EC_DEV
enabled, but I tried enabling it to see if it would solve my issue. It didn't.)