public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 1/4] serial: ns16550: da8xx (freon/primus) is not omap-like
Date: Fri, 19 Jan 2018 15:22:24 -0500	[thread overview]
Message-ID: <20180119202224.GY4660@bill-the-cat> (raw)
In-Reply-To: <CAALWOA8edyojGKKuZLwfv+Xz_1Q5r7aOgg7E5muitDMJXo9ctA@mail.gmail.com>

On Fri, Jan 19, 2018 at 05:39:32PM +0100, Matthijs van Duin wrote:
> On 19 January 2018 at 16:41, Tom Rini <trini@konsulko.com> wrote:
> > OK.  For v2, if you can convert CONFIG_SYS_NS16550_MEM32 to Kconfig as
> > well I'd appreciate it.
> 
> I'm not hugely comfortable doing that, since that would affect even
> more targets. To be honest, I don't understand why it even exists as a
> separate var instead of just testing whether
> CONFIG_SYS_NS16550_REG_SIZE is 4 or -4. Are there actually some crazy
> targets that allocate 4 bytes per register yet fail if you use 32-bit
> access?

It's most likely a case that just wasn't cleaned up.  If you want to
correct things by dropping CONFIG_SYS_NS16550_MEM32 and checking
CONFIG_SYS_NS16550_REG_SIZE instead, that's fine.

> Would you object hugely to me just implicitly setting
> CONFIG_SYS_NS16550_MEM32 in ns16550.h for the c6x uart variant? I
> think it makes a lot of sense to do so, since in that case the driver
> itself explicitly depends on being able to write a value that doesn't
> fit in a byte.

Well, it's just SOC_DA8XX that isn't doing it today, and we need to
migrate that CONFIG symbol or do away with it.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180119/b0fa3e1a/attachment.sig>

  reply	other threads:[~2018-01-19 20:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 12:50 [U-Boot] [PATCH 1/4] serial: ns16550: da8xx (freon/primus) is not omap-like Matthijs van Duin
2018-01-19 15:26 ` [U-Boot] [U-Boot, " Tom Rini
2018-01-19 15:39   ` Matthijs van Duin
2018-01-19 15:41     ` Tom Rini
2018-01-19 16:39       ` Matthijs van Duin
2018-01-19 20:22         ` Tom Rini [this message]
2018-01-19 20:34           ` Adam Ford

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=20180119202224.GY4660@bill-the-cat \
    --to=trini@konsulko.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