lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 5 Jul 2011 19:00:49 -0700 From: Greg KH <gregkh@...e.de> To: "Watkins, Melissa" <m-watkins@...com> Cc: Greg KH <greg@...ah.com>, Subhasish Ghosh <subhasish@...tralsolutions.com>, "open list:STAGING SUBSYSTEM" <devel@...verdev.osuosl.org>, "sachi@...tralsolutions.com" <sachi@...tralsolutions.com>, "davinci-linux-open-source@...ux.davincidsp.com" <davinci-linux-open-source@...ux.davincidsp.com>, "stalin.s@...tralsolutions.com" <stalin.s@...tralsolutions.com>, open list <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH v5 1/1] drivers:staging:pruss: add pruss staging mfd driver. 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@...tralsolutions.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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists