Nicolas Munnich
Nicolas Munnich
> > interrupt > > "Only one key to be pressed" does not mean "only the most recent key to be pressed". It could also mean that the first key...
> > My suggestion here would be to use "interrupt" in the name of the behaviour, and call this property `invert`. > > The name of the behavior is 'interrupt'....
> > good keywords to describe the result, but not as good keywords to describe what is happening to cause that result. > > > Here's my new suggestion: Call...
You have a point about `no-resume`. Regarding the general name I'd still prefer a different one (not necessarily one of the ones I suggested), but I'll step aside for others...
Just had a thought that perhaps it would make sense to take inspiration from `quick-tap-ms` and delete the `no-resume` property, instead setting `resume-capacity` to `-1` prevents resuming?
That would probably be a better approach entirely - somehow the possibility of using the usb connection completely slipped in my mind.
Personally I'd say your suggested function should be how it behaves, I don't see the reason why you would want to have the option to *not* sync sleep timers.
@ice9js would it be possible for you to try and upstream the drivers for those chips to Zephyr? That would be the ideal end result, and definitely beats having them...
I recall someone requesting a &sleep behaviour in addition to &soft_off, to use &sleep for power conserving and &soft_off for transportation. For that reason I would say that it's not...
Thanks for the PR! The interconnects can be found in multiple locations, having hardware metadata be another one seems like a good addition to me. I don't think plaintext is...