On Fri, Jul 22, 2022 at 12:12:05PM +0200, jerome Neanne wrote: > On 19/07/2022 15:32, Mark Brown wrote: > > On Tue, Jul 19, 2022 at 11:17:36AM +0200, Jerome Neanne wrote: > Refactoring the code with regulator_notifier_call_chain, I realized that > some of the events in TPS65219 are not listed as standard REGULATOR_EVENT in > consumer.h > > This is the case for below event list: > REGULATOR_EVENT_SCG (ShortCut to Gnd) > > REGULATOR_EVENT_RV (Residual Voltage) > > REGULATOR_EVENT_RV_SD (Residual Voltage ShutDown) > > Should I add those events to the list of standard regulator events and > assign a code? (if yes, any rule for the values?) > Would it fit with some other predefined standard macro defined elsewhere? > (if yes, could you point me to the right location?) Map them onto the existing values, the exact mapping will depend on what those events mean, force disable or out of regulation look like likely candidates for example. If there's anything that's just not covered then perhaps a new event type is needed. Please delete unneeded context from mails when replying. Doing this makes it much easier to find your reply in the message, helping ensure it won't be missed by people scrolling through the irrelevant quoted material.
Attachment:
signature.asc
Description: PGP signature
