From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752164AbcHLSex (ORCPT ); Fri, 12 Aug 2016 14:34:53 -0400 Received: from mail-oi0-f49.google.com ([209.85.218.49]:33262 "EHLO mail-oi0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751088AbcHLSev (ORCPT ); Fri, 12 Aug 2016 14:34:51 -0400 Date: Fri, 12 Aug 2016 13:34:49 -0500 From: Rob Herring To: Bjorn Andersson Cc: Mark Rutland , Ohad Ben-Cohen , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org Subject: Re: [PATCH] dt-binding: remoteproc: Document generic properties Message-ID: <20160812183448.GA32059@rob-hp-laptop> References: <1470850622-29816-1-git-send-email-bjorn.andersson@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1470850622-29816-1-git-send-email-bjorn.andersson@linaro.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 10, 2016 at 10:37:02AM -0700, Bjorn Andersson wrote: > This documents the generic properties "rprocs" and "rproc-names", used > for consumer drivers to reference a remoteproc node. How do you intend to use this? I wonder if it would not be better to expose a remote proc with existing bindings for a particular purpose (e.g. clocks, resets, etc.) rather than a generic connection. The client side would have to have specific knowledge as to what functions the remote proc provides. Rob