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: Wed, 15 Jul 2020 13:45:51 +0200 [thread overview]
Message-ID: <824b8479-e204-d087-7887-a2dbefa0f844@kontron.de> (raw)
In-Reply-To: <20200715113609.GD5431@sirena.org.uk>
On 15.07.20 13:36, Mark Brown wrote:
> On Wed, Jul 15, 2020 at 09:26:29AM +0200, Frieder Schrempf wrote:
>> On 14.07.20 21:29, Mark Brown wrote:
>>> On Tue, Jul 14, 2020 at 10:54:15AM +0200, Frieder Schrempf wrote:
>
>>>> 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?
>
>>> I'm having a hard time getting enthusiastic about it TBH - can you not
>>> just use spidev and live with the warning?
>
>> Ok, I can do that, but when I resend my patches and add "compatible =
>> 'spidev'" to my DT I expect someone to complain again as my DT does not
>> describe the hardware.
>
> That's the issue with kontron,user-spi too though :/
Yes, true.
>
>> But for obvious reasons this can't be considered a good solution and it
>> seems somewhat disturbing that the maintainer needs to propose it because of
>> lack of proper solutions ;)
>
> Hey, I proposed other solutions you didn't want to implement!
Right, but you have to admit that the other solutions turned out to be
rather out of scope for someone like me who merely wants to use the
spidev driver.
But I don't blame you. I'm now having a better idea of how things are
(or aren't) supposed to look like. So thanks for your patience!
next prev parent reply other threads:[~2020-07-15 11:45 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
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 [this message]
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=824b8479-e204-d087-7887-a2dbefa0f844@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).