public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@hansjkoch.de>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: Pratheesh Gangadhar <pratheesh@ti.com>,
	davinci-linux-open-source@linux.davincidsp.com, hjk@hansjkoch.de,
	gregkh@suse.de, tglx@linutronix.de, arnd@arndb.de,
	amit.chatterjee@ti.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 2/2] Defines DA850/AM18xx/OMAPL1-38 SOC resources used by PRUSS UIO driver
Date: Fri, 25 Feb 2011 14:02:41 +0100	[thread overview]
Message-ID: <20110225130241.GA2791@local> (raw)
In-Reply-To: <4D6796D6.5050008@mvista.com>

On Fri, Feb 25, 2011 at 02:47:34PM +0300, Sergei Shtylyov wrote:
> On 24-02-2011 17:06, Pratheesh Gangadhar wrote:
> 
> >This patch defines PRUSS, ECAP clocks, memory and IRQ resources
> >used by PRUSS UIO driver in DA850/AM18xx/OMAPL1-38 devices. UIO
> 
>    It's OMAP-L138.

>From the TI wiki: "The PRU subsystem is supported on
OMAP-L1x8/C674m/AM18xx devices (where m is an even number)."

http://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit_Subsystem

Thanks,
Hans


  reply	other threads:[~2011-02-25 13:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 14:06 [PATCH v4 0/2] Add PRUSS UIO driver support Pratheesh Gangadhar
2011-02-24 14:06 ` [PATCH v4 1/2] " Pratheesh Gangadhar
2011-02-24 14:06   ` [PATCH v4 2/2] Defines DA850/AM18xx/OMAPL1-38 SOC resources used by PRUSS UIO driver Pratheesh Gangadhar
2011-02-25 11:47     ` Sergei Shtylyov
2011-02-25 13:02       ` Hans J. Koch [this message]
2011-02-25 13:22         ` Sergei Shtylyov
2011-02-28  4:46       ` TK, Pratheesh Gangadhar
2011-02-28 10:08         ` Nori, Sekhar
2011-02-28 10:27         ` Sergei Shtylyov
2011-02-24 14:28   ` [PATCH v4 1/2] PRUSS UIO driver support Thomas Gleixner

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=20110225130241.GA2791@local \
    --to=hjk@hansjkoch.de \
    --cc=amit.chatterjee@ti.com \
    --cc=arnd@arndb.de \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=gregkh@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pratheesh@ti.com \
    --cc=sshtylyov@mvista.com \
    --cc=tglx@linutronix.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