From: Samuel Ortiz <samuel@sortiz.org>
To: "Elias, Ilan" <ilane@ti.com>
Cc: Eric Lapuyade <eric.lapuyade@linux.intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>
Subject: RE: [PATCH] NFC: Add Core support to generate tag lost event
Date: Mon, 26 Mar 2012 12:12:49 +0200 [thread overview]
Message-ID: <1332756769.5884.17.camel@sortiz-mobl> (raw)
In-Reply-To: <B30D1FD582D6484ABF57420512E5803516A9376C@DNCE03.ent.ti.com>
Hi Ilan,
On Mon, 2012-03-26 at 09:48 +0000, Elias, Ilan wrote:
> Hi Eric,
>
> > +static void nfc_check_pres_work(struct work_struct *work)
> > +{
> > + struct nfc_dev *dev = container_of(work, struct nfc_dev,
> > + check_pres_work);
> > + int rc;
> > +
> > + device_lock(&dev->dev);
> > +
> > + if (dev->activated_target_idx != NFC_TARGET_IDX_NONE &&
> > + timer_pending(&dev->check_pres_timer) == 0) {
> > + rc = dev->ops->check_presence(dev,
> > dev->activated_target_idx);
> > + if (!rc) {
> > + mod_timer(&dev->check_pres_timer, jiffies +
> > +
> > msecs_to_jiffies(NFC_CHECK_PRES_FREQ_MS));
> > + } else {
> > + nfc_target_lost(dev, dev->activated_target_idx);
> I'm unable to find the definition of the function nfc_target_lost.
This patch is based on my nfc-next branch, where nfc_target_lost is
implemented. I'm waiting for John to take patches for the next merge
window before sending him a pull request for that.
Cheers,
Samuel.
prev parent reply other threads:[~2012-03-26 10:04 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
2012-03-23 18:53 ` Lauro Ramos Venancio
2012-03-26 9:48 ` Elias, Ilan
2012-03-26 10:12 ` 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=1332756769.5884.17.camel@sortiz-mobl \
--to=samuel@sortiz.org \
--cc=aloisio.almeida@openbossa.org \
--cc=eric.lapuyade@linux.intel.com \
--cc=ilane@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox