CDP1020 Ver la hoja de datos (PDF) - Intersil
Número de pieza
componentes Descripción
Lista de partido
CDP1020 Datasheet PDF : 23 Pages
| |||
CDP1020
CURRENT STATE
Bay Empty
(device is present)
Bay Empty
(device is present)
Bay Empty
(device is present)
TABLE 3. SOFTWARE ACTION BAY STATE TRANSITION TABLE
NEXT STATE
SOFTWARE ACTION
NOTES
Device Inserted
001b -> BAY_STREQ
This transition request could be the result of a device
currently in the bay with DEVSTSCHG_EN cleared (as
such the CDP1020 hardware could not transition to the
bay state).
Device Enabled
010b -> BAY_STREQ
This transition request is a result of a device that has been
properly enumerated and enabled on its native bus(es). In
all likelihood the DEVSTSCHG_EN bit was cleared so
CDP1020 hardware could not first transition the bay state
to Device Inserted.
Removal Requested 011b -> BAY_STREQ
Unexpected OS behavior.
Bay Empty
(device is present)
Device Inserted
Device Inserted
Device Inserted
Device Enabled
Device Enabled
Device Enabled
Removal Requested
Removal Requested
Device Removal
Allowed
Device Enabled
100b -> BAY_STREQ
010b -> BAY_STREQ
Removal Requested 011b -> BAY_STREQ
Device Removal
Allowed
100b -> BAY_STREQ
Device Inserted
Removal Requested
Device Removal
Allowed
Device Inserted
Device Enabled
001b -> BAY_STREQ
011b -> BAY_STREQ
100b -> BAY_STREQ
001b -> BAY_STREQ
010b -> BAY_STREQ
Removal Requested
Device Removal
Allowed
Device Removal
Allowed
Device Inserted
100b -> BAY_STREQ
001b -> BAY_STREQ
Device Removal
Allowed
Device Enabled
010b -> BAY_STREQ
Device Removal
Allowed
Removal Requested 011b -> BAY_STREQ
Unexpected OS behavior.
Device properly enumerated and enabled on its native
bus(es).
Unexpected user behavior. User requested device
removal through the UI before the device was enabled.
OS could not enable the device. This could be a result of
the OS’s failure to properly enumerate the device, lack of
sufficient operational power, etc.
Unexpected OS behavior.
User request device removal through the UI.
Unexpected OS behavior.
Unexpected OS behavior.
OS decided that device removal was not allowed. This
could be the result of an active application disallowing the
removal. Alternatively, the user could have cancelled the
removal request through the UI.
OS has completed the device removal sequence.
User has requested to “re-use” the device through the UI.
This state transition eliminates the need for the user to
remove the device and then immediately re-insert it. This
could be especially useful in the presence of an engaged
physical security lock. This bay state transition might be
used in order to provide user feedback (via the bay status
indicator) while OS is performing steps necessary to re-
enable the device.
User has requested to “re-use” the device through the UI.
This state transition eliminates the need for the user to
remove the device and immediately re-insert it. This could
be especially useful in the presence of an engaged
physical security lock. This state transition indicates that
the device has been properly re-enumerated and re-
enabled on its native bus(es).
Unexpected OS behavior.
2-436
Share Link: 