From: Frieder Schrempf <frieder.schrempf@kontron.de>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH] spi: spidev: Add compatible for external SPI ports on Kontron boards
Date: Thu, 2 Jul 2020 16:46:09 +0200 [thread overview]
Message-ID: <24ec4eed-de01-28df-ee1f-f7bcfc80051a@kontron.de> (raw)
In-Reply-To: <20200702142511.GF4483@sirena.org.uk>
On 02.07.20 16:25, Mark Brown wrote:
> On Thu, Jul 02, 2020 at 04:18:46PM +0200, Schrempf Frieder wrote:
>> From: Frieder Schrempf <frieder.schrempf@kontron.de>
>>
>> Allow external SPI ports on Kontron boards to use the spidev driver.
>
> I'd have expected this to require loading a DT overlay for whatever's
> attached?
My intention is to use the spidev driver in the default board DT for an
interface that is routed to an extension connector and has no dedicated
slave device attached onboard. So users can attach sensors, etc. with
userspace drivers without touching the kernel or DT.
See https://patchwork.kernel.org/patch/11639075/ for the boards DT.
next prev parent reply other threads:[~2020-07-02 14:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 14:18 [PATCH] spi: spidev: Add compatible for external SPI ports on Kontron boards Schrempf Frieder
2020-07-02 14:25 ` Mark Brown
2020-07-02 14:46 ` Frieder Schrempf [this message]
2020-07-02 14:57 ` Geert Uytterhoeven
2020-07-02 16:04 ` Frieder Schrempf
2020-07-02 15:07 ` Mark Brown
2020-07-02 16:24 ` Frieder Schrempf
2020-07-13 13:19 ` Frieder Schrempf
2020-07-13 15:11 ` Mark Brown
2020-07-14 8:54 ` Frieder Schrempf
2020-07-14 19:29 ` Mark Brown
2020-07-15 7:26 ` Frieder Schrempf
2020-07-15 11:36 ` Mark Brown
2020-07-15 11:45 ` Frieder Schrempf
2020-07-15 13:10 ` Mark Brown
2020-07-15 13:48 ` Frieder Schrempf
2020-07-15 13:51 ` Mark Brown
2020-07-15 19:06 ` Geert Uytterhoeven
2020-07-16 7:53 ` Frieder Schrempf
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=24ec4eed-de01-28df-ee1f-f7bcfc80051a@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
/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).