public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/5] serial: zynq: Fix serial driver
Date: Thu, 14 Jun 2018 11:32:53 +0200	[thread overview]
Message-ID: <cover.1528968775.git.michal.simek@xilinx.com> (raw)

Hi,

this series contain some changes in this driver.
1. Coding style fixes - using BIT macro
2. Using output fifo more effectively
3. Avoid initialization after relocation again
4. Make sure that priv is valid all the time
5. Keep sparse happy

Thanks,
Michal



Michal Simek (5):
  serial: zynq: Use BIT macros instead of shifts and full hex numbers
  serial: zynq: Write chars till output fifo is full
  serial: zynq: Initialize uart only before relocation
  serial: zynq: Check priv pointer get via dev_get_priv()
  serial: zynq: Make zynq_serial_setbrg static

 drivers/serial/serial_zynq.c | 51 +++++++++++++++++++++++++++++++++-----------
 1 file changed, 39 insertions(+), 12 deletions(-)

-- 
1.9.1

             reply	other threads:[~2018-06-14  9:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-14  9:32 Michal Simek [this message]
2018-06-14  9:32 ` [U-Boot] [PATCH 1/5] serial: zynq: Use BIT macros instead of shifts and full hex numbers Michal Simek
2018-06-14 12:58   ` Simon Glass
2018-06-14  9:32 ` [U-Boot] [PATCH 2/5] serial: zynq: Write chars till output fifo is full Michal Simek
2018-06-14 12:58   ` Simon Glass
2018-06-14  9:32 ` [U-Boot] [PATCH 3/5] serial: zynq: Initialize uart only before relocation Michal Simek
2018-06-14 12:58   ` Simon Glass
2018-06-14  9:32 ` [U-Boot] [PATCH 4/5] serial: zynq: Check priv pointer get via dev_get_priv() Michal Simek
2018-06-14 12:58   ` Simon Glass
2018-06-14 13:05     ` Michal Simek
2018-06-14 14:16       ` Simon Glass
2018-06-15  6:11         ` Michal Simek
2018-06-15  7:33         ` Michal Simek
2018-06-14  9:32 ` [U-Boot] [PATCH 5/5] serial: zynq: Make zynq_serial_setbrg static Michal Simek
2018-06-14 12:58   ` Simon Glass

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=cover.1528968775.git.michal.simek@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox