From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH 1/6] dt-bindings: soc: qcom: Add label for GLINK bindings Date: Thu, 21 Dec 2017 16:39:58 -0600 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20171221013557.GE12655@minitux> Sender: linux-kernel-owner@vger.kernel.org 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" List-Id: devicetree@vger.kernel.org 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