The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Waldemar.Rymarkiewicz@tieto.com, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, hthebaud@insidefr.com,
	matti.j.aaltonen@nokia.com, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip
Date: Thu, 31 Mar 2011 16:16:51 +0200	[thread overview]
Message-ID: <20110331141650.GB2704@sortiz-mobl> (raw)
In-Reply-To: <201103291305.02293.arnd@arndb.de>

On Tue, Mar 29, 2011 at 01:05:02PM +0200, Arnd Bergmann wrote:
> On Tuesday 29 March 2011, Waldemar.Rymarkiewicz@tieto.com wrote:
> > >Yes, NFC seems to be a good fit for a new socket family. 
> > >Especially if we ever want to have a proper NFC p2p support 
> > >from the kernel.
> > >Sending HCI commands should be done through a dedicated 
> > >netlink socket too.
> > >
> > >I am currently strting to work on such solution, and I hope to 
> > >be able to come up with a basic prototype for it in a few weeks.
> > 
> > What about common drivers interface in this case.
> > Should we go for common /dev/nfcX interface as well?
> 
> I fear there can only be one. A good implementation of a socket
> interface would mean that there is no need for a character device.
My idea of an initial NFC subsystem architecture was actually the following
one:
- A core NFC layer against which NFC drivers would register.
- A netlink socket for handling the HCI commands. That would put a big part of
the NFC HCI layer in kernel land and could potentially simplify the existing
NFC stacks.
- A socket family for the LLCP abstraction, a.k.a. NFC peer to peer mode.

We can start working on the first 2 items and leave the last one as a future
enhancement, since what NFC is currently mostly used for is tag
reading/writing and smartcard emulation.

Basically, we'd replace the current character device option with a netlink
one, allowing for a single kernel entry point for multiple applications
willing to do NFC.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  parent reply	other threads:[~2011-03-31 14:16 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 10:40 [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip 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 [this message]
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
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=20110331141650.GB2704@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=Waldemar.Rymarkiewicz@tieto.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 \
    /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