From: Dirk Behme <dirk.behme@de.bosch.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] i.MX6: mx6q_sabrelite: add SATA bindings
Date: Wed, 14 Mar 2012 15:53:12 +0100 [thread overview]
Message-ID: <4F60B0D8.7020907@de.bosch.com> (raw)
In-Reply-To: <1331657978-19270-1-git-send-email-eric.nelson@boundarydevices.com>
On 13.03.2012 17:59, Eric Nelson wrote:
...
> --- a/board/freescale/mx6qsabrelite/mx6qsabrelite.c
> +++ b/board/freescale/mx6qsabrelite/mx6qsabrelite.c
...
> + /* Enable sata clock */
> + reg = readl(&imx_ccm->CCGR5); /* CCGR5 */
> + reg |= MXC_CCM_CCGR5_CG2_MASK;
> + writel(reg, &imx_ccm->CCGR5);
We touch the CCGR5 already in the imximage.cfg. So we could drop this
code completely and just add the MXC_CCM_CCGR5_CG2_MASK to the imximage.cfg.
What are the advantages/disadvantages of this?
Advantages:
Less code, touch the register only once in imximage.cfg.
Disadvantages:
Less readability, doing it in setup_sata() instead of imximage.cfg is
easier to understand and disable (by removing CONFIG_CMD_SATA).
Opinions?
It sounds like this results in the basic question: Which registers
should be touched in imximage.cfg, and which by explicit code in
drivers/board files?
Best regards
Dirk
next prev parent reply other threads:[~2012-03-14 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <http://lists.denx.de/pipermail/u-boot/2012-March/#119234>
2012-03-13 16:59 ` [U-Boot] [PATCH V2] i.MX6: mx6q_sabrelite: add SATA bindings Eric Nelson
2012-03-14 14:53 ` Dirk Behme [this message]
2012-03-15 8:28 ` Stefano Babic
2012-03-15 9:34 ` Liu Hui-R64343
2012-03-15 9:58 ` Stefano Babic
2012-03-24 7:09 ` Dirk Behme
2012-03-24 8:19 ` stefano babic
2012-03-24 21:01 ` Eric Nelson
2012-03-25 10:17 ` Stefano Babic
2012-03-25 15:33 ` Eric Nelson
2012-03-24 20:41 ` Eric Nelson
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=4F60B0D8.7020907@de.bosch.com \
--to=dirk.behme@de.bosch.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.