public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] serial: ns16550: fix different reg size access
Date: Fri, 01 Apr 2011 21:04:41 +0200	[thread overview]
Message-ID: <20110401190442.05D41142E074@gemini.denx.de> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D19F9A29D36@SC-VEXCH4.marvell.com>

Dear Prafulla Wadaskar,

In message <F766E4F80769BD478052FB6533FA745D19F9A29D36@SC-VEXCH4.marvell.com> you wrote:
> 
> 1. ns16550 is standard IP used across several SoC and has driver in place.
> 2. Your specific implementation of the same IP on your specific SoC need
> bit9 or x register to be set to 0 to work this IP correctly on your h/w.
> 3. but doing in ns16550 driver may brake other implementations.

Right.

> (correct me if I am wrong)
>
> So what I suggest here-
> 1. do not disturb/touch nx16550 driver at all.
> 2. write a small init code in cpu.c (specific to this SoC/arch) to reset this bit only.

Sorry, but I dislike this approach.  I think it would be better to
provide a proper driver infrastructure for this type of UART, as it
might be used in other appliances, and it is a good idea to keep all
related code parts together in one driver file.

Here is what I suggested (I think I repeat it the 3rd time now):

| 2) If you have additional, non-standard bits in your device, you must
|    initialize these separately.  Eventually you provide a custom
|    driver which just calls the standard NS16550 driver functions,
|    except where you have additional need to manipulate the extra,
|    non-standard bits of your device.

Thanks.

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
About the use of language: it is impossible to sharpen a pencil  with
a  blunt  ax.  It is equally vain to try to do it with ten blunt axes
instead.                                           -- Edsger Dijkstra

      reply	other threads:[~2011-04-01 19:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 15:52 [U-Boot] [PATCH] serial: ns16550: fix different reg size access Lei Wen
2011-03-31 15:58 ` Wolfgang Denk
2011-04-01  5:24   ` Lei Wen
2011-04-01  5:35     ` Wolfgang Denk
2011-04-01  5:39       ` Lei Wen
2011-04-01  7:39         ` Wolfgang Denk
2011-04-01  7:59           ` Lei Wen
2011-04-01 10:25             ` Wolfgang Denk
2011-04-01 12:03               ` Lei Wen
2011-04-01 12:41                 ` Wolfgang Denk
2011-04-01 13:07                   ` Lei Wen
2011-04-01 13:55                     ` Wolfgang Denk
2011-04-01 13:58                       ` Lei Wen
2011-04-01 14:25                         ` Wolfgang Denk
2011-04-01 14:34                           ` Lei Wen
2011-04-01 17:45                             ` Wolfgang Denk
2011-04-01 18:59                             ` Prafulla Wadaskar
2011-04-01 19:04                               ` Wolfgang Denk [this message]

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=20110401190442.05D41142E074@gemini.denx.de \
    --to=wd@denx.de \
    --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