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: Tue, 14 Jul 2020 10:54:15 +0200 [thread overview]
Message-ID: <2eb6971b-7ea4-c9c8-5452-6f4b17e8860a@kontron.de> (raw)
In-Reply-To: <20200713151108.GB4420@sirena.org.uk>
On 13.07.20 17:11, Mark Brown wrote:
> On Mon, Jul 13, 2020 at 03:19:52PM +0200, Frieder Schrempf wrote:
>
>> I would have expected that there is some kind of existing userspace API to
>> load an overlay manually, but it seems like there isn't!?
>
>> So what's the reasoning behind this? How can I solve this in a
>> mainline-compliant way, meaning without either keeping downstream patches to
>> bind spidev to my device or writing and maintaining code that does the
>> overlay loading?
>
> Basically the reasoning is that nobody's done it rather than any grand
> design not to do it. There's some issues for more complex connectors
> present on multiple boards with mapping the same connector onto multiple
> boards where a resource on the connector might be provided by different
> things on the base board so it's not quite as trivial for them as it
> should be.
Ok, thanks. I'm afraid I'm currently not in the position to work on any
generic solution to leverage the loading of DT overlays from userspace.
It would still be quite nice to benefit from the flexibility of DT
overlays not only for the SPI use case. But before I come up with any
custom solution, for now I will rather have the device in the DT statically.
I just wonder if I need to keep the DT node for the device in a separate
patch in our own tree, or if a node with a custom compatible string like
for example "kontron,user-spi" would be accepted upstream, without a
matching driver?
next prev parent reply other threads:[~2020-07-14 8:54 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
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 [this message]
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=2eb6971b-7ea4-c9c8-5452-6f4b17e8860a@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