From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] SH: extend SCI DMA support to work on SCIFA ports
Date: Tue, 23 Mar 2010 08:39:59 +0000 [thread overview]
Message-ID: <20100323083959.GC30655@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1003191452370.5412@axis700.grange>
On Tue, Mar 23, 2010 at 09:39:26AM +0100, Guennadi Liakhovetski wrote:
> On Tue, 23 Mar 2010, Paul Mundt wrote:
>
> > On Fri, Mar 19, 2010 at 02:53:04PM +0100, Guennadi Liakhovetski wrote:
> > > @@ -1407,8 +1429,21 @@ static void sci_shutdown(struct uart_port *port)
> > > static void sci_set_termios(struct uart_port *port, struct ktermios *termios,
> > > struct ktermios *old)
> > > {
> > > +#ifdef CONFIG_SERIAL_SH_SCI_DMA
> > > + struct sci_port *s = to_sci_port(port);
> > > +#endif
> > > unsigned int status, baud, smr_val, max_baud;
> > > int t = -1;
> > > + u16 scfcr = 0;
> > > +
> > > + /*
> > > + * define SH_SCI_LOOPBACK_LINE to the number of the serial interface
> > > + * to put it in the loopback mode
> > > + */
> > > +#ifdef SH_SCI_LOOPBACK_LINE
> > > + if (port->line = SH_SCI_LOOPBACK_LINE)
> > > + scfcr |= 1; /* Loopback - testing mode */
> > > +#endif
> > >
> > What's this all about? If this is something you think is useful enough to
> > add, it should probably be a module parameter and be settable from the
> > command line.
>
> Yes, I thought it was useful enough to add, but not useful enough to
> export as a module parameter;) So, if you don't like it like this, let's
> just remove it.
>
I don't have any problem with it as a module param, but that's a separate
patch. I'll strip this out of the DMA patch for now, and if you feel like
sending one for the module param then I'll apply that over top. Up to you
though!
prev parent reply other threads:[~2010-03-23 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 13:53 [PATCH] SH: extend SCI DMA support to work on SCIFA ports Guennadi Liakhovetski
2010-03-23 8:31 ` Paul Mundt
2010-03-23 8:39 ` Guennadi Liakhovetski
2010-03-23 8:39 ` Paul Mundt [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=20100323083959.GC30655@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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).