Data-Range Properties
Data ranges are used not only for data intersection, but can be accessed as device properties as well (see Pin Data-Range and Intersection Properties). For this reason, an adapter driver whose data-intersection handler takes care of all format negotiations on its pins should still include a complete set of data ranges. The data ranges should reflect as closely as possible the data-format preferences that are embodied in the adapter's data-intersection handler.
A pin's data ranges can be accessed through the following properties:
KSPROPERTY_PIN_CONSTRAINEDDATARANGES
These two properties designate the pin's static data ranges and constrained data ranges, respectively.
Constrained data ranges provide more accurate information about the current capabilities of a device because they are dynamically updated to account for any on-board resources that have already been allocated for other purposes. By comparison, static data ranges might inaccurately report hardware capabilities that depend on resources that are no longer available.
In the current PortCls implementation, the default data-intersection handlers in the port drivers use only an adapter's static data ranges.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for