linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Mark Brown" <broonie@kernel.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-spi <linux-spi@vger.kernel.org>,
	"Ralph Siemsen" <ralph.siemsen@linaro.org>
Subject: Re: [PATCH] spi: docs: improve the SPI userspace API documentation
Date: Fri, 19 Nov 2021 09:16:11 +0100	[thread overview]
Message-ID: <84b28138-8f10-f3a3-cbe8-878635b4f0d0@redhat.com> (raw)
In-Reply-To: <CAMuHMdVcsfE6TZbu8SJZP7CNKyjwBZdBiN0nDRQCibaGgpLF0g@mail.gmail.com>

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@redhat.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@linaro.org>
>> Signed-off-by: Javier Martinez Canillas <javierm@redhat.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


  reply	other threads:[~2021-11-19  8:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 21:31 [PATCH] spi: docs: improve the SPI userspace API documentation Javier Martinez Canillas
2021-11-19  7:45 ` Uwe Kleine-König
2021-11-19  8:14   ` Javier Martinez Canillas
2021-11-19  8:10 ` Geert Uytterhoeven
2021-11-19  8:16   ` Javier Martinez Canillas [this message]
2021-11-19 16:03 ` Ralph Siemsen
2021-11-19 18:01   ` Javier Martinez Canillas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84b28138-8f10-f3a3-cbe8-878635b4f0d0@redhat.com \
    --to=javierm@redhat.com \
    --cc=broonie@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=ralph.siemsen@linaro.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).