depau/libfprint
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

uru4000: Fix typos in comments

Browse source
This commit is contained in:
Bastien Nocera 2018-09-26 15:21:01 +02:00
parent 44c3f4f772
commit d09cb88e9a
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
libfprint/drivers/uru4000.c
View file

@ -295,7 +295,7 @@ static int read_regs(struct fp_img_dev *dev, uint16_t first_reg,
* *
* BIT 1: IRQ PENDING * BIT 1: IRQ PENDING
* Just had a brainwave. This bit is set when the device is trying to deliver * Just had a brainwave. This bit is set when the device is trying to deliver
* and interrupt to the host. Maybe? * an interrupt to the host. Maybe?
*/ */
static void response_cb(struct fp_img_dev *dev, int status, void *user_data) static void response_cb(struct fp_img_dev *dev, int status, void *user_data)
@ -847,7 +847,7 @@ static void imaging_complete(fpi_ssm *ssm, struct fp_dev *_dev, void *user_data)
* confused state and returns hwstat 0x85. On next app run, we don't get the * confused state and returns hwstat 0x85. On next app run, we don't get the
* 56aa interrupt. This is the best way I've found to fix it: mess around * 56aa interrupt. This is the best way I've found to fix it: mess around
* with hwstat until it starts returning more recognisable values. This * with hwstat until it starts returning more recognisable values. This
* doesn't happen on my other devices: uru4000, uru4000b, ms fp rdr v2 * doesn't happen on my other devices: uru4000, uru4000b, ms fp rdr v2
* *
* The windows driver copes with this OK, but then again it uploads firmware * The windows driver copes with this OK, but then again it uploads firmware
* right after reading the 0x85 hwstat, allowing some time to pass before it * right after reading the 0x85 hwstat, allowing some time to pass before it
@ -909,10 +909,10 @@ static void rebootpwr_run_state(fpi_ssm *ssm, struct fp_dev *_dev, void *user_da
} }
} }
/* After messing with the device firmware in it's low-power state, we have to /* After messing with the device firmware in its low-power state, we have to
* power it back up and wait for interrupt notification. It's not quite as easy * power it back up and wait for interrupt notification. It's not quite as easy
* as that: the combination of both modifying firmware *and* doing C-R auth on * as that: the combination of both modifying firmware *and* doing C-R auth on
* my ms fp v2 device causes us not to get to get the 56aa interrupt and * my ms fp v2 device causes us not to get the 56aa interrupt and
* for the hwstat write not to take effect. We have to loop a few times, * for the hwstat write not to take effect. We have to loop a few times,
* authenticating each time, until the device wakes up. * authenticating each time, until the device wakes up.
* *