From: Arnd Bergmann <arnd@arndb.de>
To: Roland Stigge <stigge@antcom.de>
Cc: srinivas.bakki@nxp.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, kevin.wells@nxp.com,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, alan@linux.intel.com
Subject: Re: [PATCH RFC] serial/8250: Adjusting FIFO parameters for LPC32xx
Date: Sun, 27 May 2012 02:32:57 +0000 [thread overview]
Message-ID: <201205270232.58253.arnd@arndb.de> (raw)
In-Reply-To: <1338048678-23991-1-git-send-email-stigge@antcom.de>
On Saturday 26 May 2012, Roland Stigge wrote:
> Hi,
>
> this is how the modified FIFO is handled in the repositories at
> git.lpclinux.com. Is there a better way for doing this (without ifdef)? Looks
> like registering additional types (like PORT_16550A) isn't encouraged. Maybe
> extending of_serial.c? The latter currently doesn't handle .fifosize and
> .tx_loadsz, though.
>
> Any suggestions appreciated.
We occasionally add new types, and I think that would be ok here too, if it's
actually a new type. It definitely doesn't look like a 16550.
I wonder if it's in fact a PORT_16654, or if we can at least pretend it's one.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] serial/8250: Adjusting FIFO parameters for LPC32xx
Date: Sun, 27 May 2012 02:32:57 +0000 [thread overview]
Message-ID: <201205270232.58253.arnd@arndb.de> (raw)
In-Reply-To: <1338048678-23991-1-git-send-email-stigge@antcom.de>
On Saturday 26 May 2012, Roland Stigge wrote:
> Hi,
>
> this is how the modified FIFO is handled in the repositories at
> git.lpclinux.com. Is there a better way for doing this (without ifdef)? Looks
> like registering additional types (like PORT_16550A) isn't encouraged. Maybe
> extending of_serial.c? The latter currently doesn't handle .fifosize and
> .tx_loadsz, though.
>
> Any suggestions appreciated.
We occasionally add new types, and I think that would be ok here too, if it's
actually a new type. It definitely doesn't look like a 16550.
I wonder if it's in fact a PORT_16654, or if we can at least pretend it's one.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Roland Stigge <stigge@antcom.de>
Cc: alan@linux.intel.com, gregkh@linuxfoundation.org,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
kevin.wells@nxp.com, srinivas.bakki@nxp.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC] serial/8250: Adjusting FIFO parameters for LPC32xx
Date: Sun, 27 May 2012 02:32:57 +0000 [thread overview]
Message-ID: <201205270232.58253.arnd@arndb.de> (raw)
In-Reply-To: <1338048678-23991-1-git-send-email-stigge@antcom.de>
On Saturday 26 May 2012, Roland Stigge wrote:
> Hi,
>
> this is how the modified FIFO is handled in the repositories at
> git.lpclinux.com. Is there a better way for doing this (without ifdef)? Looks
> like registering additional types (like PORT_16550A) isn't encouraged. Maybe
> extending of_serial.c? The latter currently doesn't handle .fifosize and
> .tx_loadsz, though.
>
> Any suggestions appreciated.
We occasionally add new types, and I think that would be ok here too, if it's
actually a new type. It definitely doesn't look like a 16550.
I wonder if it's in fact a PORT_16654, or if we can at least pretend it's one.
Arnd
next prev parent reply other threads:[~2012-05-27 2:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 16:11 [PATCH RFC] serial/8250: Adjusting FIFO parameters for LPC32xx Roland Stigge
2012-05-26 16:11 ` Roland Stigge
2012-05-27 2:32 ` Arnd Bergmann [this message]
2012-05-27 2:32 ` Arnd Bergmann
2012-05-27 2:32 ` Arnd Bergmann
2012-05-27 9:06 ` Roland Stigge
2012-05-27 9:06 ` Roland Stigge
2012-05-27 9:06 ` Roland Stigge
2012-05-27 10:23 ` Arnd Bergmann
2012-05-27 10:23 ` Arnd Bergmann
2012-05-27 10:23 ` Arnd Bergmann
2012-05-27 11:37 ` Roland Stigge
2012-05-27 11:37 ` Roland Stigge
2012-05-27 12:07 ` Arnd Bergmann
2012-05-27 12:07 ` Arnd Bergmann
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=201205270232.58253.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kevin.wells@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=srinivas.bakki@nxp.com \
--cc=stigge@antcom.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.