From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] serial: ns16550: Add register shift variable
Date: Tue, 17 Jul 2018 09:39:34 -0400 [thread overview]
Message-ID: <20180717133934.GA3196@bill-the-cat> (raw)
In-Reply-To: <c15fe0e5-0abc-9c45-d4d5-c5c2dd624b9e@suse.de>
On Tue, Jul 17, 2018 at 03:33:15PM +0200, Alexander Graf wrote:
> On 07/17/2018 03:25 PM, Tom Rini wrote:
> >On Mon, Jul 16, 2018 at 02:53:26PM +0200, Alexander Graf wrote:
> >>On 07/14/2018 05:49 PM, Tom Rini wrote:
> >>>On Sat, Jul 14, 2018 at 12:47:21PM +0200, Wolfgang Denk wrote:
> >>>>Dear Felix,
> >>>>
> >>>>In message <1531492980-16543-1-git-send-email-fb@ltec.ch> you wrote:
> >>>>>The motivation for writing this patch originates in the
> >>>>>effort of synchronizing U-Boot DT to Linux DT for am33xx SOCs.
> >>>>>The current am33xx.dtsi file from U-Boot defines the <reg-shift>
> >>>>>property for all UART nodes. The actual (4.18+) am33xx.dtsi
> >>>>>file from Linux does not define <reg-shift> anymore. To prevent
> >>>>>(probably difficult) changes in many .dts and .dtsi files once
> >>>>>the synchronization is done, one can use this new variable. For
> >>>>>the pdu001 board, for example, SYS_NS16550_REG_SHIFT is set
> >>>>>to 2; no need to clutter U-Boot and board specific dts files
> >>>>>with <reg-shift> properties.
> >>>>Does this mean that U-Boot will not be able to use the same DTB as
> >>>>Linux?
> >>>To be clear, it's the other way around. We can't use the Linux dtb/dts
> >>>files as they've dropped (and in other cases, aren't adding) these
> >>>properties as it's handled differently.
> >>What does "differently" mean? Linux tries quite hard to be platform
> >>agnostic, so a per-build-target #define surely isn't what they're doing.
> >Yes, what exactly is the Linux kernel doing here?
>
> Linux has a completely separate driver for omap3 (which is wrong too). But
> in a nutshell, it basically determines the shift value by the "compatible"
> string, so we should too.
Yes and no. For a number of years now the omap-only (ttyOx) driver has
been deprecated and the generic ns1665x driver is valid. What does the
ns1655x driver do here?
--
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/20180717/8411e0f6/attachment.sig>
next prev parent reply other threads:[~2018-07-17 13:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 14:43 [U-Boot] [PATCH] serial: ns16550: Add register shift variable Felix Brack
2018-07-13 15:08 ` Alexander Graf
2018-07-14 10:47 ` Wolfgang Denk
2018-07-14 15:49 ` Tom Rini
2018-07-15 8:43 ` Alexey Brodkin
2018-07-15 14:02 ` Felix Brack
2018-07-16 15:04 ` Alexey Brodkin
2018-07-16 15:47 ` Andy Shevchenko
2018-07-17 13:24 ` Tom Rini
2018-07-17 6:51 ` Felix Brack
2018-07-17 13:34 ` Alexander Graf
2018-07-15 11:17 ` Felix Brack
2018-07-16 12:42 ` Wolfgang Denk
2018-07-16 12:48 ` Felix Brack
2018-07-16 12:53 ` Alexander Graf
2018-07-17 13:25 ` Tom Rini
2018-07-17 13:33 ` Alexander Graf
2018-07-17 13:34 ` Alexey Brodkin
2018-07-17 13:41 ` Tom Rini
2018-07-17 13:43 ` Alexander Graf
2018-07-18 8:26 ` Lokesh Vutla
2018-07-17 21:23 ` Andy Shevchenko
2018-07-17 21:30 ` Adam Ford
2018-07-17 21:46 ` Andy Shevchenko
2018-07-17 13:39 ` Tom Rini [this message]
2018-07-15 11:05 ` Felix Brack
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=20180717133934.GA3196@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