mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>
Cc: <linux-i2c@vger.kernel.org>, <arnd@arndb.de>,
	<sameo@linux.intel.com>, <linux-kernel@vger.kernel.org>,
	<hthebaud@insidefr.com>, <matti.j.aaltonen@nokia.com>
Subject: Re: [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip
Date: Fri, 18 Mar 2011 08:50:33 -0700	[thread overview]
Message-ID: <20110318085033.9bea6dc9.rdunlap@xenotime.net> (raw)
In-Reply-To: <1300444824-13713-2-git-send-email-waldemar.rymarkiewicz@tieto.com>

On Fri, 18 Mar 2011 11:40:24 +0100 Waldemar Rymarkiewicz wrote:

> Add new driver for MicroRead NFC chip connected to i2c bus.
> 
> See Documentation/nfc/nfc-microread.txt.
> 
> Signed-off-by: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>
> ---
>  Documentation/nfc/nfc-microread.txt |   46 ++++
>  drivers/nfc/Kconfig                 |   10 +
>  drivers/nfc/Makefile                |    1 +
>  drivers/nfc/microread.c             |  465 +++++++++++++++++++++++++++++++++++
>  include/linux/nfc/microread.h       |   31 +++
>  5 files changed, 553 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/nfc/nfc-microread.txt
>  create mode 100644 drivers/nfc/microread.c
>  create mode 100644 include/linux/nfc/microread.h
> 
> diff --git a/Documentation/nfc/nfc-microread.txt b/Documentation/nfc/nfc-microread.txt
> new file mode 100644
> index 0000000..e15c49c
> --- /dev/null
> +++ b/Documentation/nfc/nfc-microread.txt
> @@ -0,0 +1,46 @@
> +Kernel driver for Inside Secure MicroRead Near Field Communication chip
> +
> +General
> +-------
> +
> +microread is the RF chip that uses Near Field Communication (NFC) for proximity
> +transactions and interactions.
> +
> +Please visit Inside Secure webside for microread specification:

                              website (or web site)

> +http://www.insidesecure.com/eng/Products/NFC-Products/MicroRead
> +
> +
> +The Driver
> +----------
> +
> +The microread driver can be found under drivers/nfc/microread.c and it's
> +compiled as a module named "microread".
> +
> +The driver supports i2c interface only.
> +
> +The userspace application can use /dev/microread device to control the chip by
> +HCI messages. In a typical scenario application will open() /dev/microread,
> +reset the chip useing ioctl() interface then poll() the device to check if

                  using

> +writing/reaing is possible.Finally, will read/write data (HCI) from/to the chip.

           reading is possible. Finally, it will

> +
> +Note that only one application can use the /dev/microread at the time.
> +
> +The driver waits for microread chip interrupt which occures if there are some

                                                       occurs

> +data to be read. Then, poll() will indicate that fact to the userspace.
> +
> +The application can use ioctl(MICROREAD_IOC_RESET)to reset the hardware.

                                              _RESET) to reset

> +
> +
> +Platform Data
> +-------------
> +
> +The below platform data should be set when configuring board.
> +
> +struct microread_nfc_platform_data {
> +	unsigned int rst_gpio;
> +	unsigned int irq_gpio;
> +	unsigned int ioh_gpio;
> +	int (*request_hardware) (struct i2c_client *client);
> +	void (*release_hardware) (void);
> +};
> +


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2011-03-18 15:50 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 10:40 Waldemar Rymarkiewicz
2011-03-18 10:40 ` Waldemar Rymarkiewicz
2011-03-18 11:03   ` Alan Cox
2011-03-18 15:00     ` Waldemar.Rymarkiewicz
2011-03-18 15:05       ` Arnd Bergmann
2011-03-18 15:12       ` Alan Cox
2011-03-18 15:15         ` Waldemar.Rymarkiewicz
2011-03-18 11:49   ` Wolfram Sang
2011-03-18 15:08     ` Waldemar.Rymarkiewicz
2011-03-18 15:31       ` Mark Brown
2011-03-18 16:43     ` Waldemar.Rymarkiewicz
2011-03-18 12:19   ` Arnd Bergmann
2011-03-18 12:51     ` Mark Brown
2011-03-18 14:20       ` Arnd Bergmann
2011-03-25 14:26     ` Samuel Ortiz
2011-03-29  8:00       ` Waldemar.Rymarkiewicz
2011-03-29 11:05         ` Arnd Bergmann
2011-03-29 11:59           ` Alan Cox
2011-03-29 12:04             ` Arnd Bergmann
2011-03-29 12:23               ` Alan Cox
2011-03-29 13:22                 ` Arnd Bergmann
2011-03-31 14:16           ` Samuel Ortiz
2011-03-31 14:42             ` Waldemar.Rymarkiewicz
2011-03-31 14:49               ` Arnd Bergmann
2011-03-31 15:09               ` Samuel Ortiz
2011-03-31 15:24                 ` Waldemar.Rymarkiewicz
2011-03-31 15:30                   ` Samuel Ortiz
2011-04-01 18:19                     ` Aloisio Almeida
2011-04-01 19:43                       ` Arnd Bergmann
2011-06-06 20:22                     ` Pavan Savoy
2011-06-06 20:30                       ` Pavan Savoy
2011-06-06 20:46                         ` Aloisio Almeida
2011-06-06 20:50                       ` Samuel Ortiz
2011-03-18 15:50   ` Randy Dunlap [this message]
2011-03-18 15:57     ` Waldemar.Rymarkiewicz
  -- strict thread matches above, loose matches on Subject: below --
2011-03-10 14:20 Waldemar Rymarkiewicz
2011-03-10 13:52 ` Arnd Bergmann
2011-03-10 14:45   ` Waldemar.Rymarkiewicz
2011-03-10 16:20     ` Arnd Bergmann
2011-03-14 14:59       ` Waldemar.Rymarkiewicz
2011-03-14 15:34         ` Arnd Bergmann
2011-03-14 15:45           ` Waldemar.Rymarkiewicz
2011-03-14 16:00             ` Arnd Bergmann
2011-03-14 16:15               ` Waldemar.Rymarkiewicz
2011-03-14 17:01                 ` Arnd Bergmann
2011-03-15  8:37                   ` Waldemar.Rymarkiewicz
2011-03-15  9:06                     ` Arnd Bergmann
2011-03-17 12:58       ` Waldemar.Rymarkiewicz
2011-03-17 13:07         ` Arnd Bergmann
2011-03-17 13:38           ` Waldemar.Rymarkiewicz
2011-03-17 13:54             ` Arnd Bergmann
2011-03-17 13:58               ` Waldemar.Rymarkiewicz

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=20110318085033.9bea6dc9.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=arnd@arndb.de \
    --cc=hthebaud@insidefr.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.j.aaltonen@nokia.com \
    --cc=sameo@linux.intel.com \
    --cc=waldemar.rymarkiewicz@tieto.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

all inboxes | Powered by JetHome®