mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vitaly Wool" <vitalywool@gmail.com>
To: "Vitaly Wool" <vitalywool@gmail.com>,
	jean-paul.saman@philips.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC] UART driver for PNX8550/8950 revised
Date: Sat, 19 Aug 2006 15:32:16 +0400	[thread overview]
Message-ID: <acd2a5930608190432l17c4afebqcc5a941c8e81ebb5@mail.gmail.com> (raw)
In-Reply-To: <20060819095210.GD25767@flint.arm.linux.org.uk>

On 8/19/06, Russell King <rmk+lkml@arm.linux.org.uk> wrote:

> > >This comment's not correct - where is the break condition disabled?
> > >I thought it might be in the next serial_out() but it seems to be
> > >missing from there as well?
> >
> > I don't think you're right here - break condition is also disabled
> > unsetting the corresponding bit in  IEN register for this particular
> > UART.
>
> Hmm, in that case why does break_ctl do this:
>
> +       lcr = serial_in(sport, PNX8XXX_LCR);
> +       if (break_state == -1)
> +               lcr |= PNX8XXX_UART_LCR_TXBREAK;
> +       else
> +               lcr &= ~PNX8XXX_UART_LCR_TXBREAK;
> +       serial_out(sport, PNX8XXX_LCR, lcr);
>
> which appears to imply that the bit for the break state is in the LCR.
> Moreover, there isn't a PNX8XXX_INT_* bit defined for break.  Confused.

Yeah, looking more attentively into docs, I must admit that you're
right here, and I'm wrong.

Vitaly

      reply	other threads:[~2006-08-19 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-19  8:26 Vitaly Wool
2006-08-19  9:04 ` Russell King
2006-08-19  9:34   ` Vitaly Wool
2006-08-19  9:52     ` Russell King
2006-08-19 11:32       ` Vitaly Wool [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=acd2a5930608190432l17c4afebqcc5a941c8e81ebb5@mail.gmail.com \
    --to=vitalywool@gmail.com \
    --cc=jean-paul.saman@philips.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®