From: Laurent Pinchart <laurent.pinchart@tbox.biz>
To: Ricardo Scop <scop@digitel.com.br>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: CPM2 SCC/SMC break handling broken
Date: Fri, 27 Oct 2006 11:01:38 +0200 [thread overview]
Message-ID: <200610271101.38911.laurent.pinchart@tbox.biz> (raw)
In-Reply-To: <200610261918.37769.scop@digitel.com.br>
Hi Ricardo,
> > Hi everybody,
> >
> > I need to generate a break on a CPM2 SMC serial port (same issue with SCC
> > serial ports).
> >
> > The tcsendbreak() man page states that the function should generate a
> > break between 250ms and 500ms, but testing showed that the break is one
> > character long (10 bits in 8N1 mode).
>
> [snip]
>
> > CPM_CR_STOP_TX is documented to generate a break of BRKCR characters. The
> > BRKCR register is initialized to 1, so only 1 break character is sent,
> > which won't last between 250ms and 500ms.
>
> [snip]
>
> > Could anyone think of a proper solution which would not disturb the other
> > drivers too much ?
>
> Well, one could always set the BRKCR parameter to the maximum number of
> break characters permitted by it's size, since the break condition will
> anyway end as soon as the RESTART TX command is issued as a consequence of
> the tty->driver->break_ctl(tty, 0) call. But I did not test this.
That's a very good idea, but the documentation is a bit misleading here. I
tested the CPM2 behaviour, and found out that the break will last BRKCR
characters, even if a RESTART TX command is sent sooner.
The user manual states
"The SMC sends a programmable number of break characters according to BRKCR
and reverts to idle or sends data if a RESTART TRANSMIT is issued before
completion."
I suppose they meant that, if a RESTART TX command is issued before completion
of the break sequence, the SMC will send data at the end of the break
sequence. This is at least the behaviour I noticed after trying your idea.
Laurent Pinchart
next prev parent reply other threads:[~2006-10-27 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 8:02 CPM2 SCC/SMC break handling broken Laurent Pinchart
2006-10-26 21:18 ` Ricardo Scop
2006-10-27 9:01 ` Laurent Pinchart [this message]
2006-10-27 18:20 ` Ricardo Scop
2006-10-30 15:23 ` Laurent Pinchart
2006-10-30 15:40 ` Vitaly Bordug
2006-10-30 21:52 ` Ricardo Scop
2006-10-31 7:58 ` [PATCH] CPM UART: Fix break generation Laurent Pinchart
2006-10-31 9:04 ` Pantelis Antoniou
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=200610271101.38911.laurent.pinchart@tbox.biz \
--to=laurent.pinchart@tbox.biz \
--cc=linuxppc-embedded@ozlabs.org \
--cc=scop@digitel.com.br \
/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).