xiaoxiang781216 commented on pull request #4508: URL: https://github.com/apache/incubator-nuttx/pull/4508#issuecomment-917661701
> > since the reset cause is very important information, should we standardize all possible cause and require SoC convert the private definition to the standard one? > > We can have a subset of the rest causes that are common, but we'll still have a few that are specific to a particular SoC. How would we handle that? I guess we can do something as easy as considering the values above the common set max to be chip specific. > Yes, we can define the common cause, and reserve a range for SoC specific cause, just like IOCTL. > As for the best way to get this info, I personally don't know which one is best between procfs and boardctl, they actually both tend to go beyond their scope (see #1132 for instance.) > We already use broadctl for stuff like uniqueid and actually reseting the board, the reset cause seems to be similar to these, is there any reason to use procfs here? procfs is good for the interactive usage, but hard to parse/use by the tool and also increase the noticeable size for tiny device. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
