From: Matt Ranostay <matt.ranostay@konsulko.com>
To: "Gaëtan Carlier" <gcembed@gmail.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: Add support of Wiegand card reader
Date: Mon, 9 Apr 2018 16:26:39 -0700 [thread overview]
Message-ID: <CAJCx=gna64NhsMGHu4MGbssvNgeyWXwcoRCFZ4wDLQbu96susg@mail.gmail.com> (raw)
In-Reply-To: <b36429ed-34cb-6f07-13a2-2ef960bd9b42@gmail.com>
On Mon, Apr 9, 2018 at 7:05 AM, Ga=C3=ABtan Carlier <gcembed@gmail.com> wro=
te:
> Hello,
> I would like to add support of Wiegand card reader [1]. Where can I place=
it : drivers/iio/access/wiegand.c or drivers/iio/security/wiegand.c?
Question here is why is this ideal for iio versus using the input subsystem=
?
Also a few issues/points:
* What is the interface to the Wiegand data? If it is inputting on a
GPIO that is for sure not going to be real time enough to get valid
data
* Aren't there multiple Wiegand transport standards?
* Most keyreaders I've seen are emulated as keyboard devices so they
use the input subsystem.
* Also if the data being output is ASCII data, then I'm not sure that
fits anywhere in iio
- Matt
>
> Thank you for your help?
> Best regards,
> Ga=C3=ABtan.
>
> [1] https://en.wikipedia.org/wiki/Wiegand_interface
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-04-09 23:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 14:05 Add support of Wiegand card reader Gaëtan Carlier
2018-04-09 23:26 ` Matt Ranostay [this message]
2018-04-10 8:57 ` Gaëtan Carlier
2018-04-11 3:37 ` Matt Ranostay
2018-04-11 8:36 ` Gaëtan Carlier
2018-04-12 3:41 ` Matt Ranostay
2018-04-12 11:24 ` Jonathan Cameron
2018-04-12 11:30 ` Lars-Peter Clausen
2018-04-12 12:20 ` Gaëtan Carlier
2018-04-12 20:59 ` Matt Ranostay
2018-04-13 8:11 ` Gaëtan Carlier
2018-04-13 18:44 ` Matt Ranostay
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='CAJCx=gna64NhsMGHu4MGbssvNgeyWXwcoRCFZ4wDLQbu96susg@mail.gmail.com' \
--to=matt.ranostay@konsulko.com \
--cc=gcembed@gmail.com \
--cc=linux-iio@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 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.