From: Mark Brown <broonie@kernel.org>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-spi@vger.kernel.org, kernel@pengutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spidev: Make probe to fail early if a spidev compatible is used
Date: Tue, 23 Nov 2021 14:55:38 +0000 [thread overview]
Message-ID: <YZ0A6rrpDlN6e5Vh@sirena.org.uk> (raw)
In-Reply-To: <9b41eb05-a095-39af-8b76-a73fa2532e92@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Fri, Nov 19, 2021 at 09:32:32AM +0100, Javier Martinez Canillas wrote:
> On 11/19/21 08:40, Uwe Kleine-König wrote:
> > Not this affects also devices that use
> > compatible = "myvender,devicename", "spidev";
> This is indeed a corner case and I'm less sure what the kernel should do
> about it. I just learned now that of_device_is_compatible() return value
TBH I feel like that falls into the same bucket as any other uses of
spidev so I'm not overly worried. Grepping around it looks like we have
no examples of this in tree, only a few plain spidevs in DTs for older
platforms that were most likely converted from board files and *probably*
aren't too relevant at this point.
> Or just consider DT nodes with a general "spidev" compatible string to
> also not be valid. I would lean towards this one I think.
Yes, I think so. Your other options are worth exploring if it turns out
to be an issue but hopefully it's not.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-11-23 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 22:59 Javier Martinez Canillas
2021-11-10 7:42 ` Uwe Kleine-König
2021-11-10 8:28 ` Javier Martinez Canillas
2021-11-18 18:21 ` Mark Brown
2021-11-19 7:40 ` Uwe Kleine-König
2021-11-19 8:32 ` Javier Martinez Canillas
2021-11-23 14:55 ` Mark Brown [this message]
2021-11-24 7:27 ` 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=YZ0A6rrpDlN6e5Vh@sirena.org.uk \
--to=broonie@kernel.org \
--cc=javierm@redhat.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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
all inboxes | Powered by JetHome®