From: Samuel Ortiz <samuel@sortiz.org>
To: "Elias, Ilan" <ilane@ti.com>
Cc: "lauro.venancio@openbossa.org" <lauro.venancio@openbossa.org>,
"aloisio.almeida@openbossa.org" <aloisio.almeida@openbossa.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] NFC: Add RF technology specific parameters to target info
Date: Wed, 21 Dec 2011 15:49:01 +0100 [thread overview]
Message-ID: <1324478941.5354.2.camel@sortiz-mobl> (raw)
In-Reply-To: <B30D1FD582D6484ABF57420512E5803504FE1669@DNCE03.ent.ti.com>
Hi Ilan,
On Wed, 2011-12-21 at 14:18 +0000, Elias, Ilan wrote:
> Hi Samuel, Lauro, Aloisio,
>
> Currently, the target information (sent as response to NFC_CMD_GET_TARGET) contains the following: target index, protocols, sens_res, and sel_res.
> As far as I understand, the sens_res (2 Octets) and sel_res (1 Octet) fields are suitable only for tech A.
>
> It seems that several RF technology specific parameters should be added to the target info:
> 1) For tech A: NFCID1 (0, 4, 7, or 10 Octets), and NFCID1 Length (1 Octet).
> 2) For tech B: SENSB_RES Response (11 or 12 Octets), and SENSB_RES Response Length (1 Octet).
> 3) For tech F: SENSF_RES Response (16 or 18 Octets) and SENSF_RES Response Length (1 Octet).
I agree. When I decided to export sens_res and sel_res, I remember we thought we would need more exports for other technologies.
So, yes, exporting all of those would make sense (e.g. the NFCID one is
on my TODO list).
Cheers,
Samuel.
prev parent reply other threads:[~2011-12-21 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 14:18 [RFC] NFC: Add RF technology specific parameters to target info Elias, Ilan
2011-12-21 14:49 ` Samuel Ortiz [this message]
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=1324478941.5354.2.camel@sortiz-mobl \
--to=samuel@sortiz.org \
--cc=aloisio.almeida@openbossa.org \
--cc=ilane@ti.com \
--cc=lauro.venancio@openbossa.org \
--cc=linux-wireless@vger.kernel.org \
/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