linux-kernel - Re: [PATCH v2 1/2] uio: dt-bindings: document binding for uio-pdrv-genirq

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <22b9c6eb06ea4e8182c4e214b2a96fce@svr-chch-ex1.atlnz.lc>
Date:   Sun, 8 Oct 2017 21:03:09 +0000
From:   Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To:     Rob Herring <robh@...nel.org>
CC:     "mark.rutland@....com" <mark.rutland@....com>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] uio: dt-bindings: document binding for
 uio-pdrv-genirq

Hi Rob, Greg,

On 04/10/17 10:38, Rob Herring wrote:
> On Fri, Sep 22, 2017 at 03:48:13AM +1200, Chris Packham wrote:
>> Document the device tree bindings for the uio-prv-genirq driver. Provide
>> some examples on how it can be used.
>>
>> Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
>> ---
>>   .../bindings/uio/linux,uio-pdrv-genirq.txt         | 28 ++++++++++++++++++++++
>>   1 file changed, 28 insertions(+)
>>   create mode 100644 Documentation/devicetree/bindings/uio/linux,uio-pdrv-genirq.txt
> 
> NAK.
> 
> I'm sure this has come up before but if you want to map a device to a
> uio driver, then add its compatible string to the driver. Bindings
> describe h/w devices.

Fair enough.

The problem for me is that the uio-pdrv-genirq is so generic it could 
apply to pretty much any hardware device. The driver has dt-awareness 
but it currently doesn't have any built-in compatible string (it is set 
via a module param).

My use-case is a microcontoller with a userspace driver all I need out 
of the kernel is i2c access and interrupts. Any suggestions as to how to 
move forward with this.