From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] davinci: Add additional JTAG code for AM-1808 and OMAP-L138 Rev 2.0 SoCs
Date: Wed, 22 Dec 2010 14:06:26 -0800 [thread overview]
Message-ID: <87aajxpin1.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1293047363-21353-1-git-send-email-michael.williamson@criticallink.com> (Michael Williamson's message of "Wed, 22 Dec 2010 14:49:23 -0500")
Michael Williamson <michael.williamson@criticallink.com> writes:
> The JTAG variant code for Rev-2.0 silicon of the OMAP-L138 has changed.
> In addition, the variant code for the AM-1808 SoC appears to match
> the Rev-2.0 code for the OMAP-L138. Add an additional entry to support
> these chips.
Tested on?
I'm assuming on the Mity platforms, right?
Kevin
> Signed-off-by: Michael Williamson <michael.williamson@criticallink.com>
> ---
> This is against davinci-linux tree.
> Changes since v0, removed whitespace fixups not related to patch.
>
> arch/arm/mach-davinci/da850.c | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-davinci/da850.c b/arch/arm/mach-davinci/da850.c
> index 78b5ae2..2d0bba5 100644
> --- a/arch/arm/mach-davinci/da850.c
> +++ b/arch/arm/mach-davinci/da850.c
> @@ -764,6 +764,13 @@ static struct davinci_id da850_ids[] = {
> .cpu_id = DAVINCI_CPU_ID_DA850,
> .name = "da850/omap-l138",
> },
> + {
> + .variant = 0x1,
> + .part_no = 0xb7d1,
> + .manufacturer = 0x017, /* 0x02f >> 1 */
> + .cpu_id = DAVINCI_CPU_ID_DA850,
> + .name = "da850/omap-l138/am18xx",
> + },
> };
>
> static struct davinci_timer_instance da850_timer_instance[4] = {
next prev parent reply other threads:[~2010-12-22 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 19:49 [PATCH v1] davinci: Add additional JTAG code for AM-1808 and OMAP-L138 Rev 2.0 SoCs Michael Williamson
2010-12-22 22:06 ` Kevin Hilman [this message]
2010-12-22 23:09 ` Michael Williamson
2010-12-23 0:11 ` Kevin Hilman
2010-12-23 5:04 ` Rajashekhara, Sudhakar
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=87aajxpin1.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.