All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@suse.de (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/1] drivers:staging:pruss: add pruss staging mfd driver.
Date: Tue, 5 Jul 2011 19:00:49 -0700	[thread overview]
Message-ID: <20110706020049.GB15988@suse.de> (raw)
In-Reply-To: <131E5DFBE7373E4C8D813795A6AA7F08034B5C4C48@dlee06.ent.ti.com>

On Tue, Jul 05, 2011 at 01:43:03PM -0500, Watkins, Melissa wrote:
> On Tue, Jun 28, 2011 at 02:01:12PM -0700, Greg KH wrote:
> > 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>
> > > 
> 
> [MW] Greg, thanks for reviewing Mistral's patch submission.  I have
> been following the traffic on their patches and will provide an
> initial response to address some of your questions. 
> 
> > > Please refresh my memory as to why this can't get merged into the
> > > "normal" part of the kernel?
> 
> [MW] Arnd had recommended moving the driver to the staging area until
> all interfaces have stabilized.  One of the main reasons it cannot
> currently be merged in the "normal" part of the kernel is the question
> of how firmware should be configured and loaded.
> (https://lkml.org/lkml/2011/5/24/230,
> https://lkml.org/lkml/2011/5/10/463)
> 
> > Dropped from my queue due to lack of response :(
> 
> > Please resend when you get the chance, and address the above comment in
> > your changelog entry (and in your TODO file as well.)
> 
> [MW] Please let us know if Mistral still needs to resubmit their patch
> or if we can continue discussions on this submission.

Please resend it, with the above information in the changelog and in the
TODO file.

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: "Watkins, Melissa" <m-watkins@ti.com>
Cc: Greg KH <greg@kroah.com>,
	Subhasish Ghosh <subhasish@mistralsolutions.com>,
	"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
	"sachi@mistralsolutions.com" <sachi@mistralsolutions.com>,
	"davinci-linux-open-source@linux.davincidsp.com" 
	<davinci-linux-open-source@linux.davincidsp.com>,
	"stalin.s@mistralsolutions.com" <stalin.s@mistralsolutions.com>,
	open list <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 1/1] drivers:staging:pruss: add pruss staging mfd driver.
Date: Tue, 5 Jul 2011 19:00:49 -0700	[thread overview]
Message-ID: <20110706020049.GB15988@suse.de> (raw)
In-Reply-To: <131E5DFBE7373E4C8D813795A6AA7F08034B5C4C48@dlee06.ent.ti.com>

On Tue, Jul 05, 2011 at 01:43:03PM -0500, Watkins, Melissa wrote:
> On Tue, Jun 28, 2011 at 02:01:12PM -0700, Greg KH wrote:
> > 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>
> > > 
> 
> [MW] Greg, thanks for reviewing Mistral's patch submission.  I have
> been following the traffic on their patches and will provide an
> initial response to address some of your questions. 
> 
> > > Please refresh my memory as to why this can't get merged into the
> > > "normal" part of the kernel?
> 
> [MW] Arnd had recommended moving the driver to the staging area until
> all interfaces have stabilized.  One of the main reasons it cannot
> currently be merged in the "normal" part of the kernel is the question
> of how firmware should be configured and loaded.
> (https://lkml.org/lkml/2011/5/24/230,
> https://lkml.org/lkml/2011/5/10/463)
> 
> > Dropped from my queue due to lack of response :(
> 
> > Please resend when you get the chance, and address the above comment in
> > your changelog entry (and in your TODO file as well.)
> 
> [MW] Please let us know if Mistral still needs to resubmit their patch
> or if we can continue discussions on this submission.

Please resend it, with the above information in the changelog and in the
TODO file.

greg k-h

  reply	other threads:[~2011-07-06  2:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31  7:45 [PATCH v5 0/1] pruss mfd drivers Subhasish Ghosh
2011-05-31  7:45 ` [PATCH v5 1/1] drivers:staging:pruss: add pruss staging mfd driver Subhasish Ghosh
2011-05-31  7:45   ` Subhasish Ghosh
2011-06-28 21:01   ` Greg KH
2011-06-28 21:01     ` Greg KH
2011-07-05 16:15     ` Greg KH
2011-07-05 16:15       ` Greg KH
2011-07-05 18:43       ` Watkins, Melissa
2011-07-05 18:43         ` Watkins, Melissa
2011-07-06  2:00         ` Greg KH [this message]
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=20110706020049.GB15988@suse.de \
    --to=gregkh@suse.de \
    --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.