From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752238Ab2FFFok (ORCPT ); Wed, 6 Jun 2012 01:44:40 -0400 Received: from mail-yx0-f174.google.com ([209.85.213.174]:64535 "EHLO mail-yx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750764Ab2FFFoi (ORCPT ); Wed, 6 Jun 2012 01:44:38 -0400 MIME-Version: 1.0 X-Originating-IP: [93.172.31.133] In-Reply-To: <4FCECD8F.8000600@codeaurora.org> References: <1337687472-23009-1-git-send-email-ohad@wizery.com> <4FBDFC4A.1060602@codeaurora.org> <4FCD276A.80505@codeaurora.org> <4FCECD8F.8000600@codeaurora.org> From: Ohad Ben-Cohen Date: Wed, 6 Jun 2012 08:44:17 +0300 Message-ID: Subject: Re: [PATCH] remoteproc: block premature rproc booting To: Stephen Boyd Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Fernando Guzman Lugo Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 6, 2012 at 6:25 AM, Stephen Boyd wrote: > What if I don't want to boot the device at kernel start-up? Do I have to > make it a module then? Currently, yeah. But we can change stuff if needed. We took that design decision because it was simple and we didn't have any reason not to do it, but I'm thinking we can let the users decide about this using runtime pm (e.g. calling pm_runtime_get_sync with an rpmsg device, which will then be propagated all the way up to the remoteproc device and power it up). From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ohad Ben-Cohen Subject: Re: [PATCH] remoteproc: block premature rproc booting Date: Wed, 6 Jun 2012 08:44:17 +0300 Message-ID: References: <1337687472-23009-1-git-send-email-ohad@wizery.com> <4FBDFC4A.1060602@codeaurora.org> <4FCD276A.80505@codeaurora.org> <4FCECD8F.8000600@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FCECD8F.8000600@codeaurora.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Stephen Boyd Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Fernando Guzman Lugo List-Id: linux-omap@vger.kernel.org On Wed, Jun 6, 2012 at 6:25 AM, Stephen Boyd wrote: > What if I don't want to boot the device at kernel start-up? Do I have to > make it a module then? Currently, yeah. But we can change stuff if needed. We took that design decision because it was simple and we didn't have any reason not to do it, but I'm thinking we can let the users decide about this using runtime pm (e.g. calling pm_runtime_get_sync with an rpmsg device, which will then be propagated all the way up to the remoteproc device and power it up). From mboxrd@z Thu Jan 1 00:00:00 1970 From: ohad@wizery.com (Ohad Ben-Cohen) Date: Wed, 6 Jun 2012 08:44:17 +0300 Subject: [PATCH] remoteproc: block premature rproc booting In-Reply-To: <4FCECD8F.8000600@codeaurora.org> References: <1337687472-23009-1-git-send-email-ohad@wizery.com> <4FBDFC4A.1060602@codeaurora.org> <4FCD276A.80505@codeaurora.org> <4FCECD8F.8000600@codeaurora.org> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Jun 6, 2012 at 6:25 AM, Stephen Boyd wrote: > What if I don't want to boot the device at kernel start-up? Do I have to > make it a module then? Currently, yeah. But we can change stuff if needed. We took that design decision because it was simple and we didn't have any reason not to do it, but I'm thinking we can let the users decide about this using runtime pm (e.g. calling pm_runtime_get_sync with an rpmsg device, which will then be propagated all the way up to the remoteproc device and power it up).