lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 21 Dec 2017 16:39:58 -0600
From:   Rob Herring <>
To:     Bjorn Andersson <>
Cc:     Chris Lew <>,
        Andy Gross <>,
        David Brown <>,
        Arun Kumar Neelakantam <>,
        linux-arm-msm <>,
        "open list:ARM/QUALCOMM SUPPORT" <>,
        "" <>
Subject: Re: [PATCH 1/6] dt-bindings: soc: qcom: Add label for GLINK bindings

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.


Powered by blists - more mailing lists