Lines Matching refs:or

36   warm or bus resets) which may keep certain parts untouched.
65   FPC, timer and control registers. It does not touch gprs, fprs or acrs.
82 For now migration of a device or bus in reset is not supported. Care must be
98 Device or Bus into an Object and pass the cold reset type. When possible
126    on other objects, such as raising or lowering a qemu_irq line or reading or
140 ``resettable_assert_reset()`` or ``resettable_reset()``, they are not
147 during either 'enter' or 'hold' phases. IOMMUs are expected to reset during
157 who want to implement or convert a class which has the resettable interface;
158 for example when specializing an existing device or bus.
163 Three methods should be defined or left empty. Each method corresponds to a
249 either its children or its own enter method is called) to the *exit*
263 *hold* or *exit* phase of another object in the same reset group.
274 DeviceClass or BusClass, or maintaining the existing code in those classes. Most
308 provides ``resettable_change_parent()``. This function allows to set, update or
314 a reset operation it must be used only in *hold* phase. Using it in *enter* or
317 do so: the function is a no-op as long as old and new parent are NULL or not
324 2. *hot bus change*; it means an existing live device is added, moved or
362    anything that directly inherits from ``TYPE_OBJECT`` or ``TYPE_DEVICE``
363    rather than from ``TYPE_SYS_BUS_DEVICE`` or some other plugs-into-a-bus
366    or ``qemu_register_reset()``).