Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751804Ab3IHM1g (ORCPT ); Sun, 8 Sep 2013 08:27:36 -0400 Received: from mail-lb0-f170.google.com ([209.85.217.170]:59028 "EHLO mail-lb0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751482Ab3IHM1d (ORCPT ); Sun, 8 Sep 2013 08:27:33 -0400 MIME-Version: 1.0 X-Originating-IP: [89.139.56.158] In-Reply-To: <5220F099.1020002@nvidia.com> References: <5220F099.1020002@nvidia.com> From: Ohad Ben-Cohen Date: Sun, 8 Sep 2013 14:27:11 +0200 Message-ID: Subject: Re: permission to move definition of struct rpmsg_channel_info To: Arjun Gopalan Cc: Brian Swetland , "linux-kernel@vger.kernel.org" , "linux-tegra@vger.kernel.org" , Paul Walmsley 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 Content-Length: 1212 Lines: 29 Hi Arjun, On Fri, Aug 30, 2013 at 9:20 PM, Arjun Gopalan wrote: > > Hi Ohad/Brian, > > I have been working on rpmsg and I need to be able to create static rpmsg channels. Channel information needs to be specified by other drivers and for this, the drivers need access to struct rpmsg_channel_info. I'm not convinced how useful it is for other Linux drivers to create static rpmsg channels? Usually these channels reflect the existence of services running on the remote processor, and their creation (or lack thereof) should be specified in the remote image. This way an rpmsg channel is published iff there is a matching remote service. The way we were planning to add static channels functionality (I should still have preliminary patches doing this somewhere but the entire work was put on hold since TI changed its focus) is by statically publishing them in the resource table, which is coupled with a specific remote image. Best, Ohad. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/