From: Michal Suchanek <hramrach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Michal Suchanek <hramrach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH v3 0/3] Spidev usability patchset update
Date: Tue, 19 Jul 2016 00:35:39 +0200 [thread overview]
Message-ID: <cover.1468880530.git.hramrach@gmail.com> (raw)
Hello,
this simplifies spidev to not pose as SPI driver but instead attach a character
device on each SPI slave indiscriminately. This does not require spidev to be
matched during driver binding and hence does not require it to be specified in
devicetree.
Any SPI slave device for which a driver is not bound to start with or from
which it is unbound is accessible with spidev.
Constructive comments on improving this patchset are welcome.
Thanks
Michal
Michal Suchanek (3):
spi: spidev: create spidev device for all spi slaves.
spi: of: allow instantiating slaves without a driver
spi: core: allow creating devices without spi-max-frequency
Documentation/spi/spidev | 40 ++---
drivers/spi/Kconfig | 2 +-
drivers/spi/spi.c | 28 +++-
drivers/spi/spidev.c | 370 ++++++++++++++++++++---------------------------
include/linux/spi/spi.h | 14 ++
5 files changed, 201 insertions(+), 253 deletions(-)
--
2.8.1
--
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:[~2016-07-18 22:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 22:35 Michal Suchanek [this message]
2016-07-18 22:35 ` [PATCH v3 1/3] spi: spidev: create spidev device for all spi slaves Michal Suchanek
[not found] ` <5bfcceff7b6132cf3447f97c24d1646043224164.1468880530.git.hramrach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-18 22:59 ` Mark Brown
[not found] ` <20160718225952.GW30372-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-07-19 11:17 ` Michal Suchanek
2016-07-19 12:44 ` Mark Brown
2016-07-19 15:32 ` Michal Suchanek
[not found] ` <CAOMqctRTNRTKKLVMXgxzdJEq0giRp5f8ujAUf-gUty9fSjqGXA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-19 17:19 ` Mark Brown
[not found] ` <20160719171959.GD30372-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-07-19 18:33 ` Michal Suchanek
2016-07-27 18:27 ` Mark Brown
2016-07-20 7:16 ` [lkp] " Fengguang Wu
2016-07-18 22:35 ` [PATCH v3 2/3] spi: of: allow instantiating slaves without a driver Michal Suchanek
[not found] ` <42e65e5c714f079cb4b85761e59fb700d4550a26.1468880530.git.hramrach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-18 23:02 ` Mark Brown
2016-07-19 8:31 ` Michal Suchanek
2016-07-19 10:52 ` Mark Brown
[not found] ` <20160719105212.GA30372-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-07-30 17:45 ` Michal Suchanek
2016-07-18 22:35 ` [PATCH v3 3/3] spi: core: allow creating devices without spi-max-frequency Michal Suchanek
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=cover.1468880530.git.hramrach@gmail.com \
--to=hramrach-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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).