Takaya Saeki 69c8d8093d devices: vvu: fix incorrect VVU PCI feature bits initialization ... At present the VVU PCI driver writes the feature bits it wants to enable to the device feature bits first, and then reads the device feature bits in the initialization sequence. However, the correct sequence is reading the device feature bits first, and writing the feature bits to enable to the driver feature bits next. This incorrect initialization sequence causes warning messages when you run the VVU driver. Fix the driver so that it follows the correct feature bits initialization sequence. BUG=b:216752120 TEST=VVU block device works with no warning message. TEST=presubmit --quick Change-Id: I7f7536143ee2a037fd71aa216513ad732b407cc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3705077 Commit-Queue: Takaya Saeki <takayas@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>		2022-06-14 17:22:35 +00:00
..
src	devices: vvu: fix incorrect VVU PCI feature bits initialization	2022-06-14 17:22:35 +00:00
Cargo.toml	crosvm: move run command to argh	2022-06-13 23:55:20 +00:00