linux-kernel - Re: [PATCH] uio: uio_pdrv_genirq: Make UIO name controllable via DT node property

lists.openwall.net		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] [day] [month] [year] [list]

Message-ID: <366c9fd3-c497-f0e7-e7b4-c668f4edcb84@zonque.org>
Date:   Thu, 15 Aug 2019 23:27:43 +0200
From:   Daniel Mack <daniel@...que.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] uio: uio_pdrv_genirq: Make UIO name controllable via DT
 node property

On 15/8/2019 10:56 PM, Greg KH wrote:
> On Sun, Aug 11, 2019 at 01:02:13PM +0200, Daniel Mack wrote:
>> When probed via DT, the uio_pdrv_genirq driver currently uses the name
>> of the node and exposes that as name of the UIO device to userspace.
>>
>> This doesn't work for systems where multiple nodes with the same name
>> (but different unit addresses) are present, or for systems where the
>> node names are auto-generated by a third-party tool.
>>
>> This patch adds the possibility to read the UIO name from the optional
>> "linux,uio-name" property.
> 
> Does that need to be documented anywhere?

This driver does not have a match table and is special in other ways
too, which is why I believe it isn't documented in
Documentation/devicetree/bindings.

I'll cook up a patch to describe how the probing works right now, and
also add a word on the newly introduced property.


Thanks,
Daniel