linux-kernel - Re: [PATCH v3 2/5] uio: dt-bindings: Add binding for "st,stm32f100"

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]

Date:   Fri, 13 Oct 2017 15:33:36 -0500
From:   Rob Herring <robh@...nel.org>
To:     Chris Packham <chris.packham@...iedtelesis.co.nz>
Cc:     mark.rutland@....com, gregkh@...uxfoundation.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/5] uio: dt-bindings: Add binding for "st,stm32f100"

On Tue, Oct 10, 2017 at 11:46:52AM +1300, Chris Packham wrote:
> The stm32f100 is a general purpose micro controller. Document a binding
> that allows a user-space driver to be implemented for these devices.

It may be general purpose, but how it is hooked up to the host is not 
and probably could be done in a variety of ways. I'd expect that to be 
described in a binding doc (that's not a suggestion to add it to this 
doc as I'm fundamentally against any binding with "UIO" in it).

Also, while the processor itself is general purpose, typically its 
function on a given board would not be except maybe on dev boards. It's 
that function (a combination of the uC and its firmware) which we want 
to describe to the host OS. There's already examples of uC used as PMICs 
or system controllers.

Rob