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 13:34:26 +0400	[thread overview]
Message-ID: <acd2a5930608190234y4b4bee8dqfc17d109f86d4318@mail.gmail.com> (raw)
In-Reply-To: <20060819090427.GB25767@flint.arm.linux.org.uk>

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.
I'd rather put it into include/asm-mips/mach-pnx8550 but it's gonna be
shared between this and other similar SoCs (when/if they are submitted
into mainline) so I'm not sure about that either.

> > +
> > +#include <asm/io.h>
> > +#include <asm/irq.h>
> > +
> > +#include <uart.h>
>
> What is uart.h?  It isn't in this patch, neither is it part of mainline.
I guess it's include/asm-mips/arch-pnx8550/uart.h, but it is not
needed and will be removed in the next version :)


> Still not using read_status_mask here, as detailed in my previous review.
>
>                         status &= sport->port.read_status_mask;
>
> is what's missing.

Oh, got it now, thanks.

> > +     /*
> > +      * 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.

> > +     if (termios->c_iflag & IGNBRK) {
> > +             sport->port.ignore_status_mask |=
> > +                     ISTAT_TO_SM(PNX8XXX_UART_INT_BREAK);
> > +             /*
> > +              * If we're ignoring parity and break indicators,
> > +              * ignore overruns too (for real raw support).
> > +              */
> > +             if (termios->c_iflag & IGNPAR)
> > +                     sport->port.ignore_status_mask |=
> > +                             ISTAT_TO_SM(PNX8XXX_UART_INT_RXOVRN);
> > +     }
>
> How about CREAD support?

I'll add it to the new version.

Vitaly

  reply	other threads:[~2006-08-19  9:34 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 [this message]
2006-08-19  9:52     ` Russell King
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=acd2a5930608190234y4b4bee8dqfc17d109f86d4318@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®