From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: jon@ringle.org
Cc: gregkh@linuxfoundation.org, jslaby@suse.cz, shc_work@mail.ru,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org, Jon Ringle <jringle@gridpoint.com>
Subject: Re: [PATCH v2] tty: serial: sc16is7xx
Date: Fri, 21 Mar 2014 10:26:09 +0200 [thread overview]
Message-ID: <20140321082609.GA3801@xps8300> (raw)
In-Reply-To: <1395324333-21221-1-git-send-email-jon@ringle.org>
Hi,
On Thu, Mar 20, 2014 at 10:05:33AM -0400, jon@ringle.org wrote:
> From: Jon Ringle <jringle@gridpoint.com>
>
> The SC16IS7xx is a slave I2C-bus/SPI interface to a single-channel
> high performance UART. The SC16IS7xx’s internal register set is
> backward-compatible with the widely used and widely popular 16C450.
So couldn't this be just a probe driver for 8250?
> +/* 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 */
At least there should not be any need to redefine those register or
their bits. Just include serial_reg.h.
Thanks,
--
heikki
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-21 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 14:05 [PATCH v2] tty: serial: sc16is7xx jon-7zJyie9iPacdnm+yROfE0A
2014-03-21 8:26 ` Heikki Krogerus [this message]
2014-03-21 12:42 ` Jon Ringle
2014-03-21 13:22 ` One Thousand Gnomes
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=20140321082609.GA3801@xps8300 \
--to=heikki.krogerus@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jon@ringle.org \
--cc=jringle@gridpoint.com \
--cc=jslaby@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).