linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Charles Coldwell" <coldwell@gmail.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org, "Jon Ringle" <jringle@gridpoint.com>,
	jon@ringle.org
Subject: Re: [PATCH v7 1/2] serial: sc16is7xx
Date: Fri, 25 Apr 2014 17:35:35 +0400	[thread overview]
Message-ID: <1398432935.28366949@f70.i.mail.ru> (raw)
In-Reply-To: <alpine.LRH.2.03.1404250914380.30160@frank.harvard.edu>

Fri, 25 Apr 2014 09:21:26 -0400 (EDT) от Charles Coldwell <coldwell@gmail.com>:
> On Thu, 24 Apr 2014, jon@ringle.org wrote:
> 
> > diff --git a/drivers/tty/serial/sc16is7xx.c b/drivers/tty/serial/sc16is7xx.c
> > new file mode 100644
> > index 0000000..ed139f5
> > --- /dev/null
> > +++ b/drivers/tty/serial/sc16is7xx.c
> 
> > +
> > +/* SC16IS7XX register definitions */
> > +#define SC16IS7XX_RHR_REG		(0x00) /* RX FIFO */
> > +#define SC16IS7XX_THR_REG		(0x00) /* TX FIFO */
> > +#define SC16IS7XX_IER_REG		(0x01) /* Interrupt enable */
> > +#define SC16IS7XX_IIR_REG		(0x02) /* Interrupt Identification */
> > +#define SC16IS7XX_FCR_REG		(0x02) /* FIFO control */
> > +#define SC16IS7XX_LCR_REG		(0x03) /* Line Control */
> > +#define SC16IS7XX_MCR_REG		(0x04) /* Modem Control */
> > +#define SC16IS7XX_LSR_REG		(0x05) /* Line Status */
> > +#define SC16IS7XX_MSR_REG		(0x06) /* Modem Status */
> > +#define SC16IS7XX_SPR_REG		(0x07) /* Scratch Pad */
> 
> Isn't this a lot of duplication?  We have already in 
> 
> /*
>  * include/linux/serial_reg.h
>  *
> #define UART_RX		0	/* In:  Receive buffer */
> #define UART_TX		0	/* Out: Transmit buffer */
> #define UART_IER	1	/* Out: Interrupt Enable Register */
> #define UART_IIR	2	/* In:  Interrupt ID Register */
> #define UART_FCR	2	/* Out: FIFO Control Register */
> #define UART_LCR	3	/* Out: Line Control Register */
> #define UART_MCR	4	/* Out: Modem Control Register */
> #define UART_LSR	5	/* In:  Line Status Register */
> #define UART_MSR	6	/* In:  Modem Status Register */
> #define UART_SCR	7	/* I/O: Scratch Register */
> 
> and the bit definitions, as well.

And it would be nice to have a small changelog,
because it is unclear what has changed with version 6.

---


  reply	other threads:[~2014-04-25 13:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  0:56 [PATCH v7 1/2] serial: sc16is7xx jon
2014-04-25  0:56 ` [PATCH v7 2/2] serial: sc16is7xx: Add bindings documentation for the SC16IS7XX UARTs jon
2014-04-25 13:21 ` [PATCH v7 1/2] serial: sc16is7xx Charles Coldwell
2014-04-25 13:35   ` Alexander Shiyan [this message]
2014-04-25 14:11     ` Jon Ringle
2014-04-25 13:44   ` Charles Coldwell
2014-04-25 14:08     ` Jon Ringle
2014-04-25 14:24       ` Charles Coldwell
2014-04-25 14:33         ` Alexander Shiyan
2014-04-25 14:36           ` Charles Coldwell
2014-04-25 14:41         ` Jon Ringle
2014-04-25 14:54           ` Alexander Shiyan
2014-04-25 16:48         ` One Thousand Gnomes
2014-04-25 17:26 ` Greg KH
     [not found]   ` <1398447618.26477952@f179.i.mail.ru>
2014-04-25 18:24     ` Jon Ringle

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=1398432935.28366949@f70.i.mail.ru \
    --to=shc_work@mail.ru \
    --cc=coldwell@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jon@ringle.org \
    --cc=jringle@gridpoint.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).