public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH] dt-binding: remoteproc: Document generic properties
Date: Fri, 12 Aug 2016 13:34:49 -0500	[thread overview]
Message-ID: <20160812183448.GA32059@rob-hp-laptop> (raw)
In-Reply-To: <1470850622-29816-1-git-send-email-bjorn.andersson@linaro.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

  reply	other threads:[~2016-08-12 18:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 17:37 [PATCH] dt-binding: remoteproc: Document generic properties Bjorn Andersson
2016-08-12 18:34 ` Rob Herring [this message]
2016-08-12 22:42   ` Bjorn Andersson
2016-09-02 21:45     ` Suman Anna
     [not found]       ` <46d4d351-336c-6d4f-b1b0-243cf3c5d68b-l0cyMroinI0@public.gmane.org>
2016-09-08 16:50         ` Rob Herring
2016-09-08 18:32           ` Suman Anna
     [not found]             ` <dfa838cf-15f6-c178-f69a-1b5488f74a7a-l0cyMroinI0@public.gmane.org>
2016-09-09  2:33               ` Rob Herring
2016-09-09  3:36                 ` Bjorn Andersson
     [not found]                 ` <CAL_JsqKF5pqWY2fSoReUrAZ6yqfMTkWLLYrJqCz4ciA8J0a2-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-16 22:12                   ` Suman Anna

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=20160812183448.GA32059@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ohad@wizery.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox