From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 2/2] tt01: add MMC support
Date: Wed, 18 Jan 2012 13:37:31 +0100 [thread overview]
Message-ID: <4F16BD0B.9040200@denx.de> (raw)
In-Reply-To: <1326883264-21618-2-git-send-email-helmut.raiger@hale.at>
On 18/01/2012 11:41, Helmut Raiger wrote:
> board_mmc_init() initializes the pins of SDHC1 and
> turns on V_MMC1 of the PMIC. Config adds support for EXT2
> and FAT.
>
> Signed-off-by: Helmut Raiger <helmut.raiger@hale.at>
> ---
Hi Helmut,
> +#ifdef CONFIG_CONSOLE_EXTRA_INFO
> +void video_get_info_str(int line_number, char *info)
This has nothing with MCC. Please extend your commit message to explain
you are also adding this feature.
> +{
> + u32 srev = get_cpu_rev();
> +
> + switch (line_number) {
> + case 2:
> + sprintf(info, " CPU : Freescale i.MX31 rev %d.%d%s at %d MHz",
> + (srev & 0xF0) >> 4, (srev & 0x0F),
> + ((srev & 0x8000) ? " unknown" : ""),
> + mxc_get_clock(MXC_ARM_CLK) / 1000000);
I know it is only one line, but it is not related to your board because
it is really print_cpuinfo() into a buffer. So this cpu part should be
moved into the SOC place (arch/arm/cpu/arm1136/mx31/generic.c).
However, which is the real reason to do that ? I have supposed that
setting video as stdout it is enough to redirect all output to the LCD,
and then the usual print_cpuinfo() works, without adding / duplicating
function that already use printf() for the output.
I do not see a lot of boards implementing video_get_info_str(), and I
understand that it is a way to customize the output. However, is it the
correct way ? Does print_cpuinfo() not work if redirect to the video ? I
have added Anatolji (video maintainer in CC) to get his opinion.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2012-01-18 12:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 16:45 [U-Boot] [PATCH] mmc: access mxcmmc from mx31 boards Helmut Raiger
2011-10-25 9:43 ` Stefano Babic
2011-10-27 12:19 ` [U-Boot] [PATCH V2] " Helmut Raiger
2011-11-02 7:02 ` [U-Boot] [PATCH V2] imx: " Helmut Raiger
2011-11-07 7:59 ` Helmut Raiger
2011-11-07 9:04 ` Stefano Babic
2011-11-14 9:06 ` Helmut Raiger
2011-11-14 10:55 ` Stefano Babic
2011-11-14 15:37 ` Helmut Raiger
2012-01-11 13:59 ` [U-Boot] [PATCH V3] " Helmut Raiger
2012-01-11 13:59 ` [U-Boot] [PATCH 1/2] " Helmut Raiger
2012-01-13 8:28 ` Stefano Babic
2012-01-17 9:56 ` Stefano Babic
2012-01-11 13:59 ` [U-Boot] [PATCH 2/2] tt01: add MMC support Helmut Raiger
2012-01-12 10:15 ` [U-Boot] [PATCH 2/2] imx: " Helmut Raiger
2012-01-13 8:32 ` [U-Boot] [PATCH 2/2] " Stefano Babic
2012-01-16 11:10 ` [U-Boot] [PATCH V2] " Helmut Raiger
2012-01-16 11:10 ` [U-Boot] [PATCH 1/2] fsl_pmic.h: add regulator mode 0 and 1 bits Helmut Raiger
2012-01-17 10:12 ` Stefano Babic
2012-01-18 10:41 ` [U-Boot] [PATCH V3 1/2] mc13783.h: create and add regulator mode 0 and 1 Helmut Raiger
2012-01-18 10:41 ` [U-Boot] [PATCH V3 2/2] tt01: add MMC support Helmut Raiger
2012-01-18 12:37 ` Stefano Babic [this message]
2012-01-19 7:21 ` Helmut Raiger
2012-01-19 7:27 ` [U-Boot] [PATCH V4] " Helmut Raiger
2012-01-30 14:35 ` Stefano Babic
2012-01-30 14:38 ` [U-Boot] [PATCH V3 1/2] mc13783.h: create and add regulator mode 0 and 1 Stefano Babic
2012-01-16 11:10 ` [U-Boot] [PATCH 2/2] tt01: add MMC support Helmut Raiger
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=4F16BD0B.9040200@denx.de \
--to=sbabic@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;
as well as URLs for NNTP newsgroup(s).