Skip to content
  1. Feb 02, 2015
    • Christophe Ricard's avatar
      NFC: st21nfcb: Add HCI transaction event support · 5d1ceb7f
      Christophe Ricard authored 
      

The transaction notifies the host (DH) that an action
is required to manage a specific Secure Element application.

Signed-off-by: default avatarChristophe Ricard <christophe-h.ricard@st.com>
Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      5d1ceb7f
    • Christophe Ricard's avatar
      NFC: st21nfcb: Add support for secure element · 8ae01f79
      Christophe Ricard authored 
      

The st21nfcb chipset has 3 SWP (Single Wire Protocol) lines and
supports up to 3 secure elements (UICC/eSE and µSD in the future).

Some st21nfcb firmware does not support the nci command
nci_nfcee_mode_set(NCI_NFCEE_DISABLE). For this reason, we assume
2 secures elements are always present (UICC and eSE).
They will be added to the SE list once successfully activated and
they will be available only after running through enable_se
handler or when the poll in listen mode is started.

During initialization, the white_list will be always set assuming
both UICC & eSE are present.

On eSE activation, the ATR bytes are fetched to build the command
exchange timeout.

The se_io hook will allow to transfer data over SWP. 2 kind of
events may appear data is sent over:
- ST21NFCB_EVT_TRANSMIT_DATA when receiving an apdu answer
- ST21NFCB_EVT_WTX_REQUEST when the secure element needs more time
  than expected to process a command. If this timeout expires, we
  send a software reset, and then a hardware one if it still fails.

Signed-off-by: default avatarChristophe Ricard <christophe-h.ricard@st.com>
Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      8ae01f79
  3. Jan 28, 2015
  5. Jan 27, 2015
    • Robert Dolca's avatar
      NFC: PN544: GPIO access that may sleep · 75dda421
      Robert Dolca authored 
      

gpio_set_value was replaced with gpio_set_value_cansleep in order
to allow GPIO access that may sleep. This is particularelly useful
when GPIO is accessed using busses like I2C, SPI, USB

Signed-off-by: default avatarRobert Dolca <robert.dolca@intel.com>
Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      75dda421
    • Christophe Ricard's avatar
      NFC: st21nfca: Adding support for secure element · 2130fb97
      Christophe Ricard authored 
      

st21nfca has 1 physical SWP line and can support up to 2 secure elements
(UICC & eSE) thanks to an external switch managed with a gpio.

The platform integrator needs to specify thanks to 2 initialization
properties, uicc-present and ese-present, if it is suppose to have uicc
and/or ese. Of course if the platform does not have an external switch,
only one kind of secure element can be supported. Those parameters are
under platform integrator responsibilities.

During initialization, the white_list will be set according to those
parameters.

The discovery_se function will assume a secure element is physically
present according to uicc-present and ese-present values and will add it
to the secure element list. On ese activation, the atr is retrieved to
calculate a command exchange timeout based on the first atr(TB) value.

The se_io will allow to transfer data over SWP. 2 kind of events may appear
after a data is sent over:
- ST21NFCA_EVT_TRANSMIT_DATA when receiving an apdu answer
- ST21NFCA_EVT_WTX_REQUEST when the secure element needs more time than
expected to compute a command. If this timeout expired, a first recovery
tentative consist to send a simple software reset proprietary command.
If this tentative still fail, a second recovery tentative consist to send
a hardware reset proprietary command.
This function is only relevant for eSE like secure element.

This patch also change the way a pipe is referenced. There can be
different pipe connected to the same gate with different host destination
(ex: CONNECTIVITY). In order to keep host information every pipe are
reference with a tuple (gate, host). In order to reduce changes, we are
keeping unchanged the way a gate is addressed on the Terminal Host.
However, this is working because we consider the apdu reader gate is only
present on the eSE slot also the connectivity gate cannot give a reliable
value; it will give the latest stored pipe value.

Signed-off-by: default avatarChristophe Ricard <christophe-h.ricard@st.com>
Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      2130fb97
    • Christophe Ricard's avatar
      NFC: microread: Change event_received gate parameter to pipe · d6365c01
      Christophe Ricard authored 
      

The below event_received hci handler has change the gate parameter to pipe.

Signed-off-by: default avatarChristophe Ricard <christophe-h.ricard@st.com>
      d6365c01
    • Christophe Ricard's avatar
      NFC: pn544: Change event_received gate parameter to pipe · 8abe3c6a
      Christophe Ricard authored 
      

The below event_received hci handler has change the gate parameter to pipe.

Signed-off-by: default avatarChristophe Ricard <christophe-h.ricard@st.com>
      8abe3c6a
  7. Jan 26, 2015
  9. Jan 25, 2015
  11. Dec 15, 2014
  13. Dec 02, 2014
  15. Dec 01, 2014
  17. Nov 28, 2014
  19. Oct 20, 2014
  21. Sep 24, 2014
  23. Sep 23, 2014