23 Jul, 2014
7 commits
-
Support for Initiator and Target mode with ISO18092 commands support:
- ATR_REQ/ATR_RES
- PSL_REQ/PSL_RES
- DEP_REQ/DEP_RESWork based on net/nfc/digital_dep.c.
st21nfca is using:
- Gate reader F for P2P in initiator mode.
- Gate card F for P2P in target mode.Felica tag and p2p are differentiated with NFCID2.
When starting with 01FE it is acting in p2p mode.On complete_target_discovered on ST21NFCA_RF_READER_F_GATE
supported_protocols is set to NFC_PROTO_NFC_DEP_MASK
for P2P.Tested against: Nexus S, Galaxy S2, Galaxy S3, Galaxy S3 Mini,
Nexus 4 & Nexus 5.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Send DM_DISCONNECT command to disconnect Terminal Host from the HCI network.
- The persistent states of the terminal host pipes, including registry values,
are not modifies. Therefore, there is no NVRAM update to disconnect the
terminal host.
- The terminal host RF card gates are disabled which means that there will be no event
related to card RF gates until communication has been restored.
- The terminal host RF reader request is reset so the RF reader polling for terminal
host is disabled.To restore the communication, the terminal host can send any HCI command or event.
Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
A DEP_RES with a SUPERVISOR PDU can be up to 16 bytes long.
In order to avoid useless read during p2p, extend first read
sequence to 16 and reduce third sequence to 12 to keep same
total on the full sequence.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
A start of frame is 7E 00 not only 7E. Make sure the first read sequence is
starting with 7E 00.
For example: 7E FF FF FF FF is as a correct crc but it is a bad frame.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
In case no data are retrieve through i2c or one specific case is not handled.
Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Add driver for STMicroelectronics ST21NFCB NFC controller.
ST21NFCB is using NCI protocol and a proprietary low level transport
protocol called NDLC used on top.NDLC:
The protocol defines 2 types of frame:
- One type carrying NCI data (referred as DATAFRAME frames).
- One type carrying protocol information used for flow control and error
control mechanisms (referred as SUPERVISOR frames).After each frame transmission to the NFC controller, the device host
SHALL waitfor an ACK (SUPERVISOR frame) reception before sending a
new frame.
The NFC controller MAY send a frame at anytime to the device host.
The NFC controller MAY send a specific WAIT supervisor frame to indicate
to device host that a NCI data packet has been received but that it could
take significant time before the NFC controller sends an ACK and thus
allows next data reception.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz
26 May, 2014
2 commits
-
Add support for the Felica protocol and Type 3 tags.
Both 212 and 424 kbps are supported.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
This patch adds support for ISO-DEP protocol over NFC-B rf technology
by adding NFC_PROTO_ISO14443_B to the supported protocols and an entry
for framing configuration.Signed-off-by: Thierry Escande
Signed-off-by: Samuel Ortiz
20 May, 2014
3 commits
-
Add support for ISO/IEC 15693 RF technology and Type 5 tags.
ISO15963 is using proprietary gate 12.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
In case anybody uses previous patchset with the CLF, add a check to make sure
missing pipe are created.
st21nfca returns its pipe list in the creation order (most recent latest).Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Add functions to recover hardware resources from the device-tree
when not provided by the platform data.Based on pn544 devicetree implementation
Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz
05 May, 2014
6 commits
-
When a bad frame is detected for a bad crc.
We were reallocating and loosing the previous frame pointer.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Stabilize communication by using a mutex.
This avoids running a write transaction during a read retry or a read
transaction during a write retry.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
A frame starts with ST21NFCA_SOF_EOF(0x7e) + 0x00.
A frame ends with ST21NFCA_SOF_EOF(0x7e).
It is possible that the i2c macrocell is stopped for other
communication interfaces with highest priority(RF or SWP).
This can be seen with some 0xFF data at the end of a received shdlc buffer.
If this happen we need to discard the frame because the CLF will repeat it.In order to push accurate data to hci layer, we add the following fix:
- Instead of looking for the first 0x7e in the frame, check that the last
received byte is 0x7e.
- Check that the first frame reception block start with start of
frame(0x7e 0x00). If not, clear the buffer.
- Check that the next frame reception block do not start with start of
frame(0x7e). If so, clear the buffer.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
There is no byte stuffing when data are stored in skb.
TAILROOM is 2 byte crc + 1 byte eof.st21nfca_hci_remove_len_crc was doing an incorrect operation on
the TAILROOM data.
If shdlc timer T2 is triggered, it will request to send the same data.
Before every hci data was lost after st21nfca_hci_remove_len_crc.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Byte stuffing was not correctly removed after a i2c read operation.
This was causing improper crc calculation when byte stuffing was
applied to more than 1 byte.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Remove unneeded includes from i2c.c
Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz
22 Apr, 2014
22 commits
-
Change in st21nfca_hci_platform_init in order to handle in a better way the
internal reboot command.
Once the reboot is completed, the driver expect to receive a 0x7e filled
buffer.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Remove struct st21nfca_i2c_phy* as this parameter can be retrieve
through i2c_get_clientdata(client)Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
st21nfca_hci_probe return 0 in case of successful call and a different
value in any other cases.There is no need to check for st21nfca_hci_probe return as this will be
checked after st21nfca_hci_i2c_probe is completed.Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
wait_tab variable is already global and may create conflicts.
Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Fix "warning: array subscript is above array bounds" in load_session
Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Fixing "sparse: cast to restricted __be16" message when building with
make C=1 CF=-D__CHECK_ENDIAN__Signed-off-by: Christophe Ricard
Signed-off-by: Samuel Ortiz -
Fixes a null pointer exception occurring when the IRQ request in
pn544_hci_i2c_probe fails and no platform data is available.Signed-off-by: Clément Perrochaud
Signed-off-by: Samuel Ortiz -
Now that the NFC digital layer has support for the ISO/IEC 14443-B
protocol and type 4B tags, add the corresponding support to the
trf7970a driver.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
The trf7970a driver currently uses a fixed autosuspend delay of 30 seconds.
To enable users to customize the delay as they see fit, add support for the
new 'autosuspend-delay' DTS property (part of the nfc node) which can
override the default 30 seconds.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
trf7970a_switch_rf_on() no longer returns anything other than 0 so make
it void and clean up the code that checks for errors when its called.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
Add pm_runtime support by moving the code that enables the trf7970a to
the pm_runtime hook routines. The pm_runtime 'autosuspend' feature is
used so that the device isn't disabled until at least 30 seconds have
passed since trf7970a_switch_rf_off() was last called.The result is that when trf7970a_switch_rf_on() is called, the device
will be enabled and initialized (if it isn't already). When
trf7970a_switch_rf_off() is called, it will turn off the RF immediately
but leave the device enabled for at least 30 seconds.
If 30 seconds have passed and the pm_runtime facility decides to suspend
the driver, the device will be disabled then.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
The NFC digital layer calls the 'switch_rf' hook to turn the RF on before
it configures the RF technology and framing. There is potential to confuse
a tag doing it this way so don't enable the RF until the RF technology and
initial framing have been configured.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
Currently, the trf7970a driver assumes that the Vin voltage is 5V when
it writes to the 'Chip Status Control' register. That may not be correct
so use the regulator facility to get the Vin voltage and set the VRS5_3
bit correctly when writing to that register.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
Currently the driver writes the same value to the 'Modulator and SYS_CLK
Control' register no matter what RF technology is being used. That works
for now but new RF technologies (e.g., ISO/IEC 14443-B) will require
different values to be written to that register. To support this, add a
member to the trf7970a structure which is set by the RF technology handling
code and used by the framing code when it writes to that register.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
Writing to the 'ISO Control' register may cause the contents of the
'Modulator and SYS_CLK Control' register to change so be sure to write
to 'Modulator and SYS_CLK Control' after writing to 'ISO Control'.Note that writing to the 'Modulator and SYS_CLK Control' register
shouldn't be necessary at all according to the trf790a manual but testing
shows that it is necessary.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
The current code always writes to the 'ISO Control' register when the
RF framing is set. That's not necessary since the register's value
doesn't always change. Instead, only write to it when its value is
actually being changed.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
Sometimes after sending a frame there is tx data leftover in the FIFO
which the driver will think is part of the receive frame. That data can
be cleared when an 'End of TX' interrupt is received by issuing the
'FIFO Reset' command.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
Due to a trf7970a erratum, the 'NFC Target Detection Level' register
(0x18) must be cleared after power-up.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
Only initiate the abort command process when there is an active command.
If the abort process were started and there wasn't an active command
then the next command issued by the digital layer would be incorrectly
aborted.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
After further testing periods of ~16 ms have been observed
between interrupts indicating that there is receive data in
the FIFO. To accomodate that, increase the time the driver
waits before deciding there is no more data to receive to
20 ms. The macro that represents that delay is
'TRF7970A_WAIT_FOR_RX_DATA_TIMEOUT'.Signed-off-by: Mark A. Greer
Signed-off-by: Samuel Ortiz -
Add functions to recover hardware resources from the device-tree when not
provided by the platform data.Signed-off-by: Clément Perrochaud
Signed-off-by: Samuel Ortiz
