From: Javier Martinez Canillas <javierm@redhat.com>
To: Mark Brown <broonie@kernel.org>
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: Wed, 24 Nov 2021 08:27:55 +0100 [thread overview]
Message-ID: <10d86e45-67fa-a361-db74-468c1cc686fb@redhat.com> (raw)
In-Reply-To: <YZ0A6rrpDlN6e5Vh@sirena.org.uk>
Hello Mark,
On 11/23/21 15:55, Mark Brown wrote:
> 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.
>
Agreed.
>> 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.
>
I think that's a good plan.
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
prev parent reply other threads:[~2021-11-24 7:28 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
2021-11-24 7:27 ` Javier Martinez Canillas [this message]
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=10d86e45-67fa-a361-db74-468c1cc686fb@redhat.com \
--to=javierm@redhat.com \
--cc=broonie@kernel.org \
--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®