From: Mark Brown <broonie@kernel.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Subject: Re: [PATCH] spi: Force the registration of the spidev devices
Date: Wed, 30 Apr 2014 18:18:11 -0700 [thread overview]
Message-ID: <20140501011811.GF3245@sirena.org.uk> (raw)
In-Reply-To: <20140430180609.GC3000@lukather>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On Wed, Apr 30, 2014 at 11:06:09AM -0700, Maxime Ripard wrote:
> On Tue, Apr 29, 2014 at 11:37:58AM -0700, Mark Brown wrote:
> > Why can we not handle this by using sysfs to bind spidev to the
> > device?
> I just tried it, and apparently, you can't really use this, since spi
> devices are created from the device tree (or ACPI) whenever the master
> registers.
Can you be more specific as to what the issue is here? If we actually
have a specific kernel driver for a device I would strongly expect that
we would want to use it and not spidev, if we don't have one I don't see
the issue.
> It doesn't really work either for a device that would be bound to a
> driver, that you unbind, and then try to bind to spidev instead. It
> looks like the device is released whenever you unbind it, so you can't
> really use it afterwards.
I guess this is the issue... what exactly is the use case here? I
would only expect spidev to be used if there is no in kernel driver for
a device.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-01 1:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 17:22 [PATCH] spi: Force the registration of the spidev devices Maxime Ripard
2014-04-29 18:37 ` Mark Brown
2014-04-30 18:06 ` Maxime Ripard
2014-05-01 1:18 ` Mark Brown [this message]
2014-05-01 22:36 ` Maxime Ripard
2014-05-01 23:28 ` Geert Uytterhoeven
2014-05-02 16:55 ` Mark Brown
2014-05-05 4:17 ` Maxime Ripard
2014-05-05 7:10 ` Geert Uytterhoeven
2014-05-05 13:57 ` Alexandre Belloni
2014-05-05 14:22 ` Geert Uytterhoeven
2014-05-05 19:16 ` Mark Brown
2014-05-02 17:40 ` Mark Brown
2014-05-05 4:21 ` Maxime Ripard
2014-05-05 19:17 ` Mark Brown
2014-05-08 2:22 ` Maxime Ripard
-- strict thread matches above, loose matches on Subject: below --
2015-05-12 20:33 Maxime Ripard
2015-05-13 11:26 ` Mark Brown
2015-05-13 12:35 ` Michal Suchanek
2015-05-13 12:51 ` Maxime Ripard
2015-05-13 14:36 ` Mark Brown
2015-05-13 15:31 ` Michal Suchanek
2015-05-13 17:43 ` Mark Brown
2015-05-13 19:09 ` Maxime Ripard
2015-05-13 19:10 ` Geert Uytterhoeven
2015-05-13 19:41 ` Maxime Ripard
2015-05-13 15:37 ` Greg Kroah-Hartman
2015-05-13 15:52 ` Michal Suchanek
2015-05-13 17:13 ` Mark Brown
2015-05-13 17:20 ` Greg Kroah-Hartman
2015-05-13 17:39 ` Mark Brown
2015-05-13 18:16 ` Greg Kroah-Hartman
2015-05-13 18:32 ` Mark Brown
2015-05-13 18:36 ` Greg Kroah-Hartman
2015-05-13 18:51 ` Mark Brown
2015-05-13 19:17 ` Maxime Ripard
2015-05-13 17:50 ` Maxime Ripard
2015-05-13 18:12 ` Mark Brown
2015-05-13 18:17 ` Greg Kroah-Hartman
2015-05-13 19:23 ` Geert Uytterhoeven
2015-05-13 19:26 ` Maxime Ripard
2015-05-13 22:33 ` Greg Kroah-Hartman
2015-05-14 14:34 ` Mark Brown
2015-05-15 8:09 ` Maxime Ripard
2015-07-15 6:27 ` Lucas De Marchi
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=20140501011811.GF3245@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
/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