linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: scottwood@freescale.com, linuxppc-dev@ozlabs.org,
	linux-serial@vger.kernel.org
Subject: Re: [PATCHv2] cpm_uart: Fix break generation
Date: Thu, 24 Jul 2008 17:52:39 +0200	[thread overview]
Message-ID: <200807241752.42543.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <EFAF51F5-D2A4-4A8F-AB94-0A746B67E190@kernel.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

On Thursday 24 July 2008, Kumar Gala wrote:
> 
> On Jul 24, 2008, at 9:21 AM, Laurent Pinchart wrote:
> 
> > When generating a break condition on a serial port, the CPM must be  
> > told beforehand how long the break should be. Unfortunately, this  
> > information is not available through the current serial break handling
> > API. This patch works around the problem by requesting a 32767 characters
> > break followed by a 0 characters break after the requested duration. The
> > CPM will stop the first break when the second one is requested. This might
> > not work with future CPM revisions.
> 
> What do you mean by future CPM revision?  Do you mean QE?

I was thinking about minor revisions of the CPM2 silicon as described in http://www.freescale.com/files/32bit/doc/app_note/AN2291.pdf

-- 
Laurent Pinchart
CSE Semaphore Belgium

Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium

T +32 (2) 387 42 59
F +32 (2) 387 42 75

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2008-07-24 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 11:38 [RFC] cpm_uart: Fix break generation Laurent Pinchart
2008-07-24 14:21 ` [PATCHv2] " Laurent Pinchart
2008-07-24 15:14   ` Kumar Gala
2008-07-24 15:52     ` Laurent Pinchart [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=200807241752.42543.laurentp@cse-semaphore.com \
    --to=laurentp@cse-semaphore.com \
    --cc=galak@kernel.crashing.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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).