All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [[PATCH v2]pandaboard: 1/1] Modification of Elpida DDR2 RAM for Pandaboard-ES Rev B3
Date: Thu, 14 Nov 2013 13:41:48 -0600	[thread overview]
Message-ID: <5285277C.8050400@ti.com> (raw)
In-Reply-To: <1384423612-18697-2-git-send-email-hardik.patel@volansystech.com>

On 11/14/2013 04:06 AM, Hardik wrote:
> From: Hardik Patel <hardik.patel@volansystech.com>
Add some details about the change -> commit message is usually
suggested as a good thing to have.

[...]
> diff --git a/board/ti/panda/panda.c b/board/ti/panda/panda.c
> index c104024..5a7f80a 100644
> --- a/board/ti/panda/panda.c
> +++ b/board/ti/panda/panda.c
> @@ -122,6 +122,30 @@ int get_board_revision(void)
>  	return board_id;
>  }
>  
> +/*
> +* Routine: is_panda_es_rev_b3
> +* Description: Detect if we are running on B3 version of ES panda board,
> +*              This can be done by reading the level of GPIO 171 
> +*              and checking the processor revisions.
> +*              GPIO171: 1 => Panda ES Rev B3
> +*/

will be good to see some kernel-doc style comments here..
/**
 * u8 is_panda_es_rev_b3 - Detect if we are running on B3 version of
ES panda
 *
 * This can be done by reading the level of GPIO 171 and checking the
 * processor revisions.  GPIO171: 1 => Panda ES Rev B3 (if using OMAP4460)
 */

u8 is_panda_es_rev_b3(void)


> +u8 is_panda_es_rev_b3(void)
> +{
> +        int processor_rev = omap_revision();
> +        int ret = 0;
> +
> +        if ((processor_rev >= OMAP4460_ES1_0 &&
> +             processor_rev <= OMAP4460_ES1_1)) {
> +
> +                /* Setup the mux for the common board ID pins (gpio 171) */
> +                writew((IEN | M3), (*ctrl)->control_padconf_core_base + UNIPRO_TX0);
Could rather belong to mux code in board/ti/panda/panda_mux_data.h?

> +
> +                /* if processor_rev is panda ES and GPIO171 is 1, it is rev b3 */
> +                ret = gpio_get_value(PANDA_BOARD_ID_2_GPIO);
> +        }
> +        return ret;
> +}
Why cant we do something equivalent to beagle here? see
board/ti/beagle/beagle.c

> +
>  /**
>   * @brief misc_init_r - Configure Panda board specific configurations
>   * such as power configurations, ethernet initialization as phase2 of
> 


-- 
Regards,
Nishanth Menon

  parent reply	other threads:[~2013-11-14 19:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 15:42 [U-Boot] [[PATCH]pandaboard: 0/1] Modification of Elpida DDR2 RAM for Pandaboard-ES Rev B3 Hardik
2013-10-25 15:42 ` [U-Boot] [[PATCH]pandaboard: 1/1] " Hardik
2013-10-28 12:51   ` Dan Murphy
2013-10-28 13:04     ` Tom Rini
2013-10-29 14:17       ` Hardik Patel
2013-10-29 15:54         ` Tom Rini
2013-11-14 10:05           ` [U-Boot] [[PATCH v2]pandaboard: 0/1] " Hardik
2013-11-14 10:06           ` Hardik
2013-11-14 10:06           ` [U-Boot] [[PATCH v2]pandaboard: 1/1] " Hardik
2013-11-14 15:29             ` Robert Nelson
2013-11-14 15:41             ` Michael Trimarchi
2013-11-14 16:19             ` Tom Rini
2013-11-14 16:28               ` Michael Trimarchi
2013-11-14 16:32                 ` Tom Rini
2013-11-14 18:43                   ` Hardik Patel
2013-11-14 18:58                     ` Michael Trimarchi
2013-11-14 19:02                     ` Tom Rini
2013-11-14 19:41             ` Nishanth Menon [this message]
2013-11-14 19:49               ` Tom Rini
2013-11-14 20:26               ` Nishanth Menon
2013-11-21  9:17                 ` jmgrimaud
2013-11-27 15:46                 ` [U-Boot] [[PATCH v3]pandaboard: 0/1] ARM:OMAP4+: panda-es: Support Rev B3 Elpida DDR2 RAM Hardik
2013-11-27 15:46                 ` [U-Boot] [[PATCH v3]pandaboard: 1/1] " Hardik
2013-12-04 22:05                   ` [U-Boot] [U-Boot, [PATCH, v3] pandaboard: " Tom Rini

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=5285277C.8050400@ti.com \
    --to=nm@ti.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.