linux-kernel - Re: [PATCH] spi: docs: improve the SPI userspace API documentation

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: <84b28138-8f10-f3a3-cbe8-878635b4f0d0@redhat.com>
Date:   Fri, 19 Nov 2021 09:16:11 +0100
From:   Javier Martinez Canillas <javierm@...hat.com>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mark Brown <broonie@...nel.org>,
        Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
        linux-spi <linux-spi@...r.kernel.org>,
        Ralph Siemsen <ralph.siemsen@...aro.org>
Subject: Re: [PATCH] spi: docs: improve the SPI userspace API documentation

Hello Geert

On 11/19/21 09:10, Geert Uytterhoeven wrote:
> Hi Javier,
> 
> On Thu, Nov 18, 2021 at 10:32 PM Javier Martinez Canillas
> <javierm@...hat.com> wrote:
>> This doc is fairly outdated and only uses legacy device instantiation
>> terminology. Let us update it and also mention the OF and ACPI device
>> tables, to make easier for users to figure out how should be defined.
>>
>> Also, mention that devices bind could be done in user-space now using
>> the "driver_override" sysfs entry.
>>
>> Suggested-by: Ralph Siemsen <ralph.siemsen@...aro.org>
>> Signed-off-by: Javier Martinez Canillas <javierm@...hat.com>
> 
> Thanks for your patch!
>

You are welcome!
 
[snip]

>> +
>> +NOTE: it used to be supported to define an SPI device using the "spidev"
>> +      name.  For example as .modalias = "spidev" or compatible = "spidev".
>> +      But this is no longer supported by the Linux kernel and instead a
>> +      real SPI device name as listed in one of the tables should be used.
> 
> This reads as the tables are fixed.
> Perhaps add
> 
>     You are encouraged to add an entry for your SPI device name to
>      one of the tables.
>

Indeed, you are correct. I'll add that too in v2.

Best regards,
-- 
Javier Martinez Canillas
Linux Engineering
Red Hat