Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753846AbdLUWkX (ORCPT ); Thu, 21 Dec 2017 17:40:23 -0500 Received: from mail.kernel.org ([198.145.29.99]:54056 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751256AbdLUWkU (ORCPT ); Thu, 21 Dec 2017 17:40:20 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 64E76218CA Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=robh@kernel.org X-Google-Smtp-Source: ACJfBosjqRm7j1yvcJzDT5IXocBpJQqlp6PWx97CjJelOooPvjmMmLHqkEEN3h3Y88Mqla+TQPPLxuZQzTgNPL+zHMU= MIME-Version: 1.0 In-Reply-To: <20171221013557.GE12655@minitux> References: <1513634534-22861-1-git-send-email-clew@codeaurora.org> <1513634534-22861-2-git-send-email-clew@codeaurora.org> <20171220183000.rhxgyikfqzxmqkjo@rob-hp-laptop> <20171221013557.GE12655@minitux> From: Rob Herring Date: Thu, 21 Dec 2017 16:39:58 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 1/6] dt-bindings: soc: qcom: Add label for GLINK bindings To: Bjorn Andersson Cc: Chris Lew , Andy Gross , David Brown , Arun Kumar Neelakantam , linux-arm-msm , "open list:REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM" , "open list:ARM/QUALCOMM SUPPORT" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 919 Lines: 22 On Wed, Dec 20, 2017 at 7:35 PM, Bjorn Andersson wrote: > On Wed 20 Dec 10:30 PST 2017, Rob Herring wrote: > >> On Mon, Dec 18, 2017 at 02:02:09PM -0800, Chris Lew wrote: >> > Add a label property to identify the edge this node represents. >> >> Why does a user need to know this? >> > > We have multiple remoteproc instances, each one having one or more > associated SMD or GLINK links (this node), exposing logical > communication channels. Some of these logical channels are exposed to > user space and we need a way to distinguish them there. They should have some sort of discoverable property. There must be some reason why you need a specific channel. I think of label as being a sticker or silkscreen on a device which doesn't seem to be the case here. This seems more like wanting fixed device numbering like disks and I assume you know the position on fixed device numbers. Rob