From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] omap3: cm-t3517: add board specific get_board_rev()
Date: Tue, 10 Nov 2015 19:33:08 +0200 [thread overview]
Message-ID: <56422A54.1010103@compulab.co.il> (raw)
In-Reply-To: <1447161464-29638-1-git-send-email-lifshitz@compulab.co.il>
On 11/10/15 15:17, Dmitry Lifshitz wrote:
> CM-T3517 has several HW revisions.
> Add board specific get_board_rev() callback to retrieve revision number.
>
> Signed-off-by: Dmitry Lifshitz <lifshitz@compulab.co.il>
Reviewed-by: Igor Grinberg <grinberg@compulab.co.il>
> ---
>
> Igor, Tom
>
> I forgot to add a mailing list address in send-email.
> Resending the patch.
you may want to use aliases to simplify the stuff, check out doc/git-mailrc.
>
> v2: Make proper use of cl_eeprom_get_board_rev() parameter.
>
> board/compulab/cm_t3517/cm_t3517.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/board/compulab/cm_t3517/cm_t3517.c b/board/compulab/cm_t3517/cm_t3517.c
> index d1c74db..8aae248 100644
> --- a/board/compulab/cm_t3517/cm_t3517.c
> +++ b/board/compulab/cm_t3517/cm_t3517.c
> @@ -98,6 +98,15 @@ int board_init(void)
> return 0;
> }
>
> +/*
> + * Routine: get_board_rev
> + * Description: read system revision
> + */
> +u32 get_board_rev(void)
> +{
> + return cl_eeprom_get_board_rev(CONFIG_SYS_I2C_EEPROM_BUS);
> +};
> +
> int misc_init_r(void)
> {
> cl_print_pcb_info();
>
--
Regards,
Igor.
next prev parent reply other threads:[~2015-11-10 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 11:20 [U-Boot] [PATCH] omap3: cm-t3517: add board specific get_board_rev() Dmitry Lifshitz
2015-10-08 18:45 ` Igor Grinberg
2015-11-10 13:17 ` [U-Boot] [PATCH v2] " Dmitry Lifshitz
2015-11-10 17:33 ` Igor Grinberg [this message]
2015-11-18 22:34 ` [U-Boot] [U-Boot, " 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=56422A54.1010103@compulab.co.il \
--to=grinberg@compulab.co.il \
--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