From: Samuel Ortiz <samuel@sortiz.org>
To: Lauro Ramos Venancio <lauro.venancio@openbossa.org>
Cc: Eric Lapuyade <eric.lapuyade@linux.intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>
Subject: Re: [PATCH] NFC: Add Core support to generate tag lost event
Date: Fri, 23 Mar 2012 18:48:14 +0100 [thread overview]
Message-ID: <1332524894.5884.15.camel@sortiz-mobl> (raw)
In-Reply-To: <CAK3JMAZhJP=RC09gA7jHf7Z5ZhuscHbsLW2dPq9Wk52uGQt7YA@mail.gmail.com>
On Fri, 2012-03-23 at 14:11 -0300, Lauro Ramos Venancio wrote:
> 2012/3/23 Eric Lapuyade <eric.lapuyade@linux.intel.com>:
> > Some HW/drivers get notifications when a tag moves out of the radio field.
> > This notification is now forwarded to user space through netlink.
>
> I think to put a timer in the NFC core is not the best solution for
> this problem.
> This solution is not suitable for devices that receive an event when
> the tag moves out of the field.
One more thing: If the device provides such capability, the driver can
then call nfc_target_lost() directly, and not register a
presence_check() ops. Without such an ops, the timer won't get started,
obviously.
presence_check() is for drivers that are limited to asking the firmware
about the target being on the field or not.
Cheers,
Samuel.
next prev parent reply other threads:[~2012-03-23 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 11:19 [PATCH] NFC: Add Core support to generate tag lost event Eric Lapuyade
2012-03-23 14:15 ` Samuel Ortiz
2012-03-23 17:11 ` Lauro Ramos Venancio
2012-03-23 17:33 ` Samuel Ortiz
2012-03-26 9:40 ` Elias, Ilan
2012-03-23 17:48 ` Samuel Ortiz [this message]
2012-03-23 18:53 ` Lauro Ramos Venancio
2012-03-26 9:48 ` Elias, Ilan
2012-03-26 10:12 ` Samuel Ortiz
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=1332524894.5884.15.camel@sortiz-mobl \
--to=samuel@sortiz.org \
--cc=aloisio.almeida@openbossa.org \
--cc=eric.lapuyade@linux.intel.com \
--cc=lauro.venancio@openbossa.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sameo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.