nfc_initiator_poll_targets() could have more human understandable arguments

[GoogleCodeExporter]

IMHO, even it works, we could provide easier API to poll targets:

i.e: these parameters are not easy to understand
btPollNr: specifies the number of polling 
btPeriod: indicates the polling period in units of 150 ms

Original issue reported on code.google.com by romu...@libnfc.org on 6 Mar 2011 at 1:08

[GoogleCodeExporter]

r1161 simplifies the polling we don't need a nfc_target_t array but a simple 
pointer.

Original comment by romu...@libnfc.org on 3 Oct 2011 at 2:52

[GoogleCodeExporter]

In my opinion, we could provide a function that only need a period (in ms or 
timeval struct) during the polling function will act.
We can compute the number of polling with the period.

We can also provide a second function that allow to set more precisely theses 
parameters (nfc_poll_target_ext() ) or create some options to set the way we 
compute the thing :)

What do you think about that ?

Original comment by romu...@libnfc.org on 17 Oct 2011 at 5:17

[GoogleCodeExporter]

Good idea IMHO.
Tuning the parameters of the polling itself is not that important in 99% of 
cases.
At least this would provide a common denominator between native polling of 
PN532 and sw polling of the other chips.

Original comment by yob...@gmail.com on 18 Oct 2011 at 7:12