All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Shikha Singh <shikha.singh@st.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	linux-nfc@lists.01.org, manoj.kumar@st.com,
	sylvain.fidelis@st.com, raphael.collado@st.com,
	MMS_MMY_Applications_SW@list.st.com,
	Rob Herring <robh@kernel.org>
Subject: Re: [linux-nfc] [[PATCH v1] 0/6] Support of ST NFC Transceiver
Date: Tue, 2 May 2017 08:58:45 +0200	[thread overview]
Message-ID: <C4E99B67-D95D-46E6-828A-49FFE447272B@holtmann.org> (raw)
In-Reply-To: <1493705023-8710-1-git-send-email-shikha.singh@st.com>

Hi Shikha,

> *** V1.0 ***
> This patch series is generated on top of latest
> code available on nfc-next.
> 
> This patch series introduces the following features:
> 
> (a) A generic Digital NFC UART framework.
> The framework itself is an LDISC registered
> with the tty core. Any NFC transciever implementing
> the digital specs and connected on an UART
> (or on an emulated tty, such as /dev/ttyUSBx, /dev/ttyACMx)
> interface with the host, will require this support.
> 
> (b) An ST NFC Transciever core framework. This implements the
> required digital ops and exposes an interface for the
> underlying phy drivers (UART/ SPI). The services of the phy drivers
> are required when the core wants to transmit/receive frames.
> Also it provides helper functions for the phy drivers, for
> example phy drivers registers with the core when it detects
> a Transciever connected on the corresponding interface.
> The framework currently supports NFC Type 2, Type 4A, Type 4B,
> Type 5 tag read/write.
> 
> (c) An ST NFC UART LDisc driver that registers with the
> Digital NFC UART framework, and with the ST NFC Transciever
> core framework as the UART Phy driver.

lets stop this please and move towards serdev support. We really do not need more line disciplines for this.

Regards

Marcel

  parent reply	other threads:[~2017-05-02  6:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  6:03 [[linux-nfc][PATCH v1] 0/6] Support of ST NFC Transceiver Shikha Singh
2017-05-02  6:03 ` [[linux-nfc][PATCH v1] 1/6] NFC: add generic UART support Shikha Singh
2017-05-02  6:03 ` [[linux-nfc][PATCH v1] 2/6] NFC: nfcst: Add ST NFC Transceiver core framework Shikha Singh
2017-06-25 23:04   ` Samuel Ortiz
2017-06-30  4:46     ` Shikha SINGH
2017-05-02  6:03 ` [[linux-nfc][PATCH v1] 3/6] NFC: nfcst: Add UART LDisc Driver Shikha Singh
2017-05-02  6:03 ` [[linux-nfc][PATCH v1] 4/6] NFC: nfcst: Add ST NFC SPI Driver Shikha Singh
2017-05-02  6:03 ` [[linux-nfc][PATCH v1] 5/6] DT: bindings: net: nfc: stnfc binding doc Shikha Singh
2017-05-02  6:03 ` [[linux-nfc][PATCH v1] 6/6] DRIVERS: NFC: Remove st95hf name reference Shikha Singh
2017-05-02  6:58 ` Marcel Holtmann [this message]
2017-05-02 11:56   ` [linux-nfc] [[PATCH v1] 0/6] Support of ST NFC Transceiver Shikha SINGH

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=C4E99B67-D95D-46E6-828A-49FFE447272B@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=MMS_MMY_Applications_SW@list.st.com \
    --cc=linux-nfc@lists.01.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=manoj.kumar@st.com \
    --cc=raphael.collado@st.com \
    --cc=robh@kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=shikha.singh@st.com \
    --cc=sylvain.fidelis@st.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.