From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] serial: ns16550: Add register shift variable
Date: Mon, 16 Jul 2018 14:42:48 +0200 [thread overview]
Message-ID: <20180716124248.1872E24015D@gemini.denx.de> (raw)
In-Reply-To: <1b0d33fa-adfb-9825-5ae8-8bded1678c0c@ltec.ch>
Dear Felix,
In message <1b0d33fa-adfb-9825-5ae8-8bded1678c0c@ltec.ch> you wrote:
>
> >> This needs to be rewritten.
> >
> > To try and help clarify, the property in question means "quantity to
> > shift the register offsets by." It should be clear in our Kconfig help
> > entry as well that this is what we're looking for.
> >
> Thanks for this! The help text will be fixed in v2.
None of the places I could find in the Linux
Documentation/devicetree/bindings directory actually explains what
"shift the register offsets" means. Only the code reveals that
this means a LEFT shift of the register address (offset).
At least one place in Linux interprets <reg-shift> differently; here
it operates on the _data_ (instead there they use <reg-spacing>):
"devicetree/bindings/ipmi/ipmi-smic.txt":
- reg-shift - The amount to shift the registers to the right to get the data
into bit zero.
(see ipmi_si_mem_io.c
So can we please add an explanation what _exactly_ this means?
Thanks.
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
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
It is easier to write an incorrect program than understand a correct
one.
next prev parent reply other threads:[~2018-07-16 12:42 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 [this message]
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
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=20180716124248.1872E24015D@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