| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Support for chaining is added based on maximum length supported by and passed in ATS
by peer and maximum length supported by the device.
Change-Id: I8f9f8468ff8ac9d3579bc8b6afbe3e2072e56de8
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a NFCIP frame is received (NXP_EVT_NFC_RCV_DATA event) before a call to
phHal4Nfc_Receive() function, the frame was lost. This could happen if the local
host acts as a Target and the remote peer sends its first frame too fast.
The data is actually saved in a temporary buffer but, when the phHal4Nfc_Receive()
is eventualy called, it triggers a callback with a status code
NFCSTATUS_MORE_INFORMATION, which is handled as an error.
This patch fixes this behaviour and makes sure that the correct status
code is provided with the frame itself.
Change-Id: I5311762ca70c71f98dea0287b0844eb1c8dddb6b
|
| |
|
|
|
|
|
|
| |
When disconnecting while an internal transceive was ongoing,
the HAL context was corrupted. This has been fixed by adding a
dedicated context for the disconnect operation.
Change-Id: I279474f29164b3ab7d40cdd0e9b8f71f842774b0
|
|
|
Source: Trusted_NFC_Device_Host_AA03.01e02_google.zip code drop (23-Sep-2010)
Change-Id: Ie47f18423f949a8d3e0815d13f55c814312add24
Signed-off-by: Nick Pelly <npelly@google.com>
|
