public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Jon Ringle" <jon@ringle.org>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Jon Ringle" <jringle@gridpoint.com>
Subject: Re: [PATCH v7 1/2] serial: sc16is7xx
Date: Fri, 25 Apr 2014 22:28:10 +0400	[thread overview]
Message-ID: <1398450490.22421425@f292.i.mail.ru> (raw)
In-Reply-To: <CAMwGMjz+=rvYBVPpkC9f1bpW46_1srmokH8-PzDS+2Z2OqCOtQ@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2462 bytes --]

Fri, 25 Apr 2014 14:24:23 -0400 от Jon Ringle <jon@ringle.org>:
> On Fri, Apr 25, 2014 at 1:40 PM, Alexander Shiyan <shc_work@mail.ru> wrote:
> > Fri, 25 Apr 2014 10:26:40 -0700 от Greg KH <gregkh@linuxfoundation.org>:
> >> On Thu, Apr 24, 2014 at 08:56:06PM -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.
> >> >
> >> > The SC16IS7xx also provides additional advanced features such as
> >> > auto hardware and software flow control, automatic RS-485 support, and
> >> > software reset.
> >> >
> >> > Signed-off-by: Jon Ringle <jringle@gridpoint.com>
> >> > ---
> >> >  drivers/tty/serial/Kconfig       |    9 +
> >> >  drivers/tty/serial/Makefile      |    1 +
> >> >  drivers/tty/serial/sc16is7xx.c   | 1279 ++++++++++++++++++++++++++++++++++++++
> >> >  include/uapi/linux/serial_core.h |    3 +
> >> >  4 files changed, 1292 insertions(+)
> >> >  create mode 100644 drivers/tty/serial/sc16is7xx.c
> >>
> >> I get a few build warnings with this patch applied:
> >>
> >> drivers/tty/serial/sc16is7xx.c:1059:12: warning: ‘sc16is7xx_probe’ defined but not used [-Wunused-function]
> >>  static int sc16is7xx_probe(struct device *dev,
> >>             ^
> >> drivers/tty/serial/sc16is7xx.c:1175:12: warning: ‘sc16is7xx_remove’ defined but not used [-Wunused-function]
> >>  static int sc16is7xx_remove(struct device *dev)
> >>             ^
> >> drivers/tty/serial/sc16is7xx.c:1214:29: warning: ‘regcfg’ defined but not used [-Wunused-variable]
> >>  static struct regmap_config regcfg = {
> >>                              ^
> >>
> >> Can you send a follow-on patch to fix them?
> >
> > Seems this just should contain: "depends on I2C" in the Kconfig.
> 
> I can add "depends on I2C" in Kconfig for now, but I'm just wondering
> how would this be dealt with when sometime in the future this driver
> supports either I2C or SPI? Can the "depends on" be conditional
> somehow?

If anyone adds SPI support later, this can be represented as:
depends on I2C || SPI_MASTER
select REGMAP_I2C if I2C
select REGMAP_SPI if SPI_MASTER

---

ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

      reply	other threads:[~2014-04-25 18:28 UTC|newest]

Thread overview: 16+ 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
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 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 [this message]

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=1398450490.22421425@f292.i.mail.ru \
    --to=shc_work@mail.ru \
    --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