From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] serial: sh-sci: modify sci_break_ctl()
Date: Wed, 11 Apr 2012 04:28:05 +0000 [thread overview]
Message-ID: <20120411042805.GC19696@linux-sh.org> (raw)
In-Reply-To: <4F7E3FE2.4050902@renesas.com>
On Fri, Apr 06, 2012 at 02:39:00PM +0900, Shimoda, Yoshihiro wrote:
> 2012/04/06 14:11, Simon Horman wrote:
> > On Fri, Apr 06, 2012 at 12:50:00PM +0900, Shimoda, Yoshihiro wrote:
> >>
> >> If userland calls ioctl with TIOCSBRK/TIOCCBRK, the sci_break_ctl
> >> is called. After TIOCSBRK we cannot send data from SCIF.
> >> After TIOCCBRK, we can send data from SCIF.
> >
> > Thanks, that make a lot of sense.
> >
> > Unfortunately the ecovec doesn't exercise the new code
> > as the regtype of its scif is SCIx_SH4_SCIF_NO_SCSPTR_REGTYPE
> > but your code only operates on SCIx_SH4_SCIF_REGTYPE.
>
> Sorry I forgot that the SH7724 has SCIF and SCIFA.
> The ecovec uses SCIF, and it doesn't have SCSPTR.
Well, one thing that you can do is test for the SCSPTR existence and
simply not care about the port type. This is roughly what the generic
sci_init_pins() does for example.
You would have to ensure that the bits you are twiddling also exist for
the SCIx_SH2_SCIF_FIFODATA_REGTYPE, SCIx_SH2_SCIF_FIFODATA_REGTYPE, and
SCIx_SH4_SCIF_FIFODATA_REGTYPE, though.
> I checked the ecovec schematics, but it cannot use SCIFA because
> other functions use the multiplex pins.
>
You should be able to plug them in for the port and let the sh-sci driver
try to grab the port. The port will simply be skipped if pin demux fails.
Take a look at 50f0959ad4f9ac1c5ee208bb820de299a1b3730b for an idea of
how to wire it up.
next prev parent reply other threads:[~2012-04-11 4:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 0:59 [PATCH v2] serial: sh-sci: modify sci_break_ctl() Shimoda, Yoshihiro
2012-04-06 1:57 ` Simon Horman
2012-04-06 2:13 ` Shimoda, Yoshihiro
2012-04-06 2:44 ` Simon Horman
2012-04-06 3:50 ` Shimoda, Yoshihiro
2012-04-06 5:11 ` Simon Horman
2012-04-06 5:39 ` Shimoda, Yoshihiro
2012-04-06 11:13 ` Simon Horman
2012-04-09 7:59 ` Paul Mundt
2012-04-11 4:28 ` Paul Mundt [this message]
2012-04-11 9:36 ` Shimoda, Yoshihiro
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=20120411042805.GC19696@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.