linux-kernel - Re: [STLinux Kernel] [PATCH v2 3/4] remoteproc: Supply controller driver for ST's Remote Processors

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150901091243.GP4796@x1>
Date:	Tue, 1 Sep 2015 10:12:43 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Peter Griffin <peter.griffin@...aro.org>
Cc:	Nathan Lynch <Nathan_Lynch@...tor.com>, ohad@...ery.com,
	devicetree@...r.kernel.org, kernel@...inux.com,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [STLinux Kernel] [PATCH v2 3/4] remoteproc: Supply controller
 driver for ST's Remote Processors

On Tue, 01 Sep 2015, Peter Griffin wrote:

> Hi,
> 
> On Tue, 01 Sep 2015, Lee Jones wrote:
> 
> > On Fri, 28 Aug 2015, Nathan Lynch wrote:
> > 
> > > On 08/28/2015 05:31 AM, Lee Jones wrote:
> > > > diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig
> > > > index 28c711f..72e97d7 100644
> > > > --- a/drivers/remoteproc/Kconfig
> > > > +++ b/drivers/remoteproc/Kconfig
> > > > @@ -77,4 +77,13 @@ config DA8XX_REMOTEPROC
> > > >  	  It's safe to say n here if you're not interested in multimedia
> > > >  	  offloading.
> > > >  
> > > > +config ST_REMOTEPROC
> > > > +	tristate "ST remoteproc support"
> > > > +	depends on ARCH_STI
> > > > +	select REMOTEPROC
> > > > +	help
> > > > +	  Say y here to support ST's adjunct processors via the remote
> > > > +	  processor framework.
> > > > +	  This can be either built-in or a loadable module.
> > > > +
> > > 
> > > The code uses reset_control_* APIs, so this should depend on
> > > RESET_CONTROLLER, no?
> > 
> > There's no need to explicitly depend on RESET_CONTROLLER.
> > 
> > With !RESET_CONTROLLER the user is WARN()ed about using the reset_*
> > API.
> 
> ARCH_STI selects RESET_CONTROLLER, so it will always be enabled.

That too.  Thanks for pointing that out.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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/