public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Subhasish Ghosh <subhasish@mistralsolutions.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
	sachi@mistralsolutions.com, stalin.s@mistralsolutions.com,
	Greg Kroah-Hartman <gregkh@suse.de>,
	open list <linux-kernel@vger.kernel.org>,
	m-watkins@ti.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 1/1] drivers:staging:pruss: add pruss staging mfd driver.
Date: Tue, 28 Jun 2011 14:01:12 -0700	[thread overview]
Message-ID: <20110628210112.GA31081@kroah.com> (raw)
In-Reply-To: <1306827939-4133-2-git-send-email-subhasish@mistralsolutions.com>

On Tue, May 31, 2011 at 01:15:39PM +0530, Subhasish Ghosh wrote:
> This patch adds the pruss MFD driver and associated include files.
> For details regarding the PRUSS please refer the folowing link:
> http://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit_Subsystem
> 
> The rational behind the MFD driver being the fact that multiple devices can
> be implemented on the cores independently. This is determined by the nature
> of the program which is loaded into the PRU's instruction memory.
> A device may be de-initialized and another loaded or two different devices
> can be run simultaneously on the two cores.
> It's also possible, as in our case, to implement a single device on both
> the PRU's resulting in improved load sharing.
> 
> Signed-off-by: Subhasish Ghosh <subhasish@mistralsolutions.com>

Please refresh my memory as to why this can't get merged into the
"normal" part of the kernel?

> --- /dev/null
> +++ b/drivers/staging/pruss/TODO
> @@ -0,0 +1,14 @@
> +TODO:
> +
> +0. Functionality wise, everything works.
> +
> +1. Currently the plan is to add sysfs attributes for
> +	a. prux/load
> +	b. prux/unload
> +	c. prux/run
> +	d. prux/halt
> +   These will add to a more dynamic firmware management for the PRU.

Why sysfs?


> +
> +2. But, not sure how the fdt will effect these entries.
> +
> +Please send patches to Greg Kroah-Hartman <greg@kroah.com>.

Don't you want people to Cc: you as well?

I'm not going to adopt this driver, I have enough as it is :)

thanks,

greg k-h

  reply	other threads:[~2011-06-28 21:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1306827939-4133-1-git-send-email-subhasish@mistralsolutions.com>
2011-05-31  7:45 ` [PATCH v5 1/1] drivers:staging:pruss: add pruss staging mfd driver Subhasish Ghosh
2011-06-28 21:01   ` Greg KH [this message]
2011-07-05 16:15     ` Greg KH
2011-07-05 18:43       ` Watkins, Melissa
2011-07-06  2:00         ` Greg KH

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=20110628210112.GA31081@kroah.com \
    --to=greg@kroah.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-watkins@ti.com \
    --cc=sachi@mistralsolutions.com \
    --cc=stalin.s@mistralsolutions.com \
    --cc=subhasish@mistralsolutions.com \
    /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