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 15:55:19 +0200	[thread overview]
Message-ID: <20110401135519.7271CF0320A@gemini.denx.de> (raw)
In-Reply-To: <AANLkTinqAyDx7=61FMgPdCg3ULt9nk93jF-y0Sdi=5uX@mail.gmail.com>

Dear Lei Wen,

In message <AANLkTinqAyDx7=61FMgPdCg3ULt9nk93jF-y0Sdi=5uX@mail.gmail.com> you wrote:
>
> >> I think my code also could handle this. They only could set the
> >> CONFIG_SYS_NS16550_REG_SIZE =A0to be 1
> >> and CONFIG_SYS_NS16550_MAX_REG_SIZE to be 4. Then
> >> the other bits is untouched by this driver.
> >
> > I don't think so. You still use just a single writel() call then. =A0To
> > leave the other bits untouched, you would have to perform a readl()
> > first, then insert one data byte, and then write it back. =A0Your patch
> > does not do that.
> 
> My original patch is like below, so where it call writel?...
> +#elif (CONFIG_SYS_NS16550_REG_SIZE == 1) || (CONFIG_SYS_NS16550_REG_SIZE == -1)
> +#ifdef CONFIG_SYS_NS16550_PORT_MAPPED
> +#define serial_out(x, y)       outb(x, y)
> +#define serial_in(y)           inb(y)
> +#else
> +#define serial_out(x, y)       writeb(x, y)
> +#define serial_in(y)           readb(y)

If you use writeb() [as the current driver would do as well}, then how
do you expect to set this bit 8 (which is in the next byte) to 0 as
you claim you have to?

Either I don't understand what you want, or you don't understand how
the ns16550 driver works.

I can see no shortcomings in the existent driver, thus no need to
make it more complicated than it already is.


Best regards,

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
Time is a drug. Too much of it kills you.
                                      - Terry Pratchett, _Small Gods_

  reply	other threads:[~2011-04-01 13:55 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 [this message]
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

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=20110401135519.7271CF0320A@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