Difference between revisions of "Add device-tree support to pn544 NFC driver"

From eLinux.org
Jump to: navigation, search
(add proposal page)
 
(Add not selected status info)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
; Summary: Add device-tree support to the pn544 NFC driver
 
; Summary: Add device-tree support to the pn544 NFC driver
 
; Proposer: Tim Bird, Sony Mobile
 
; Proposer: Tim Bird, Sony Mobile
 +
; Status: Not selected in 2013 to be sponsored by the CE Workgroup
  
 
== Description ==
 
== Description ==
 
The NXP PN544 NFC chipset is used in a very large number of Linux-based devices.
 
The NXP PN544 NFC chipset is used in a very large number of Linux-based devices.
The driver in mainline was submitted by developers at Nokia, and was last
+
It is missing any integration with device-tree. Such integration would make it
worked on in 2011.  It is missing any integration with device-tree. Such
+
easier to use in current products.  Some companies are apparently using their
integration would make it easier to use in current products.  Some companies
+
own driver for the PN544.  It would be worth investigating if the driver in
are apparently using their own driver for the PN544.  It would be worth
+
mainline is missing some functionality that prevents its use, and fixing that as well.
investigating if the driver in mainline is missing some functionality
 
that prevents its use, and fixing that as well.
 
  
 
This project would consist of adding device-tree awareness to the existing
 
This project would consist of adding device-tree awareness to the existing
driver, at drivers/nfc/pn544.c. This awareness would consist of integrating
+
driver, at drivers/nfc/pn544/* This awareness would consist of integrating
 
the driver with the DT-isms for regulators (and/or gpios) and i2c.
 
the driver with the DT-isms for regulators (and/or gpios) and i2c.
  
 
== Related work ==
 
== Related work ==
None that I can think of.
+
 
 +
== Resources ==
 +
* [http://www.nxp.com/documents/leaflet/75016890.pdf Product leaflet]
 +
 
  
 
== Scope ==
 
== Scope ==
Line 26: Line 28:
  
 
== Comments ==
 
== Comments ==
 +
Tim asks: Why isn't NXP maintaining the Linux driver for this?
 +
 +
=== Reasons for CEWG not selecting this project ===
 +
 +
Not enough AG members used this chip to be interested in collaborating
 +
on the funding of it. (At least, of those attending the meeting).
 +
The upstream driver is not compatible with Android, and the out-of-tree
 +
driver is not difficult to maintain, with most of the functionality
 +
residing in the user-space library.  It was decided there was not
 +
enough return on investment to justify funding this work.
  
 
[[Category:Project proposals 2013]]
 
[[Category:Project proposals 2013]]

Latest revision as of 13:15, 30 December 2013

Summary
Add device-tree support to the pn544 NFC driver
Proposer
Tim Bird, Sony Mobile
Status
Not selected in 2013 to be sponsored by the CE Workgroup

Description

The NXP PN544 NFC chipset is used in a very large number of Linux-based devices. It is missing any integration with device-tree. Such integration would make it easier to use in current products. Some companies are apparently using their own driver for the PN544. It would be worth investigating if the driver in mainline is missing some functionality that prevents its use, and fixing that as well.

This project would consist of adding device-tree awareness to the existing driver, at drivers/nfc/pn544/* This awareness would consist of integrating the driver with the DT-isms for regulators (and/or gpios) and i2c.

Related work

Resources


Scope

Rough estimate is 2 to 4 weeks. Maybe quicker with someone familiar with device-tree stuff.

Contractor Candidates

None yet.

Comments

Tim asks: Why isn't NXP maintaining the Linux driver for this?

Reasons for CEWG not selecting this project

Not enough AG members used this chip to be interested in collaborating on the funding of it. (At least, of those attending the meeting). The upstream driver is not compatible with Android, and the out-of-tree driver is not difficult to maintain, with most of the functionality residing in the user-space library. It was decided there was not enough return on investment to justify funding this work.