Modify

Opened 12 years ago

Closed 9 years ago

#104 closed enhancement (fixed)

Extension of pcilib register API

Reported by: Suren A. Chilingaryan Owned by: Suren A. Chilingaryan
Priority: minor Milestone:
Component: pcilib Version:
Keywords: Cc: Suren A. Chilingaryan, Matthias Vogelgesang

Description

We need some extension of pcitool API to provide more information about registers:

  • ticket #67 requires min/max fields in the pcilib_register_description_t: There is already a default value field. However, it would be extremely helpful to have minimum and maximum possible values (this is possible with GParamSpec) for each register (AFAICT the CMOSIS spec provides them).
  • ticket #77 requires enums describing device statuses.

As matter of fact we probably should introduce two types of registers (more?): range and enums. First should include min & max values (function transcoding the value in standard units?), second the string names of all possible values.
Also we may provide a get_status function for event engine. Cons: doing it in scripts is more flexible. Pros: from application it is easier to call library function than external script.

Attachments (0)

Change History (1)

comment:1 Changed 9 years ago by Suren A. Chilingaryan

Resolution: fixed
Status: newclosed

Since r320 the public-API functions pcilib_get_register_info and pcilib_get_register_list provide information on ranges and names if specified in XML.

The status can be provided using new property API and programmed using Python scripts (currently only one-liners are supported, but will be extended in future).

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Suren A. Chilingaryan.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.