From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Network Development <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH net-next 8/8] net: qualcomm: add QCA7000 UART driver
Date: Tue, 20 Sep 2016 17:32:36 +0200 [thread overview]
Message-ID: <2EE064FD-FCC1-4559-819D-471BD000F5AF@holtmann.org> (raw)
In-Reply-To: <1474376544-20515-9-git-send-email-stefan.wahren@i2se.com>
Hi Stefan,
> This patch adds the Ethernet over UART driver for the
> Qualcomm QCA7000 HomePlug GreenPHY.
>
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> ---
> drivers/net/ethernet/qualcomm/Kconfig | 12 +
> drivers/net/ethernet/qualcomm/Makefile | 2 +
> drivers/net/ethernet/qualcomm/qca_common.h | 6 +
> drivers/net/ethernet/qualcomm/qca_uart.c | 447 +++++++++++++++++++++++++++++
> include/uapi/linux/tty.h | 1 +
> 5 files changed, 468 insertions(+)
> create mode 100644 drivers/net/ethernet/qualcomm/qca_uart.c
>
> diff --git a/drivers/net/ethernet/qualcomm/Kconfig b/drivers/net/ethernet/qualcomm/Kconfig
> index 0d33728..0ede46e 100644
> --- a/drivers/net/ethernet/qualcomm/Kconfig
> +++ b/drivers/net/ethernet/qualcomm/Kconfig
> @@ -30,6 +30,18 @@ config QCA7000_SPI
> To compile this driver as a module, choose M here. The module
> will be called qcaspi.
>
> +config QCA7000_UART
> + tristate "Qualcomm Atheros QCA7000 UART support"
> + select QCA7000
> + depends on TTY
> + ---help---
> + This UART protocol driver supports the Qualcomm Atheros QCA7000.
> + The driver implements the tty line discipline N_QCA7K and supports
> + only one netdevice.
> +
> + To compile this driver as a module, choose M here. The module
> + will be called qcauart.
> +
this seems to be another candidate for having a proper UART or serial bus. Instead of adding one line discipline after another, I think we need to get quickly to having an enumerable bus here.
Regards
Marcel
next prev parent reply other threads:[~2016-09-20 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 13:02 [PATCH net-next 0/8] " Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 1/8] net: qualcomm: remove unnecessary includes Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 2/8] net: qca_debug: use net_device_ops instead of direct call Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 3/8] net: qualcomm: move qcaspi_tx_cmd to qca_spi.c Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 4/8] net: qualcomm: rename qca_framing.c to qca_common.c Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 5/8] net: qualcomm: move MTU handling to qca_common Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 6/8] net: qualcomm: prepare frame decoding for UART driver Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 7/8] net: qualcomm: make qca_common a separate kernel module Stefan Wahren
2016-09-20 13:02 ` [PATCH net-next 8/8] net: qualcomm: add QCA7000 UART driver Stefan Wahren
2016-09-20 14:44 ` kbuild test robot
2016-09-20 16:43 ` Stefan Wahren
2016-09-20 15:32 ` Marcel Holtmann [this message]
2016-09-21 7:49 ` Stefan Wahren
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=2EE064FD-FCC1-4559-819D-471BD000F5AF@holtmann.org \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stefan.wahren@i2se.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®