From: Kyle Roeschley <kyle.roeschley-acOepvfBmUk@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: spidev: Instantiating from DT as "spidev"
Date: Wed, 29 Nov 2017 09:04:36 -0600 [thread overview]
Message-ID: <20171129150435.5npybjuu2ndmtx2v@senary> (raw)
Hello,
Since commit 956b200a846e ("spi: spidev: Warn loudly if instantiated from DT as
"spidev""), listing "spidev" directly in a device tree is not recommended.
Instead, what I see in the (many) past discussions is that I should change my
device tree to describe the actual hardware and add whatever new ID I create to
spidev_dt_ids. That seems perfectly reasonable.
However, our SPI master [1] is similar to the Raspberry Pi or Beaglebone in
that we don't know at kernel build time what device may be attached to the SPI
bus. Because the end users of our device are usually young students, we also
can't expect them to rebuild their kernel or mess with device tree overlays
just to interface with some arbitrary SPI device.
Is there a "correct" solution to this problem? Both the Raspberry Pi [2] and
Beaglebone [3] kernels have just added "spidev" back to the match table, but I
would rather not carry a patch around just for some printk spam.
Regards,
--
Kyle Roeschley
Software Engineer
National Instruments
[1] http://www.ni.com/en-us/support/model.roborio.html
[2] https://github.com/raspberrypi/linux/commit/dc08459ce87f0e73422c17abe20d0ac6c72153ad
[3] https://github.com/beagleboard/linux/commit/1596f3a6a0966969089be73c58e4a6294ffbcb09
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-11-29 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 15:04 Kyle Roeschley [this message]
2017-11-29 16:32 ` spidev: Instantiating from DT as "spidev" Geert Uytterhoeven
[not found] ` <CAMuHMdUps9Ti=CRZM7UxrHLD8GA+FKD+_RFLW3H9wUpSRTYs8w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-29 19:24 ` Kyle Roeschley
2017-11-29 22:18 ` Geert Uytterhoeven
[not found] ` <CAMuHMdX62=vC6=P-v=SPe_hq0F12tOZCgePaS7=MZZg_4PkvUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-30 2:07 ` Trent Piepho
[not found] ` <1512007657.9792.45.camel-cgc2CodaaHDQT0dZR+AlfA@public.gmane.org>
2017-11-30 8:03 ` Geert Uytterhoeven
[not found] ` <CAMuHMdXv2WsGCUBD4Td9K1zOfZ9DOfeW5rYtCyq27Ucp21xGRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-30 22:24 ` Kyle Roeschley
2017-12-12 18:44 ` Kyle Roeschley
2017-11-29 20:22 ` Trent Piepho
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=20171129150435.5npybjuu2ndmtx2v@senary \
--to=kyle.roeschley-acoepvfbmuk@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).