From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] mpc83xx: update LCRR register handling
Date: Thu, 27 Aug 2009 13:11:25 +0200 [thread overview]
Message-ID: <m2fxbdzf36.fsf@ohwell.denx.de> (raw)
In-Reply-To: <20090826173628.ddb2bdd4.kim.phillips@freescale.com> (Kim Phillips's message of "Wed, 26 Aug 2009 17:36:28 -0500")
Hi Kim,
> o LCRR_PDYP, granted dangerous in your case, is obviously a writeable
> bit (not read-only), and documented as such in later documentation. In
> fact, there are no non-writeable bits in LCRR.
Well, "reserved" != "non-writable" (usually there is a comment that
writing reserved bits produces undefined behaviour) so I agree with
Heiko that as long the documentation that we have access to, designates
bits as reserved, it makes sense to have such a mask.
> o the user loses visibility into what is going on if they
> decide to drop/add sensitive bits such as LCRR_DBYP in their board's
> CONFIG_SYS_LCRR settings, and there's a mask lurking in the background.
>
> o let's be practical here - in a board port, LCRR settings have to be
> paid attention to, no matter what hidden behaviours or new bits there
> are lying underneath - perhaps the form of 'protection' you seek is in
> the form of a comment in the code?
So what is it that you propose? That Heiko uses a LCRR in his board
config (over-)writing reserved bits?
Cheers
Detlev
--
vi vi vi - the roman numeral of the beast.
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2009-08-27 11:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 9:05 [U-Boot] mpc83xx: update LCRR register handling Heiko Schocher
2009-08-25 9:14 ` Liu Dave-R63238
2009-08-25 11:31 ` [U-Boot] [PATCH v2] " Heiko Schocher
2009-08-25 12:19 ` Liu Dave-R63238
2009-08-25 15:39 ` Kim Phillips
2009-08-26 6:28 ` Heiko Schocher
2009-08-26 22:36 ` Kim Phillips
2009-08-27 6:20 ` [U-Boot] [PATCH v3] " Heiko Schocher
2009-08-27 11:41 ` Jerry Van Baren
2009-08-27 20:53 ` Kim Phillips
2009-09-16 4:51 ` Kumar Gala
2009-09-25 23:19 ` [U-Boot] [PATCH] mpc83xx: retain POR values of non-configured ACR, SPCR, SCCR, and LCRR bitfields (was: Re: [PATCH v3] mpc83xx: update LCRR register handling) Kim Phillips
2009-09-26 10:37 ` [U-Boot] [PATCH] mpc83xx: retain POR values of non-configured ACR, SPCR, SCCR, and LCRR bitfields Heiko Schocher
2009-09-27 1:46 ` Kim Phillips
2009-09-27 1:54 ` Kim Phillips
2009-08-27 11:11 ` Detlev Zundel [this message]
2009-08-27 20:49 ` [U-Boot] [PATCH v2] mpc83xx: update LCRR register handling Kim Phillips
2009-08-28 10:36 ` Detlev Zundel
2009-08-28 12:02 ` Wolfgang Denk
2009-08-28 16:01 ` Kim Phillips
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=m2fxbdzf36.fsf@ohwell.denx.de \
--to=dzu@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