mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Subject: [PATCH v4 0/2] ns16550-related patches
Date: Wed, 18 Jan 2012 10:31:52 +0400	[thread overview]
Message-ID: <1326868316-29385-1-git-send-email-antonynpavlov@gmail.com> (raw)

This patch series consist of two ns16550-related patches.

[PATCH v4 1/4] ns16550: support for UART with broken FIFO
[PATCH v4 2/4] ns16550: make ns16550_serial_init_port() shorter
[PATCH v4 3/4] ns16550: write zero to ier only once
[PATCH v4 4/4] ns16550: fix ier selection

The 1st one adds the flag (NS16650_FLAG_DISABLE_FIFO) in internal
ns16550 data structure to recognise UART with broken FIFO
(or UART without FIFO at all) and the code to use this flag.
The flag can be set in board-related code.

The 2nd one use the fact that ns16550_serial_init_port() and
ns16550_setbaudrate() functions have many common code.
It change the most of ns16550_serial_init_port() code for
one ns16550_setbaudrate() call.

The 3rd one removes unnecessary interrupt disable on every
speed change operation.

The 4th one adds explicit IER register selection before accessing it.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-01-18  6:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18  6:31 Antony Pavlov [this message]
2012-01-18  6:31 ` [PATCH v4 1/4] ns16550: support for UART with broken FIFO Antony Pavlov
2012-01-18  6:31 ` [PATCH v4 2/4] ns16550: make ns16550_serial_init_port() shorter Antony Pavlov
2012-01-18  6:31 ` [PATCH v4 3/4] ns16550: write zero to ier only once Antony Pavlov
2012-01-18  6:31 ` [PATCH v4 4/4] ns16550: fix ier selection Antony Pavlov

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=1326868316-29385-1-git-send-email-antonynpavlov@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.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