Lines Matching +full:introspection +full:- +full:subsystem
4 <!--
32 -->
34 <article class="markdown-body">
62 <!--Fixme why are pandoc auto references not working ? -->
107 - historically the PF reference implementation was used to abstract hardware
108 - the subsystem term would arguably fit best is already used.
110 (FIXME: choose "subsystem" instead of "hardware" ?)
156 - memory layout
157 - value constrains
161 - pretty display parameter values (not just a as an array of bits)
162 - check for user error when setting it (out of bound, invalid...)
163 - offer a type safe API
290 - scales the user value to the hardware value (client => syncer)
291 - converts the hardware value to the user's value space. (syncer => client)
302 <note>For example a hardware integer parameter could have a range 64-128 but it might
303 be necessary for upper layer to access in a range 0-100.</note>\
310 <note>For example a Q2,2 (see [fix-point-parameter]) when setting 1
326 - Affine adaptation: `affAd(value) = slope * value + offset` where slope and
327 offset and user-defined constants
330 - Logarithm adaptation: `logAd(base, value) = ln(value) / ln(base)` where
331 `ln` is the natural logarithm and base is a user-defined constant.
409 ## Parameter introspection
410 The syncer API **SHOULD** allow introspection of the mapped parameters.
417 - This formation is object oriented. Requirements should not require any programing paradigm.
418 - Is this section about syncer creation and builders too close to implementation ?
434 - Is this syncer library concept not a definition ? Ie a syncer builder set.
435 - The concept is needed by other requirement but it does not stand by itself.
436 - Why is there a requirement of "same hardware" ?
463 Such syncer plugins **SHOULD** have an unique entry point that -- when called --
487 - Plugins
488 - association builder <-> parameters
502 <why>To allow introspection of the hardware.</why>
506 <why>The user may want to group the synchronization of multiple parameters --
507 for instance if a syncer contains more than 1 parameter -- in order to avoid
511 Syncers **MAY** report an 'out-of-sync' condition indicating that the hardware
514 <why>This can happen when the underlying hardware subsystem
518 When a syncer reports an out-of-sync condition, the PF **MUST** try to resync
554 - 1 value: (A) or (B) or (C); or
555 - 2 values: (A,B) or (A,C) or (B,C); or
556 - 3 values: (A,B,C).
583 configuration in a domain -- see below.</why>
600 - rules on start\
601 - state changes
607 state set (`Input -> states == identity`)
616 `"ab" -> ["", "a", "b", "ab"]`</note>
618 <note>An empty value set is allowed as its combination -- a set containing the
619 empty set -- would not be empty. The empty set would be the only possible
660 - from `Tx = "on" and Rx = "on"` (state 1) \
661 - to `Tx = "off" and Rx = "off"` (state 2) \
662 <!-- FIXME: why are list closing the why block ? -->
701 - ask to the client/user
702 - having configuration predicate mutual exclusive
703 - choose randomly
704 - group configuration applicable on the same in a priority ordered set
767 - parameters tree
768 - configurations:
769 - selection rule
770 - parameter/value couples
771 - domain:
772 - list of associated configurations
773 - order of priority
811 This is kind of like the bash -x feature.
814 # Introspection chapter
816 In order to debug the user configuration, allow introspection of PF data at runtime.
826 - listing \
831 - getting their properties. Including:\
838 - printing parameter value in decimal
840 - pretty print parameter tree (such as the Unix tree command for files)
895 To address this need, a fast modify-update-test cycle should be possible.
902 <why>To enable a fast modify-update-test cycle during tuning.
904 - recompile \
905 - restart the host process/service
912 - exposed in the PF API
913 - changing a config file and sending a signal to the PF
914 - providing a IPC
915 - directly modifying the memory
943 <note>This requirement is fulfilled by remote-processor and remote-command on the reference impleme…
945 ## Introspection & tunning
946 This command line interface **SHOULD** support all tuning and introspection ability.
978 - hardware description
979 - settings
997 - Linux (and Android)
998 - Windows
999 - Mac OSX
1058 - cross platform support of multi-threading
1059 - remove dependency to pthread
1060 - reduce the gap with the "next" branch
1073 choose a built-in that may not match what he wants.
1089 <why>To enable a fast modify-update-test cycle on PF configuration.</why>
1102 Framework but only used as a passthrough to the underlying subsystem (think
1104 subsystem differs from the one the Parameter Framework is running on, an