| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
DSAP and SSAP were switched on with the other at multiple location
in the code. This patch fix those.
Change-Id: Iea8e499049a2cd4a234155a3044b875eb9c6ca7a
|
|\ \
| |/
|/|
| | |
* commit '700428d8f73604f27f4416fd14d3ef1cb86fca9e':
|
| |\
| | |
| | |
| | | |
* commit '8c56cd9e0bc2808d73e6596ba3bb128cc2fbcd7c':
|
| | |\
| | | |
| | | |
| | | | |
Change-Id: Iee6e204b8a44a1efb75dea184cc1a69baac91f06
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This enables the server to avoid losing packets, especially when
receiving them in an aggregated packet. The size of the buffer is
determined by the size of the working buffer provided by the application.
Change-Id: Ia3c72e19fdb74e2a43390af5607c497c2275fe46
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If phLibNfc_Llcp_Recv() is called in the callback of a previous
phLibNfc_Llcp_Recv(), it could be rejected due to the
bSocketRecvPending flag which was not properly reset.
Change-Id: I6c41469480b50bb7adc9a721ec96f715e5d56a60
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Call the callback only if the context is not null.
Change-Id: I783d9e8ddedb2546eff85837826703db189f9f59
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Interal buffer increased to 2178 = 3 (max LLCP header size)
+ 128 (default MIU)
+ 2047 (max MIU)
Change-Id: I3cc2ff705e74ae657d93b5e50a577b0e7e5ebfcf
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some internal variables used in reveive window checkings were not
reset on socket closure/re-opening. This was leading to have the
send() function waiting forever for remote acknowledgments.
Change-Id: Ic7741b004de80af3f851f620842d46c42f654804
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The V(SA) is an internal variable used in LLCP connection-oriented
data links to check receive window conditions. It corresponds to
the last frame number acknowledged by remote peer + 1.
The patch makes sure this variable is updated evry time it is needed.
Change-Id: Ie5ac925a6f1dfa19b22ac2b6e96659440d5daf21
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Clear out send callback if send was not accepted.
- Set transport busy status for RR/RNR frames.
Change-Id: Idf8986f6b82995644b176247a644e36d2c879ebf
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously, in LLCP v1.0, the only way to use the SDP (Service
Discovery Protocol) service was to send a CONNECT frame containing
the Service Name to the SDP service. This was implicitly
preforming a connection request to the requested service.
LLCP v1.1 introduced a way to discover services more efficiently
and without implicit connection. It also enables connectionless
services to have a service name. It is based on a new protocol
based on a new SNL frame containing discovery requests and
responses.
This update comes with new APIs:
- phLibNfc_Llcp_DiscoverServices() function can be used to discover
remote services. It can take multiple service names and resolve
all of them in a single call.
- Register service name at bind time. Cache LLCP service name/sap pairs.
In LLCP 1.1 specification defines at section 5.9 that any service
lookup answer must be valid for the whole LLCP session duration.
To enforce this, we cache the SAP/SN pairs locally and make sure
that the applications don't break the cache.
The stack remains fully retro-compatible with v1.0 devices.
Change-Id: I052edd3838013cee65e7415d0ed01fc3e9cad36d
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The pending operations were handled at the connection-oriented sockets
level, with no possibility for other transport types to handle
pending operations.
A dispatcher has been added at the generic transport level to
remove this limitation.
This feature is needed to implement LLCP v1.1.
Change-Id: I69e37ba800d1c531396ca97ab0a0480e0f53d63f
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes one of the crashes occuring when turning the screen off
during p2p transfers. One remaining.
Change-Id: I3e45be9b8f4be40350ba4dd9db7e596631206bd1
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When a connectionless socket is closed, Connectionless_Abort()
is called, which in turn calls the send and receive callbacks
to indicate abortion. But since these callbacks are not cleared
out after a previous send/receive has completed, this can lead
to spurious callbacks and consequently memory corruption.
Change-Id: Iea7a34829c4db1cae3b49f33117b25b50205683f
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some parts of the code reset the state to an operation state,
even if the link has already been shutdown. This allowed for a second
deactivation callback, causing a crash higher up in the stack.
Bug: 5765077
Change-Id: I2f2ac720756353d45d82634d27a3dd9acecae43d
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
See https://android-git.corp.google.com/g/#/c/157220
Bug: 5449033
Change-Id: I935ee4450e2e62ced1537bafb787ad402cfcb69c
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
See https://android-git.corp.google.com/g/157065
Bug: 5449033
Change-Id: I05dd3a5e5f671c0fdc17bf4e3d52395ccdb56e45
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
See https://android-git.corp.google.com/g/156016
Bug: 5449033
Change-Id: Ie5dac4fad8942433d2b8fe3c0539e4c3c678a082
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
* commit '593d6d4a79601c530825ce9a52fd3f4cf03e1b6f':
|
| |\ \ \
| | |/ /
| |/| /
| | |/ |
Change-Id: If89fd19c4cd2215ee43c5ef1dbd151c049d940d2
|
|\ \ \
| | |/
| |/|
| | | |
Change-Id: Iaf498cf86a8995a7c51b3b88c3b1acebdf0185b7
|
| |\ \
| | |/
| |/| |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit 'b99be65c277b0cc65a00a33e784ed49461531737':
Use NFC HAL for some libnfc settings.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The NFC HAL in libhardware allows us to store and retrieve
product-specific settings. This patch moves two product-specific
settings to the HAL: the device port, and the usage of the i2c
workaround we had for crespo. This means configuring the port
no longer needs to be done from JNI land.
Change-Id: I2e19b6f188f808bc2f2a1f1abc28f2a6c47e6a4c
|
|\ \ \
| |/ /
|/| /
| |/ |
Change-Id: I1f8bab351bcf7e2e90623aae71c725a123144440
|
| |\
|/ / |
|
| |\ |
|
| | |\ |
|
| | | |\ |
|
| | | | |\ |
|
| | | | | |\ |
|
| | | | | | |\ |
|
| | | | | | | |\ |
|
| | | | | | | | |\ |
|
| | | | | | | | | |\ |
|
| | | | | | | | | | |\ |
|
| | | | | | | | | | | |\ |
|
| | | | | | | | | | | | |\ |
|
| | | | | | | | | | | | | |\ |
|
| | | | | | | | | | | | | | |\ |
|
| | | | | | | | | | | | | | | |\ |
|
| | | | | | | | | | | | | | | | |\ |
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
This reverts commit 294b456a3692cd69f45713bc8e9700132a0e5aec.
@#$% the pn544.
This patch to execute FW download mode with 64 byte frames has some kind of
side-affect. It causes the pn544 to send
> NFC I2C Received buffer: 0xB2 0x83 0x53 0xC9 0x6B
every 2 seconds. We do not yet know what this command means, it is undocumented.
This side affect appear permanent - even after reverting to a 512 byte FW
download, the NFC controller continues to send these messages.
Reverting ASAP to minimize damage.
Change-Id: I139a4a76c045f580df9760dc11d1c6df7b317a50
|
|\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | | |
This provides a path to flush RX, necessary when we enter FW download mode
with bogus data already in RX. This fixes a problem where NFC was dead on several
HSPA and LTE devices.
Also decrease FW timeout completition from 120s to 60s. Typically FW download
takes 30s, and 120 is unnecessarily large and causes a long delay to bring up
NFC when we need to retry FW.
Bug: 5468674
Change-Id: I0fd40c199daac861fe5acda4f2d214bdcff8e869
|
| |/ / / / / / / / / / / / / / / / /
|/| | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
This provides a path to flush RX, necessary when we enter FW download mode
with bogus data already in RX. This fixes a problem where NFC was dead on several
HSPA and LTE devices.
Also decrease FW timeout completition from 120s to 60s. Typically FW download
takes 30s, and 120 is unnecessarily large and causes a long delay to bring up
NFC when we need to retry FW.
Bug: 5468674
Change-Id: I0fd40c199daac861fe5acda4f2d214bdcff8e869
|
|\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / / / / / / / / / /
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | |
MERGE)." into ics-mr0
* commit '17abc6eb45b326f574c657e227670a8fddf9385e':
Remove NFC I2C workaround for Prime (DO NOT MERGE).
|