From: Charles Coldwell <coldwell@gmail.com>
To: Charles Coldwell <coldwell@gmail.com>
Cc: jon@ringle.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
shc_work@mail.ru, Jon Ringle <jringle@gridpoint.com>
Subject: Re: [PATCH v7 1/2] serial: sc16is7xx
Date: Fri, 25 Apr 2014 09:44:52 -0400 (EDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1404250941590.2625@frank.harvard.edu> (raw)
In-Reply-To: <alpine.LRH.2.03.1404250914380.30160@frank.harvard.edu>
On Fri, 25 Apr 2014, Charles Coldwell wrote:
> 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?
Actually, the whole thing seems like duplication to me. The SC16IS7X0
parts are designed to be 16550-compatible (hence the duplication in the
register map), and so I would vote for putting the driver into the
drivers/tty/serial/8250 framework. There's really not much difference
between these parts and other 16550 parts except that they are reached
over the SPI/I2C bus.
--
Charles M. Coldwell, W1CMC
"Turn on, log in, tune out"
Belmont, Massachusetts, New England (FN42jj)
GPG ID: 852E052F
GPG FPR: 77E5 2B51 4907 F08A 7E92 DE80 AFA9 9A8F 852E 052F
next prev parent reply other threads:[~2014-04-25 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 0:56 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
2014-04-25 14:11 ` Jon Ringle
2014-04-25 13:44 ` Charles Coldwell [this message]
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 16:48 ` One Thousand Gnomes
2014-04-25 17:26 ` Greg KH
2014-04-25 17:40 ` Alexander Shiyan
2014-04-25 18:24 ` Jon Ringle
2014-04-25 18:28 ` Alexander Shiyan
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=alpine.LRH.2.03.1404250941590.2625@frank.harvard.edu \
--to=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 \
--cc=shc_work@mail.ru \
/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®