From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] serial: ns16550: Add register shift variable
Date: Tue, 17 Jul 2018 09:21:39 -0400 [thread overview]
Message-ID: <20180717132139.GA10857@bill-the-cat> (raw)
In-Reply-To: <4881796E12491D4BB15146FE0209CE64681150DE@DE02WEMBXB.internal.synopsys.com>
On Tue, Jul 17, 2018 at 12:45:51PM +0000, Alexey Brodkin wrote:
> Hi Felix,
>
> > -----Original Message-----
> > From: Felix Brack [mailto:fb at ltec.ch]
> > Sent: Tuesday, July 17, 2018 3:13 PM
> > To: Alexander Graf <agraf@suse.de>; Lokesh Vutla <lokeshvutla@ti.com>; u-boot at lists.denx.de
> > Cc: Wolfgang Denk <wd@denx.de>; Tom Rini <trini@konsulko.com>; Marek Vasut <marek.vasut@gmail.com>; Patrice Chotard
> > <patrice.chotard@st.com>; Michal Simek <michal.simek@xilinx.com>; Simon Glass <sjg@chromium.org>; Alexey Brodkin
> > <Alexey.Brodkin@synopsys.com>; Bin Meng <bmeng.cn@gmail.com>; Ley Foon Tan <ley.foon.tan@intel.com>; Patrick Delaunay
> > <patrick.delaunay@st.com>; Mario Six <mario.six@gdsys.cc>; Stefan Roese <sr@denx.de>; Bernhard Messerklinger
> > <bernhard.messerklinger@br-automation.com>
> > Subject: Re: [PATCH v2] serial: ns16550: Add register shift variable
>
> [snip]
>
> > Adding a separate PORT in ns16550_serial_ids for a particular
> > architecture, platform or SoC would be an option. However the patch I
> > posted is much more generic as it offers to set the reg-shift property
> > for no matter what architecture, platform or SoC. It can also easily be
> > extended by adding more conditional defaults to the Kconfig file.
>
> I'd say we're dealing with just one corner-case here.
> If I understand a concept of Device Tree it is supposed to describe your
> hardware. Thus if reg shift exists in your HW it should be explicitly mentioned in
> your .dts. If for some [historical] reason you have to deal with "incorrect" .dts then
> I'd prefer to have mentioned quirk with a separate PORT in ns16550_serial_ids
> instead of adding yet another Kconfig option.
So, this is part of the problem I suppose. I don't know _why_ we can't
just add the correct and valid reg-shift property to the dtsi file in
Linux and be done with it. Then the U-Boot driver would work because we
parse that property.
--
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/086be57d/attachment.sig>
next prev parent reply other threads:[~2018-07-17 13:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 7:02 [U-Boot] [PATCH v2] serial: ns16550: Add register shift variable Felix Brack
2018-07-17 7:55 ` Lokesh Vutla
2018-07-17 9:12 ` Alexander Graf
2018-07-17 9:21 ` Lokesh Vutla
2018-07-17 9:27 ` Alexander Graf
2018-07-17 9:31 ` Lokesh Vutla
2018-07-17 12:12 ` Felix Brack
2018-07-17 12:45 ` Alexey Brodkin
2018-07-17 13:21 ` Tom Rini [this message]
2018-07-17 13:34 ` Felix Brack
2018-07-17 13:38 ` Alexander Graf
2018-07-17 13:45 ` Tom Rini
2018-07-17 12:22 ` 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=20180717132139.GA10857@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