On Mon, Jun 08, 2015 at 11:18:21PM +0200, Samuel Ortiz wrote: > Hi Mark, > > On Fri, Apr 24, 2015 at 10:37:22AM -0700, Mark A. Greer wrote: > > The current versions of the trf7970a has an erratum where it returns > > an extra byte in the response to 'Read Multiple Block' (RMB) commands. > > This command is issued to Type 5 tags (i.e., ISO/IEC 15693 tags) by > > the neard daemon. > > > > To handle this, define a new Device Tree property, > > 't5t-rmb-extra-byte-quirk', which indicates that the associated > > trf7970a device has this erratum. The trf7970a device driver > > will then ensure that the response length to RMB commands is > > reduced by one byte (for devices with the erratum). > > > > Signed-off-by: Mark A. Greer <mgreer@xxxxxxxxxxxxxxx> > > --- > > .../devicetree/bindings/net/nfc/trf7970a.txt | 4 ++++ > > drivers/nfc/trf7970a.c | 23 ++++++++++++++++++---- > > 2 files changed, 23 insertions(+), 4 deletions(-) > Applied to nfc-next, thanks. Cool! Thanks Samuel. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
