From: Greg KH <greg@kroah.com>
To: "Hans J. Koch" <hjk@hansjkoch.de>
Cc: Pratheesh Gangadhar <pratheesh@ti.com>,
linux-kernel@vger.kernel.org, gregkh@suse.de, tglx@linutronix.de,
sshtylyov@mvista.com, arnd@arndb.de, amit.chatterjee@ti.com,
davinci-linux-open-source@linux.davincidsp.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v11 1/1] PRUSS UIO driver support
Date: Mon, 7 Mar 2011 13:09:50 -0800 [thread overview]
Message-ID: <20110307210950.GA21433@kroah.com> (raw)
In-Reply-To: <20110305003004.GA1295@local>
On Sat, Mar 05, 2011 at 01:30:04AM +0100, Hans J. Koch wrote:
> On Sat, Mar 05, 2011 at 04:30:17AM +0530, Pratheesh Gangadhar wrote:
> > This patch implements PRUSS (Programmable Real-time Unit Sub System)
> > UIO driver which exports SOC resources associated with PRUSS like
> > I/O, memories and IRQs to user space. PRUSS is dual 32-bit RISC
> > processors which is efficient in performing embedded tasks that
> > require manipulation of packed memory mapped data structures and
> > handling system events that have tight real time constraints. This
> > driver is currently supported on Texas Instruments DA850, AM18xx and
> > OMAP-L138 devices.
> > For example, PRUSS runs firmware for real-time critical industrial
> > communication data link layer and communicates with application stack
> > running in user space via shared memory and IRQs.
> >
> > Signed-off-by: Pratheesh Gangadhar <pratheesh@ti.com>
> > Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
> > Reviewed-by: Arnd Bergmann <arnd@arndb.de>
>
> Signed-off-by: Hans J. Koch <hjk@hansjkoch.de>
>
> I think, we've got it. Thanks for your contribution and your patience.
> Not many UIO programmers hang on through 11 patch versions...
Thanks so much for all of you doing this review as well, that too take
persistance :)
greg k-h
prev parent reply other threads:[~2011-03-07 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 23:00 [PATCH v11 0/1] Add " Pratheesh Gangadhar
2011-03-04 23:00 ` [PATCH v11 1/1] " Pratheesh Gangadhar
2011-03-05 0:30 ` Hans J. Koch
2011-03-07 21:09 ` Greg KH [this message]
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=20110307210950.GA21433@kroah.com \
--to=greg@kroah.com \
--cc=amit.chatterjee@ti.com \
--cc=arnd@arndb.de \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=gregkh@suse.de \
--cc=hjk@hansjkoch.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
all inboxes | Powered by JetHome®