From: Felipe Balbi <balbi@ti.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: "Mark A. Greer" <mgreer@animalcreek.com>,
Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
Felipe Balbi <balbi@ti.com>, Erick Macias <emacias@ti.com>,
Thierry Escande <thierry.escande@linux.intel.com>,
<linux-wireless@vger.kernel.org>, <linux-nfc@ml01.01.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/3] NFC: trf7970a: Add driver with ISO/IEC 14443 Type 2 Tag Support
Date: Thu, 20 Feb 2014 19:20:14 -0600 [thread overview]
Message-ID: <20140221011955.GC19336@saruman.home> (raw)
In-Reply-To: <20140221005059.GS18868@zurbaran>
[-- Attachment #1: Type: text/plain, Size: 233 bytes --]
Hi,
On Fri, Feb 21, 2014 at 01:50:59AM +0100, Samuel Ortiz wrote:
> > +#define TRF7970A_QUIRK_IRQ_STATUS_READ_ERRATA BIT(0)
> Are there actually any TRF970 devices that do not need this quirk ?
in the oven ;-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-02-21 1:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 22:17 [PATCH 0/3] NFC: trf7970a: Add driver with NFC Type 2 and Type V Support Mark A. Greer
2014-01-31 22:17 ` [PATCH 1/3] NFC: trf7970a: Add driver with ISO/IEC 14443 Type 2 Tag Support Mark A. Greer
2014-02-21 0:50 ` Samuel Ortiz
2014-02-21 1:20 ` Felipe Balbi [this message]
2014-02-26 21:53 ` Mark A. Greer
2014-03-03 18:11 ` Mark A. Greer
2014-03-03 20:37 ` Samuel Ortiz
2014-03-05 0:19 ` Mark A. Greer
2014-03-05 12:36 ` Samuel Ortiz
2014-01-31 22:17 ` [PATCH 2/3] NFC: trf7970a: Add ISO/IEC 15693 Support Mark A. Greer
2014-02-21 1:00 ` Samuel Ortiz
2014-02-26 21:53 ` Mark A. Greer
2014-01-31 22:17 ` [PATCH 3/3] NFC: trf7970a: Add DTS Documentation Mark A. Greer
2014-02-21 1:04 ` Samuel Ortiz
2014-02-26 21:54 ` Mark A. Greer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140221011955.GC19336@saruman.home \
--to=balbi@ti.com \
--cc=aloisio.almeida@openbossa.org \
--cc=devicetree@vger.kernel.org \
--cc=emacias@ti.com \
--cc=lauro.venancio@openbossa.org \
--cc=linux-nfc@ml01.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mgreer@animalcreek.com \
--cc=sameo@linux.intel.com \
--cc=thierry.escande@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).