From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: 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 10:52:10 +0100 [thread overview]
Message-ID: <20060819095210.GD25767@flint.arm.linux.org.uk> (raw)
In-Reply-To: <acd2a5930608190234y4b4bee8dqfc17d109f86d4318@mail.gmail.com>
On Sat, Aug 19, 2006 at 01:34:26PM +0400, Vitaly Wool wrote:
> Hello Russell,
> >serial_pnx8xxx.h just contains structure and register definitions for
> >this driver - wouldn't it make more sense for it to be in drivers/serial
> >along side this driver?
>
> Well it's used in arch/mips/philips/... so I doubt it's a right thing
> to move it to drivers/serial.
Okay, then it should stay where it is.
> >> + /*
> >> + * Disable all interrupts, port and break condition.
> >> + */
> >> + serial_out(sport, PNX8XXX_IEN, 0);
> >
> >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.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-08-19 9:52 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 [this message]
2006-08-19 11:32 ` Vitaly Wool
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=20060819095210.GD25767@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=jean-paul.saman@philips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vitalywool@gmail.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
all inboxes | Powered by JetHome®