public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: sshtylyov@mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] davinci: Add additional JTAG code for AM-1808 and OMAP-L138 Rev 2.0 SoCs
Date: Fri, 24 Dec 2010 14:25:41 +0300	[thread overview]
Message-ID: <4D148335.8070209@mvista.com> (raw)
In-Reply-To: <1293132288-22325-1-git-send-email-michael.williamson@criticallink.com>

Hello.

On 23-12-2010 22:24, Michael Williamson wrote:

> From: Sudhakar Rajashekhara<sudhakar.raj@ti.com>

> 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.

> This patch is orignally from a patch on the arago project, here:
> http://arago-project.org/git/projects/?p=linux-omapl1.git;a=commit;h=6157618435e313a444cdf059702bd34036a6e2b7

> Further information related to the need for this patch can be located at
> http://e2e.ti.com/support/embedded/f/354/p/67290/248486.aspx
> http://linux.davincidsp.com/pipermail/davinci-linux-open-source/2010-November/021224.html

> This patch was tested using an AM-1808 SoC on a MityARM-1808 SoM card.  It
> was also tested using a Rev 1.0 silicon OMAP-L138 on a MityDSP-L138F card.

> Signed-off-by: Michael Williamson <michael.williamson@criticallink.com>
> Tested-by: Michael Williamson <michael.williamson@criticallink.com>
> Reported-by: Nicolas Luna <luna.id@gmail.com>

    I saw that the original patch was signed off by Sudhakar -- why you 
omitted that?

WBR, Sergei

  reply	other threads:[~2010-12-24 11:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23 19:24 [PATCH v2] davinci: Add additional JTAG code for AM-1808 and OMAP-L138 Rev 2.0 SoCs Michael Williamson
2010-12-24 11:25 ` Sergei Shtylyov [this message]
2010-12-24 13:40   ` Michael Williamson
2010-12-24 16:04     ` Sergei Shtylyov

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=4D148335.8070209@mvista.com \
    --to=sshtylyov@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox