This is probably also a good way to document the more complex operations 😅. I personally have difficulty using the "API" as it's mostly implicitly implementation-defined. Would be awesome to specify it in a structured way, and pick tests according to that.

from svdtools.

I am specifying the structure of the yaml files here. Of course is a work in progress.

This is probably also a good way to document the more complex operations.

Yes, this could solve also #5

I personally have difficulty using the "API" as it's mostly implicitly implementation-defined. Would be awesome to specify it in a structured way, and pick tests according to that.

Yes, if somebody who has experience with this tool does it it would be awesome.
Maybe here we can define a general structure for each of the patch commands.

For example something like this could be created for each patch command:

include

_include let you specify other yaml file that will be merged with this one.
_include can be only specified at the root of the yaml file or at the peripheral level.

PERIPH:
  _include:
    - path/to/peripheral_patch.yaml

_include:
  - path/to/other_patch.yaml

Example

See first post for an example.

from svdtools.